commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COMMONSSITE-30) Add Module profiles to parent poms
Date Fri, 23 May 2008 06:13:56 GMT

    [ https://issues.apache.org/jira/browse/COMMONSSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599283#action_12599283
] 

Niall Pemberton commented on COMMONSSITE-30:
--------------------------------------------

The checkstyle configuration in component poms was the next problem to cause this to fail
- I've fixed all the components that use checkstyle:
    http://svn.apache.org/viewvc?view=rev&revision=659438

> Add Module profiles to parent poms
> ----------------------------------
>
>                 Key: COMMONSSITE-30
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-30
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Niall Pemberton
>         Attachments: COMMONSSITE-30-module-profiles-v2.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.


Mime
View raw message