You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:49:09 UTC
[jira] [Created] (OOZIE-196) GH-225: Remove
groupId/artifactId/version parameterization from POMs
GH-225: Remove groupId/artifactId/version parameterization from POMs
--------------------------------------------------------------------
Key: OOZIE-196
URL: https://issues.apache.org/jira/browse/OOZIE-196
Project: Oozie
Issue Type: Bug
Reporter: Hadoop QA
Currently POMs have groupId/artifactId/version parameterized.
This makes the POMs unusable when deployed as dependency resolution (at POM fetching time) does not resolve properties.
In addition, when using the release manager plugin (which takes care of tagging a release, updating all versions to release values and then creating the SNAPSHOT versions for the next version) properties gets resolved and all the parameterization is gone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OOZIE-196) GH-225: Remove
groupId/artifactId/version parameterization from POMs
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-196.
----------------------------------
Resolution: Fixed
> GH-225: Remove groupId/artifactId/version parameterization from POMs
> --------------------------------------------------------------------
>
> Key: OOZIE-196
> URL: https://issues.apache.org/jira/browse/OOZIE-196
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Currently POMs have groupId/artifactId/version parameterized.
> This makes the POMs unusable when deployed as dependency resolution (at POM fetching time) does not resolve properties.
> In addition, when using the release manager plugin (which takes care of tagging a release, updating all versions to release values and then creating the SNAPSHOT versions for the next version) properties gets resolved and all the parameterization is gone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-196) GH-225: Remove
groupId/artifactId/version parameterization from POMs
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099878#comment-13099878 ]
Hadoop QA commented on OOZIE-196:
---------------------------------
tucu00 remarked:
Closed by 7373b7ea9a282bc1b49dc88711a1cb4a3bedb706 Remove groupId/artifactId/version parameterization from POMs
Removed all parameterization of groupId/artifactId/version.
Added explicit versions for all plugins in pluginManagement section in main POM.
(this is to ensure repetitive builds and to remove some warnings given my Maven3).
Removed all properties propagation for testcases as the used version of Maven &
sure-fire plugins propagate them when running testcases in a forked JVM.
Fixed some exclusions in dependencies and removed some leftover versions in
dependencies, all versions for all dependencies are now in the dependencyManagement
section of the main POM.
Updated ENG_Building twiki.
> GH-225: Remove groupId/artifactId/version parameterization from POMs
> --------------------------------------------------------------------
>
> Key: OOZIE-196
> URL: https://issues.apache.org/jira/browse/OOZIE-196
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Currently POMs have groupId/artifactId/version parameterized.
> This makes the POMs unusable when deployed as dependency resolution (at POM fetching time) does not resolve properties.
> In addition, when using the release manager plugin (which takes care of tagging a release, updating all versions to release values and then creating the SNAPSHOT versions for the next version) properties gets resolved and all the parameterization is gone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira