Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355831 - Move download.eclipse.org/gemini.web to download.eclipse.org/gemini/web
Summary: Move download.eclipse.org/gemini.web to download.eclipse.org/gemini/web
Status: CLOSED FIXED
Alias: None
Product: Gemini.Web
Classification: RT
Component: unknown (show other bugs)
Version: 2.0.0.RELEASE   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.0.1.RELEASE   Edit
Assignee: Glyn Normington CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-25 09:30 EDT by Glyn Normington CLA
Modified: 2011-12-06 04:32 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2011-08-25 09:30:27 EDT
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.
Comment 1 Glyn Normington CLA 2011-08-25 09:35:53 EDT
Targetting 2.1.0.RELEASE.
Comment 2 Glyn Normington CLA 2011-12-05 11:37:28 EST
Marking as 2.0.1.RELEASE so this shows up in the list of bugs for that release since it does affect that release.
Comment 3 Violeta Georgieva CLA 2011-12-05 15:23:08 EST
(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
Comment 4 Chris Frost CLA 2011-12-05 16:53:17 EST
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.
Comment 5 Glyn Normington CLA 2011-12-06 04:32:44 EST
(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.