Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318327 - Java Workflow Tooling (JWT) Move
Summary: Java Workflow Tooling (JWT) Move
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Servers (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-29 09:59 EDT by Christian Saad CLA
Modified: 2010-07-19 10:30 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Saad CLA 2010-06-29 09:59:50 EDT
The move review for the JWT project was successfully completed some time ago, but we decided to postpone the move until after Helios, so now we're finally ready to go ;)

JWT was accepted to move from the Technology TLP to SOA TLP, which affects the following items:

* The CVS repository technology/org.eclipse.jwt including all contained subfolders should go to soa/org.eclipse.jwt. We would prefer SVN over CVS, so if it would be possible to combine the move with a migration to SVN (while keeping the v* tags) that would be perfect!

* Meta data: Please change technology.jwt to soa.jwt

* news://news.eclipse.org/eclipse.technology.jwt should go to news://news.eclipse.org/eclipse.jwt

* We plan to move our update sites from download.eclipse.org/technology/jwt/* download.eclipse.org/soa/jwt/* but currently don't have write permissions for that folder

* Committer rights don't change

Thanks,
Chris
Comment 1 Christian Saad CLA 2010-06-29 12:35:51 EDT
Sorry, I forgot to mention the Bugzilla entries which of course also should be classified as part of SOA TLP.
Comment 2 Eclipse Webmaster CLA 2010-07-02 13:49:32 EDT
I can combine the move with a transition to SVN, but while the import tooling does it's best, there is the potential for some loses(see documentation here: http://cvs2svn.tigris.org/cvs2svn.html ) .  Something else to be aware of is that by default we only allow SVN access over svn+ssh.  When we're ready to go I'll do a test import and put the repository up for you to confirm that everything is as you'd expect.

I'd also like to move your downloads and update sites to /jwt instead of /soa/jwt to be consistent with our 'new' project layouts.  

As I can't rename newsgroups, I'll close the old one and create eclipse.jwt . 

When is a good time to do this?

-M.
Comment 3 Christian Saad CLA 2010-07-05 04:44:39 EDT
> When we're ready to go I'll do a test import and put the repository up for you
> to confirm that everything is as you'd expect.

That would be great, thanks!

> I'd also like to move your downloads and update sites to /jwt instead of
> /soa/jwt to be consistent with our 'new' project layouts.  

Ok

> As I can't rename newsgroups, I'll close the old one and create eclipse.jwt . 

Ok

> When is a good time to do this?

I'll inform the committers that the codebase is freezed until the move is completed, so any time from now on
Comment 4 Sharon Corbett CLA 2010-07-05 09:24:02 EDT
Hi Christian;

As part of an approved move, the IP team must check all committer legal paperwork to ensure there are no barriers to prevent any of the committers from moving to the new TLP project.  This check has now been completed and all committers can be moved to soa.jwt.

I've adjusted the soa.jwt database record to active in order that I can arrange to move all JWT IPzilla CQs to soa.jwt.  As I have to wait a short period of time for that change to populate in our systems, I should be able to perform the CQ moves tomorrow.

Regards,
Sharon
Comment 5 Eclipse Webmaster CLA 2010-07-05 14:37:27 EDT
I've put the initial import here: http://dev.eclipse.org/svnroot/soa/org.eclipse.jwt/ .  It's read only but can you confirm it has everything you expect?

-M.
Comment 6 Christian Saad CLA 2010-07-06 07:58:27 EDT
(In reply to comment #5)
> I've put the initial import here:
> http://dev.eclipse.org/svnroot/soa/org.eclipse.jwt/ .  It's read only but can
> you confirm it has everything you expect?
> 
> -M.

I've downloaded all projects and everything seems fine!
Comment 7 Sharon Corbett CLA 2010-07-06 09:12:17 EDT
IPzilla CQs have been moved.

Over to Webmaster to move Committers.

Regards,
Sharon
Comment 8 Eclipse Webmaster CLA 2010-07-06 10:52:16 EDT
Ok, I've set the SVN repo as read/write, updated the meta-data, moved the downloads/archive areas and the committers.  As the newsgroup changes occurred last night I think we're almost done here.

All that remains is for the project to update it's download/update/archive links and that should be it.

-M.
Comment 9 Christian Saad CLA 2010-07-13 06:00:50 EDT
Unfortunately, currently I'm always getting

Authentication error.
svn: MKACTIVITY of '/svnroot/soa/org.eclipse.jwt/!svn/act/b87b3ccb-2901-0010-af61-076f5e895d66': 403 Forbidden (http://dev.eclipse.org)

when trying to do a commit.
Comment 10 Eclipse Webmaster CLA 2010-07-13 09:26:22 EDT
It looks like you're trying to commit via HTTP, which provides read-only access.   By default we only enable svn+ssh access for commits.

-M.
Comment 11 Christian Saad CLA 2010-07-15 09:42:48 EDT
Thanks, seems I forgot to change the protocol setting.

Now we just need to get the Hudson build to work :)
Comment 12 Christian Saad CLA 2010-07-19 09:07:12 EDT
Just a small point: I noticed that we're not listed in the online source code browsing tool (http://dev.eclipse.org/viewcvs/index.cgi/). Would it be possible to add an entry for JWT?
Comment 13 Eclipse Webmaster CLA 2010-07-19 10:30:39 EDT
Done.

-M.