Jason van Zyl wrote:
I don't think we will be adding many new plugins here at Apache and we
consider Mojo an equal wrt hosting plugins. The mojo groupId is a
default as well when dealing with plugins so at Apache or Codehaus it
makes no difference where you work or what you work on.
As far a
On 30 Aug 06, at 12:26 PM 30 Aug 06, Jochen Wiedmann wrote:
The goal is to get people integrated into our process and
encourage contributions and collaboration so we would adapt as
necessary to attain that goal. For example if you did all the work
for the foo-plugin then I would support yo
Jason van Zyl wrote:
The PMC must approve a release, and anyone doing a release would most
likely be on the PMC but I don't believe that is a strict requirement.
So if you were very motivated to release the JAR plugin and went through
our standard process to release it then I would support tha
On 31/08/2006, at 12:06 AM, Jochen Wiedmann wrote:
ok, I grew angry possibly, sorry! So let's (the "us" in fact being
"me", like Louis XIV ...) calm down and return to discussion.
I'm often short in mails too - don't read any anger into it :)
I think we agree on that. However, you haven't
cent tests and passes the docck
minimum requirements. You can pump out as many snapshots as you
want though.
That's a policy I'd like to see for the "Maven Sandbox for Apache
Committers" (MSAC) too. But what about the second, third, ...
release? Can I (or we) as the plugins
ests and passes the docck minimum
requirements. You can pump out as many snapshots as you want though.
That's a policy I'd like to see for the "Maven Sandbox for Apache
Committers" (MSAC) too. But what about the second, third, ... release?
Can I (or we) as the plugins auth
On 30 Aug 06, at 6:51 AM 30 Aug 06, Jochen Wiedmann wrote:
Jochen Wiedmann wrote:
Brett Porter wrote:
-1
(snapshots are fine).
The ability to publish half-baked, undocumented releases (which
is what they are if they can't garner votes to get out of the
sandbox) allows us to get lazy mea
On 30 Aug 06, at 5:53 AM 30 Aug 06, Jochen Wiedmann wrote:
When can I start to use it? :-) I'd immediately move the XML plugin
from Mojo and contribute two plugins, which are related to Axis 2.
Honestly, I've never been glad having to use the Mojo project, because
a) I do not have committ
Hi,
ok, I grew angry possibly, sorry! So let's (the "us" in fact being "me",
like Louis XIV ...) calm down and return to discussion.
Brett Porter wrote:
Obviously we need a balance, and I was referring to a harder stance on
pre-release sandbox plugins rather than ongoing support of already
On 30/08/2006, at 8:51 PM, Jochen Wiedmann wrote:
Jochen Wiedmann wrote:
Brett Porter wrote:
-1
(snapshots are fine).
The ability to publish half-baked, undocumented releases (which
is what they are if they can't garner votes to get out of the
sandbox) allows us to get lazy meaning full
Jochen Wiedmann wrote:
Brett Porter wrote:
-1
(snapshots are fine).
The ability to publish half-baked, undocumented releases (which is
what they are if they can't garner votes to get out of the sandbox)
allows us to get lazy meaning full releases don't arrive and we've
suffered enough for
Brett Porter wrote:
-1
(snapshots are fine).
The ability to publish half-baked, undocumented releases (which is what
they are if they can't garner votes to get out of the sandbox) allows us
to get lazy meaning full releases don't arrive and we've suffered enough
for it already.
Ok, but wh
On 30/08/2006, at 7:53 PM, Jochen Wiedmann wrote:
One question, though: Even if a plugin does have sandbox status, it
should, IMO, nevertheless be able to publish releases. How do
others feel here?
-1
(snapshots are fine).
The ability to publish half-baked, undocumented releases (which i
When can I start to use it? :-) I'd immediately move the XML plugin from
Mojo and contribute two plugins, which are related to Axis 2.
Honestly, I've never been glad having to use the Mojo project, because
a) I do not have committers access there, which makes me loose a lot
of time and
b)
+1, good idea.
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: mercredi 30 août 2006 01:01
> To: Maven Developers List
> Subject: Maven Sandbox for Apache Committers
>
> Hi,
>
> I'm sending this here as folks develo
+1
Emmanuel
Jason van Zyl a écrit :
Hi,
I'm sending this here as folks developing Maven projects probably all
subscribe here.
On the PMC list we've talked about setting up a sandbox that all Apache
committers would have access to so that experimentation with Maven
projects can happen easi
+1 Nice idea.
Regards,
Alan
Jason van Zyl wrote:
Hi,
I'm sending this here as folks developing Maven projects probably all
subscribe here.
On the PMC list we've talked about setting up a sandbox that all
Apache committers would have access to so that experimentation with
Maven projects c
Hi All,
I'm not sure if I'm allowed to vote but I will put my two cents in
anyways. I think this would make things a lot easier on those like me
trying to get involved in Continuum and Maven. I spent 2 hours last night
trying to figure out how IntelliJ screwed up my working copy just so I
did
Hi,
I'm sending this here as folks developing Maven projects probably all
subscribe here.
On the PMC list we've talked about setting up a sandbox that all
Apache committers would have access to so that experimentation with
Maven projects can happen easily.
Case in point: Jeremy and Edwi
19 matches
Mail list logo
