Bug 26819 - Migrate existing external tool configs and project builders to launch configs
Summary: Migrate existing external tool configs and project builders to launch configs
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.1   Edit
Hardware: PC All
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Jared Burns CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2002-11-20 17:55 EST by Jared Burns CLA
Modified: 2002-11-22 16:39 EST (History)
0 users

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 Jared Burns CLA 2002-11-20 17:55:05 EST 
External tool configurations and external tool project builders from version
2.0 and 2.1 need to be migrated to launch configurations.

External tool configurations, stored in the metadata as externaltools.xml (2.0)
or .xtools/*.xtool (2.1), can be moved to launch configurations that reside in
the metadata. I believe we can do this essentially at startup.

External tool project builders should be interpreted as configurations at
runtime, and stored as configurations only when they are edited. This should
allow people who want to share a project between users on Eclipse 2.0 and
Eclipse 2.1 to coexist. We should also consider prompting the user before
converting the builders and explaining that they will not be compatible with
older versions of Eclipse if they are edited.
Comment 1 Jared Burns CLA 2002-11-22 16:37:17 EST 
For now, we are electing to only migrate project builders. The data for the
old external tools will be left in the metadata in case we change our minds
in the future.
Comment 2 Jared Burns CLA 2002-11-22 16:39:50 EST 
Won't fix migration of tool configurations.

Bug 26415 deals with migrating project builders.