>> About the file we have, I sent some mails a few month ago on
this topic, I'll try to sum it up:
>> * multiple.target: points to the composite target site, good to use inside IDE
with PDE since it also contains source (PDE is greedy and also finds sources from the
composite)
> should really get another name than multiple.
why not:
multiple -> composite
local is replaced by maven mirroring
unified - > aggregated
wether they are composite, aggregated, multiple or unified is rather irrelevant IMO. (its
important for build setup for sure)
Its whats in them that is different - one has source jars, the others dont.
One is for building against, the other is for PDE.
multiple shouldn't actually be used by anyone but PDE users.
or unified should get these added too.
...but the build need to be very clear that the final result does not include the full
target platform since that would now point to unnecessary sources
/max