I have noticed one issue with the servicemix-common sources jar that we had trouble with earlier. The md5 and sha1 no longer match the artifact (they probably match the original, before we added the gpg sigs). So I am thinking we probably need a new release with the permanent fix to get that artifact signed properly.
Chris -- Chris Custine FUSESource :: http://fusesource.com My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Felix :: http://felix.apache.org Apache Directory Server :: http://directory.apache.org On Thu, Mar 11, 2010 at 1:52 PM, Jean-Baptiste Onofré < [email protected]> wrote: > Hi, > > Finally after an issue on Nexus (need to restart Nexus server), an issue on > servicemix-eip (I raise a Jira task about this and release process cleanup > in general) and finally a signing issue on servicemix-common (comment added > to the same Jira task), the components 2010.01 release is on stage !! Thanks > a lot to Gert and Chris for the help. > > We solved 26 issues in this release: > >> SMXCOMP-34 CxfSeEndpoint totally ignored service="..." and >> enpoint="..." attributes >> SMXCOMP-161 running servicemix-http unit tests stalls intermittently >> SMXCOMP-683 In ServiceMix 4, the use of <cxfse:proxy/> is far from >> easy because the injection of a ComponentContext SMXCOMP-687 We need >> create a endpoint which delegate the endpoint lifecycle to the camel context >> SMXCOMP-688 servicemix-cxf-bc endpoint cannot load busCfg file when >> packaged as an OSGi bundle >> SMXCOMP-694 Build fails on AIX - activemq.port1 environment variable >> not available in tests >> SMXCOMP-695 WSNComponentTest intermitently fail or hang on slow >> machine >> SMXCOMP-696 namespace missing of the message used for >> CxfBcProviderAddressingTest >> SMXCOMP-697 add delegateToJaas so that we can disable endpoint >> delegate to JAASAuthenticationService to do the authentication if necessary >> SMXCOMP-699 JMS component doesn't recognize the jca-consumer endpoint >> SMXCOMP-700 Upgrade to CXF 2.1.9/2.2.6 >> SMXCOMP-702 New JMS Provider endpoint should allow per message >> setting of JMSPriority or JMSTimeToLive >> SMXCOMP-703 Servicemix CXF-BC component JbiJAASInterceptor should >> catch UndeclaredThrowableException >> SMXCOMP-705 Upgrade to commons-pool 1.5.4 >> SMXCOMP-706 Poor interceptor chain management and memory leak in >> CxfBc >> SMXCOMP-709 cxf-bc doesn't need to conver to InputStream >> SMXCOMP-711 JBIJAASInterceptor incorrectly positioned in interceptor >> chain when WS-SP support enabled >> SMXCOMP-712 CXF-BC Consumer / Provider can't accept generic >> properties in configurtion options. >> SMXCOMP-713 Threading problem in Servicemix-HTTP which renders the >> component unusable. >> SMXCOMP-715 Properties of NormalizedMessage can be lost >> SMXCOMP-716 Upgrade to Camel 2.2.0 >> SMXCOMP-717 Http Provider Endpoint does not handle Jetty exchange >> expiration (Read timeout). >> SMXCOMP-718 Improper handling of exchange if there is no out message >> in exchange. >> SMXCOMP-720 Enable validation when no namespace information is >> present in the XML >> SMXCOMP-721 update xmlschema version to 1.4.5 >> > > Staging repository: > https://repository.apache.org/content/repositories/orgapacheservicemix-005/ > > After release TODO: > Update archetypes > Prepare ServiceMix 3.3.2-SNAPSHOT, NMR 1.1.0-SNAPSHOT and features > 4.1.0-SNAPSHOT to use this components release. > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > > Thanks, > Regards > JB > >
