| Summary: | Wrong behaviour when use Facet with stereotype-based Exclusion and profile is not applied | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Maria Kolchinskaja <mshulgina> | ||||
| Component: | Facet | Assignee: | Project Inbox <tigerstripe.facet-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | yuri | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 0.5M0 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Maria Kolchinskaja
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.
Patch applied. Verified |