Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341917 - provide help or tools to migrate projects to new Virgo IDE tooling
Summary: provide help or tools to migrate projects to new Virgo IDE tooling
Status: RESOLVED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 368762
  Show dependency tree
 
Reported: 2011-04-05 10:00 EDT by Martin Lippert CLA
Modified: 2012-01-17 12:42 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Lippert CLA 2011-04-05 10:00:32 EDT 
We need to provide some help/tools/guidance for people who would like to migrate their projects from the old dm Server tooling to the new Virgo IDE support.

I don't know at the moment what exactly we can/should do here, but we definitely need to tell people the smoothest migration path that is available then.
Comment 1 Miles Parker CLA 2012-01-16 13:46:45 EST 
Does this cover the issue: http://wiki.eclipse.org/Virgo/Tooling#Migration ?
Comment 2 Glyn Normington CLA 2012-01-17 07:00:06 EST 
(In reply to comment #1)
> Does this cover the issue: http://wiki.eclipse.org/Virgo/Tooling#Migration ?

I would say so, but I haven't gone through the details. Martin?
Comment 3 Martin Lippert CLA 2012-01-17 07:02:37 EST 
(In reply to comment #1)
> Does this cover the issue: http://wiki.eclipse.org/Virgo/Tooling#Migration ?

Yes, exactly! :-)

We made a similar tool for STS to support m2e project migrations, so maybe we could share some code and insights how this was implemented for the SpringSource Tool Suite.
Comment 4 Glyn Normington CLA 2012-01-17 08:34:08 EST 
I *think* Miles's question was whether the existence of the Tooling#Migration wiki page was sufficient to fix this bug. I think it probably is. I can't see that we can justify investing in automation of this migration unless that is pretty straightforward (which it may be).
Comment 5 Miles Parker CLA 2012-01-17 12:42:39 EST 
It does seem to me to be a tremendous amount of work -- and auto migration often causes more trouble than it is worth as there are so many special cases and artifacts to deal with. I'm going to close this; please re-open if people feel that the current solution is not sufficient.