On Wed, Dec 14, 2011 at 7:09 AM, Stephen Connolly
wrote:
> well the primary issue that i required mrm-maven-plugin for was refusing
> the proxy settings of the invoking maven within the invoked maven.
>
> mrm-maven-plugin can be configured to serve all artifacts available and
> thus the @local-rep
hmm some strangeness with site:stage-deploy but the content can be found if
you dig down ;-)
+1 from me btw
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 13 Dec 2011 17:2
well the primary issue that i required mrm-maven-plugin for was refusing
the proxy settings of the invoking maven within the invoked maven.
mrm-maven-plugin can be configured to serve all artifacts available and
thus the @local-repo@ speedup can be used without having to seed the local
repo with a
>
> 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
>>>
>>>
On Tue, Dec 13, 2011 at 6:14 PM, Stephen Connolly
wrote:
> would mrm-maven-plugin help your integration tests?
Is that Mock Repository Manager?
Because the integration tests detect a real failure, unable to use URL
resources behind a firewall, I need to solve it properly.
Its just I happen to be
2011/12/13 Mark Derricutt :
> 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 artists are
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 wrote:
> So we can wait
2011/12/13 Olivier Lamy :
> 2011/12/13 Brett Porter :
>>
>> On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
>>
>>> Le 13 décembre 2011 09:35, Arnaud Héritier a écrit :
Olivier increased it to 30 min
https://jira.codehaus.org/browse/WAGON-365
http://svn.apache.org/viewvc?view=revision
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 :
> I presume you mean "enthusiastic hacker" and not "enthusiast hacker"
> as the latter would be closer to "amat
Hi!
It was great seeing that others have the same problem with complex
objects for Maven configuration and the generated documentation.
For the android maven plugin
http://code.google.com/p/maven-android-plugin/
I have derived a bit of a standard on how we deal with this and we have
implement
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 hacker"s... unless we have set
the bar too low ;-)
On 13 December 2011 17:08, Olivier Lamy wrote:
> No.
> There is a branc
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&styleName=Html&version=18224
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11144&status=1
Staging repo:
https://repository.apache.org/con
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 :
> If you are cutting a new RC, does that mean that my recent
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 wrote:
> 2011/12/13 Brett Porter :
>>
>> On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
>>
>>> Le 13 décembre 2011 09:35, Arnaud Héritier a écrit :
Olivier increased it to
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 wrote:
> 2011/12/13 Brett Porter :
>>
>> On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
>>
>>> Le 13 décembre 2011 09:35, Arnaud Héritier a écrit :
Olivier increased it
2011/12/13 Brett Porter :
>
> On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
>
>> Le 13 décembre 2011 09:35, Arnaud Héritier a écrit :
>>> Olivier increased it to 30 min
>>> https://jira.codehaus.org/browse/WAGON-365
>>> http://svn.apache.org/viewvc?view=revision&revision=1213414
>>>
>>> Thus I su
On 13/12/2011, at 7:38 PM, Olivier Lamy wrote:
> Le 13 décembre 2011 09:35, Arnaud Héritier a écrit :
>> Olivier increased it to 30 min
>> https://jira.codehaus.org/browse/WAGON-365
>> http://svn.apache.org/viewvc?view=revision&revision=1213414
>>
>> Thus I suppose we have to prepare another RC
Even if they are not scanned by AV - repo managers may be verifying the
checksums of the downloaded files before sending them on.
/James
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
Sent: 13 December 2011 08:25
To: Mave
Le 13 décembre 2011 09:35, Arnaud Héritier a écrit :
> Olivier increased it to 30 min
> https://jira.codehaus.org/browse/WAGON-365
> http://svn.apache.org/viewvc?view=revision&revision=1213414
>
> Thus I suppose we have to prepare another RC ?
> Is there others feedback to listen before launching
Olivier increased it to 30 min
https://jira.codehaus.org/browse/WAGON-365
http://svn.apache.org/viewvc?view=revision&revision=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, 2
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 en
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 -
22 matches
Mail list logo
