Maven model does not provide enough information to properly implement workspace dependency resolution for classified artifacts. We implemented some heuristics to support classifier=tests, but maven project model changes are required to implement workspace dependency resolution for all classifiers.
-- Regards, Igor On 11-12-09 8:33 AM, Benson Margulies wrote:
I configured the maven-war-plugin with: <attachClasses>true</attachClasses> and then declared the resulting classified artifact as a dependency. M2E appears to be struggling with this; when I launch for debugging, classes from the classified artifact are missing, and I get some strange warnings from slf4j that suggest that other parts of the webapp project are being dragged into the classpath. Note that the webapp project is inside my eclipse workspace. If this is news, I can make a test case and attach it to a bz. _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
