When does maven check to see if the dependencies are there? Is there a way to overwrite this with a maven goal? I'd like to create a maven goal called 'development-build' that would hopefully be able to ignore the fact that the subproject jars are missing, and instead use a classpath that points to the compiled .class files.
-Randy
Randy Xu wrote:
Currently, it seems like the subproject dependency order in a multiproject is figured out using the dependency information. So if APP-GUI depends on APP-LIB, then APP-GUI's project.xml will have the APP_LIB jar has a dependency. Is there another way to specify or enforce the build order of subprojects? I'd like to skip jarring to speed up development.
-Randy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
