> It looks like this dependency is coming from RT packaging, not Saphire:
That makes more sense. All Sapphire dependencies are written very broadly since the Juno release is actually compatible back to Helios. For org.eclipse.core.commands, our sole dependency is written like so: <required namespace='osgi.bundle' name='org.eclipse.core.commands' range='[3.6.0,4.0.0)'/> Thanks, - Konstantin From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Paul Webster Sent: Wednesday, June 13, 2012 7:02 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Status and Outlook for Juno! On Wed, Jun 13, 2012 at 9:45 AM, John Arthorne <john_artho...@ca.ibm.com> wrote: org.eclipse.core.commands 3.6.1.v20120521-2332 It looks like this dependency is coming from RT packaging, not Saphire: org.eclipse.rtp.package.feature.group - RT Package - Eclipse RTP - 1.0.0.v20120606-1022 <required namespace='org.eclipse.equinox.p2.iu' name='org.eclipse.core.commands' range='[3.6.1.v20120521-2332,3.6.1.v20120521-2332]'/> Maybe compiling against 3.8 instead of 4.2? As is, this can't be installed into any EPP packages, but maybe that's not its purpose. PW -- Paul Webster Hi floor. Make me a sammich! - GIR
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
