+1
Arnaud
On Jan 10, 2008 10:04 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> +1
>
> On 10-Jan-08, at 12:32 PM, Brian E. Fox wrote:
>
> > I'd like to release maven-common-artifact-filters 1.0
> >
> >
> >
> > This contains some of the shared filters moved out of maven artifact
> > and
> > also t
Issue Subscription
Filter: Design & Best Practices (29 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
It will warn or fail the build. It's a gatekeeper not a negotiator ;-)
-Original Message-
From: dhoffer [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 10, 2008 9:49 PM
To: dev@maven.apache.org
Subject: Re: Version ranges and snapshots
Does maven-enforcer-plugin just stop a build from
Does maven-enforcer-plugin just stop a build from including a snapshot or
does it force it to find a release? You know what I mean? Is it a
after-the-fact filter or does it change the behavior of maven?
Michael McCallum-3 wrote:
>
> On Wed, 09 Jan 2008 15:15:55 Michael McCallum wrote:
>> > I
We have thought about this but since it cannot prevent local snapshots it is
not really a solution only a technique to limit the problem. BTW, we use
TeamCity for CI, builds get farmed out to many build agents so what is in
their local repo is quite random; sometimes it works sometimes it doesn't
Hilco, I'll have to take a deeper look, it's possible that I missed some
other cases. I had to manually read and interpret the poms since I
couldn't get them unmolested from the core. Can you open a jira and
attach a sample so I can debug it?
-Original Message-
From: Hilco Wijbenga [mailt
Hi Brian,
On Jan 10, 2008 5:40 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> The enforcer plugin requirePluginVersions rule intentionally scans
> everything in your pom inheritance to see anything that isn't defined.
> This also includes things you haven't declared but are being used by the
> stan
Hi Hilco,
The enforcer plugin requirePluginVersions rule intentionally scans
everything in your pom inheritance to see anything that isn't defined.
This also includes things you haven't declared but are being used by the
standard lifecycle (compile,install etc etc). The alternative is that
everytim
I ran into some issues with the Maven Enforcer plugin. Since I'm using
the latest and greatest straight from Subversion I didn't want to
create a JIRA ticket without first making sure that that would be
helpful.
Given that 1.0-alpha-3 doesn't support requirePluginVersions I want to
use 1.0-SNAPSHO
another thought...
by default you could not have snapshot repositories enabled and just enable
them with a profile...
that way all builds by default have no snapshots, you could even have separate
profiles and snapshot repos for different departments to a allow more
flexible integration
--
M
On Jan 10, 2008 3:19 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Olivier Lamy wrote:
> > Ok (in fact license header was not here even before release).
>
> Yes it was there before the first release cycle. I caught it in the
> commit email:
>
> https://svn.apache.org/viewvc/maven/plugins/trunk/m
Olivier Lamy wrote:
Ok (in fact license header was not here even before release).
Yes it was there before the first release cycle. I caught it in the
commit email:
https://svn.apache.org/viewvc/maven/plugins/trunk/maven-jar-plugin/pom.xml?r1=610166&r2=610863&diff_format=h
I will revert the
Ok (in fact license header was not here even before release).
I will revert the release.
Let me know when you will have finished this documentation.
Thanks,
--
Olivier
2008/1/10, Dennis Lundberg <[EMAIL PROTECTED]>:
> -1, because the pom lost the license header during release:prepare.
>
> Also -0
+1 (non binding)
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Olivier Lamy
> Sent: Friday, 11 January 2008 5:36 AM
> To: Maven Developers List
> Subject: [***POSSIBLE SPAM***] - [VOTE] Release Maven Jar
> plugin version 2.2 - Sender is forged (
-1, because the pom lost the license header during release:prepare.
Also -0, because I have a few things I'd like to fix in the docs before
the release.
Olivier Lamy wrote:
Hi,
I'd like to release the Maven Jar Plugin version 2.2.
We solved 26 issues:
http://jira.codehaus.org/secure/Release
+1
On 10-Jan-08, at 12:32 PM, Brian E. Fox wrote:
I'd like to release maven-common-artifact-filters 1.0
This contains some of the shared filters moved out of maven artifact
and
also the filters previously contained by the dependency plugin.
The release is staged at:
http://people.apach
+1
-john
On Jan 10, 2008 3:32 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> I'd like to release maven-common-artifact-filters 1.0
>
>
>
> This contains some of the shared filters moved out of maven artifact and
> also the filters previously contained by the dependency plugin.
>
>
>
> The release
I'd like to release maven-common-artifact-filters 1.0
This contains some of the shared filters moved out of maven artifact and
also the filters previously contained by the dependency plugin.
The release is staged at:
http://people.apache.org/~brianf/staging-repository
Vote is open for 7
+1
2008/1/10, Olivier Lamy <[EMAIL PROTECTED]>:
>
> Hi,
>
> I'd like to release the Maven Jar Plugin version 2.2.
>
> We solved 26 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12878&styleName=Html&projectId=11137&Create=Create
>
> Staging repo : http://people.apache.org/~ol
+1
Emmanuel
> Hi,
>
> I'd like to release the Maven Jar Plugin version 2.2.
>
> We solved 26 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12878&styleName=Html&projectId=11137&Create=Create
>
> Staging repo : http://people.apache.org/~olamy/staging-repo
>
> Staging Site :
> h
+1
Olivier Lamy wrote:
Hi,
I'd like to release the Maven Jar Plugin version 2.2.
We solved 26 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12878&styleName=Html&projectId=11137&Create=Create
Staging repo : http://people.apache.org/~olamy/staging-repo
Staging Site :
http:/
Hi,
I'd like to release the Maven Jar Plugin version 2.2.
We solved 26 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12878&styleName=Html&projectId=11137&Create=Create
Staging repo : http://people.apache.org/~olamy/staging-repo
Staging Site :
http://people.apache.org/~olamy/
On Jan 10, 2008 12:11 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> I had a chat on #maven with someone trying to delete a folder external
> to his source tree. This works fine when running the child directly, but
> in a reactor build it doesn't work. I peeked at the code and was
> surprised to fin
I've commited changes on PerformReleaseMojo to add a new "releaseProfiles"
parameter.
Please review and tell me if anything is wrong.
Nico.
2008/1/10, nicolas de loof <[EMAIL PROTECTED]>:
>
> Right.
>
> Until this maven core issue is fixed, a parameter is usefull to fix this
> on release plugin.
Right.
Until this maven core issue is fixed, a parameter is usefull to fix this on
release plugin.
It also looks cleaner not to put too much untyped configuration in
arguments. The goals parameter for example could also be set using
arguments, but has it's own configuration.
Nico.
2008/1/10, Vin
Hi Nico,
2008/1/10, nicolas de loof <[EMAIL PROTECTED]>:
> There will be 2 times "-P" option : the one set by arguments, and the one
> set by copying the release:perform maven runtime.
Sounds like MNG-3268
Cheers,
Vincent
>
> Nico.
>
> 2008/1/10, Brian E. Fox <[EMAIL PROTECTED]>:
> >
> > What'
There will be 2 times "-P" option : the one set by arguments, and the one
set by copying the release:perform maven runtime.
Nico.
2008/1/10, Brian E. Fox <[EMAIL PROTECTED]>:
>
> What's wrong with using the arguments command that is already there?
>
> -Original Message-
> From: [EMAIL PRO
What's wrong with using the arguments command that is already there?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of nicolas de loof
Sent: Thursday, January 10, 2008 3:16 AM
To: Maven Developers List
Subject: [release] introduce a "releaseProfiles" parame
On Jan 10, 2008 9:16 AM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'd like to introduce a new option in the release:perform mojo to set some
> additional profiles to get enabled during release (MRELEASE-313).
A big non-binding +1 - it would be very useful (at least IMHO).
> In my p
Hello,
I'd like to introduce a new option in the release:perform mojo to set some
additional profiles to get enabled during release (MRELEASE-313).
In my projects I use to put all tasks non required at developemnt time in a
"release" profile (example : add buildnumber in jar MANIFEST, ...) so th
30 matches
Mail list logo
