[jbosstools-dev] Who uses .target file? Alternative suggestion

Okey, so after reading/hearing about all the concerns I think i might have an answer. Nick/Mistria's concern is that they want to build updatesites easily and claim building it from .target file is too much overhead, but i'm not sure why that is. My guess is the format of the file is problematic or !? But afaik they want to build from feature+site.xml instead. And Denis/Rob/Me would like to have a .target file for various reasons (deterministic, reproducibility and ease of use for target platform in PDE). Thus my suggestion is: 1) feature/site.xml is used for building the TP updatesites AND for creating matching .target file. 2) This .target file gets committed and version into what is today called targetplatform (if multiple target platforms it should be release under different name/versions) Now both sides are happy. Only two concerns I can see right now is: A) #1 above must not result in additional "virtual" features being present in the updatesites - whatever features used to define the TP is purely an implementation detail. Is that doable? B) the feature.xml/site.xml is just an ease of use - the .target file used in #2 is still the thing that should be used for limiting the versions so p2/tycho is deterministic. Makes sense? Complaints/other ideas? /max