[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[virgo-dev] Fwd: [Spring JIRA] (SPR-8903) Users of the SpringSource EBR need Spring framework bundles to continue to be published there for Spring 3.2

fyi

Regards,
Glyn

Begin forwarded message:

From: "Glyn Normington (JIRA)" <jira@xxxxxxxxxxxxxxxxxxx>
Subject: [Spring JIRA] (SPR-8903) Users of the SpringSource EBR need Spring framework bundles to continue to be published there for Spring 3.2
Date: 8 December 2011 11:42:13 GMT

Glyn Normington created SPR-8903:
------------------------------------

            Summary: Users of the SpringSource EBR need Spring framework bundles to continue to be published there for Spring 3.2
                Key: SPR-8903
                URL: https://jira.springsource.org/browse/SPR-8903
            Project: Spring Framework
         Issue Type: Story
         Components: Build
   Affects Versions: 3.2 M1
           Reporter: Glyn Normington
           Priority: Critical


The planned implementation of SPR-8116 for Spring 3.2 excludes support for publishing Spring framework bundles to the SpringSource Enterprise Bundle Repository (EBR). The subset of the OSGi community that uses Spring, which includes the communities surrounding the popular Eclipse Virgo and Gemini Blueprint projects, will be impacted if such support is not put in place or some suitable workaround found.

The particular value of publishing Spring framework bundles to the EBR is that the EBR captures those bundles' transitive dependencies on "bundleised" versions of 3rd party libraries such as Hibernate which are present in the EBR. If Spring framework 3.2 bundles are omitted from the EBR, then users will need to resort to educated guesswork to determine the correct "bundleised" transitive dependencies.

The purpose of this JIRA is to track the work to implement or work around the issue, but also to raise awareness of the issue among the user community and to encourage discussion.

Although this feels more like a blocker for the OSGi/Spring community, I have raised it as critical to provide a more balanced view from the perspective of the much larger Spring community.

BTW let's not use this issue to discuss the rationale for switching to Gradle - that's the subject of SPR-8116.

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