Jason Dillon wrote:
Ugh... I hope not.
I forget why we needed yoko and non-yoko versions, but if we can avoid
needing more assemblies we should aim for that.
The Yoko code and the Sun ORB code don't comfortably co-exist because of
the requirement that the yoko code be in endorsed.dir. I don't think
we're prepared to just jump into the deep end of the pool with the Yoko
stuff yet, so there will be a period where we'll probably have to
support both versions...at least until we've achieved certification
using the Yoko code.
Rick
--jason
On Sep 13, 2006, at 1:55 AM, Rick McGuire wrote:
Jason Dillon (JIRA) wrote:
[
http://issues.apache.org/jira/browse/GERONIMO-2399?page=comments#action_12434328
] Jason Dillon commented on GERONIMO-2399:
----------------------------------------
Does that mean we have 2x more assemblies too? (hope not)
Me too, since I've already seen it proposed that we'd need yoko and
non-yoko versions of the assemblies too (at least the full j2ee
versions).
Support both jetty 5 and jetty 6
--------------------------------
Key: GERONIMO-2399
URL:
http://issues.apache.org/jira/browse/GERONIMO-2399
Project: Geronimo
Issue Type: New Feature
Security Level: public(Regular issues) Components: Jetty
Affects Versions: 1.2
Reporter: David Jencks
Fix For: 1.2
For a while I think we're going to want to support both jetty 5 and
jetty 6. In order to support this I suggest we rename trunk
geronimo-jetty and geronimo-jetty-builder to geronimo-jetty5 and
geronimo-jetty5-builder and similarly for the configs and rename
the similar modules in sandbox/servlet2.5 geronimo-jetty6 and
geronimo-jetty6-builder. I would like to get the proposed
geronimo-jetty6* modules into trunk as soon as possible: I suggest
the default profile does not build them but we have an additional
profile that does.
I realize there are issues with jee5 schema support that will
require additional work to resolve: I'm planning to look into
this. Jan has obviously made a big start in the servlet2.5 branch.
