I think you need to file a request under HAUS, since it's not a
codehaus project (ie, controlled by xircles), and we don't have admin
privileges there any more.
- Brett
On 26/04/2008, at 2:53 AM, nicolas de loof wrote:
Please can someone grant me write access to Maven space on wiki
(My con
Please can someone grant me write access to Maven space on wiki
(My confluence id is "ndeloof")
cheers,
Nicolas
Yes, I agree. I will change to the ArtifactRepositoryFactory instead of using
the constructor directly unless anyone has objections.
Benjamin Bentmann wrote:
Author: olamy
Date: Fri Apr 18 14:10:33 2008
New Revision: 649690
URL: http://svn.apache.org/viewvc?rev=649690&view=rev
Log:
[MINVOKER-
Author: olamy
Date: Fri Apr 18 14:10:33 2008
New Revision: 649690
URL: http://svn.apache.org/viewvc?rev=649690&view=rev
Log:
[MINVOKER-22] Add feature to install plugin to a local repository.
Submitted by Paul Gier
Modified:
maven/plugins/trunk/maven-invoker-plugin/src/main/java/org/apache/mav
Another use case as described in the issue is that if you script your call to
maven with a -P parameter, and then you want to pass an additional profile in
when calling the script, using multiple -P makes things simpler.
Jesse McConnell wrote:
well, configuration on something like the release
While you're in there, any change you can see why the -P-profile syntax
isn't working? MNG-3545 and MNG-3527
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Friday, April 25, 2008 11:43 AM
To: Maven Developers List
Subject: Re: Multiple -P options
Ok, I'll add an integ
well, configuration on something like the release plugin can specify
-Papache-release and then the user might have a profile being activated from
the commandline of the release like -Pall-modules which results in whatever
is munging these things together has to find the different instances and to
d
Why do you need multiple -P when you can specify -Pone,two,three ?
On 25-Apr-08, at 8:08 AM, Paul Gier wrote:
Hi Everyone,
Currently maven only handles a single -P option to activate
profiles. I created a small patch for this issue (http://jira.codehaus.org/browse/MNG-3268
) that allows -P
Yeah, you're probably talking about the same issue that I ran into
(MRELEASE-288) that caused me to look into this.
Jesse McConnell wrote:
just a note that this would make an annoying part of the release plugin
easier as well, it tries to gather up and reformat mulitple -P options that
might a
Ok, I'll add an integration test for it.
Brian E. Fox wrote:
This can go into 2.0.10 but we need an IT to test the behavior.
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Friday, April 25, 2008 11:08 AM
To: Maven Developers List
Subject: Multiple -P options
Hi Ev
just a note that this would make an annoying part of the release plugin
easier as well, it tries to gather up and reformat mulitple -P options that
might aggregate into a cli execution and misses a case or two I think.
jesse
On Fri, Apr 25, 2008 at 10:08 AM, Paul Gier <[EMAIL PROTECTED]> wrote:
This can go into 2.0.10 but we need an IT to test the behavior.
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Friday, April 25, 2008 11:08 AM
To: Maven Developers List
Subject: Multiple -P options
Hi Everyone,
Currently maven only handles a single -P option to activ
Hi Everyone,
Currently maven only handles a single -P option to activate profiles. I created
a small patch for this issue (http://jira.codehaus.org/browse/MNG-3268) that
allows -P to be specified multiple times on the command line. Before I apply
it, is this something that can go into maven
On 25/04/2008, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> You always need three pmc. Go ahead and stage the release to your p.a.o
> folder and then call a vote. Once you get the 3 PMC + 72hrs, you can use
> the stage plugin to move it to central.
Right, thanks for clarifying Brian.
Staging repo:
You always need three pmc. Go ahead and stage the release to your p.a.o
folder and then call a vote. Once you get the 3 PMC + 72hrs, you can use
the stage plugin to move it to central.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, April 25, 2008 6:57 AM
To:
Check your repository whether the commons beanutils is there
And check which version of beanutils you are
using().
-Original Message-
From: sangeeth jagadish [mailto:[EMAIL PROTECTED]
Sent: Friday, April 25, 2008 12:06 PM
To: [EMAIL PROTECTED]
Subject: thanks in advance -- > issue runni
On 25/04/2008, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 25, 2008 at 6:24 PM, Mark Hobson <[EMAIL PROTECTED]> wrote:
> > I just want to check before performing the release: are regular
> > committers allowed to release artifacts within the Maven project?
>
> Yes. Any committer can ta
On Fri, Apr 25, 2008 at 6:24 PM, Mark Hobson <[EMAIL PROTECTED]> wrote:
> I just want to check before performing the release: are regular
> committers allowed to release artifacts within the Maven project?
Yes. Any committer can tag the svn repo and stage a release. The
only time PMC membershi
David Jencks wrote:
Would it be possible for the release plugin to do the following?
1. modify working copy poms to release version
2. do a working copy to repo copy for the new tag
3. adjust the working copy poms to the new version, or revert if the new
version is the same as the old version
I just want to check before performing the release: are regular
committers allowed to release artifacts within the Maven project?
Checking the committer settings [1], apache.releases seems to be
reserved for PMC only.
[1] http://maven.apache.org/developers/committer-settings.html
Cheers,
Mark
O
+1
Arnaud
On Fri, Apr 25, 2008 at 8:07 AM, Milos Kleint <[EMAIL PROTECTED]> wrote:
> +1
> Milos
>
> On Fri, Apr 25, 2008 at 6:17 AM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> > +1
> >
> > --jason
> >
> >
> >
> >
> > On Apr 25, 2008, at 5:10 AM, Raphaël Piéroni wrote:
> >
> >
> > > Hi,
> > >
>
I'm assuming a lazy consensus and moving maven-runtime out of the
sandbox for a first release.
Cheers,
Mark
On 23/04/2008, Mark Hobson <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I'd like to move maven-runtime out of the sandbox and release 1.0-alpha-1:
>
> http://svn.apache.org/repos/asf/maven
22 matches
Mail list logo