Ralph Goers wrote:
So this is one way to get us motivated to get 2.2 out.
Do you think it's still feasible to release 2.2 with only ECM+ and maven build?
Probably trunk already passed 2.2 release point...
Vadim
Jean-Baptiste Quenot schrieb:
* Carsten Ziegeler:
I think we don't need to moch the whole spec but just the
listener. So it's one interface. As soon as we use 2.3 for
compilation we can't ensure
So if I understand correctly, you suggest that I extract
I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep
compatibility with servlet 2.2, by making servlet2.3-requiring
components optional.
WDYT?
--
Jean-Baptiste Quenot
http://caraldi.com/jbq/
Jean-Baptiste Quenot schrieb:
I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep
compatibility with servlet 2.2, by making servlet2.3-requiring
components optional.
You can't check if a component uses 2.3 functionality, so if we just
upgrade we might end up with a not 2.2
Carsten Ziegeler wrote:
Jean-Baptiste Quenot schrieb:
I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep
compatibility with servlet 2.2, by making servlet2.3-requiring
components optional.
You can't check if a component uses 2.3 functionality, so if we just
upgrade
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Jean-Baptiste Quenot schrieb:
I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep
compatibility with servlet 2.2, by making servlet2.3-requiring
components optional.
You can't check if a component uses 2.3
On 25.01.2006 15:37, Sylvain Wallez wrote:
So depending on servlet 2.3 shouldn't be that much of a problem.
But in 2.1 branch what 1. we assume is legacy, 2. we want to assure
compatibility according to our versioning manifesto [1].
Jörg
[1] http://cocoon.apache.org/versioning.html
I'd be in favor of that but you cannot follow our versioning plan and
introduce it in 2.1.9. We'd have to announce our intent first. On the
other hand, we can always override that with a vote.
Carsten Ziegeler wrote:
Servlet 2.3 has been released more than 4 years ago[1]. IMO it is safe
to
Joerg Heinicke wrote:
On 25.01.2006 15:37, Sylvain Wallez wrote:
So depending on servlet 2.3 shouldn't be that much of a problem.
But in 2.1 branch what 1. we assume is legacy, 2. we want to assure
compatibility according to our versioning manifesto [1].
Btw, Cocoon 2.2 is based on
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
So depending on servlet 2.3 shouldn't be that much of a problem.
Yes, that's why I said in an earlier response that we can vote on
upgrading the requirements to servlet 2.3 officially.
Ok, let's vote!
Sylvain
--
Sylvain Wallez
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
So depending on servlet 2.3 shouldn't be that much of a problem.
Yes, that's why I said in an earlier response that we can vote on
upgrading the requirements to servlet 2.3 officially.
Ok, let's vote!
Upayavira wrote:
Sylvain Wallez wrote:
Ok, let's vote!
Why? What does it give us? It _may_ bring an incompatability for some
users, so I'd want to understand what the benefits are.
Personally, I think we should go 2.3 or even 2.4 with Cocoon 2.2, but
stick as we are in 2.1.x. After
Sylvain Wallez schrieb:
Upayavira wrote:
Sylvain Wallez wrote:
Ok, let's vote!
Why? What does it give us? It _may_ bring an incompatability for some
users, so I'd want to understand what the benefits are.
Personally, I think we should go 2.3 or even 2.4 with Cocoon 2.2, but
* Carsten Ziegeler:
Sylvain Wallez schrieb:
Jean-Baptiste can elaborate on this, but AFAIU this is because
an interesting XSP patch requires a servlet listener, which is
something that was added in servlets 2.3.
So, he could just add a mock class for the listener to the xsp
block,
Jean-Baptiste Quenot wrote:
* Carsten Ziegeler:
Sylvain Wallez schrieb:
Jean-Baptiste can elaborate on this, but AFAIU this is because
an interesting XSP patch requires a servlet listener, which is
something that was added in servlets 2.3.
So, he could just add a mock class for the
Upayavira wrote:
Jean-Baptiste Quenot wrote:
* Carsten Ziegeler:
Sylvain Wallez schrieb:
Jean-Baptiste can elaborate on this, but AFAIU this is because
an interesting XSP patch requires a servlet listener, which is
something that was added in servlets 2.3.
So, he
Sylvain Wallez wrote:
Upayavira wrote:
Jean-Baptiste Quenot wrote:
* Carsten Ziegeler:
Sylvain Wallez schrieb:
Jean-Baptiste can elaborate on this, but AFAIU this is because
an interesting XSP patch requires a servlet listener, which is
something that was added in
Upayavira wrote:
Mocking a 4-year old specification. This is s dinosaurish in this
web 2.0 world...
Hmm. If the whole spec is required, I can see where Jean-Baptiste is
coming from. We could extend the build process to use servlet 2.3 for
compilation, but keep the app running with
Upayavira wrote:
Sylvain Wallez wrote:
Upayavira wrote:
Jean-Baptiste Quenot wrote:
* Carsten Ziegeler:
Sylvain Wallez schrieb:
Jean-Baptiste can elaborate on this, but AFAIU this is because
an interesting XSP patch requires a servlet
So this is one way to get us motivated to get 2.2 out.
Carsten Ziegeler said:
I think we don't need to moch the whole spec but just the listener. So
it's
one interface. As soon as we use 2.3 for compilation we can't ensure
that noone else is using 2.3 features.
With the same arguments we
Hello,
To implement a servlet context listener for COCOON-1170, I need to
update servlet_2_2.jar to a newer version in branch 2.1.
Anybody objects to this?
Where do I find the « official » servlet jar?
--
Jean-Baptiste Quenot
http://caraldi.com/jbq/
Jean-Baptiste Quenot wrote:
Hello,
To implement a servlet context listener for COCOON-1170, I need to
update servlet_2_2.jar to a newer version in branch 2.1.
Anybody objects to this?
Where do I find the « official » servlet jar?
You can find version 2.3 in the tools/jetty/lib
* Carsten Ziegeler:
Jean-Baptiste Quenot wrote:
To implement a servlet context listener for COCOON-1170, I
need to update servlet_2_2.jar to a newer version in branch
2.1.
You can find version 2.3 in the tools/jetty/lib directory.
Cocoon 2.1.x is based on version 2.2 of
23 matches
Mail list logo
