Jason van Zyl wrote:
On 23 Sep 07, at 12:20 AM 23 Sep 07, [EMAIL PROTECTED] wrote:
Author: rgoers
Date: Sun Sep 23 00:20:24 2007
New Revision: 578553
URL: http://svn.apache.org/viewvc?rev=578553&view=rev
Log:
Allow the managed dependencies of projects to be imported into the
managed dependencies of other projects.
I assume you're limiting this in scope somehow, I can't remember if
you said it's by a group ID, lineage, or by the reactor. Generally we
don't want POMs we pull in from third parties to affect out depMan
elements. If commons-beanutils has some depMan element we obviously
don't want that affecting the project at hand. I know you added some
types or scopes to retain backward compat but just wanted to make sure
this isn't a general importing.
Yes, you have to specify <scope>import</scope> for the import to happen.
The type also has to be a pom. Ideally when doing this projects would
create a bill of materials pom for others to use and then use the import
only in poms that they use to build with. Presumably, that project would
also import the bill of materials pom as well. At least, that was how
the use case was described to me by the folks who want it.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
