You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In its current form, I can define a version in my -generate instruction. As far as I understand the code, this is only taken into account for generators, where a Main method is called.
result = doGenerateMain(pluginName, range, st._attrs(), arguments, stdin, stdout, stderr);
} else {
result = doGeneratePlugin(pluginName, st._attrs(), arguments, stdin, stdout, stderr);
}
For generator plugins, it seems to use the first or last version that is found. In our EMF Codegenerator workspace we want to use baselining. The baseline repo naturally contains the previous version of the codegenerator developed in this workspace. When I set the baseline repo, it always uses the old generator and the tests for the new features fail subsequently.
Thus it would be great to have a possibility to define a version(range) requirement for all types of generators. From my perspective it would be sufficient to use the bundle version. More fine grained on the plugin level would also be fine.
The text was updated successfully, but these errors were encountered:
In its current form, I can define a version in my
-generate
instruction. As far as I understand the code, this is only taken into account for generators, where a Main method is called.bnd/biz.aQute.bndlib/src/aQute/bnd/build/ProjectGenerate.java
Lines 200 to 211 in 5853f25
For generator plugins, it seems to use the first or last version that is found. In our EMF Codegenerator workspace we want to use baselining. The baseline repo naturally contains the previous version of the codegenerator developed in this workspace. When I set the baseline repo, it always uses the old generator and the tests for the new features fail subsequently.
Thus it would be great to have a possibility to define a version(range) requirement for all types of generators. From my perspective it would be sufficient to use the bundle version. More fine grained on the plugin level would also be fine.
The text was updated successfully, but these errors were encountered: