I also think that 60s timeout is way too short for corporate users. I
suggest something like at least 180s (500s would be even better). If
we go with 60s, I know for sure that it will fail for most of my
corporate customers and Maven will be the focus of some more bad
talks. Please don't do this -
Same for MRMs, to perform checksum/signature/content analysis... to be
able to cleanly refuse maven when asking for broken artifact (and
having checksum/signature/content validation on).
Otherwise, if would be done while streaming, currently there's no
clean way to say to client (Maven) at _the
Olivier increased it to 30 min
https://jira.codehaus.org/browse/WAGON-365
http://svn.apache.org/viewvc?view=revisionrevision=1213414
Thus I suppose we have to prepare another RC ?
Is there others feedback to listen before launching another RC ?
Others problems with the RC3 ?
On Tue, Dec 13,
Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit :
Olivier increased it to 30 min
https://jira.codehaus.org/browse/WAGON-365
http://svn.apache.org/viewvc?view=revisionrevision=1213414
Thus I suppose we have to prepare another RC ?
Is there others feedback to listen
To: Maven Developers List
Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
I also think that 60s timeout is way too short for corporate users. I suggest
something like at least 180s (500s would be even better). If we go with 60s, I
know for sure that it will fail for most of my corporate
On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit :
Olivier increased it to 30 min
https://jira.codehaus.org/browse/WAGON-365
http://svn.apache.org/viewvc?view=revisionrevision=1213414
Thus I suppose we have to prepare
2011/12/13 Brett Porter br...@apache.org:
On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit :
Olivier increased it to 30 min
https://jira.codehaus.org/browse/WAGON-365
30 minutes is a high enough value that I think we'll be ok. Thanks Olivier.
On Tue, Dec 13, 2011 at 8:53 AM, Olivier Lamy ol...@apache.org wrote:
2011/12/13 Brett Porter br...@apache.org:
On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
Le 13 décembre 2011 09:35, Arnaud Héritier
If you are cutting a new RC, does that mean that my recent fix creeps in?
On Tue, Dec 13, 2011 at 8:53 AM, Olivier Lamy ol...@apache.org wrote:
2011/12/13 Brett Porter br...@apache.org:
On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
Le 13 décembre 2011 09:35, Arnaud Héritier
No.
There is a branch
http://svn.apache.org/repos/asf/maven/maven-3/branches/maven-3.0.4-RCx/
.
This branch is to track more easily changes between RC and to not
prevent enthusiast hacker to commit in trunk.
2011/12/13 Benson Margulies bimargul...@gmail.com:
If you are cutting a new RC, does
I presume you mean enthusiastic hacker and not enthusiast hacker
as the latter would be closer to amateur hacker and I don't know
that we consider PMC members amateur hackers... unless we have set
the bar too low ;-)
On 13 December 2011 17:08, Olivier Lamy ol...@apache.org wrote:
No.
There is
sorry due to my french native language, I don't know all the english
language refinement especially very fine ones :-) (I have enough to
learn in french!)
2011/12/13 Stephen Connolly stephen.alan.conno...@gmail.com:
I presume you mean enthusiastic hacker and not enthusiast hacker
as the latter
2011/12/13 Olivier Lamy ol...@apache.org:
2011/12/13 Brett Porter br...@apache.org:
On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
Le 13 décembre 2011 09:35, Arnaud Héritier aherit...@gmail.com a écrit :
Olivier increased it to 30 min
https://jira.codehaus.org/browse/WAGON-365
At this rate Aether and Sisu will probably have finally passed thru Eclipse
and we can start the process all over again ;-)
Mark
--
Great artists are extremely selfish and arrogant things — Steven Wilson,
Porcupine Tree
On Wed, Dec 14, 2011 at 7:44 AM, Olivier Lamy ol...@apache.org wrote:
2011/12/13 Mark Derricutt m...@talios.com:
At this rate Aether and Sisu will probably have finally passed thru Eclipse
and we can start the process all over again ;-)
possible :-)
BTW that's good to take care of quality (especially using RC candidate
release model :P )
Mark
--
Great
I definitely prefer release wagon 2.2 as those warning will generate
too much confusion.
2.1.1 instead of 2.2?
So we can wait 1/2 more weeks again :-)
In wagon trunk I have added more methods in Wagon api level to set
this timeout (will be better)
- Brett
--
Brett Porter
2011/12/12 Brett Porter br...@apache.org:
I've noticed a potential problem when using a repository manager. The new
wagon library seems to have introduced a read time out:
Could not transfer artifact [...]: Read timed out - [Help 1]
This is going to fail the first time you hit an artifact
On 12/12/2011, at 7:42 PM, Olivier Lamy wrote:
2011/12/12 Brett Porter br...@apache.org:
I've noticed a potential problem when using a repository manager. The new
wagon library seems to have introduced a read time out:
Could not transfer artifact [...]: Read timed out - [Help 1]
This
2011/12/12 Brett Porter br...@apache.org:
On 12/12/2011, at 7:42 PM, Olivier Lamy wrote:
2011/12/12 Brett Porter br...@apache.org:
I've noticed a potential problem when using a repository manager. The new
wagon library seems to have introduced a read time out:
Could not transfer artifact
Agree.
I will add it in release and complete documentation here:
http://maven.apache.org/guides/mini/guide-http-settings.html
This seems like a pretty big change and not enough people will read
that and start to freak out. If maven worked all this time with no
read timeout, why change it now?
2011/12/12 Brian Fox bri...@infinity.nu:
Agree.
I will add it in release and complete documentation here:
http://maven.apache.org/guides/mini/guide-http-settings.html
This seems like a pretty big change and not enough people will read
that and start to freak out. If maven worked all this
m2e has read timeout of 60s by default (IDE is different environment,
we can't afford blocking build thread forever). There were
bugreports about this. Some corporate users reported wait times in tens
of minutes due to conservative firewall setup that fully downloads
artifacts and does antivirus
+1 to have it set to 5 or 10 minutes by default and with a big warning and
associated doc in the release note
Even if I understand Brian about the why do we fix something not reported
as broken, I would better consider it as an improvement and not a fix.
Do we have to release a 3.1 just for this
Le 12 décembre 2011 16:21, Arnaud Héritier aherit...@gmail.com a écrit :
http://maven.apache.org/docs/3.0.4/release-notes.html
+1 to have it set to 5 or 10 minutes by default and with a big warning and
I will setup to 30 minutes. (don't know yet if need a wagon release or
not will see later)
On Mon, Dec 12, 2011 at 4:46 PM, Olivier Lamy ol...@apache.org wrote:
Le 12 décembre 2011 16:21, Arnaud Héritier aherit...@gmail.com a écrit :
http://maven.apache.org/docs/3.0.4/release-notes.html
+1 to have it set to 5 or 10 minutes by default and with a big warning
and
I will setup to 30
If we don't change things - the http settings guide should be updated, but
also RELEASE NOTES for the new release should mention the change, and call
it out.
--
Great artists are extremely selfish and arrogant things — Steven Wilson,
Porcupine Tree
On Tue, Dec 13, 2011 at 3:28 AM, Brian Fox
I've noticed a potential problem when using a repository manager. The new wagon
library seems to have introduced a read time out:
Could not transfer artifact [...]: Read timed out - [Help 1]
This is going to fail the first time you hit an artifact proxied by a
repository manager that takes
2011 20:04:58 +0100
Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
To: dev@maven.apache.org
Jesse,
First huge thanks for your tests, that's very important for us to have
feedbacks.
But please note it's *not* an official release so this will never be
distribute as an official
2011/12/8 Marvin Froeder velo...@gmail.com:
Well, it was working already on 3.0.3 but when I moved to 3.0.4-RC I start
getting missing poms warnings.
The layout is declared inside my plugin and this plugin has extensionstrue
on plugin configuration.
I will try to create a reproducible case.
Hello,
i'm observing things like the following with a build:
[INFO] Failsafe report directory:
C:\workspace\nereus\nereus-web-it\target\failsafe-reports
wagon http use multi threaded http connection manager maxPerRoute 20, max
total 40
Downloading:
Looks to be due to a cookie path not rewrite.
Do you have a http frontend before your rpm ?
If yes see http://markmail.org/message/djcagmgqg56zrlf4
2011/12/8 Karl Heinz Marbaise k...@soebes.de:
Hello,
i'm observing things like the following with a build:
[INFO] Failsafe report directory:
Hi,
Olivier Lamy wrote
Looks to be due to a cookie path not rewrite.
Do you have a http frontend before your rpm ?
Hm...rpm ?
I have downloaded the maven-3.0.4-RC3 from the stage site...and started my
build mvn 3.0.4-RC3 instead of maven 3.0.3 and seeing those results...
Kind
2011/12/8 Karl Heinz Marbaise k...@soebes.de:
Hi,
Olivier Lamy wrote
Looks to be due to a cookie path not rewrite.
Do you have a http frontend before your rpm ?
.
Hm...rpm ?
I mean Repository Manager :-) in your case looks nexus.
So just check in case you have a http frontend, cookie path
List
Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Looks to be due to a cookie path not rewrite.
Do you have a http frontend before your rpm ?
If yes see http://markmail.org/message/djcagmgqg56zrlf4
2011/12/8 Karl Heinz Marbaise k...@soebes.de:
Hello,
i'm observing things like
: Olivier Lamy [mailto:ol...@apache.org]
Sent: 08 December 2011 12:53
To: Maven Developers List
Subject: Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Looks to be due to a cookie path not rewrite.
Do you have a http frontend before your rpm ?
If yes see http://markmail.org/message
Hi Oliver,
Olivier Lamy wrote
I mean Repository Manager :-) in your case looks nexus.
;-) RPM has a different meaning for Redhat Package Manager thanks for
the explanation...
Olivier Lamy wrote
So just check in case you have a http frontend, cookie path is
correctly rewrite.
BTW
Seems weird to me to get back expires returns in non en format.
A sample:
mbp-olamy:maven-plugins olamy$ curl -H Accept-Language: de -I
http://www.google.de
HTTP/1.1 200 OK
Date: Thu, 08 Dec 2011 15:14:54 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=ISO-8859-1
I've tried it out on a few relatively tame builds...failsafe and
dependency plugins being about the most exotic things tested.
Everything looks like it's functioning well here. I'll try to take it
out for a more aggressive test run today.
On 12/5/11 9:28 AM, Olivier Lamy wrote:
Hello,
FYI - NetBeans nightly development builds [1] are now bundling RC3, to shake
out problems in either the embedded APIs or general usage.
[1] http://bits.netbeans.org/download/trunk/nightly/latest/
-
To unsubscribe, e-mail:
Jesse,
First huge thanks for your tests, that's very important for us to have
feedbacks.
But please note it's *not* an official release so this will never be
distribute as an official Apache Maven release.
It's only a rc build to get feedbacks from users. The staged
repository will be deleted (at
FWIW, 3.0.4-RC3 didn't worked with a custom repository layout
Like
http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/
I did not pin down the problem yet, but seems a regression from 3.0.3.
On Mon, Dec 5, 2011 at 12:28 PM, Olivier Lamy ol...@apache.org
2011/12/7 Marvin Froeder velo...@gmail.com:
FWIW, 3.0.4-RC3 didn't worked with a custom repository layout
Like
http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/
I did not pin down the problem yet, but seems a regression from 3.0.3.
How do you get that
On 12/07/2011 02:04 PM, Olivier Lamy wrote:
please note it's *not* an official release so this will never be
distribute as an official Apache Maven release.
It's only a rc build to get feedbacks from users.
Yes of course. This is only temporary until another RC or a final build is
published -
I'm +1ing this - have been doing releases all day without issue.
Someone did make a comment about memory usage the other day, I am seeing
OOM exceptions more often in my large reactor build under the RC, but
that's mostly Rhino stuff that has an evil leak in it.
I did see a Permgen in Javac
I ran my current day-job nightmare. It showed the same failure of the
assembly plugin to resolve a war dependency from the reactor that I
see with 2.2.1 and 3.0.3, so that's all good.
On Mon, Dec 5, 2011 at 9:28 AM, Olivier Lamy ol...@apache.org wrote:
Hello,
Apache Maven 3.0.4-RC3 has been
Look good to me, the issue reported by me for RC2 is fixed
-Dan
On Mon, Dec 5, 2011 at 6:28 AM, Olivier Lamy ol...@apache.org wrote:
Hello,
Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a
preview of the coming 3.0.4 official release)
The repository is available here:
Tested on a couple of builds with mostly standard plugins, looks good.
Regards Mirko
--
Sent from my phone
http://illegalstateexception.blogspot.com
http://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Dec 5, 2011 3:28 PM, Olivier Lamy ol...@apache.org wrote:
Hello,
47 matches
Mail list logo
