first of all - nice work with the plugin. This plugin has been very useful to build my own plugin from the Workbench without diving into all the PDE details (most of which are focused on headless builds, which I don't want to do yet). Also looking at the svn for this plugin I finally got the right pointers to correctly set up my source features.
However I had the problem that during the build the version number for my feature was not updated - it always stayed at 0.0.0
After a few hours of head scratching and trying a million things I took a look at the customTargets.xml and on the second reading I found the little note, that the feature version is only replaced, if it ends with a ">" in the plugin.xml.
For whatever reason my feature had provider-name as the last attribute in the <feature> element, so the version number did not end with a > and was not replaced.
Why I see the reason for doing the "dirty trick", it could be documented more prominently to save others from the frustating experience.
brgds
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
first of all - nice work with the plugin. This plugin has been very useful to build my own plugin from the Workbench without diving into all the PDE details (most of which are focused on headless builds, which I don't want to do yet). Also looking at the svn for this plugin I finally got the right pointers to correctly set up my source features.
However I had the problem that during the build the version number for my feature was not updated - it always stayed at 0.0.0
After a few hours of head scratching and trying a million things I took a look at the customTargets.xml and on the second reading I found the little note, that the feature version is only replaced, if it ends with a ">" in the plugin.xml.
For whatever reason my feature had provider-name as the last attribute in the <feature> element, so the version number did not end with a > and was not replaced.
Why I see the reason for doing the "dirty trick", it could be documented more prominently to save others from the frustating experience.
brgds
Thomas
Sorry for that crude hack. The version replacement is now done more flexible with replaceregexp.