forking lifecycle of javadoc:jar goal results in release-plugin error
---------------------------------------------------------------------
Key: MJAVADOC-170
URL: http://jira.codehaus.org/browse/MJAVADOC-170
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: maven 2.0.8
Reporter: Sandro Sonntag
Priority: Blocker
In my complex scenario the release plugin fails because the javadoc:jar goal
forks a new lifcycle "generate-sources".
"javadoc:jar" is decalared in the project pom to build automaticly. The error
occours if there are plugins attached on the "generate-sources" phase
how need artifacts of the reactor build.
In my case the xdoclet and attributes plugins are attached.
The following error occoures if I use the release plugin:
Missing:
----------
1) de.kqv.ec.tarif:tarif-freundschaftswerbung-businesslogic:jar:1.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=de.kqv.ec.tarif
-DartifactId=tarif-freundschaftswerbung-businesslogic -Dversion=1.0
-Dpackaging=jar -
Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file there:
mvn deploy:deploy-file -DgroupId=de.kqv.ec.tarif
-DartifactId=tarif-freundschaftswerbung-businesslogic -Dversion=1.0
-Dpackaging=jar -Df
ile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
de.kqv.ec.tarif:tarif-freundschaftswerbung-businesslogic-ejb:ejb:1.0
2)
de.kqv.ec.tarif:tarif-freundschaftswerbung-businesslogic:jar:1.0
If I remove the javadoc plugin all workes fine. There is no possible workaround
know. A solution could be to remove the "execute phase" of the plugin. I cant
imagine that somebody use the goal standalone. I thing its a general Maven
design problem.
Forking a phase sould only be executed if the goal is running standalone. But
I´m not the expert.
Greetings Sandro
The source plugin has the same problem see:
http://jira.codehaus.org/browse/MSOURCES-31
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
