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

["Donald Woods (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENJPA-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated OPENJPA-772:
---------------------------------

    Summary: Proper maven pluginManagement and use ianal-maven-plugin for enforcing legal files  (was: Use maven-remote-resources-plugin and ianal-maven-plugin for Legal files and enforcement)

Splitting the original JIRA into 2, as there were several unrelated changes in the original patches, along with a couple of the original changes (like using the apache pom as the parent) already being incorporated into trunk.
This JIRA will focus on:
1) using maven pluginManagement to set common plugin versions in the parent pom, which will make it easier to maintain the child poms
2) adding missing groupId settings for some of the plugins in the poms
3) adding missing versions for some plugins.  where versions were missing, we'll go with the latest released artifacts.  this will help remove build surprises when new levels of plugins are released that include changed APIs or behavior and will make tagged releases easier to rebuild in the future
4) added the ianal plugin to automatically check generated artifacts (jar, war, ear, ...) for inclusion of required license and notice files


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