To make this clear, and allow me to ask a question, let's look at an example
case study, and tell me if this is how it will happen.
A Geronimo User is running G2.2 and want to deploy a G3.0 server side-by-side.
User has a web application with the deployment plan WEB-INF/geronimo-web.xml
To be
Try out juel el implementation
--
Key: GERONIMO-6183
URL: https://issues.apache.org/jira/browse/GERONIMO-6183
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Upgrade PAX Logging
---
Key: GERONIMO-6184
URL: https://issues.apache.org/jira/browse/GERONIMO-6184
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Logging
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
[
https://issues.apache.org/jira/browse/GERONIMO-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13122259#comment-13122259
]
Jarek Gawor commented on GERONIMO-6184:
---
Switched trunk to 1.6.4-SNAPSHOT in
[
https://issues.apache.org/jira/browse/GERONIMO-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-5396.
---
Resolution: Fixed
Fix Version/s: 3.0
The work-around was removed now as part of
2011/10/7 Russell E Glaue rgl...@cait.org
To make this clear, and allow me to ask a question, let's look at an
example
case study, and tell me if this is how it will happen.
A Geronimo User is running G2.2 and want to deploy a G3.0 server
side-by-side.
User has a web application with the
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
