Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[rt-pmc] [CQ 3932] activation-1.1.jar Version: duplication of package (PB CQ1308)

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=3932


Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeff@xxxxxxxxxxxxxxxxx




--- Comment #8 from Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>  2010-04-13 10:33:43 ---
Great discussion. Let me try to distill out the key points
- Virgo has a user base and wants to do a "release" of what is basically the
current code but from Eclipse
- The current shape of that code is that it uses third party bundles from EBR
- To do an Eclipse release we need all third party code to have been reviewed
and approved
- To make a download from Eclipse.org that includes third party code there must
be a CQ that has at least reached the "checkinto CVS" stage.
- We also have a very strong preference for releases being signed by
eclipse.org (can't quite say that it is a rule...)

I don't know what to do about your use of Import-Bundle. It is a step above
Require-Bundle but appears to still suffer from some elements of the packaging
brittleness problem.  I'm not sure what the current Orbit mindset is but:
- having a third party lib that is renamed to a fourth party's name (e.g.,
com.springsource...) and then distributed from Orbit feels off. javax... or
org.eclipse.javax... I could understand.
- Recall as well that for release train participation, projects using the same
third party lib have to agree on the shape and consume it from Orbit. (that is
not saying how the build works, just that the bytes shipped must be the Orbit
bytes)


So, path forward seems to be:
- approve this CQ at least to the checkintoCVS stage so that Virgo can get on
with making downloads available. More would need to be done if a release is
contemplated.
- Virgo to look at the path forward for bundle name independence and
participation in the release train
- Virgo should look at participation in Orbit to make the Orbit bundle
manifests "trusted"

Makes sense?


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.


Back to the top