Envoyé le : Jeudi, 24 Juillet 2008, 9h35mn 37s
Objet : Re: Re : [PLEASE TEST] Maven 2.0.10-RC2
I have seen this in 2.0.9 but not able to produce it.
-D
On Thu, Jul 24, 2008 at 12:31 AM, Julien HENRY <[EMAIL PROTECTED]> wrote:
During my build, Maven try to download artifacts from
http://cvs
FWIW, I've opened http://jira.codehaus.org/browse/MNG-3684
for this issue.
-john
Marvin Froeder wrote:
Running a report mojo (extends AbstractMojo and implements MavenReport)
I inject build:
/**
* @parameter expression="${project.build}"
* @required
* @readonly
*/
klisted wrong repo url like cvs.a.o. I guess this logic
could be include in the core.
Cheers,
Vincent
Regards
- Message d'origine
De : Brett Porter <[EMAIL PROTECTED]>
À : Maven Developers List
Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s
Objet : Re: [PLEASE TE
yep, I have others to throw on that stack then :) gl
On Thu, Jul 24, 2008 at 1:00 PM, John Casey <[EMAIL PROTECTED]> wrote:
> See http://jira.codehaus.org/browse/MNG-3680
>
> -j
>
> Fabrice Bellingard wrote:
>>
>> Hi,
>>
>> well, a couple of things:
>>
>>
>> 1- I also had the stack trace issue (bu
See http://jira.codehaus.org/browse/MNG-3680
-j
Fabrice Bellingard wrote:
Hi,
well, a couple of things:
1- I also had the stack trace issue (but Brett apparently just fixed it in
SVN)
2- the following output appears several times in the build log of one of my
projects (which I don't have w
gt;>> nor in my settings.xml). Is it a bug?
>>>
>>> Nope. I already noticed that when I worked on MPIR.
>>>
>>> It is due that some repositories like cvs.apache.org was specifiedin
>>> the transitive dependencies pom or in the plugins pom.
>>> In MP
[EMAIL PROTECTED]>
À : Maven Developers List
Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s
Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2
Fixed in SVN (you can also see comment on the RC1 thread for the
reason this was occuring).
- Brett
On 24/07/2008, at 1:10 PM, Michael McCallum wrote:
> could be include in the core.
>
> Cheers,
>
> Vincent
>
>>
>> Regards
>>
>>
>>
>> - Message d'origine
>> De : Brett Porter <[EMAIL PROTECTED]>
>> À : Maven Developers List
>> Envoyé le : Jeudi, 24 Juille
eers,
Vincent
>
> Regards
>
>
>
> - Message d'origine
> De : Brett Porter <[EMAIL PROTECTED]>
> À : Maven Developers List
> Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s
> Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2
>
>
> Fixed in SVN (
http://jira.codehaus.org/browse/MNG-3679
On Thu, Jul 24, 2008 at 7:46 AM, John Casey <[EMAIL PROTECTED]> wrote:
> I'll take a look at it. If you have a small test case you could put into a
> JIRA ticket, that would help me out quite a bit.
>
> Thanks,
>
> -john
>
> Dan Tran wrote:
>>
>> in 2.0.9,
a bug?
Regards
- Message d'origine
De : Brett Porter <[EMAIL PROTECTED]>
À : Maven Developers List
Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s
Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2
Fixed in SVN (you can also see comment on the RC1 thread for the
reason this was occuring)
Please file a JIRA for this issue, and if you can include a failing test
case that will make it much simpler to fix the issue.
Thanks,
-john
Marvin Froeder wrote:
Running a report mojo (extends AbstractMojo and implements MavenReport)
I inject build:
/**
* @parameter expression="${p
I'll take a look at it. If you have a small test case you could put into
a JIRA ticket, that would help me out quite a bit.
Thanks,
-john
Dan Tran wrote:
in 2.0.9, i used to beable to do this
${some.custom.var}
Not any more with 2.0.10-RC2
here is the error:
[INFO] ---
lt;[EMAIL PROTECTED]>
À : Maven Developers List
Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s
Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2
Fixed in SVN (you can also see comment on the RC1 thread for the
reason this was occuring).
- Brett
On 24/07/2008, at 1:10 PM, Michael McCallum wrote:
Running a report mojo (extends AbstractMojo and implements MavenReport)
I inject build:
/**
* @parameter expression="${project.build}"
* @required
* @readonly
*/
protected Build build;
At some point I get build directory:
build.getDirectory()
But is returning "${proje
Hi,
well, a couple of things:
1- I also had the stack trace issue (but Brett apparently just fixed it in
SVN)
2- the following output appears several times in the build log of one of my
projects (which I don't have with 2.0.9):
[WARNING] POM for 'bcel:bcel:pom:5.1:compile' is
on't know where this repository come from (it's not in my pom.xml nor in
> my settings.xml). Is it a bug?
>
> Regards
>
>
>
> - Message d'origine
> De : Brett Porter <[EMAIL PROTECTED]>
> À : Maven Developers List
> Envoyé le : Jeudi, 24
come from (it's not in my pom.xml nor in
> my settings.xml). Is it a bug?
>
> Regards
>
>
>
> - Message d'origine
> De : Brett Porter <[EMAIL PROTECTED]>
> À : Maven Developers List
> Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s
> Objet :
MAIL PROTECTED]>
À : Maven Developers List
Envoyé le : Jeudi, 24 Juillet 2008, 6h52mn 20s
Objet : Re: [PLEASE TEST] Maven 2.0.10-RC2
Fixed in SVN (you can also see comment on the RC1 thread for the
reason this was occuring).
- Brett
On 24/07/2008, at 1:10 PM, Michael McCallum wrote:
> I'
Fixed in SVN (you can also see comment on the RC1 thread for the
reason this was occuring).
- Brett
On 24/07/2008, at 1:10 PM, Michael McCallum wrote:
I'm getting stack traces rather than the nice message when an
artifact does
not exist the repository...
Downloading:
http://mvn.somedomain
On Thu, 24 Jul 2008 15:10:40 Michael McCallum wrote:
> I'm getting stack traces rather than the nice message when an artifact does
> not exist the repository...
For regular maven user you could almost get away with this... but for newbies
its will give them the willies and drive them away getting
I'm getting stack traces rather than the nice message when an artifact does
not exist the repository...
Downloading:
http://mvn.somedomaindev.co.nz/central/nz/co/somedomain/nz.co.somedomain.parent/14-java4/nz.co.somedomain.parent-14-java4.pom
org.apache.maven.wagon.ResourceDoesNotExistException:
Subject: Re: [PLEASE TEST] Maven 2.0.10-RC2
in 2.0.9, i used to beable to do this
${some.custom.var}
Not any more with 2.0.10-RC2
here is the error:
[INFO]
[ERROR] BUILD ERROR
[INFO
in 2.0.9, i used to beable to do this
${some.custom.var}
Not any more with 2.0.10-RC2
here is the error:
[INFO]
[ERROR] BUILD ERROR
[INFO] ---
Hello everyone,
Okay, I think we've got all of the problems with RC1 sorted out, and the
integration tests are finally passing again.
So, without further ado, let's get RC2 out there for testing! You can
find the distribution here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10
25 matches
Mail list logo
