Re: [january-dev] Our builds have all died with a p2 January error

[Matthew Webber <matthew@xxxxxxxxxxxxxx>]

That's definitely the way to proceed. There is no need to specify the version required number both in the p2 repo URL, and then again redundantly as a version dependency.

I believe they are now building against the release version 1.0.0, so it works with the current hard-coded version values, but that breaks next release.

On 15 November 2016 at 13:47, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

Hi Matt,

In your target file you have referenced a specific version of the
bundle. As you are pointing at continuous builds, the qualifier keeps
changing as improvements arrive:
https://github.com/eclipse/dawnsci/blob/master/org.eclipse.dawnsci.targetplatform/org.eclipse.dawnsci.targetplatform.target#L48

You can use "lazy" versions so it always picks up the most recent for
a specfic p2 repo:
I wrote an SO answer to show how:
http://stackoverflow.com/questions/33646330/how-to-avoid-the-specific-feature-versions-in-eclipse-target-definitions
(key is that target editor does not allow you to do it in the GUI)

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com