I've got the NPE fixed, but it took awhile to write an integration test
that would help verify it without requiring a Hudson instance. ;)
I'll work on the sources jar next, once the full IT run I just started
is finished.
Daniel Kulp wrote:
I'm testing with CXF trunk: (jdk 1.5)
https://svn.apache.org/repos/asf/cxf/trunk/
I think the NPE is hit with:
mvn install -Peverything,nochecks
The sources jar issue I hit with:
mvn install -Pdeploy,everything,nochecks -Dmaven.test.skip.exec=true
and then checking the source jars that were generated.
Dan
On Tuesday 12 August 2008 11:53:32 am John Casey wrote:
Hi Daniel, Mauro,
In either of these cases, can anyone give me some specific steps (and
the project SVN URL, if possible) to reproduce the problem? I tried
running 'mvn clean source:jar' last night on maven-project and
maven-model, but apparently that's too simplistic to reproduce the
problem...all of the sources were present.
I'd like to open another JIRA for this, but I need more to go on before
I can come up with a description for the ticket that makes any real sense.
Thanks,
-john
Mauro Talevi wrote:
Daniel Kulp wrote:
John,
Performance is a bit better, but in a multi-project reactor build, the
source jars are now all "wrong". None of the source ends up in the
jars. Just the "extra" things from the remote-resources.
Yes - I can confirm that. In fact, another symptom of this is running
cobertura. The coverage report is produced, but when clicking on any
class it shows an error because it cannot find the java source.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
