On 02/12/2011, at 8:27 AM, ol...@apache.org wrote:
> +// ensure we didn't use chuncked transfer which doesn't work on ngnix
> +for ( DeployedResource deployedResource :
> putHandler.deployedResources )
> +{
> +if ( StringUtils.equalsIgnoreCase( "chuncked",
>
Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
https://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
On Fri, Dec 2, 2011 at 1:15 AM, Benson Margulies wrote:
> This was misdirected. Apologies.
>
> On Thu, Dec 1, 2011 at 9:03 AM, Benson Margulies
> wrote:
>> There is a system property that disables it -- read once -- in a static
>> block.
>>
>> Does anyone thing it would be possible to create an
On 12/1/11 3:28 PM, John Casey wrote:
On 12/1/11 3:25 PM, Benson Margulies wrote:
It seems to me that one of the major values of an 'RC' discipline is
that it's uniquely tagged and bagged we can tell which bugs where
found or fixed in which RC.
This in turn could argue for a scheme in which we
Please change subject thread for such discussion !
Again, I don't have issue with this RC mode and I will take care next time.
--
Olivier go back to hack
2011/12/1 Benson Margulies :
> It seems to me that one of the major values of an 'RC' discipline is
> that it's uniquely tagged and bagged we
On 12/1/11 3:25 PM, Benson Margulies wrote:
It seems to me that one of the major values of an 'RC' discipline is
that it's uniquely tagged and bagged we can tell which bugs where
found or fixed in which RC.
This in turn could argue for a scheme in which we vote and release
'milestone' releases:
It seems to me that one of the major values of an 'RC' discipline is
that it's uniquely tagged and bagged we can tell which bugs where
found or fixed in which RC.
This in turn could argue for a scheme in which we vote and release
'milestone' releases: available for general testing, protected by th
On 12/1/11 10:27 AM, Olivier Lamy wrote:
2011/12/1 Jörg Schaible:
Benjamin Bentmann wrote:
Olivier Lamy wrote:
I'd like to release Apache Maven 3.0.4 (take 2).
[...]
Note the difference with first vote is an upgrade of aether to 1.13.1
What about the memory issue that Jörg brought up? Shou
+1 non-binding.
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On Thu, Dec 1, 2011 at 10:20 PM, Olivier Lamy wrote:
> Hello,
>
> I'd like to release Apache Maven 3.0.4 (take 2).
>
> We fixed 31 issues.
> See release notes:
>
> http://jira.codehaus.
It's been so long I guess people have forgotten RCs used to be made.
The release of "Apache Maven" itself is sufficiently different to just a
plugin that a more formal release does make sense, but on the flip side
after all the arguments trying to get this out I guess people just "want it
out ther
Hi,
Jörg Schaible wrote:
> Hi Oliver,
>
> Olivier Lamy wrote:
>
>> @Jörg any open source projects you can share ?
>
> Sorry, no, but I am try some runs now on a dedicated build server ... a
> run takes some time though
It took a while, because I was hit by a real M3 regression first: MNG-5207
2011/12/1 Jörg Schaible :
> Benjamin Bentmann wrote:
>
>> Olivier Lamy wrote:
>>
>>> I'd like to release Apache Maven 3.0.4 (take 2).
>>> [...]
>>> Note the difference with first vote is an upgrade of aether to 1.13.1
>>
>> What about the memory issue that Jörg brought up? Shouldn't we at least
>>
yes we should have done it...
Lesson to learn for next releases ...
On Thu, Dec 1, 2011 at 3:17 PM, Jason van Zyl wrote:
> Does no one else think it reasonable to do RCs like we have been doing for
> the last 2 years?
>
> On Dec 1, 2011, at 1:20 AM, Olivier Lamy wrote:
>
> > Hello,
> >
> > I'd l
Benjamin Bentmann wrote:
> Olivier Lamy wrote:
>
>> I'd like to release Apache Maven 3.0.4 (take 2).
>> [...]
>> Note the difference with first vote is an upgrade of aether to 1.13.1
>
> What about the memory issue that Jörg brought up? Shouldn't we at least
> understand the cause and potential
sure why not for next one.
2011/12/1 Jason van Zyl :
> Does no one else think it reasonable to do RCs like we have been doing for
> the last 2 years?
>
> On Dec 1, 2011, at 1:20 AM, Olivier Lamy wrote:
>
>> Hello,
>>
>> I'd like to release Apache Maven 3.0.4 (take 2).
>>
>> We fixed 31 issues.
>>
Olivier Lamy wrote:
I'd like to release Apache Maven 3.0.4 (take 2).
[...]
Note the difference with first vote is an upgrade of aether to 1.13.1
What about the memory issue that Jörg brought up? Shouldn't we at least
understand the cause and potential impact on other users before
continuing
This was misdirected. Apologies.
On Thu, Dec 1, 2011 at 9:03 AM, Benson Margulies wrote:
> There is a system property that disables it -- read once -- in a static block.
>
> Does anyone thing it would be possible to create an independent class
> loader and load this class into it a second time, w
Does no one else think it reasonable to do RCs like we have been doing for the
last 2 years?
On Dec 1, 2011, at 1:20 AM, Olivier Lamy wrote:
> Hello,
>
> I'd like to release Apache Maven 3.0.4 (take 2).
>
> We fixed 31 issues.
> See release notes:
> http://jira.codehaus.org/secure/ReleaseNote.
+1 Thanks!Cletus
> Date: Thu, 1 Dec 2011 10:01:37 +0100
> Subject: Re: [VOTE] Apache Maven SCM 1.6
> From: emmanuel.veni...@gmail.com
> To: dev@maven.apache.org
>
> +1
>
> Emmanuel
>
> On Tue, Nov 29, 2011 at 2:26 PM, Olivier Lamy wrote:
>
> > Hello,
> >
> > I'd like to release Apache Maven
There is a system property that disables it -- read once -- in a static block.
Does anyone thing it would be possible to create an independent class
loader and load this class into it a second time, with the property
set, and then talk to it via reflection?
---
+1
On Thu, Dec 1, 2011 at 12:48 PM, Anders Hammar wrote:
> +1
>
> Checksums are now created correctly when deploying a snapshot to
> Codehaus's Nexus instance.
>
> /Anders
>
> On Thu, Dec 1, 2011 at 12:08, kreyssel wrote:
> > +1
> >
> > --
> > View this message in context:
> http://maven.40175.
+1
Checksums are now created correctly when deploying a snapshot to
Codehaus's Nexus instance.
/Anders
On Thu, Dec 1, 2011 at 12:08, kreyssel wrote:
> +1
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/VOTE-Apache-Maven-3-0-4-take-2-tp5038109p5038345.html
> Sent from
+1
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Apache-Maven-3-0-4-take-2-tp5038109p5038345.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr
Hello,
I'd like to release Apache Maven 3.0.4 (take 2).
We fixed 31 issues.
See release notes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=17215
Note the difference with first vote is an upgrade of aether to 1.13.1
(to prevent chuncked transfer encoding when deployin
+1
Emmanuel
On Tue, Nov 29, 2011 at 2:26 PM, Olivier Lamy wrote:
> Hello,
>
> I'd like to release Apache Maven SCM 1.6
>
> We fixed 18 issues:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17296&styleName=Text&projectId=10527&Create=Create
>
> Staged repo: https://repository.apa
+1
Kristian
Den 30.11.2011 16:56, skrev John Casey:
+1
On 11/29/11 6:44 AM, Benson Margulies wrote:
Hi,
We solved an issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS%7C083f4f243731b9ee702e76ba2ccc07788ab70ac3%7Clin&version=16798&styleName=Text&projectId=1
26 matches
Mail list logo
