commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <>
Subject [jira] Updated: (COMMONSSITE-30) Add Module profiles to parent poms
Date Fri, 23 May 2008 05:55:55 GMT


Niall Pemberton updated COMMONSSITE-30:

    Attachment: COMMONSSITE-30-module-profiles-v2.patch

The JavaDoc problems can be fixed by upgrading to the latest maven-javadoc-plugin and setting
aggregate to false.

Attaching a revised patch for commons-parent:
   * COMMONSSITE-30-module-profiles-v2.patch

We have a couple of multi-moduie projects (JCI and VFS from memory) - so would probably need
to configure the maven-javadoc-plugin with aggregate set to true in their component poms.

> Add Module profiles to parent poms
> ----------------------------------
>                 Key: COMMONSSITE-30
>                 URL:
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Niall Pemberton
>         Attachments: COMMONSSITE-30-module-profiles-v2.patch, COMMONSSITE-30-module-profiles.patch
> Seeing the felix project's pom with different modules in profiles made me think this
might be useful for commons  - with "trunks-proper" or "trunks-sandbox".
> I tried it out, but running mvn -Ptrunks-proper site failed bizarely:
>  * on commons-io it objected to JDK 1.5 features saying the source option was 1.3 - so
it seemed to be using the commons-parent default, rather than the individual property setting
for projects
>  * on lang though it objected to enum - so seemed to ignore those settings.
> Perhaps someone else knows how to get it working properly - at the least its useful for
cleaning up all the modules.

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

View raw message