Community
Participate
Working Groups
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.
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.
Versions fixed with commit fbba9f3a02c568a927094465cc05e76001eef3b9 Check whether everything is OK and mark the bug as CLOSED. Regards Violeta
Virgo build is correct now.