gbif/motherpom

Definition of <site><url> in motherpom breaks GitHub pages in projects

cgendreau opened this issue · 2 comments

In order to push the JavaDoc to GitHub when we release an artefact we used the following code:

<distributionManagement>
...
    <site>
      <id>gh-pages</id>
      <url>http://gbif.github.io/${project.artifactId}/</url>
    </site>
</distributionManagement>

When used in a project (e.g. gbif-common), the following behaviour will be observed at the 'stage' phase:

maven-site-plugin:3.4:stage
[INFO] Pushing /tmp/gbif-common/target/site
[INFO]    >>> to file:///tmp/gbif-common/target/staging/../gbif-common/gbif-common

For an obscure reason (maybe https://issues.apache.org/jira/browse/MSITE-691), the site plugin will moved the generated JavaDoc outside the "staging" folder.
This will prevent the 'maven-scm-plugin' to find the JavaDocs files and will pushed an empty directory to GitHub pages (http://dev.gbif.org/issues/browse/POR-3043).

Considering Maven team doesn't even use it in their own motherpom I propose we remove it. This implies to rework a little bit the release target.