commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COMMONSSITE-46) Multi-module projects fail when using the "rc" profile in commons-parent
Date Thu, 03 Dec 2009 23:22:20 GMT

     [ https://issues.apache.org/jira/browse/COMMONSSITE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Niall Pemberton updated COMMONSSITE-46:
---------------------------------------

    Attachment: commons-parent-pom.patch

> Multi-module projects fail when using the "rc" profile in commons-parent
> ------------------------------------------------------------------------
>
>                 Key: COMMONSSITE-46
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-46
>             Project: Commons All
>          Issue Type: Bug
>          Components: Commons Parent Pom
>            Reporter: Niall Pemberton
>         Attachments: commons-parent-pom.patch
>
>
> The "rc" profile doesn't current work with multi-module projects (when the project has
not been previously installed in your local repo for the current version)
> For example running the following command on JCI
> {code}
>     mvn -Prc clean install
> {code}
> fails with the following error:
> {code}
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Missing:
> ----------
> 1) org.apache.commons:commons-jci-core:jar:1.1-SNAPSHOT
> ...
> {code}
> I found this is caused by trying to run the site plugin in the "rc" profile:
> {code}
>           <plugin>
>             <artifactId>maven-site-plugin</artifactId>
>             <executions>
>               <execution>
>                 <goals>
>                   <goal>site</goal>
>                 </goals>
>                 <phase>package</phase>
>               </execution>
>             </executions>
>           </plugin>
> {code}
> The intention of the above was so that when the assembly plugin ran to create the binary
distros then the site would be available to include in the distro. AFAIK we are now only shipping
javadocs in the binary distros and not any component sites. So I plan to remove the site plugin
from the "rc" profile and add a "javadoc" goal in the javadoc plugin in the "rc" profile.
This resolves the issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message