This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 338992 - Wrong behaviour when use Facet with stereotype-based Exclusion and profile is not applied
Summary: Wrong behaviour when use Facet with stereotype-based Exclusion and profile is...
Status: CLOSED FIXED
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Facet (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-05 00:45 EST by Maria Kolchinskaja CLA
Modified: 2011-04-06 00:08 EDT (History)
1 user (show)

See Also:

Attachments
338992 patch (1.48 KB, patch)
2011-04-01 00:51 EDT, Anton Salnik CLA 		no flags Details | Diff
View All 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 Maria Kolchinskaja CLA 2011-03-05 00:45:09 EST 
Build Identifier: 

1. Create a Tigerstripe Project with datatype artifact.
2. Create profile.
3. Create stereotype datatype_stereo for datatype artifact.
4. Create Contract Facet
5. Apply profile.
6. Open datatype artifact. Add datatype_stereo stereotype. Save changes.
7. Add stereotype to stereotype-based Exclusion Facet.
8. Reset profile to default. 
9. Open datatype artifact to verify that 'datatype_stereo' stereotype marked as 'Undefined'.
10. Create Generator project and set 'use facet'
11. Generate project with active facet.

Result:
1. Project is generated using stereotype-based Exclusion. But the profile is not active and the stereotype is undefined.
2. Open 'Scope' tab on Facet. Click 'Add' button for stereotype-based Exclusion. Dialog is emplty, but error is displayed:
Unknown stereotype 'datatype_stereo'. Ignoring
An exception stack trace is not available.


Reproducible: Always
Comment 1 Anton Salnik CLA 2011-04-01 00:51:40 EDT 
Created attachment 192335 [details]
338992 patch

1. From my point of view the behaviour is correct. If stereotype configuration isn't available (profile with the stereotype isn't active) you can't edit the stereotype definition for an artifact. But since stereotypes definition consist of name and attributes they are available for generators.
2. Exception logging removed.
Comment 2 Yuri Strot CLA 2011-04-04 05:03:34 EDT 
Patch applied.
Comment 3 Maria Kolchinskaja CLA 2011-04-06 00:08:58 EDT 
Verified