[
https://issues.apache.org/jira/browse/GORA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated GORA-43:
-------------------------------------
Attachment: GORA-43-v3.patch
Hopefully this is the final patch attached. It excludes the two rogue plugins
from the org.jdom dependency, these were the ones causing trouble and failing
my local build. In addition I've added the gora-sql test target to the pom.
This can be removed should it be covered in a separate issue.
{code}
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] Apache Gora ........................................... SUCCESS [6.854s]
[INFO] Apache Gora :: Core ................................... SUCCESS
[3:09.720s]
[INFO] Apache Gora :: Hbase .................................. SUCCESS [13.199s]
[INFO] Apache Gora :: Cassandra .............................. SUCCESS [39.622s]
[INFO] Apache Gora :: SQL .................................... SUCCESS [18.727s]
[INFO] Apache Gora :: Tutorial ............................... SUCCESS [6.166s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 34 seconds
[INFO] Finished at: Tue Nov 22 21:37:12 GMT 2011
[INFO] Final Memory: 67M/165M
{code}
> 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-v2.patch, GORA-43-v3.patch, 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