|Enable Maven Dependencies Breaks Other Projects [message #646953]
||Mon, 03 January 2011 14:28
| Michael Giroux
Registered: July 2009
Location: Phoenix, AZ
I have two projects in my eclipse workspace. Project A implements database access objects. Project B implements business logic. The build path for project B includes a project reference to project A. In fact, my workspace has nearly 20 projects that include project A in their build path.|
I installed m2eclipse, and enabled maven dependency management for project A. This immediately caused compile errors in project B (and other projects that reference A)
It appears that m2eclipse "Enable Dependency Management" is an all or nothing option. If any project that is referenced by another project uses maven dependency management, then all the projects that reference the project must also enable dependency management.
This seems like a bug. Enabling maven dependency management on a project allows it to build correctly. If the project is referenced by other non-maven projects, they too should build correctly.
Is there an option that will allow the project that is using maven dependency management to export itself as before the dependency management was enabled?
Am I using m2eclipse correctly?
Powered by FUDForum
. Page generated in 0.08080 seconds