Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333440

Summary:

[Regression] Warning message generated for global rules

Product:

[Technology] Tigerstripe

Reporter:

Navid Mehregani <nmehrega>

Component:

Plugin

Assignee:

Project Inbox <tigerstripe.plugin-inbox>

Status:

VERIFIED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

rcraddoc, yuri

Version:

unspecified

Target Milestone:

0.5M0

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
Projects	none
TS-333440.txt	none
Patch_2	none

Description Navid Mehregani

2011-01-03 15:23:27 EST

Build Identifier: 

This is a regression of bugzilla#324148

Reproducible: Always

Steps to Reproduce:
1. Import the two attached projects (Model project and generator project).
2. Open ts-plugin.xml of MyGenerator
3. Under Overview tab > Select Package and deploy this generator > OK
4. Open tigerstripe.xml of MyProject > Switch to Generator Settings > Enable MyGenerator > Click on 'G' toolbar button to initiate model generation > Notice that a warning message is displayed indicating that none of the rules matched the artifacts under this project.  However, the generator has a global rule defined and the generation is successful.  The warning message should not be displayed

Comment 1 Navid Mehregani

2011-01-03 15:38:05 EST

Created attachment 185971 [details]
Projects

Comment 2 Navid Mehregani

2011-01-04 09:47:06 EST

*** Bug 333470 has been marked as a duplicate of this bug. ***

Comment 3 Valentin Yerastov

2011-01-16 03:57:40 EST

Created attachment 186883 [details]
TS-333440.txt

Fixed.

Comment 4 Yuri Strot

2011-01-17 05:38:15 EST

Valentin's patch applied.

Comment 5 Navid Mehregani

2011-01-17 10:21:03 EST

Reopening issue per our discussion on the call.  The generation dialog's headline still reads 'Warning during generation' even though there are no warnings displayed.

Comment 6 Valentin Yerastov

2011-01-19 10:54:30 EST

Created attachment 187122 [details]
Patch_2

Fixed.

Comment 7 Yuri Strot

2011-01-24 03:49:37 EST

Second patch applied as well.

Comment 8 Navid Mehregani

2011-01-24 12:59:02 EST

Verified. Thanks!