whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-747) Whirr builds with new version require mvn install before site can be generated
Date Wed, 25 Sep 2013 22:30:02 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778178#comment-13778178
] 

Andrei Savu commented on WHIRR-747:
-----------------------------------

+1 
                
> 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

Mime
View raw message