[
https://issues.apache.org/jira/browse/GORA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152304#comment-13152304
]
Chris A. Mattmann commented on GORA-43:
---------------------------------------
Lewis, great work. You nailed down the major differences. It's interesting that
we're failing on 2 maven plugins that aren't available in Central that seem to
be referenced from JDOM and JAXEN. One thing that we might do is an exclusion
of org.jdom in the gora-hbase dependencies which seems to drive
both plugin incompatibilities. WDYT?
If exclusion fixes it, then my +1 to simply commit your forward port to trunk
and then call this sucker done. Thoughts?
> Forward port 0.1.1 incubating Maven poms to trunk
> -------------------------------------------------
>
> Key: GORA-43
> URL: https://issues.apache.org/jira/browse/GORA-43
> Project: Gora
> Issue Type: Improvement
> Components: build process
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.2-incubating
>
> Attachments: GORA-43.patch
>
>
> I improved the Maven poms in 0.1.1-incubating, and trimmed them down to a
> publishable set of dependencies.
> My improvements:
> 1. reduce the redundancy in the deps section by not repeating deps in each
> sub-project.
> 2. use explicit dependency and module version #s which are required to not
> have "moving target" dependencies in the downstream applications and that
> allow each individual gora-* module to be included on its own (without having
> to include gora-core).
> I'd like to forward port these to trunk and then update per trunk's
> dependencies.
--
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
