Re: [epp-dev] Exceptions when starting Neon M4 packages

[Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>]

On 18.12.15 15:52, Markus Knauer wrote:
> I should have been more specific: In both cases I meant your workaround
> A, i.e. adding the annotations bundle to all packages by extending the
> EPP common feature, because that is independent from the Simultaneous
> Release contribution and much easier to accomplish, especially in the
> week before Christmas.
> 
> Disabling / not publishing some packages on the download page is easy
> and that's something that we do all the time during milestones. But the
> EPP p2 repository always contains the metadata of *all* packages and it
> is much harder to remove a few of the packages. If we publish the M4 EPP
> p2 repository everyone gets an update to the new version... and my
> intention was to prevent this from happening.

Thank you for explanation.

With that scheme upgrades from M3 EPP packages to M4 packages would
work, as they would update of the
org.eclipse.epp.package.common.feature, which would pull in
org.eclipse.jdt.annotations.

The only upgrade scenario that would not work is if someone's Eclipse
was not an EPP package (and hence had no
org.eclipse.epp.package.common.feature) *and* did not already include
org.eclipse.jdt.annotations. Then an update using the M4 update site
would update the AERI bundles, but not install the now required
org.eclipse.jdt.annotations. I think this case is rather esoteric.

Best wishes,

Andreas

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940