Community
Participate
Working Groups
As part of the work on enhancement https://bugs.eclipse.org/bugs/show_bug.cgi?id=343543 i need to be able to reference them in virgo-build. Below is a list of p2 and the jars it depends on. They are all included in the Equinox SDK so no IP approval is required. Here is the download location where the SDK can be found: http://download.eclipse.org/equinox/drops/S-3.7M7-201104280848/download.php?dropFile=equinox-SDK-3.7M7.zip org.eclipse.ant.core, org.eclipse.core.contenttype, org.eclipse.core.jobs, org.eclipse.core.runtime, org.eclipse.core.runtime.compatibility.registry, org.eclipse.core.variables, org.eclipse.ecf, org.eclipse.ecf.filetransfer, org.eclipse.ecf.identity, org.eclipse.ecf.provider.filetransfer, org.eclipse.ecf.provider.filetransfer.ssl, org.eclipse.ecf.ssl, org.eclipse.equinox.app, org.eclipse.equinox.p2.artifact.repository, org.eclipse.equinox.p2.console, org.eclipse.equinox.p2.core, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.engine, org.eclipse.equinox.p2.garbagecollector, org.eclipse.equinox.p2.jarprocessor, org.eclipse.equinox.p2.metadata, org.eclipse.equinox.p2.metadata.repository, org.eclipse.equinox.p2.publisher, org.eclipse.equinox.p2.repository, org.eclipse.equinox.p2.touchpoint.eclipse, org.eclipse.equinox.p2.touchpoint.natives, org.eclipse.equinox.p2.transport.ecf, org.eclipse.equinox.preferences, org.eclipse.equinox.registry, org.eclipse.equinox.security, org.sat4j.core, org.sat4j.pb The source are also included in the SDK.
The org.sat4j.* bundles do not appear to be from Eclipse. If so, we'll need piggy-back CQs to cover them.
(In reply to comment #0) > As part of the work on enhancement > https://bugs.eclipse.org/bugs/show_bug.cgi?id=343543 i need to be able to > reference them in virgo-build. Please could you clarify whether these dependencies need to be referenced in the virgo-build git repo or whether they need to be downloaded via Ivy in Virgo builds which use virgo-build.
Here are CQs for sat4j: https://dev.eclipse.org/ipzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=sat4j&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Importance&field0-0-0=noop&type0-0-0=noop&value0-0-0= Equinox uses 2.2.0, but since there are many CQs i could not understand which to pick.
It seems there are two 2.2.0 versions to choose from: * 2.2.0 (2010 02 25) * 2.2.0 2010 04 20 Which does Equinox use?
Based on what's packed inside the downloadable Equinox SDK it should be * 2.2.0 2010 04 20
Thanks. Please would you raise a Virgo CQ to piggy-back on CQ 3911. (Use the foundation portal and when you are asked to search for an existing CQ, enter "3911".)
The list specified above is a bit changed, some of the bundles are excluded, but i added some new ones as e.g. the Equinox launcher which is needed for the p2 efforts. The CQ that needs piggy-backing for sat4j is: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5011 and here is the piggy-back CQ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=345966
Created attachment 195756 [details] The org.eclipse.osgi update for EBR
Created attachment 195757 [details] org.sat4j update for EBR
Seems i opened the piggy-back CQ wrong. Here's the new good one: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5175
For the record, the JAR files should not include versions. I am fixing these as I go, so no need to re-upload zips. For example, I renamed: org.sat4j.core_2.3.0.v20110329.jar to: org.sat4j.core.jar and: org.sat4j.core_2.3.0.v20110329-sources.jar to: org.sat4j.core-sources.jar
sat4j published to EBR and committed to EBR at b2d1b8aa62b4249ce36d030aca765fdd3fb0691b
p2 and dependencies (other than sat4j) published to EBR and committed to EBR at 0fb60ec9528ef45709fabccad881777f110820b8
p2 PDE publishing JAR (embedded in p2 publisher bundle) published to EBR and committed to EBR at d18b69fd505b3d1e95381dc1335bafafa5c22d71. This is needed for Java compilation only as the embedded JAR could not be used as part of a normal classpath.
