[
https://issues.apache.org/jira/browse/WHIRR-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer updated WHIRR-747:
-------------------------------
Attachment: WHIRR-747.patch
The patch splits out parent and top-level POMs, and arranges the
assembly/site/javadoc aggregation/etc appropriately. Makes running the build
with a new version generally easier, and speeds the full build (including site,
package, etc) up by a couple minutes.
> Whirr builds with new version require mvn install before site can be generated
> ------------------------------------------------------------------------------
>
> Key: WHIRR-747
> URL: https://issues.apache.org/jira/browse/WHIRR-747
> Project: Whirr
> Issue Type: Bug
> Components: build
> Affects Versions: 0.8.2
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Fix For: 0.9.0
>
> Attachments: WHIRR-747.patch
>
>
> Pet peeve, I admit, but... Currently, you have to run mvn install before you
> can run mvn site (or do aggregate javadocs, etc) when you change versions.
> That's...annoying. And unnecessary. The way to fix this is to split the
> current parent+top-level POM into two - a parent POM that everything inherits
> from, which has the dependency management, common plugin definitions,
> profiles, etc, and a top-level POM that serves as the root of the reactor
> (i.e., has the module list in it), has the aggregate-specific logic in it
> (i.e., assembly stuff, site stuff, the like), and itself inherits from the
> parent POM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
