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
When auto-generating Maven projects, we should inspect the explicit import <class>; statements and build the dependencies accordingly (ClassUtils.getLocation() followed by POM class magic).
This might not be necessary, however, if scripting-java makes the complete class path available anyway. But it would still be nice: when exporting a .jar file, it would contain a perfect pom.xml automatically.
The text was updated successfully, but these errors were encountered:
When auto-generating Maven projects, we should inspect the explicit
import <class>;
statements and build the dependencies accordingly (ClassUtils.getLocation()
followed byPOM
class magic).This might not be necessary, however, if
scripting-java
makes the complete class path available anyway. But it would still be nice: when exporting a.jar
file, it would contain a perfectpom.xml
automatically.The text was updated successfully, but these errors were encountered: