[mojo-dev] [jira] (MNBMODULE-218) Treat pom-dependencies as own dependencies to be able to use dependency clusters in nbm projects

[Inge Solvoll (JIRA)]

Inge Solvoll commented on MNBMODULE-218 Treat pom-dependencies as own dependencies to be able to use dependency clusters in nbm projects Now that's what I call a quick answer To clarify: My setup works just fine if the dependencies are set as direct dependency to the netbeans module I'm building. If I insert one level of indirection (pom type dependency), the maven compilation and dependency resolution still works, but the nbm-maven-plugin crashes with the following message when building the new nbm: [ERROR] Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:3.9:manifest (default-manifest) on project viewscene: Uncategorized problems with NetBeans dependency verification (maybe MNBMODULE-102 or wrong maven dependency metadata). Class usages: [com.myclass.Blah, com.mypackage.Blah2] The issue https://jira.codehaus.org/browse/MNBMODULE-102 points to the problem of having an nbm -> jar -> nbm dependency chain. This is similar, only that I would like to have an nbm -> pom -> nbm chain. The level of indirection is desirable in order to "shield" all the application from the versioning details of the framework. Ideally, I would like to release the framework NBMs much more independently but that would cause problems maintaining the versions against a high number of client apps.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email