able mechanism for distributing pre-release
> code...would that have helped you all?
>
> -john
>
> On 4/12/07, Kevin Menard <[EMAIL PROTECTED]> wrote:
> >
> > I agree. I am suggesting that it's a little too easy to
> use SNAPSHOTs
> > and th
tand the consequences. It's
> like me picking up an unstable version of some jar and then
> complaining that it broke later and asking the creators to
> stop releasing unstable versions at all(that are clearly
> marked as such). People would then just go get the code anyway.
>
etc, but it is most
> definitely stable and reproducible. (even if our repo disappears).
>
> -Original Message-
> From: Kevin Menard [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 12, 2007 12:50 PM
> To: Maven Developers List
> Subject: RE: Remove auto-resolution of
A bit of a departure from the discussion, but still related . . .
It may be worthwhile to rethink the whole SNAPSHOT system, too, then.
Way too many plugins and dependencies sit in a SNAPSHOT limbo,
presumably because it's simpler than cutting a release. And then
SNAPSHOT to SNAPSHOT may break bu
ies I
> mentioned. It's also easier to get your builds onto the
> central repository so people can easily use them.
>
> Hope that helps.
>
> --Brian
>
> -Original Message-
> From: Kevin Menard [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 05, 2007 8:0
es. Is it
just an SVN area? Where would plugin docs, site, etc. be hosted? Is
there some sort of graduation path up to a fully supported plugin?
Thanks,
Kevin
Kevin Menard
Servprise International, Inc.
800.832.3823 x308
-
To u
