would mrm-maven-plugin help your integration tests?
- 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 00:55, "Barrie Treloar" wrote:
> On Tue, Dec 13, 2011 at 10
- 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 00:55, "Barrie Treloar" wrote:
> On Tue, Dec 13, 2011 at 10:56 AM, Brett Porter wrote:
> > I'm not quite sure w
Ok, I've managed to get it working, specifically I have done the
following (is this sane?):
Added to pom.xml
org.apache.maven:maven-settings:2.0.8
org.apache.maven.wagon:wagon-provider-api:2.1
Added to the Mojo:
/**
* @component
* @required
* @readonly
*/
private Wago
On Mon, Dec 12, 2011 at 8:01 PM, Brett Porter wrote:
> On 10/12/2011, at 9:44 AM, Benson Margulies wrote:
>
>> On the substance of the original problem:
>>
>> user runs 'mvn site:site'
>>
>> site:site finds javadoc and checkstyle, trigger a forked lifecycle to
>> generate sources.
>>
>> In this pa
On 10/12/2011, at 9:44 AM, Benson Margulies wrote:
> On the substance of the original problem:
>
> user runs 'mvn site:site'
>
> site:site finds javadoc and checkstyle, trigger a forked lifecycle to
> generate sources.
>
> In this particular case, 'generate-sources' in module 'b' depends on
> r
On Tue, Dec 13, 2011 at 10:56 AM, Brett Porter wrote:
> I'm not quite sure what your question is. Are you looking for the Wagon
> Javadocs [1], or an explanation of how to set the proxy info (just below the
> snippet you gave in the source code), or the maven 3.x comment (not sure it
> matters
I'm not quite sure what your question is. Are you looking for the Wagon
Javadocs [1], or an explanation of how to set the proxy info (just below the
snippet you gave in the source code), or the maven 3.x comment (not sure it
matters due to backwards compat...)
- Brett
[1]http://maven.apache.or
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
On Wed, Oct 19, 2011 at 8:01 PM, Olivier Lamy wrote:
> Hello,
> You must use wagon for that and setup a wagon instance with various
> informations from settings.
> As a sample you can have a look atproject-info-reports plugin
>
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-in
On Mon, Dec 12, 2011 at 4:46 PM, Olivier Lamy wrote:
> Le 12 décembre 2011 16:21, Arnaud Héritier 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
Le 12 décembre 2011 16:21, Arnaud Héritier 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)
> associated doc in t
+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
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 s
2011/12/12 Brian Fox :
>> 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 n
> 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 no
2011/12/12 Brett Porter :
>
> On 12/12/2011, at 7:42 PM, Olivier Lamy wrote:
>
>> 2011/12/12 Brett Porter :
>>> 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 time
+2048 ;-)
Regards Mirko
--
Sent from my phone
http://illegalstateexception.blogspot.com
http://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Dec 12, 2011 3:49 AM, "Jesse Farinacci" wrote:
> On Sun, Dec 11, 2011 at 9:47 PM, Benson Margulies
> wrote:
> > This is something tha
On 12/12/2011, at 7:42 PM, Olivier Lamy wrote:
> 2011/12/12 Brett Porter :
>> 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 g
2011/12/12 Brett Porter :
> 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
19 matches
Mail list logo
