[jbosstools-dev] Who uses .target file?

[Max Rydahl Andersen]

>> I would/want to use it if we enable slide planner mode on it so the dependencies becomes *deterministic*. They aren't now.
> If we reverse the current process so:
> 1. we create a "dependency" site with Tycho in the traditional way
> 2. we create a .target file relying on this site
> Then we would simplify the way we handle our 3rd-party dependencies, and provide a target platform that would be usable by PDE at dev-time.

> But I think there is an issue we miss with a .target file, example: Component as depends on component jmx, what .target file do we provide for it? The same target file as we deliver to deltacloud (which depends on as) ?

This problem of the target file or feature files being huge and describing tons of features and then forcing each component to resolve that is a problem in both cases I beleive. 

>> And then I would like to get target files that I can apply in eclipse - but the current one is just too big/slow to work.
> The big/slow issue is IMHO impossible to avoid for our big product.

Not if it was split up in a bit smaller pieces - *alot* of the dependencies are only needed for a few modules.

>> Using an updatesite would not help on that either afaik.
> It won't probably help on performance, but it will help in dependency management.

Don't understand this - having it on an updatesite does not restrict the versions.

Feature's neither since they resolve with version ranges.

target files can be used to *fixate* the version, making it deterministic.

/max