Hmm, if we remove the default-environment, will some mport-packages be used
in those builders ? And is it allowed to define dependencies in the
deployment plans ? If not, it looks to me that there are many things are
required to considered. As now, many functions depend on the dependency
tree.
David,
I think these additional jar added to startup.properties are not
always present. For example, when starting the framework assembly
(which used to start without any errors) I see the following errors
(although the server still starts up ok):
Artifact
In the past, we have a plugin named jee-specs, which contains all the
dependencies for those spec APIs, I am thinking that whether we could have
one in Geronimo 3.0. So that, the EARConfigBuilder could adds it as the
defaultEnvironment, with this, we might have less issues for those
applications
Jarek,
I was under the impression that this commit was entirely reverted after a few
days when it produced a lot of instability. I didn't check though. I don't
see any reason any of these bundles you mention should be in startup.properties.
Ivan,
In my local code that is more osgi oriented
