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

Bug 367729

Summary:	Version constraint to Virgo Utils prevents independent releases of the Virgo and GW projects
Product:	[RT] Gemini.Web	Reporter:	Borislav Kapukaranov <b.kapukaranov>
Component:	unknown	Assignee:	Violeta Georgieva <milesg78>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	milesg78
Version:	2.0.1.RELEASE
Target Milestone:	2.1.0.M02
Hardware:	All
OS:	All
Whiteboard:

Description Borislav Kapukaranov

2012-01-03 04:22:23 EST

GW has a tight constraint on Virgo's utils version.
If Virgo is released independently without re-building and re-releasing GW it would still include the latest released version of GW. At this point it would have outdated range constraint to Virgo's utils.

This leads to crashes at initial provisioning as p2 is unable to resolve the product. It also can lead to unresolved GW bundles at runtime.

So far we only had joint Virgo and GW releases which hid the problem as both projects were simultaneously updated.

One way to fix that permanently is to agree on a contract to keep Virgo's utils backwards compatible and relief GW on its version constraint. This way it could use any version of the Virgo Utils and thus allow independent releases.

Comment 1 Borislav Kapukaranov

2012-01-03 12:13:42 EST

Note that this would allow relaxing only the runtime dependency of GW to Virgo Utils. 
The build dependency should continue to be updated when releasing GW as it is now.

Comment 2 Violeta Georgieva

2012-01-14 16:51:30 EST

Versions fixed with commit fbba9f3a02c568a927094465cc05e76001eef3b9
Check whether everything is OK and mark the bug as CLOSED.

Regards
Violeta

Comment 3 Violeta Georgieva

2012-02-11 07:38:28 EST

Virgo build is correct now.