You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Raul Kripalani (JIRA)" <ji...@apache.org> on 2012/12/09 22:21:21 UTC

[jira] [Comment Edited] (SMX4-1257) Release Apache ServiceMix 4.5.0

    [ https://issues.apache.org/jira/browse/SMX4-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527635#comment-13527635 ] 

Raul Kripalani edited comment on SMX4-1257 at 12/9/12 9:20 PM:
---------------------------------------------------------------

Between Camel 2.10.2 and 2.10.3, these third-party libraries have been upgraded:
\\
{code}
-    <ahc-version>1.7.5</ahc-version>
+    <ahc-version>1.7.8</ahc-version>
-    <hawtdispatch-version>1.11</hawtdispatch-version>
+    <hawtdispatch-version>1.12</hawtdispatch-version>
-    <jackson-version>1.9.7</jackson-version>
+    <jackson-version>1.9.10</jackson-version>
-    <leveldbjni-version>1.2</leveldbjni-version>
+    <leveldbjni-version>1.3</leveldbjni-version>
-    <mqtt-client-version>1.2</mqtt-client-version>
+    <mqtt-client-version>1.4</mqtt-client-version>
-    <netty-version>3.5.8.Final</netty-version>
+    <netty-version>3.5.11.Final</netty-version>
-    <pojosr-version>0.1.8</pojosr-version>
+    <pojosr-version>0.2.0</pojosr-version>
-    <xbean-spring-version>3.5</xbean-spring-version>
+    <xbean-spring-version>3.12</xbean-spring-version>
{code}

None of these dependencies overlap with those of the SMX assembly, so that's a good guarantee that Camel 2.10.3 can be a swap-in replacement for Camel 2.10.2 in this release.

Regards,
Raúl.
                
      was (Author: raulvk):
    Between Camel 2.10.2 and 2.10.3, these libraries have been upgraded:

{code}
-    <ahc-version>1.7.5</ahc-version>
+    <ahc-version>1.7.8</ahc-version>
-    <hawtdispatch-version>1.11</hawtdispatch-version>
+    <hawtdispatch-version>1.12</hawtdispatch-version>
-    <jackson-version>1.9.7</jackson-version>
+    <jackson-version>1.9.10</jackson-version>
-    <leveldbjni-version>1.2</leveldbjni-version>
+    <leveldbjni-version>1.3</leveldbjni-version>
-    <mqtt-client-version>1.2</mqtt-client-version>
+    <mqtt-client-version>1.4</mqtt-client-version>
-    <netty-version>3.5.8.Final</netty-version>
+    <netty-version>3.5.11.Final</netty-version>
-    <pojosr-version>0.1.8</pojosr-version>
+    <pojosr-version>0.2.0</pojosr-version>
-    <xbean-spring-version>3.5</xbean-spring-version>
+    <xbean-spring-version>3.12</xbean-spring-version>
{code}

None of these dependencies overlap with those of the SMX assembly, so that's a good guarantee that Camel 2.10.3 can be a swap-in replacement for Camel 2.10.2 in this release.

Regards,
Raúl.
                  
> Release Apache ServiceMix 4.5.0
> -------------------------------
>
>                 Key: SMX4-1257
>                 URL: https://issues.apache.org/jira/browse/SMX4-1257
>             Project: ServiceMix 4
>          Issue Type: Task
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: 4.5.0
>
>
> In order to get Apache ServiceMix 4.5.0 release, we need these new releases (in that order):
> || Subproject || Version || JIRA link || Status ||
> | specs | 2.1.0 | https://issues.apache.org/jira/browse/SMX4/fixforversion/12321273 | in progress |
> | servicemix-utils | 1.6.0 | https://issues.apache.org/jira/browse/SM/fixforversion/12320251 | TODO |
> | components | 2012.01 | https://issues.apache.org/jira/browse/SMXCOMP/fixforversion/12316521 | TODO |
> | nmr | 1.6.0 | https://issues.apache.org/jira/browse/SMX4NMR/fixforversion/12318846 | TODO |
> | features | 4.5.0 | https://issues.apache.org/jira/browse/SMX4/fixforversion/12319159 | TODO |
> | archetypes | 2012.01 | https://issues.apache.org/jira/browse/SM/fixforversion/12319168 | TODO |
> Major dependency versions
> || Dependency || Version || Remarks ||
> | ActiveMQ | 5.7.0 | |
> | Camel | 2.10.3 | |
> | CXF | 2.6.3 | |
> | Karaf | 2.2.9 | |

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira