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

Bug 314747

Summary:	Generation using plugins has issues...
Product:	[Technology] Tigerstripe	Reporter:	Steve Jerman <sjerman>
Component:	Headless	Assignee:	Project Inbox <tigerstripe.core-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	rcraddoc
Version:	0.5
Target Milestone:	0.5M0
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Steve Jerman

2010-05-27 14:27:43 EDT

Notice the Nulls....

Also the 'name' used for keying the generator ishas the version concatenated into it (rather than using the version attribute. This will cause problems one we start using versioning.

Steve

Tigerstripe Workbench Base Plug-in (Incubation) (v0.5.0.201005240433)
Active Profile: XMP-IM Model Profile 1.40b
Generation project: /EclipseWorkspaces/xmp-customizations/xmp-customizations/base-test-model
[Project: null, Plugin: xmp-validation(0.0.1.qualifier)]
Generation Successful.

[Project: null, Plugin: xmp-pojo-generator(0.0.1.qualifier)]
Generation Successful.

Generation complete. Took 13297 milliseconds.

Comment 1 Richard Craddock

2010-05-28 04:49:22 EDT

Not sure I follow the exact problem here:

Obviously the name should not be null!

Not sure what you mena by "using the version attribute" - is there such athing?

Can you describe what you actually want to see - I could guess .. but...

Comment 2 Steve Jerman

2010-05-30 11:09:14 EDT

I have checked in a fix for the null name (substitute ModelId for name). However, the other issue is more pervasive... 

what I mean is that the name of the plugin has the version appended to it in the tigerstripe.xml file. For example:

pluginId="xmp-palIce-metadata(0.0.1.qualifier)" version="0.0.1.qualifier">

We need to be able to use osgi version ranges .. and not edit the ts.xml everytime we release a plugin.

Comment 3 Steve Jerman

2010-06-22 09:46:10 EDT

Fix works...