On 24 Sep 07, at 6:49 AM 24 Sep 07, Mark Hobson wrote:
On 24/09/2007, Ralph Goers <[EMAIL PROTECTED]> wrote:
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.
Was this approach actually agreed upon? Last I remember there was a
brief discussion on the dev list. I'd have thought the proposal &
vote approach should be taken for something as substantial as this
before committing to both 2.0.x and 2.1. Also, I'd rather see 2.0.8
released before throwing more features in at the last minute. I'm not
convinced that this new virtual scope is a good way forward.
For the trunk I think trying it is fine. I agree that I don't think
it is the best way forward and we should look at how this would
actually be used and I believe it's going to be within an
organization that this happens. But Ralph is trying out a prototype
and is being blocked so I think it best not throw a gauntlet in front
of people trying to improve things but Ralph I don't think you can
become attached to the import thing. It's a good PoC but I think we
need to decide what the intent is and I know what you're trying to
do. Maybe we could do something like scope it to a groupId.
But Ralph is always very careful in preserving existing behavior
while adding new functionality so I think we're fine provided a
proposal is drafted at some point (soon), put in the wiki and then
we'll decide how to handle it. But for these sorts of things its
probably best to implement them in a feature branch. That said I
don't think this is a big deal and it's good we have people looking
at the dependency management issues because it is the single biggest
problem we have.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
