I thought the startup.poperties is mainly the bootstrap bundles that are
not expected to be changed for custom distros.
Do you think it is really necessary to change the startup.properties for
custom distros? There is still the featuresBoot in features.cfg where
you can specify other features to load. I think the startup.properties
should be as small as possbile as for example you only have the fake
maven lookups at this point not the full features of pax url.
As mentioned in my other mail you can already use flat file names in
startup.properties. So the maven like structure of the system repo is
not mandatory.
Christian
Am 07.05.2012 03:26, schrieb David Jencks:
I hope I don't understand your proposal.... if I do I'm -1 on it.
Right now you can aggregate any number of features from any number of feature
repositories into the startup properties. I've found this useful building
custom assemblies.
To get the equivalent using a features in one or more features repositories you
are either going to have to create a new feature somewhere or provide a way to
load a lot of features from a lot of repositories.
Also, you will be using features in two different ways: as the startup bundles
and as regular features.
I think this is too complicated and confusing.
If you really want to pursue this further I'd also suggest considering
something more like the subsystems spec idea of a feature.
And as I mentioned before I think we should remove the fake mvn urls from
startup.properties and make the system repo flat..... which should simplify the
startup code quite a bit.
thanks
david jencks
On May 6, 2012, at 1:28 PM, Christian Schneider wrote:
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
