[
https://issues.apache.org/jira/browse/AVRO-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey updated AVRO-771:
-----------------------------
Description:
This is not a blocker.
This is the 'mvn versions:display-dependency-updates'
The following dependencies in Dependency Management are using the newest
version:
[INFO] net.sf.jopt-simple:jopt-simple ................................... 3.2
[INFO] org.apache.hadoop:hadoop-core ................................. 0.20.2
[INFO]
[INFO] The following dependencies in Dependency Management have newer versions:
[INFO] com.thoughtworks.paranamer:paranamer ................ 2.3 -> 2.3-debug
[INFO] org.apache.velocity:velocity ...................... 1.6.4 -> 1.7-beta1
[INFO] org.codehaus.jackson:jackson-mapper-asl ............... 1.4.2 -> 1.7.3
[INFO] org.jboss.netty:netty ..................... 3.2.1.Final -> 3.2.4.Final
[INFO] org.mortbay.jetty:jetty ............................. 6.1.22 -> 6.1.26
[INFO]
[INFO] The following dependencies in Dependencies have newer versions:
[INFO] junit:junit ........................................... 4.8.1 -> 4.8.2
[INFO] org.slf4j:slf4j-api .................................. 1.5.11 -> 1.6.1
[INFO] org.slf4j:slf4j-simple ............................... 1.5.11 -> 1.6.1
We should consider a newer Jackson version, at least the latest 1.4.x, but
perhaps higher.
Junit is a trivial upgrade.
slf4j has some changes affecting compatibility (but is API compatible) in
1.6.x. We may want to delay that one.
Jetty and Netty can be upgraded.
The most important one above is Jackson since it is the most likely to have
classpath collisions. Even though we do not use features from newer versions,
it might be wise to move to that.
For plugins, there are these updates:
[INFO] The following plugin updates are available:
[INFO] maven-surefire-plugin ................................ 2.7.1 -> 2.7.2
[INFO] org.codehaus.mojo:exec-maven-plugin ...................... 1.1 -> 1.2
Both of which seem minor by their release notes.
(see mvn versions:help for more useful tools)
was:
This is not a blocker.
This is the 'mvn versions:display-dependency-updates'
The following dependencies in Dependency Management are using the newest
version:
[INFO] net.sf.jopt-simple:jopt-simple ................................... 3.2
[INFO] org.apache.hadoop:hadoop-core ................................. 0.20.2
[INFO]
[INFO] The following dependencies in Dependency Management have newer versions:
[INFO] com.thoughtworks.paranamer:paranamer ................ 2.3 -> 2.3-debug
[INFO] org.apache.velocity:velocity ...................... 1.6.4 -> 1.7-beta1
[INFO] org.codehaus.jackson:jackson-mapper-asl ............... 1.4.2 -> 1.7.3
[INFO] org.jboss.netty:netty ..................... 3.2.1.Final -> 3.2.4.Final
[INFO] org.mortbay.jetty:jetty ............................. 6.1.22 -> 6.1.26
[INFO]
[INFO] The following dependencies in Dependencies have newer versions:
[INFO] junit:junit ........................................... 4.8.1 -> 4.8.2
[INFO] org.slf4j:slf4j-api .................................. 1.5.11 -> 1.6.1
[INFO] org.slf4j:slf4j-simple ............................... 1.5.11 -> 1.6.1
We should consider a newer Jackson version, at least the latest 1.4.x, but
perhaps higher.
Junit is a trivial upgrade.
slf4j has some changes affecting compatibility (but is API compatible) in
1.6.x. We may want to delay that one.
Jetty and Netty can be upgraded.
The most important one above is Jackson since it is the most likely to have
classpath collisions. Even though we do not use features from newer versions,
it might be wise to move to that.
For plugins, there are these updates:
[INFO] The following plugin updates are available:
[INFO] maven-surefire-plugin ................................ 2.7.1 -> 2.7.2
[INFO] org.codehaus.mojo:exec-maven-plugin ...................... 1.1 -> 1.2
Both of which seem minor by their release notes.
(see mvn versions:help for more useful tools)
Fix Version/s: 1.5.0
> Java: Upgrade dependencies for 1.5.0
> ------------------------------------
>
> Key: AVRO-771
> URL: https://issues.apache.org/jira/browse/AVRO-771
> Project: Avro
> Issue Type: Improvement
> Reporter: Scott Carey
> Fix For: 1.5.0
>
>
> This is not a blocker.
> This is the 'mvn versions:display-dependency-updates'
> The following dependencies in Dependency Management are using the newest
> version:
> [INFO] net.sf.jopt-simple:jopt-simple ...................................
> 3.2
> [INFO] org.apache.hadoop:hadoop-core .................................
> 0.20.2
> [INFO]
> [INFO] The following dependencies in Dependency Management have newer
> versions:
> [INFO] com.thoughtworks.paranamer:paranamer ................ 2.3 ->
> 2.3-debug
> [INFO] org.apache.velocity:velocity ...................... 1.6.4 ->
> 1.7-beta1
> [INFO] org.codehaus.jackson:jackson-mapper-asl ............... 1.4.2 ->
> 1.7.3
> [INFO] org.jboss.netty:netty ..................... 3.2.1.Final ->
> 3.2.4.Final
> [INFO] org.mortbay.jetty:jetty ............................. 6.1.22 ->
> 6.1.26
> [INFO]
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] junit:junit ........................................... 4.8.1 ->
> 4.8.2
> [INFO] org.slf4j:slf4j-api .................................. 1.5.11 ->
> 1.6.1
> [INFO] org.slf4j:slf4j-simple ............................... 1.5.11 ->
> 1.6.1
> We should consider a newer Jackson version, at least the latest 1.4.x, but
> perhaps higher.
> Junit is a trivial upgrade.
> slf4j has some changes affecting compatibility (but is API compatible) in
> 1.6.x. We may want to delay that one.
> Jetty and Netty can be upgraded.
> The most important one above is Jackson since it is the most likely to have
> classpath collisions. Even though we do not use features from newer
> versions, it might be wise to move to that.
> For plugins, there are these updates:
> [INFO] The following plugin updates are available:
> [INFO] maven-surefire-plugin ................................ 2.7.1 -> 2.7.2
> [INFO] org.codehaus.mojo:exec-maven-plugin ...................... 1.1 -> 1.2
> Both of which seem minor by their release notes.
> (see mvn versions:help for more useful tools)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
