Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352883

Summary:	Update to p2 version to Juno M1
Product:	z_Archived	Reporter:	Tobias Oberlies <t-oberlies>
Component:	Tycho	Assignee:	Project Inbox <tycho-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	igor, kai
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Tobias Oberlies

2011-07-22 11:26:15 EDT

In order to benefit from the investments in p2 M1 (e.g. bug 325622), Tycho needs to update the embedded p2 version. This issue shall make it transparent when this happens.

The general plan is to integrate new p2 milestone versions immediately, and stage a new Tycho release one week after each Juno milestone. Depending on how the work on 0.13.0 progresses, p2 M1 will either be in 0.13.0 or the successor of 0.13.0.

Comment 1 Tobias Oberlies

2011-08-23 09:58:12 EDT

I have updated OSGi runtime to use Juno M1. The versions used directly from the Maven part are not yet updated.

@Igor: Could you please do that? IIRC this requires upload to Maven central, which is easier for you. You can find the right versions when opening tycho-p2-resolver/tycho-bundles-target/eclipse.target with the target editor on the "Content" tab.

Comment 2 Igor Fedorenko

2011-08-25 12:21:53 EDT

Updated equinox and jdt to juno m1. https://github.com/sonatype/sonatype-tycho/commit/048054f214925d79ad376f7ec452893d424d7e19

Comment 3 Kai Kreuzer

2011-08-26 08:22:23 EDT

Since this commit, optional dependencies do not seem to be regarded at compilation time anymore - which breaks existing builds.
Is there any workaround for this to make them again available at build time (besides removing the optional flag)?

Comment 4 Tobias Oberlies

2011-08-30 07:34:02 EDT

(In reply to comment #3)
> Since this commit, optional dependencies do not seem to be regarded at
> compilation time anymore - which breaks existing builds.
> Is there any workaround for this to make them again available at build time
> (besides removing the optional flag)?
This is a known bug, which will unfortunately now become more visible: bug 351842.