This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 219703 - Add artifact input type
Summary: Add artifact input type
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Jason Losh CLA
QA Contact:
URL: http://wiki.eclipse.org/COSMOS_Use_Ca...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-20 19:09 EST by Mark McCraw CLA
Modified: 2012-01-03 13:53 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 Mark McCraw CLA 2008-02-20 19:09:50 EST 
The functionality of expandable artifact input sets is analogous to the Plugin Development Environment within the eclipse IDE. The process of adding a new artifact type definition can be thought of in the same way as adding an editor in Eclipse.

   1. The end user clicks the Configure menu and selects "Add Artifact Type"
   2. The runtime configuration tool prompts the user for the location of the inspection component (which has a well-defined structure much like an eclipse plugin). The inspection component may be located from the filesystem, a CVS repository, etc. The workflow should mirror the behviour of the Eclipse IDE when you click on "Import" from the file menu or a context menu.
   3. The entries are added to an XML file used to track metadata about artifact types that are known.
Comment 1 Ruth Lee CLA 2009-01-15 12:20:46 EST 
Reassigning to the project lead of Management Enablement for assessment to determine if these should be triaged to someone else or canceled.