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 19:13:55 GMT


Niall Pemberton updated COMMONSSITE-30:

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

Attaching v2 of the patch: COMMONSSITE-30-module-profiles-v3.patch

All seems to work OK now except for the following:
 * The source and test xref's don't get generated for individual components
 * The individual sites don't have their own custom menus at the top - uses the standard commons

So atm its no good for re-generating/deploying all the component sites - but its useful for
cleaning, testing and testing commons-parent pom changes (e.g. upgrading a plugin version
and seeing if it affects any components). So I think this change should be applied - its non-invasive
since its in a separate profile - if you don't activate that profile, then it doesn't affect
anyone. If no-one objects I'll commit this.

> 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-v3.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