Community
Participate
Working Groups
This is for consistency with other projects such as jpa and dbaccess. But it would need to be done carefully (and not just prior to any urgent 2.0.1 build that might be necessary). I suggest copying the contents initially so we don't break existing links and then deleting the old content after the links have been fixed. Note that we will also have to update our build scripts to publish Gemini Web builds to the right place. Copying Chris on that front.
Targetting 2.1.0.RELEASE.
Marking as 2.0.1.RELEASE so this shows up in the list of bugs for that release since it does affect that release.
(In reply to comment #0) > Note that we will also have to update our build scripts to publish Gemini Web > builds to the right place. Copying Chris on that front. Do we have changes in the build scripts? Do we have changes in the upload location for the maven artifacts? Thanks Vily
Hi Villy, I remember promising this at the last conference. Please raise a bug and we can figure out what would be best. These things are hard baked in to virgo-build, I'm a little tempted to fork Virgo build in to Gemini.Web. What do you think? Chris.
(In reply to comment #4) > Hi Villy, > > I remember promising this at the last conference. Please raise a bug and we can > figure out what would be best. These things are hard baked in to virgo-build, > I'm a little tempted to fork Virgo build in to Gemini.Web. What do you think? > > Chris. Better to parameterise than fork. We still need to evolve Virgo build across both Virgo and Gemini Web as witnessed by the recent p2 publishing support.