On 24 Sep 07, at 9:23 AM 24 Sep 07, Mark Hobson wrote:
On 24/09/2007, Jason van Zyl <[EMAIL PROTECTED]> wrote:
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.
Okay, but I do think a feature branch is the best for prototyping new
features - it stops blocking the developer and doesn't cause
unnecessary problems for others. Do we really need to merge it into
2.0.x? 2.0.8 is due out soon which means users can start using this
prototype which will lock us into supporting this functionality in
future.
I don't think Ralph was planning on trying to merge this as there are
changes in the separated maven-artifact. I don't think this can go in
2.0.8. Ralph, just verifying but you're not intending to put this in
2.0.8 are you?
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]
