You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/09/24 21:51:05 UTC

[jira] [Created] (WHIRR-747) Whirr builds with new version require mvn install before site can be generated

Andrew Bayer created WHIRR-747:
----------------------------------

             Summary: 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


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