| Summary: | Artifact type of a rule is not correctly applied | ||
|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Navid Mehregani <nmehrega> |
| Component: | Plugin | Assignee: | Navid Mehregani <nmehrega> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | stjerman |
| Version: | unspecified | ||
| Target Milestone: | 0.5M0 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
Fixed. Modified file: ArtifactBasedRuleDetailsPage |
Build Identifier: This defect seems to be a regression. In a plugin descriptor, when you add a new Artifact Rule > Select 'Entity' as Artifact Type > Switch to Source tab, you'll notice that the wrong artifact type has been specified. It incorrectly specifies the IEnumArtifact!! This is the 'rule' element that's generated: <rule description="blah" enabled="true" name="aRule0" type="org.eclipse.tigerstripe.workbench.plugins.IArtifactBasedTemplateRule"> <body artifactFilterClass="" artifactType="org.eclipse.tigerstripe.workbench.model.deprecated_.IEnumArtifact" includeDependencies="true" modelClass="" modelClassName="wrapper" outputFile="${artifact.Name}.out" overwriteFiles="true" suppressFiles="true" template="templates/interface.vm"/> </rule> As a result of this, the plugin doesn't apply its rules properly to the specified artifacts! Reproducible: Always