pom dependency with import scope is actually new to me. That solves the versioning part of my problem, yes. Thank you so much for that tip

It would still very much like to define the sets of dependencies needed for different modules and apps in our system. It would be a big win if our client apps did not have to know about those sets.

I don't know the maven system well enough to know if this breaks anything else. But it seems like you don't see any problem with considering the transitive dependencies from a pom dependency as direct dependencies nbm-wise?

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

Reply via email to