Community
Participate
Working Groups
It would be useful to support version ranges in .target files. I believe this has 2 parts: * One is allowing version ranges in parser and .target file resolver * The other is about creating some efficient UI.
Are you talking about version ranges when selecting IUs for p2 repo locations?
(In reply to Curtis Windatt from comment #1) > Are you talking about version ranges when selecting IUs for p2 repo > locations? Yes.
Would probably be helpful to list some concrete examples of where this would be helpful. I bet Orbit, right? :) IMHO, the purpose of the .target file is to specify exact versions, to have reproducible builds. So, I hope we don't end up encouraging people to make "loose builds". BUT, I believe even now you can specify "4.5.0" (no qualifier) and it's simply taken as "4.5.0" or higher, So, ... I guess .. if someone is doing that, it would improve reproducibility if they specify [4.5.0...4.5.1) or similar.
(In reply to David Williams from comment #3) > Would probably be helpful to list some concrete examples of where this would > be helpful. I bet Orbit, right? :) > IMHO, the purpose of the .target file is to specify exact versions, to have > reproducible builds. So, I hope we don't end up encouraging people to make > "loose builds". I share your appreciation about fully qualified version in .target making build more predictable and more reproducible, and that's what I'd encourage anyone to use. However, IIRC the reason behing this request (that's not actually mine although I'm reporting it) is that some people find it's too much maintenance for example when moving from a milestone to another and would like to use version ranges, which are a tradeoff between fully qualified version, and a too magic 0.0.0.
This Stack Overflow article refers to an alternative to be used: * [How to avoid the specific feature versions in eclipse target definitions|http://stackoverflow.com/questions/33646330/how-to-avoid-the-specific-feature-versions-in-eclipse-target-definitions] There the [Target Platform Definition DSL and Generator|https://github.com/mbarbero/fr.obeo.releng.targetplatform/] is suggested to be used. Maybe this also provides some ideas to implement it in Eclipse PDE?
