You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Casey <jd...@commonjava.org> on 2008/07/31 22:50:41 UTC
Maven 2.0.10-RC4
Hi,
I've got a new release candidate for people to try out:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
Major changes:
- Bumped wagon version to 1.0-beta-4
- Improved handling of mirror definitions without an <id/> element
The only outstanding potential issue has something to do with the
MJAVADOC-172 and MJAVADOC-194 integration tests, in the
maven-javadoc-plugin. I'm unable to even build this plugin on my
localhost due to unit test failures (even using Maven 2.0.9), so
unfortunately I can't even attempt to figure out what the specific
failure is in these cases.
Hopefully, RC4 will make it possible to distill a failing test case I
can use to fix the issue in the core (if it's in the core).
Enjoy.
-john
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Fabrice Bellingard <be...@gmail.com>.
No more problem - builds fine on my projects.
:-)
- Fabrice
bellingard@apache.org
On Thu, Jul 31, 2008 at 10:50 PM, John Casey <jd...@commonjava.org> wrote:
> Hi,
>
> I've got a new release candidate for people to try out:
>
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/>
>
> Major changes:
>
> - Bumped wagon version to 1.0-beta-4
> - Improved handling of mirror definitions without an <id/> element
>
> The only outstanding potential issue has something to do with the
> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
> maven-javadoc-plugin. I'm unable to even build this plugin on my localhost
> due to unit test failures (even using Maven 2.0.9), so unfortunately I can't
> even attempt to figure out what the specific failure is in these cases.
>
> Hopefully, RC4 will make it possible to distill a failing test case I can
> use to fix the issue in the core (if it's in the core).
>
> Enjoy.
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Maven 2.0.10-RC4
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Benjamin,
For the first one, I guess that javadoc:javadoc was not call from core.
For jdk6, I have no clue about BSH but I noticed that
maven-javadoc-plugin version is 2.4 and not 2.5-snap.
Thanks to have a glance :)
Vincent
2008/7/31 Benjamin Bentmann <be...@udo.edu>:
> Vincent Siveton wrote:
>
>> I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
>> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
>
> MJAVADOC-180 is a strange one: The IT's verify.bsh is run only if
> System.getProperty( "java.specification.version" ).equals( "1.5" )
> ??
>
> Anyway, I run "mvn clean verify" on Windows using RC4 once with Sun Java 1.5
> and once with Java 1.6. The debug logs I got are amazingly different. I left
> them at
> http://people.apache.org/~bentmann/maven/MJAVADOC-180/
> for inspection.
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Benjamin Bentmann <be...@udo.edu>.
Vincent Siveton wrote:
> I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
MJAVADOC-180 is a strange one: The IT's verify.bsh is run only if
System.getProperty( "java.specification.version" ).equals( "1.5" )
??
Anyway, I run "mvn clean verify" on Windows using RC4 once with Sun Java
1.5 and once with Java 1.6. The debug logs I got are amazingly
different. I left them at
http://people.apache.org/~bentmann/maven/MJAVADOC-180/
for inspection.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by John Casey <jd...@commonjava.org>.
Hmm, I don't remember taking that out. I'll have to check it out.
You're right, we need to make it consistent.
-j
Brett Porter wrote:
>
> On 01/08/2008, at 8:03 AM, John Casey wrote:
>
>> Until I can get the javadoc plugin working on OS X there's nothing I
>> can do to even peek at this.
>
> Fixed (it was relying on tools.jar, I made the behaviour the same as
> javac).
>
>>
>>
>> Why is it failing? Can you formulate a MNG issue with the relevant
>> details that are causing the ITs to fail? If I had some sort of set of
>> steps to reproduce the problem, it would help a lot.
>
>
> Technically, this was a bug in the javadoc plugin (MJAVADOC-211) - it
> doesn't create the reporting output directory if it doesn't exist (nor
> does the javadoc tool). I've fixed that so it passes on RC4 as well now.
>
> However, that means the functionality change was that it now doesn't
> create the target and target/site directories up front (which are
> configured in the POM). While that's a good thing, since they may not be
> used, it's probably going to break a plugin here and there, so it might
> be better to go back to the behaviour of making them that was in 2.0.9.
> I haven't filed an MNG or IT for this though.
>
> Glad to know it's a minor thing though :)
>
> Cheers,
> Brett
>
>>
>>
>> -john
>>
>> Vincent Siveton wrote:
>>> Hi John,
>>> I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
>>> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
>>> Cheers,
>>> Vincent
>>> 2008/7/31 John Casey <jd...@commonjava.org>:
>>>> Hi,
>>>>
>>>> I've got a new release candidate for people to try out:
>>>>
>>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>>>
>>>>
>>>> Major changes:
>>>>
>>>> - Bumped wagon version to 1.0-beta-4
>>>> - Improved handling of mirror definitions without an <id/> element
>>>>
>>>> The only outstanding potential issue has something to do with the
>>>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>>>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>>>> localhost
>>>> due to unit test failures (even using Maven 2.0.9), so unfortunately
>>>> I can't
>>>> even attempt to figure out what the specific failure is in these cases.
>>>>
>>>> Hopefully, RC4 will make it possible to distill a failing test case
>>>> I can
>>>> use to fix the issue in the core (if it's in the core).
>>>>
>>>> Enjoy.
>>>>
>>>> -john
>>>>
>>>> --
>>>> John Casey
>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by John Casey <jd...@commonjava.org>.
This is filed under MNG-3694.
I think I have a solution now, and I've written an integration test that
fails under 2.0.10-RC4...I'm running the test now vs. the fixed version,
and then I'll verify that I didn't break anything else.
-john
Brett Porter wrote:
> Yeah, I spoke too soon.
>
> getSourcePaths() in the javadoc plugin now ends up with:
> [${project.basedir}/src/main/java, ${project.basedir}/src/main/java]
>
> ie, uninterpolated. the prune method them removes them since they aren't
> found, and so it does nothing (as there are no sourcePaths).
>
> So, basically, the problem is that getCompileSourceRoots() is not
> interpolated.
>
> HTH,
> Brett
>
> On 02/08/2008, at 12:12 AM, Vincent Siveton wrote:
>
>> Hi Brett,
>>
>> Unfortunetely, under windows, ITs fail again.
>> I flag the debug mode for invoker plugin so I guess it could be useful
>> for John or others.
>>
>> Thanks a lot Brett for your support.
>>
>> Vincent
>>
>> 2008/8/1 Brett Porter <br...@apache.org>:
>>>
>>> On 01/08/2008, at 8:03 AM, John Casey wrote:
>>>
>>>> Until I can get the javadoc plugin working on OS X there's nothing I
>>>> can
>>>> do to even peek at this.
>>>
>>> Fixed (it was relying on tools.jar, I made the behaviour the same as
>>> javac).
>>>
>>>>
>>>>
>>>> Why is it failing? Can you formulate a MNG issue with the relevant
>>>> details
>>>> that are causing the ITs to fail? If I had some sort of set of steps to
>>>> reproduce the problem, it would help a lot.
>>>
>>>
>>> Technically, this was a bug in the javadoc plugin (MJAVADOC-211) - it
>>> doesn't create the reporting output directory if it doesn't exist
>>> (nor does
>>> the javadoc tool). I've fixed that so it passes on RC4 as well now.
>>>
>>> However, that means the functionality change was that it now doesn't
>>> create
>>> the target and target/site directories up front (which are configured
>>> in the
>>> POM). While that's a good thing, since they may not be used, it's
>>> probably
>>> going to break a plugin here and there, so it might be better to go
>>> back to
>>> the behaviour of making them that was in 2.0.9. I haven't filed an
>>> MNG or IT
>>> for this though.
>>>
>>> Glad to know it's a minor thing though :)
>>>
>>> Cheers,
>>> Brett
>>>
>>>>
>>>>
>>>> -john
>>>>
>>>> Vincent Siveton wrote:
>>>>>
>>>>> Hi John,
>>>>> I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
>>>>> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
>>>>> Cheers,
>>>>> Vincent
>>>>> 2008/7/31 John Casey <jd...@commonjava.org>:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I've got a new release candidate for people to try out:
>>>>>>
>>>>>>
>>>>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>>>>>
>>>>>>
>>>>>> Major changes:
>>>>>>
>>>>>> - Bumped wagon version to 1.0-beta-4
>>>>>> - Improved handling of mirror definitions without an <id/> element
>>>>>>
>>>>>> The only outstanding potential issue has something to do with the
>>>>>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>>>>>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>>>>>> localhost
>>>>>> due to unit test failures (even using Maven 2.0.9), so
>>>>>> unfortunately I
>>>>>> can't
>>>>>> even attempt to figure out what the specific failure is in these
>>>>>> cases.
>>>>>>
>>>>>> Hopefully, RC4 will make it possible to distill a failing test case I
>>>>>> can
>>>>>> use to fix the issue in the core (if it's in the core).
>>>>>>
>>>>>> Enjoy.
>>>>>>
>>>>>> -john
>>>>>>
>>>>>> --
>>>>>> John Casey
>>>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> --
>>>> John Casey
>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> --
>>> Brett Porter
>>> brett@apache.org
>>> http://blogs.exist.com/bporter/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Brett Porter <br...@apache.org>.
Yeah, I spoke too soon.
getSourcePaths() in the javadoc plugin now ends up with:
[${project.basedir}/src/main/java, ${project.basedir}/src/main/java]
ie, uninterpolated. the prune method them removes them since they
aren't found, and so it does nothing (as there are no sourcePaths).
So, basically, the problem is that getCompileSourceRoots() is not
interpolated.
HTH,
Brett
On 02/08/2008, at 12:12 AM, Vincent Siveton wrote:
> Hi Brett,
>
> Unfortunetely, under windows, ITs fail again.
> I flag the debug mode for invoker plugin so I guess it could be useful
> for John or others.
>
> Thanks a lot Brett for your support.
>
> Vincent
>
> 2008/8/1 Brett Porter <br...@apache.org>:
>>
>> On 01/08/2008, at 8:03 AM, John Casey wrote:
>>
>>> Until I can get the javadoc plugin working on OS X there's nothing
>>> I can
>>> do to even peek at this.
>>
>> Fixed (it was relying on tools.jar, I made the behaviour the same
>> as javac).
>>
>>>
>>>
>>> Why is it failing? Can you formulate a MNG issue with the relevant
>>> details
>>> that are causing the ITs to fail? If I had some sort of set of
>>> steps to
>>> reproduce the problem, it would help a lot.
>>
>>
>> Technically, this was a bug in the javadoc plugin (MJAVADOC-211) - it
>> doesn't create the reporting output directory if it doesn't exist
>> (nor does
>> the javadoc tool). I've fixed that so it passes on RC4 as well now.
>>
>> However, that means the functionality change was that it now
>> doesn't create
>> the target and target/site directories up front (which are
>> configured in the
>> POM). While that's a good thing, since they may not be used, it's
>> probably
>> going to break a plugin here and there, so it might be better to go
>> back to
>> the behaviour of making them that was in 2.0.9. I haven't filed an
>> MNG or IT
>> for this though.
>>
>> Glad to know it's a minor thing though :)
>>
>> Cheers,
>> Brett
>>
>>>
>>>
>>> -john
>>>
>>> Vincent Siveton wrote:
>>>>
>>>> Hi John,
>>>> I tried RC4 under javadoc plugin and I have now 3 ITs failures on
>>>> my
>>>> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
>>>> Cheers,
>>>> Vincent
>>>> 2008/7/31 John Casey <jd...@commonjava.org>:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I've got a new release candidate for people to try out:
>>>>>
>>>>>
>>>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>>>>
>>>>> Major changes:
>>>>>
>>>>> - Bumped wagon version to 1.0-beta-4
>>>>> - Improved handling of mirror definitions without an <id/> element
>>>>>
>>>>> The only outstanding potential issue has something to do with the
>>>>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>>>>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>>>>> localhost
>>>>> due to unit test failures (even using Maven 2.0.9), so
>>>>> unfortunately I
>>>>> can't
>>>>> even attempt to figure out what the specific failure is in these
>>>>> cases.
>>>>>
>>>>> Hopefully, RC4 will make it possible to distill a failing test
>>>>> case I
>>>>> can
>>>>> use to fix the issue in the core (if it's in the core).
>>>>>
>>>>> Enjoy.
>>>>>
>>>>> -john
>>>>>
>>>>> --
>>>>> John Casey
>>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://blogs.exist.com/bporter/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Brett,
Unfortunetely, under windows, ITs fail again.
I flag the debug mode for invoker plugin so I guess it could be useful
for John or others.
Thanks a lot Brett for your support.
Vincent
2008/8/1 Brett Porter <br...@apache.org>:
>
> On 01/08/2008, at 8:03 AM, John Casey wrote:
>
>> Until I can get the javadoc plugin working on OS X there's nothing I can
>> do to even peek at this.
>
> Fixed (it was relying on tools.jar, I made the behaviour the same as javac).
>
>>
>>
>> Why is it failing? Can you formulate a MNG issue with the relevant details
>> that are causing the ITs to fail? If I had some sort of set of steps to
>> reproduce the problem, it would help a lot.
>
>
> Technically, this was a bug in the javadoc plugin (MJAVADOC-211) - it
> doesn't create the reporting output directory if it doesn't exist (nor does
> the javadoc tool). I've fixed that so it passes on RC4 as well now.
>
> However, that means the functionality change was that it now doesn't create
> the target and target/site directories up front (which are configured in the
> POM). While that's a good thing, since they may not be used, it's probably
> going to break a plugin here and there, so it might be better to go back to
> the behaviour of making them that was in 2.0.9. I haven't filed an MNG or IT
> for this though.
>
> Glad to know it's a minor thing though :)
>
> Cheers,
> Brett
>
>>
>>
>> -john
>>
>> Vincent Siveton wrote:
>>>
>>> Hi John,
>>> I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
>>> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
>>> Cheers,
>>> Vincent
>>> 2008/7/31 John Casey <jd...@commonjava.org>:
>>>>
>>>> Hi,
>>>>
>>>> I've got a new release candidate for people to try out:
>>>>
>>>>
>>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>>>
>>>> Major changes:
>>>>
>>>> - Bumped wagon version to 1.0-beta-4
>>>> - Improved handling of mirror definitions without an <id/> element
>>>>
>>>> The only outstanding potential issue has something to do with the
>>>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>>>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>>>> localhost
>>>> due to unit test failures (even using Maven 2.0.9), so unfortunately I
>>>> can't
>>>> even attempt to figure out what the specific failure is in these cases.
>>>>
>>>> Hopefully, RC4 will make it possible to distill a failing test case I
>>>> can
>>>> use to fix the issue in the core (if it's in the core).
>>>>
>>>> Enjoy.
>>>>
>>>> -john
>>>>
>>>> --
>>>> John Casey
>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Brett Porter <br...@apache.org>.
On 01/08/2008, at 8:03 AM, John Casey wrote:
> Until I can get the javadoc plugin working on OS X there's nothing I
> can do to even peek at this.
Fixed (it was relying on tools.jar, I made the behaviour the same as
javac).
>
>
> Why is it failing? Can you formulate a MNG issue with the relevant
> details that are causing the ITs to fail? If I had some sort of set
> of steps to reproduce the problem, it would help a lot.
Technically, this was a bug in the javadoc plugin (MJAVADOC-211) - it
doesn't create the reporting output directory if it doesn't exist
(nor does the javadoc tool). I've fixed that so it passes on RC4 as
well now.
However, that means the functionality change was that it now doesn't
create the target and target/site directories up front (which are
configured in the POM). While that's a good thing, since they may not
be used, it's probably going to break a plugin here and there, so it
might be better to go back to the behaviour of making them that was in
2.0.9. I haven't filed an MNG or IT for this though.
Glad to know it's a minor thing though :)
Cheers,
Brett
>
>
> -john
>
> Vincent Siveton wrote:
>> Hi John,
>> I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
>> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
>> Cheers,
>> Vincent
>> 2008/7/31 John Casey <jd...@commonjava.org>:
>>> Hi,
>>>
>>> I've got a new release candidate for people to try out:
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>>
>>> Major changes:
>>>
>>> - Bumped wagon version to 1.0-beta-4
>>> - Improved handling of mirror definitions without an <id/> element
>>>
>>> The only outstanding potential issue has something to do with the
>>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>>> localhost
>>> due to unit test failures (even using Maven 2.0.9), so
>>> unfortunately I can't
>>> even attempt to figure out what the specific failure is in these
>>> cases.
>>>
>>> Hopefully, RC4 will make it possible to distill a failing test
>>> case I can
>>> use to fix the issue in the core (if it's in the core).
>>>
>>> Enjoy.
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by John Casey <jd...@commonjava.org>.
Until I can get the javadoc plugin working on OS X there's nothing I can
do to even peek at this.
Why is it failing? Can you formulate a MNG issue with the relevant
details that are causing the ITs to fail? If I had some sort of set of
steps to reproduce the problem, it would help a lot.
-john
Vincent Siveton wrote:
> Hi John,
>
> I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
> side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
>
> Cheers,
>
> Vincent
>
> 2008/7/31 John Casey <jd...@commonjava.org>:
>> Hi,
>>
>> I've got a new release candidate for people to try out:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>
>> Major changes:
>>
>> - Bumped wagon version to 1.0-beta-4
>> - Improved handling of mirror definitions without an <id/> element
>>
>> The only outstanding potential issue has something to do with the
>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>> maven-javadoc-plugin. I'm unable to even build this plugin on my localhost
>> due to unit test failures (even using Maven 2.0.9), so unfortunately I can't
>> even attempt to figure out what the specific failure is in these cases.
>>
>> Hopefully, RC4 will make it possible to distill a failing test case I can
>> use to fix the issue in the core (if it's in the core).
>>
>> Enjoy.
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Vincent Siveton <vi...@gmail.com>.
Hi John,
I tried RC4 under javadoc plugin and I have now 3 ITs failures on my
side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194
Cheers,
Vincent
2008/7/31 John Casey <jd...@commonjava.org>:
> Hi,
>
> I've got a new release candidate for people to try out:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>
> Major changes:
>
> - Bumped wagon version to 1.0-beta-4
> - Improved handling of mirror definitions without an <id/> element
>
> The only outstanding potential issue has something to do with the
> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
> maven-javadoc-plugin. I'm unable to even build this plugin on my localhost
> due to unit test failures (even using Maven 2.0.9), so unfortunately I can't
> even attempt to figure out what the specific failure is in these cases.
>
> Hopefully, RC4 will make it possible to distill a failing test case I can
> use to fix the issue in the core (if it's in the core).
>
> Enjoy.
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Brett Porter <br...@apache.org>.
We already had that discussion and decided it would be overkill - once
2.0.10 is released nobody will be concerned with the difference
between these release candidates (And they won't be available for
download any more anyway). There are few enough changes between each
that you can use timestamps/svn history to determine it if needed.
- Brett
On 01/08/2008, at 7:47 AM, Rahul Thakur wrote:
> OTOH, there is a 'Fix Version' property in JIRA that you can use to
> assign a release/build/version id.
>
> Rahul
>
> On Fri, Aug 1, 2008 at 9:28 AM, Paul Benedict <pb...@apache.org>
> wrote:
>> Is there anywhere in JIRA we can tag some issues as being fixed in
>> RC1, RC2,
>> etc.? I liked how Bugzilla had flags to mark items. Anything like
>> that in
>> JIRA?
>>
>> Paul
>>
>> On Thu, Jul 31, 2008 at 4:16 PM, Brett Porter <br...@apache.org>
>> wrote:
>>
>>> Would this be a good one to push to users@, particularly
>>> highlighting the
>>> need to test projects with creative uses of interpolation and
>>> various
>>> deployment setups?
>>>
>>> Cheers,
>>> Brett
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Rahul Thakur <ra...@gmail.com>.
OTOH, there is a 'Fix Version' property in JIRA that you can use to
assign a release/build/version id.
Rahul
On Fri, Aug 1, 2008 at 9:28 AM, Paul Benedict <pb...@apache.org> wrote:
> Is there anywhere in JIRA we can tag some issues as being fixed in RC1, RC2,
> etc.? I liked how Bugzilla had flags to mark items. Anything like that in
> JIRA?
>
> Paul
>
> On Thu, Jul 31, 2008 at 4:16 PM, Brett Porter <br...@apache.org> wrote:
>
>> Would this be a good one to push to users@, particularly highlighting the
>> need to test projects with creative uses of interpolation and various
>> deployment setups?
>>
>> Cheers,
>> Brett
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Paul Benedict <pb...@apache.org>.
Is there anywhere in JIRA we can tag some issues as being fixed in RC1, RC2,
etc.? I liked how Bugzilla had flags to mark items. Anything like that in
JIRA?
Paul
On Thu, Jul 31, 2008 at 4:16 PM, Brett Porter <br...@apache.org> wrote:
> Would this be a good one to push to users@, particularly highlighting the
> need to test projects with creative uses of interpolation and various
> deployment setups?
>
> Cheers,
> Brett
Re: Maven 2.0.10-RC4
Posted by John Casey <jd...@commonjava.org>.
it'd be a simple enough operation to lookup the timestamp on the RCs on
my staging repo, and do a date-based search using those values...
What's the value in providing this level of resolution, though?
Paul Benedict wrote:
> Brett, I know those discussions existed. I was apart of them :-) and I
> recommended we should not create extra JIRA versions for 1 and 2 tickets. My
> question this time, however, is a bit different. I just wanted to know if we
> should somehow mark the ticket with RC1, RC2, etc. within the version just
> so we can have a history of which tickets popped up when. It may be even as
> simple as adding another field or adding it to the environment.
>
> Paul
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Brett Porter <br...@apache.org>.
Ah :)
perhaps "fixed in RCx" as the last comment is enough?
- Brett
On 01/08/2008, at 1:35 PM, Paul Benedict wrote:
> Brett, I know those discussions existed. I was apart of them :-) and I
> recommended we should not create extra JIRA versions for 1 and 2
> tickets. My
> question this time, however, is a bit different. I just wanted to
> know if we
> should somehow mark the ticket with RC1, RC2, etc. within the
> version just
> so we can have a history of which tickets popped up when. It may be
> even as
> simple as adding another field or adding it to the environment.
>
> Paul
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Paul Benedict <pb...@apache.org>.
Brett, I know those discussions existed. I was apart of them :-) and I
recommended we should not create extra JIRA versions for 1 and 2 tickets. My
question this time, however, is a bit different. I just wanted to know if we
should somehow mark the ticket with RC1, RC2, etc. within the version just
so we can have a history of which tickets popped up when. It may be even as
simple as adding another field or adding it to the environment.
Paul
RE: Maven 2.0.10-RC4
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Until we actually think all the known issues are resolved, we shouldn't
send it to users@. We don't want to lose their attention by bringing RCs
in an early stage.
-----Original Message-----
From: John Casey [mailto:jdcasey@commonjava.org]
Sent: Thursday, July 31, 2008 6:04 PM
To: Maven Developers List
Subject: Re: Maven 2.0.10-RC4
Yes, I believe this would be a good candidate to push to users@. I'll
put together the message now.
It's worth remembering that we may have a problem expressed somewhere in
the javadoc plugin, so this may not be the last RC. But it's becoming
must more stable with this RC.
-john
Brett Porter wrote:
> Would this be a good one to push to users@, particularly highlighting
> the need to test projects with creative uses of interpolation and
> various deployment setups?
>
> Cheers,
> Brett
>
> On 01/08/2008, at 6:50 AM, John Casey wrote:
>
>> Hi,
>>
>> I've got a new release candidate for people to try out:
>>
>>
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apac
he/maven/apache-maven/2.0.10-RC4/
>>
>>
>> Major changes:
>>
>> - Bumped wagon version to 1.0-beta-4
>> - Improved handling of mirror definitions without an <id/> element
>>
>> The only outstanding potential issue has something to do with the
>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>> localhost due to unit test failures (even using Maven 2.0.9), so
>> unfortunately I can't even attempt to figure out what the specific
>> failure is in these cases.
>>
>> Hopefully, RC4 will make it possible to distill a failing test case I
>> can use to fix the issue in the core (if it's in the core).
>>
>> Enjoy.
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by John Casey <jd...@commonjava.org>.
Yes, I believe this would be a good candidate to push to users@. I'll
put together the message now.
It's worth remembering that we may have a problem expressed somewhere in
the javadoc plugin, so this may not be the last RC. But it's becoming
must more stable with this RC.
-john
Brett Porter wrote:
> Would this be a good one to push to users@, particularly highlighting
> the need to test projects with creative uses of interpolation and
> various deployment setups?
>
> Cheers,
> Brett
>
> On 01/08/2008, at 6:50 AM, John Casey wrote:
>
>> Hi,
>>
>> I've got a new release candidate for people to try out:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>
>>
>> Major changes:
>>
>> - Bumped wagon version to 1.0-beta-4
>> - Improved handling of mirror definitions without an <id/> element
>>
>> The only outstanding potential issue has something to do with the
>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>> localhost due to unit test failures (even using Maven 2.0.9), so
>> unfortunately I can't even attempt to figure out what the specific
>> failure is in these cases.
>>
>> Hopefully, RC4 will make it possible to distill a failing test case I
>> can use to fix the issue in the core (if it's in the core).
>>
>> Enjoy.
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Brett Porter <br...@apache.org>.
Would this be a good one to push to users@, particularly highlighting
the need to test projects with creative uses of interpolation and
various deployment setups?
Cheers,
Brett
On 01/08/2008, at 6:50 AM, John Casey wrote:
> Hi,
>
> I've got a new release candidate for people to try out:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>
> Major changes:
>
> - Bumped wagon version to 1.0-beta-4
> - Improved handling of mirror definitions without an <id/> element
>
> The only outstanding potential issue has something to do with the
> MJAVADOC-172 and MJAVADOC-194 integration tests, in the maven-
> javadoc-plugin. I'm unable to even build this plugin on my localhost
> due to unit test failures (even using Maven 2.0.9), so unfortunately
> I can't even attempt to figure out what the specific failure is in
> these cases.
>
> Hopefully, RC4 will make it possible to distill a failing test case
> I can use to fix the issue in the core (if it's in the core).
>
> Enjoy.
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Benjamin Bentmann <be...@udo.edu>.
Arnaud HERITIER wrote:
> What are the errors in javadoc tests ?
MJAVADOC-210, the plugin was searching for tools.jar which isn't found
on Mac, so the unit test to check the auto-detection of taglets failed.
> I'm building it successfuly on Mac OS X.
Strange. How about the ITs, do they fail for you with RC4, too?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Arnaud HERITIER <ah...@gmail.com>.
What are the errors in javadoc tests ?
I'm building it successfuly on Mac OS X.
I remember I had to add the JAVA_HOME
(JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home)
and tests passed
Arnaud
On Thu, Jul 31, 2008 at 10:50 PM, John Casey <jd...@commonjava.org> wrote:
> Hi,
>
> I've got a new release candidate for people to try out:
>
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/>
>
> Major changes:
>
> - Bumped wagon version to 1.0-beta-4
> - Improved handling of mirror definitions without an <id/> element
>
> The only outstanding potential issue has something to do with the
> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
> maven-javadoc-plugin. I'm unable to even build this plugin on my localhost
> due to unit test failures (even using Maven 2.0.9), so unfortunately I can't
> even attempt to figure out what the specific failure is in these cases.
>
> Hopefully, RC4 will make it possible to distill a failing test case I can
> use to fix the issue in the core (if it's in the core).
>
> Enjoy.
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
Re: Maven 2.0.10-RC4
Posted by John Casey <jd...@commonjava.org>.
I'm tracking this under http://jira.codehaus.org/browse/MNG-3693
I've already got the fix in place in RC5-snapshot, but it's going to
take a little while to produce a self-contained integration test for it.
-john
Mauro Talevi wrote:
> John Casey wrote:
>> Hi,
>>
>> I've got a new release candidate for people to try out:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>>
>>
>> Major changes:
>>
>> - Bumped wagon version to 1.0-beta-4
>> - Improved handling of mirror definitions without an <id/> element
>>
>> The only outstanding potential issue has something to do with the
>> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
>> maven-javadoc-plugin. I'm unable to even build this plugin on my
>> localhost due to unit test failures (even using Maven 2.0.9), so
>> unfortunately I can't even attempt to figure out what the specific
>> failure is in these cases.
>>
>> Hopefully, RC4 will make it possible to distill a failing test case I
>> can use to fix the issue in the core (if it's in the core).
>>
>
> John,
>
> this RC has a major regression wrt 2.0.9 when building Pico:
>
> To reproduce:
> svn co https://svn.codehaus.org/picocontainer/java/2.x/trunk/pico
> cd pico
> mvn install
>
> You'll see that when it builds the TCK module - whose src is a sub-part
> of the core test src - it fails to compile because it cannot find as a
> dependency the core which had been previously built, and declared as a
> dependency in the parent management section.
>
> I'll see if there is an IT for this scenario (and it not I'll add it),
> but I suspect some of the changes in the dependencies resolution will be
> at the root.
>
> Cheers
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 2.0.10-RC4
Posted by Mauro Talevi <ma...@aquilonia.org>.
John Casey wrote:
> Hi,
>
> I've got a new release candidate for people to try out:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/
>
>
> Major changes:
>
> - Bumped wagon version to 1.0-beta-4
> - Improved handling of mirror definitions without an <id/> element
>
> The only outstanding potential issue has something to do with the
> MJAVADOC-172 and MJAVADOC-194 integration tests, in the
> maven-javadoc-plugin. I'm unable to even build this plugin on my
> localhost due to unit test failures (even using Maven 2.0.9), so
> unfortunately I can't even attempt to figure out what the specific
> failure is in these cases.
>
> Hopefully, RC4 will make it possible to distill a failing test case I
> can use to fix the issue in the core (if it's in the core).
>
John,
this RC has a major regression wrt 2.0.9 when building Pico:
To reproduce:
svn co https://svn.codehaus.org/picocontainer/java/2.x/trunk/pico
cd pico
mvn install
You'll see that when it builds the TCK module - whose src is a sub-part
of the core test src - it fails to compile because it cannot find as a
dependency the core which had been previously built, and declared as a
dependency in the parent management section.
I'll see if there is an IT for this scenario (and it not I'll add it),
but I suspect some of the changes in the dependencies resolution will be
at the root.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org