| Re: [gemini-dev] Release 2.0.0 of gemini-blueprint |
Hi Dmitry First of all, sorry for the late reply. Indeed, the situation with the availability of the Spring OSGi artifacts is complicated. I had the opportunity to ask Jürgen Höller at GOTO Amsterdam last week regarding the status of Spring’s OSGi support. From his point of view, the Virgo team is responsible for publishing the Spring OSGi artifacts. They were provided with the old conversion templates for this purpose [1]. However, the EBR / Virgo team is partially the same J. I take it the EBR project should incorporate suitable templates, which would be provided by Virgo, and should subsequently be published in a “suitable repository”. Regardless, the artifacts are not there yet. However, the Apache ServiceMix team did great work publishing all Spring artifacts, including the recent releases [2]. How about using those? I haven’t looked at the artifacts yet, but I trust the ServiceMix team did a clean conversion. Kind regards, Olaf [2] http://mvnrepository.com/artifact/org.apache.servicemix.bundles From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Sklyut Olaf, The build is already in publishing SNAPSHOTS to repo.eclipse.org. My main concern about releasing 2.0 is our inability to easily upgrade spring framework related artifacts. Spring EBR is dead. Eclipse EBR is focused only on Eclipse artifacts only (if I understand it’s chapter properly). I have finished upgrading all of the frameworks to R5 compliant releases. Next step is to remove deprecated pieces, like PackageAdmin and support for ancient versions of frameworks. I would like to resolve the spring framework dependency issue prior to releasing of 2.0. What are your thoughts? Kind Regards, -- On June 10, 2014 at 9:54:47 AM, Olaf Otto (olaf@xxxxxxx) wrote:
|