You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2009/01/29 19:43:59 UTC

[jira] Commented: (OPENJPA-772) Proper maven pluginManagement and use ianal-maven-plugin for enforcing legal files

    [ https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668549#action_12668549 ] 

David Jencks commented on OPENJPA-772:
--------------------------------------

Michael --

The maven-remote-resources plugin basically gets the LICENSE and NOTICE files from a common location ("resource-bundle").  You can add more stuff to particular (sub) projects easily.

The ianal plugin checks that the maven-remote-resources plugin did its job :-) and that there actually are LICENSE and NOTICE files in all the generated artifacts including source and javadoc jars.  It seems to be pretty easy to misconfigure the m-r-r-p so that source and/or javadoc jars are missing the legal goo and the ianal plugin really cuts down on the number of release attempts you need to make as you gradually discovery these by looking at each one manually :-)


> Proper maven pluginManagement and use ianal-maven-plugin for enforcing legal files
> ----------------------------------------------------------------------------------
>
>                 Key: OPENJPA-772
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-772
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: build / infrastructure
>    Affects Versions: 2.0.0
>            Reporter: David Jencks
>            Assignee: Donald Woods
>             Fix For: 2.0.0
>
>         Attachments: OPENJPA-772-2.patch, OPENJPA-772-branches12x.patch, OPENJPA-772-trunk.patch, OPENJPA-772.patch
>
>
> Its fairly standard in apache projects to use the apache pom as the parent.  Among other things it specifies the apache snapshot repo as one of the repositories which will be needed until the 2.0 spec jar is finalized.

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