[
https://issues.apache.org/jira/browse/OOZIE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149920#comment-13149920
]
[email protected] commented on OOZIE-601:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2803/
-----------------------------------------------------------
(Updated 2011-11-14 21:06:50.928362)
Review request for oozie.
Changes
-------
And now we have patch :)
Summary
-------
Oozie's POMs should use org.apache.oozie as group.
Excluding the deployment of the distro JAR which is a dummy
This addresses bug OOZIE-601.
https://issues.apache.org/jira/browse/OOZIE-601
Diffs (updated)
-----
/trunk/client/pom.xml 1200686
/trunk/core/pom.xml 1200686
/trunk/distro/pom.xml 1200686
/trunk/docs/pom.xml 1200686
/trunk/examples/pom.xml 1200686
/trunk/minitest/pom.xml 1200686
/trunk/pom.xml 1200686
/trunk/sharelib/pom.xml 1200686
/trunk/webapp/pom.xml 1200686
Diff: https://reviews.apache.org/r/2803/diff
Testing
-------
tested installing them locally 'mvn install -DskipTests' to verify they are
installed in the M2 cache with the right group.
Thanks,
Alejandro
> Oozie's POMs should use org.apache.oozie as group
> -------------------------------------------------
>
> Key: OOZIE-601
> URL: https://issues.apache.org/jira/browse/OOZIE-601
> Project: Oozie
> Issue Type: Bug
> Reporter: Alejandro Abdelnur
>
> Currently they are using com.yahoo.oozie
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
