Community
Participate
Working Groups
Hi, At present when doing a headless build I get this output: Tigerstripe Workbench Base Plug-in (Incubation) (v0.5.0.201007010319) Active Profile: XMP-IM Model Profile 1.47 Imported xmp-im-connectivity-module into workspace. Generation project: /EclipseWorkspaces/new-build-proper/xmp-im-connectivity-module [Project: xmp-im-connectivity-module, Plugin: xmp-validation(1.0.0), Facet: default] Generation Successful. [Project: xmp-im-connectivity-module, Plugin: XMP Hibernate Mapping Generator(1.0.0), Facet: default] Generation Successful. [Project: xmp-im-connectivity-module, Plugin: xmp-pojo-generator(1.0.0), Facet: default] Generation Successful. [Project: xmp-im-connectivity-module, Plugin: xmp-palIce-metadata(1.0.0), Facet: default] Generation Successful. Generation complete. Took 14851 milliseconds. [INFO] Generation passed! Note that I see the 'real' version of the Tigerstripe workbench, but not the OSGI versions of the plugins or the profile. It would be really good for traceability to see the actual OSGI plugin version in this list. The profile version is coming from a version number in the profile file rather than the plugin version... The plugin versions are better, but still miss off the qualifier number. Steve
The information in the report is correct and useful IMHO, so I thik we just need to augment it. Note that none of these *need* to be in an OSGI plugin, so this additional infor would be optional. Also note that the plugin version is not necessarily the same as the OSGI version number I think this means someting like: Active Profile: XMP-IM Model Profile 1.47 (**osgi plugin **) and [Project: xmp-im-connectivity-module, Plugin: XMP Hibernate Mapping Generator(1.0.0) (**osgi plugin **), Facet: default] Generation Successful. Does that make sense?
Is this information currently available in the plugins? Are you just referring to reporting the version number? Currently the information about a plugin as defined in tigerstripe.xml looks like this: <plugin disableLogging="false" enabled="true" groupId="Cisco System, XMP team" logLevel="3" pluginId="XMP Hibernate Mapping Generator(1.1.1)" version="1.1.1"> Say we changed the version tag to version="[1.1.1,2.0.0)" is this the osgi version you are referring to showing? If that is the case I don't see why we don't just show the version tag in the log all the time. But maybe I am all wrong about what you want/expect. :)
Reporting of the profile version is currently limited to the text content of the version field in the profile file. Reporting the bundle where the profile file was originally located is very problematic, mainly because the location is no longer "accurate" - the profile is actually copied out to a different location, AND the profile does not necessarily contained in a bundle anyway. We need to see if we can work out an acceptable solution. You have mentioned that the text version is not sufficient - can we understand why? Is it not maintained accurately? Looking at actual TS projects, the version there would be the text from the tigerstripe.xml
Created attachment 179466 [details] patch_319290 I was not able to add versioning for the profiles, but have added it for plugins and their owning project. Class Changed: PluginRunStatus
Patch submitted. Thanks!
