Closed bckfnn closed 10 years ago
This is a tricky one, but you can workaround it for now by adding the classpath to the jar that is used in the module explicitly in the classpath property for the plugin, and use vertx:runModOnCP
runmodXXX now no longer exists and a vertx_classpath.txt is used to configure classpath
Dependencies that is added to a module pom.xml is not picked up by vertx:runModIDEA
In testcase https://github.com/bckfnn/findingdependencies try running:
and a java.lang.NoClassDefFoundError is thrown.
For this to work the command must be replaced with
but now runModIDEA depends on the files that is copied to target/mods/... folder. And the target/mods folder must be kept up-to-date in order for runModIDEA to keep working.
IMO runModIDEA should never look in target/mods and should be based on the dependency list found in pom.xml.