On 8/1/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Brett Porter wrote:
> So the solution that best corresponds to this is an incubation repository.
That's what's been said, but you're one of the Maven ... er ... mavens. :-)
If it helps Noel, here's a couple of use cases.
In ActiveMQ we ship a bunch of examples for users to try out the code.
They are built using Maven 2 and all the artifacts they require
contain 'incubator in their name'. The problem is because there is no
maven 2 repo to put these dependencies, the example programs we ship
in releases don't even compile.
Another use case is quite a few projects depend on ActiveMQ both
inside and outside of Apache. e.g. ServiceMix, Jencks, Lingo et al.
We'd like folks to try out the code that is being incubated (not the
releases from a year ago on codehaus) - so consequently we'd like
those other projects to migrate to the Apache version of the code
ASAP.
Right now we have a snapshot repo which is good so that projects can
actually compile. However only snapshot jars are available - which
means that (i) we can't make stable milestones for dependent projects
to use and (ii) the dependent projects can never release themselves.
I understand the concerns of keeping incubating code separate from the
rest of Apache and away from the mirrors - I just don't yet see the
issue with having somewhere on incubator.apache.org where we put a
folder containing releases of incubating projects?(i.e. a maven 2
repo).
--
James
-------
http://radio.weblogs.com/0112098/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
