|Re: Eclipse maven multi module project issues [message #1719446 is a reply to message #1704261]
||Fri, 08 January 2016 02:33
| krishna Mising name
Registered: July 2009
You should put this as the first line in M2E documentation and in the plugin, I mean how hard is to remove the referenced libraries that use M2_REPO convention whereas you guys use maven dependencies, just an alert message that mvn eclipse:eclipse should not be used would save all our times.|
What about other issues above?
And what about the issue in Eclipse where you add a dependency module project, it does not update the parent maven project classpath with this dependency module as a project dependency but still keeps the dependency module it as a jar dependency?
[Updated on: Mon, 11 January 2016 07:06]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02276 seconds