You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current release of org.dominokit:gwt-datetimeformat's jar has a .gwt.xml file with all of the correct inherits in it. However, the sources jar has a different .gwt.xml file, one which is missing inherits statements.
The copy found in the sources jar is identical to the one in gwt-datetimeformat/src/main/resources - it seems likely that it replaced the generated one. Instead, consider moving the gwt.xml file to gwt-datetimeformat/src/main/module.gwt.xml, and let the gwt maven plugin do the work of emitting the file into both jars.
Technically, this artifact shouldnt be needed by downstream libraries or applications, but I've just seen a project where the -sources jar ended up replacing the regular jar's contents on the classpath of IJ's built-in dev mode.
The text was updated successfully, but these errors were encountered:
The current release of org.dominokit:gwt-datetimeformat's jar has a .gwt.xml file with all of the correct inherits in it. However, the sources jar has a different .gwt.xml file, one which is missing inherits statements.
The copy found in the sources jar is identical to the one in gwt-datetimeformat/src/main/resources - it seems likely that it replaced the generated one. Instead, consider moving the gwt.xml file to gwt-datetimeformat/src/main/module.gwt.xml, and let the gwt maven plugin do the work of emitting the file into both jars.
Technically, this artifact shouldnt be needed by downstream libraries or applications, but I've just seen a project where the -sources jar ended up replacing the regular jar's contents on the classpath of IJ's built-in dev mode.
The text was updated successfully, but these errors were encountered: