[
https://issues.apache.org/jira/browse/GORA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152186#comment-13152186
]
Lewis John McGibbney edited comment on GORA-43 at 11/17/11 6:42 PM:
--------------------------------------------------------------------
OK so I undertook the exercise of seeing what can/could possibly be upgraded by
doing searches on Maven Central. The following outcomes can be interpreted as
artifact id: current version: latest version
avro:1.3.2:1.3.3
hbase:0.90.0:0.90.4
cassandra-all:0.8.1:1.0.2
cassandra-thrift:ditto (by the way do we require this if we are shifting to
Hector client???)
hector-core:0.8.0-1:1.0-1
guava:r09:10.0.1
commons-lang:2.5:2.6
jdom:1.1:1.1.2
sqlbuilder:2.0.6:2.0.10
hsqldb:2.0.0:2.2.4
mysql-connector-java:5.1.13:5.1.18
slf4j-api:1.58:1.6.4
slf4j-simple:ditto
slf4j-jdk14:ditto
log4j:1.2.15:1.2.16
junit:4.6:4.10
commons-logging:1.1.1: at newest, however I don't see this actually being used
anywhere can someone clarify why this is present.
libthrift:0.5.0:0.7.0 however same comment as above
As we all know hadoop can stay at 0.20.2 for the foreseeable future. The
concern I have is with compatibility! This is an area I do not have much
experience and I'm trying to get used to it. Once this is done the ant/ivy can
follow suit fine, I don't have a problem with that.
Further to this, as explained above, I have not looked for any plugins for the
pom.xml or anything similar
Thanks
was (Author: lewismc):
OK so I undertook the exercise of seeing what can/could possibly be
upgraded by doing searches on Maven Central. The following outcomes can be
interpreted as
artifact id: current version: latest version
avro:1.3.2:1.3.3
hbase:0.90.0:0.90.4
cassandra-all:0.8.1:1.0.2
cassandra-thrift:ditto (by the way do we require this if we are shifting to
Hector client???)
hector-core:0.8.0-1:1.0-1
guava:r09:10.0.1
commons-lang:2.5:2.6
jdom:1.1:1.1.2
sqlbuilder:2.0.6:2.0.10
hsqldb:2.0.0:2.2.4
mysql-connector-java:5.1.13:5.1.18
slf4j-api:1.58:1.6.4
slf4j-simple:ditto
slf4j-jdk14:ditto
log4j:1.2.15:1.2.16
junit:4.6:4.10
As we all know hadoop can stay at 0.20.2 for the foreseeable future. The
concern I have is with compatibility! This is an area I do not have much
experience and I'm trying to get used to it. Once this is done the ant/ivy can
follow suit fine, I don't have a problem with that.
Further to this, as explained above, I have not looked for any plugins for the
pom.xml or anything similar
Thanks
> 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
>
>
> 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