After spending 2 whole workdays on it (this time), it's clearly time for
help.  
 
Let's rewind to the core problem.  I want to run javadoc and jxr reports
with aggregates/non-aggregates and still be able to do release builds.
 
Back in 2007 I opened a bug and even provided a zip file so it could be
reproduced:
 
http://jira.codehaus.org/browse/MNG-3336
 
Fast forward to the present and with Maven 2.0.9 and all the latest
plugin versions.  So the site is generated and all works great until we
try to do an official release build for QA.  If we didn't use release
builds and versioning, which is at the core of Maven, all would be fine.

 
So my next approach was to take the reporting stuff out into a separate
pom that inherits from the main pom and use 
 
  mvn -f reporting.xml install site:site site:deploy
 
This mostly worked, but would always run into some strange error even on
pretty much identical configuration.  It's like there a bunch of
assumptions that fail when using the -f approach.  
 
I generated a pom using help:effective-pom to remove the complication of
inheriting a pom and still I got strange errors. 
  mvn -f reporting.xml help:effective-pom > orphan.xml    [and removing
the parent definition]
 
I had errors from PMD "Failure executing PMD ... Can't use enum as a
keyword in pre-JDK 1.5 target" which was really weird because I had
removed PMD completely from the pom I was using and using effective-pom
I verified that it had been removed.  It's like one of those horror
movies where the tv still comes on after it's unplugged.  I guess maybe
because the child projects inherit from the real parent pom, maybe
that's how PMD finds it way back into the mix.  
 
I've seen messages like "[INFO] Unable to load parent project from a
relative path: Could not find the model file", which is probably a
flashing red symptom of different behavior when using mvn -f!
 
Layout:
/pom.xml
/reporting.xml
/child/pom.xml
/child2/pom.xml
 
So clearly -f is not going to work.  The only idea I have left is that I
haven't tried using the new syntax for config with 2.5 javadoc plugin,
i.e
 
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.
html
 
using "aggregate goal" instead of "aggregate parameter".  Any other
ideas?  It's kind of a big deal risking breaking release builds and it
may be a month before I can try again if it's not already too late.
 
Paul Sundling
 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to