This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 175137 - Create a way to define an SDK when it is does not match predefined rules
Summary: Create a way to define an SDK when it is does not match predefined rules
Status: CLOSED FIXED
Alias: None
Product: MTJ (Archived)
Classification: Tools
Component: MTJ projects (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Horowitz CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-22 11:17 EST by Kevin Horowitz CLA
Modified: 2008-05-01 19:24 EDT (History)
1 user (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 Kevin Horowitz CLA 2007-02-22 11:17:17 EST 
We need a way for the user to add an SDK when it does not match the rules already supplied by MTJ or other vendors.  This should implement the goals from our Release 2 planning documents  (http://wiki.eclipse.org/index.php/Release_2_Planning#Create_Generic_SDK_Interface)
Comment 1 Kevin Horowitz CLA 2007-02-22 11:25:08 EST 
There is a new Device Provider (org.eclipse.mtj.extension.dpp.usersupplied) that will be called when no other device provider matches.  This will then prompt the user to fill in all the details about the device.

Current implementation does not include the ability to set the security model, or the launch emulator.
Comment 2 Kevin Horowitz CLA 2007-02-22 11:47:07 EST 
A new plug-in org.eclipse.mtj.extension.dpp.usersupplied has been created to provide this functionality.  The code should be in a manner that allows new providers to take parts of the functionality to simply newer device providers.
Comment 3 Gustavo de Paula CLA 2008-05-01 19:24:55 EDT 
closed on mtj 0.7