John Casey wrote:
I'm not sure what decisions led to that approach over, say, creating a
trunk per plugin (ugly, I know)...but I'd think what's good for one
would work for all. It would also help to maintain consistency here,
IMO. So, I guess that leads me to say let's use one set of
trunk/tags/b
+1
Lukas
John Casey wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I noticed that this issue has stagnated on the dev list. Since Brett's
post was last and seemed to recommend a reasonable course of action, I'd
like to put it to a vote.
The basic concept is to create a new top-leve
+1
Arnaud
> -Message d'origine-
> De : John Casey [mailto:[EMAIL PROTECTED]
> Envoyé : mardi 22 novembre 2005 02:12
> À : Maven Developers List
> Objet : [vote] Create maven-shared SVN space for shared, non-core APIs
>
> -BEGIN PGP SIGNED MESSAGE-
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
forgot my +1 :)
John Casey wrote:
| Hi,
|
| I noticed that this issue has stagnated on the dev list. Since Brett's
| post was last and seemed to recommend a reasonable course of action, I'd
| like to put it to a vote.
|
| The basic concept is to crea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Porter wrote:
| +1, though I have some concerns having thought more about it
|
| - where do we trunk/branch/etc?
Well, the mojo project is probably the closest analogy to this new svn
space, unless it's the plugins space on ASF. In both cases
On Tue, 22 Nov 2005, Emmanuel Venisse wrote:
+1
> +1
>
> Emmanuel
>
> John Casey a écrit :
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi,
> >
> > I noticed that this issue has stagnated on the dev list. Since Brett's
> > post was last and seemed to recommend a reasonable course
+1, though I have some concerns having thought more about it
- where do we trunk/branch/etc?
- how does this impact the bootstrap?
- not sure this is a good idea for any libraries closely ties to maven
core releases.
Keeping them truely separate is probably the best alternative here. If
maven
+1
Emmanuel
John Casey a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I noticed that this issue has stagnated on the dev list. Since Brett's
post was last and seemed to recommend a reasonable course of action, I'd
like to put it to a vote.
The basic concept is to create a new to
+1
On Mon, 2005-11-21 at 20:11 -0500, John Casey wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I noticed that this issue has stagnated on the dev list. Since Brett's
> post was last and seemed to recommend a reasonable course of action, I'd
> like to put it to a vote.
>
>
+1
On 11/21/05, John Casey <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I noticed that this issue has stagnated on the dev list. Since Brett's
> post was last and seemed to recommend a reasonable course of action, I'd
> like to put it to a vote.
>
> The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I noticed that this issue has stagnated on the dev list. Since Brett's
post was last and seemed to recommend a reasonable course of action, I'd
like to put it to a vote.
The basic concept is to create a new top-level project in the Maven SVN
rep
11 matches
Mail list logo
