Jean-Baptiste, I've checked the servicemix-pom and servicemix-utils artifacts and built the source and those two seem to be OK. Could you add your public key to the http://svn.apache.org/repos/asf/servicemix/KEYS to make it a bit easier to validate the signatures on these artifacts?
However, I don't think we can release components-pom the way it is now. Once it gets released, we should start upgrading components to use that parent pom to pick up the latest servicemix-utils before we release the components. However, that will break the builds because the components would then depend on ServiceMix 3.3.2 for testing purposes and that version hasn't been released yet. We usually stick to the latest previously released version (i.e. 3.3.1) for testing the components while releasing them and then include the new components release in the next version of the container. Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/11/10 Jean-Baptiste Onofré <[email protected]>: > Hi, > > in preparation for the components 2009.02 release, I have staged the > following releases: > - servicemix-pom 4: delete deprecated maven repositories (download.java.net, > jaxb repo, etc) > - servicemix-utils 1.2.0: delete local definition of maven repositories to > use the servicemix-pom 4 one > - components-pom 4: use servicemix-pom 4, servicemix-utils 1.2.0 and > servicemix 3.3.2 (when released). > > When these releases will be accepted, I will upgrade all components to use > these dependencies. > > Staging repository: > https://repository.apache.org/content/repositories/orgapacheservicemix-002/ > > 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 >
