On 03/14/2012 05:41 PM, Max Rydahl Andersen wrote:

Noone uses it right now since it is not set up as it should be afaik

Good news for us :P

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) ?

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.

Using an updatesite would not help on that either afaik.

It won't probably help on performance, but it will help in dependency management.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets