Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313251 - Name and ModelId are *really* confusing.
Summary: Name and ModelId are *really* confusing.
Status: CLOSED FIXED
Alias: None
Product: Tigerstripe
Classification: Technology
Component: Core (show other bugs)
Version: 0.5   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal with 6 votes (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-17 17:56 EDT by Steve Jerman CLA
Modified: 2012-02-28 09:46 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 Steve Jerman CLA 2010-05-17 17:56:34 EDT 
The introduction of modelId seems to have made the 'name' attribute obsolete in the tigerstripe.xml file. However, there are lots of loose ends:

1) The created project has "" for a name attribute.
2) artifact.getProject().getName() returns ""

Given were we are, I would suggest that getName() should return modelId. It would also be good to remove the XML stuff.
Comment 1 Navid Mehregani CLA 2010-09-09 14:16:17 EDT 
Bug#310049 is another defect that's effected by this.
Comment 2 Navid Mehregani CLA 2010-09-09 14:18:18 EDT 
another related defect: bug#311783
Comment 3 Richard Craddock CLA 2010-11-30 07:27:14 EST 
One problem area was that you cannot specify the modelId in the name of a global rule.

I have updated the Expander to take the following syntax:

${modelId} 

or 

${project.ModelId}

So you can now do this effectively.
Comment 4 Valentin Yerastov CLA 2012-02-27 06:16:35 EST 
Fixed
Comment 5 Navid Mehregani CLA 2012-02-28 09:46:46 EST 
Verified. Thanks!