[JBoss JIRA] (ARQ-1853) Drop Tomcat 5.5 support
by Ian Brandt (JIRA)
[ https://issues.jboss.org/browse/ARQ-1853?page=com.atlassian.jira.plugin.s... ]
Ian Brandt updated ARQ-1853:
----------------------------
Fix Version/s: tomcat_1.0.0.Final
> Drop Tomcat 5.5 support
> ------------------------
>
> Key: ARQ-1853
> URL: https://issues.jboss.org/browse/ARQ-1853
> Project: Arquillian
> Issue Type: Task
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Reporter: Ian Brandt
> Assignee: Ian Brandt
> Priority: Optional
> Fix For: tomcat_1.0.0.Final
>
>
> I'm working on further DRY'ing up the Tomcat container code, continuing the work done in ARQ-598 and ARQ-600. The Tomcat 5.5 managed container is the only Tomcat 5.5.x container that has been requested or implemented (per ARQ-597), and it's a bit different from the others:
> * Tomcat 5.5.x implements the [the Servlet 2.4 spec|http://tomcat.apache.org/whichversion.html]. The earliest Arquillian protocol is [Servlet 2.5|https://docs.jboss.org/author/display/ARQ/Servlet+2.5]. While the Arquillian Servlet 2.5 protocol has been shown to work with Tomcat 5.5.x, the test archives themselves should really be Servlet 2.4-based, but that introduced a dependency conflict on the Servlet APIs.
> * It's not supported by any version of Weld, which means its injection tests and related dependencies are different from those of every other Tomcat container implementation.
> I'm finding these subtle differences are introducing impediments to sharing test and POM code between this particular container implementation and all the others. With extra effort I'm sure I can achieve some degree of reuse, and otherwise this container could just fork it's own code, but I have to question whether either is worth the trouble? [Tomcat 5.5 was end-of-lifed|http://tomcat.apache.org/tomcat-55-eol.html] two years ago now.
> Short of any strong objections I propose we drop support for this container going forward to better focus on Tomcat 6, 7 and 8. Anyone still using Tomcat 5.5 with Arquillian could continue to do so with [org.jboss.arquillian.container:arquillian-tomcat-managed-5.5:1.0.0.CR7|ht...] or earlier.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (ARQ-1853) Drop Tomcat 5.5 support
by Ian Brandt (JIRA)
[ https://issues.jboss.org/browse/ARQ-1853?page=com.atlassian.jira.plugin.s... ]
Ian Brandt updated ARQ-1853:
----------------------------
Description:
I'm working on further DRY'ing up the Tomcat container code, continuing the work done in ARQ-598 and ARQ-600. The Tomcat 5.5 managed container is the only Tomcat 5.5.x container that has been requested or implemented (per ARQ-597), and it's a bit different from the others:
* Tomcat 5.5.x implements the [the Servlet 2.4 spec|http://tomcat.apache.org/whichversion.html]. The earliest Arquillian protocol is [Servlet 2.5|https://docs.jboss.org/author/display/ARQ/Servlet+2.5]. While the Arquillian Servlet 2.5 protocol has been shown to work with Tomcat 5.5.x, the test archives themselves should really be Servlet 2.4-based, but that introduced a dependency conflict on the Servlet APIs.
* It's not supported by any version of Weld, which means its injection tests and related dependencies are different from those of every other Tomcat container implementation.
I'm finding these subtle differences are introducing impediments to sharing test and POM code between this particular container implementation and all the others. With extra effort I'm sure I can achieve some degree of reuse, and otherwise this container could just fork it's own code, but I have to question whether either is worth the trouble? [Tomcat 5.5 was end-of-lifed|http://tomcat.apache.org/tomcat-55-eol.html] two years ago now.
Short of any strong objections I propose we drop support for this container going forward to better focus on Tomcat 6, 7 and 8. Anyone still using Tomcat 5.5 with Arquillian could continue to do so with [org.jboss.arquillian.container:arquillian-tomcat-managed-5.5:1.0.0.CR7|ht...] or earlier.
was:
I'm making a big push to further DRY up the Tomcat container code, continuing the work done in ARQ-598 and ARQ-600. The Tomcat 5.5 managed container is the only Tomcat 5.5.x container that has been requested or implemented (per ARQ-597), and it's a bit different from the others:
* Tomcat 5.5.x implements the [the Servlet 2.4 spec|http://tomcat.apache.org/whichversion.html]. The earliest Arquillian protocol is [Servlet 2.5|https://docs.jboss.org/author/display/ARQ/Servlet+2.5]. While the Arquillian Servlet 2.5 protocol has been shown to work with Tomcat 5.5.x, the test archives themselves should really be Servlet 2.4-based, but that introduced a dependency conflict on the Servlet APIs.
* It's not supported by any version of Weld, which means its injection tests and related dependencies are different from those of every other Tomcat container implementation.
I'm finding these subtle differences are introducing impediments to sharing test and POM code between this particular container implementation and all the others. With extra effort I'm sure I can achieve some degree of reuse, and otherwise this container could just fork it's own code, but I have to question whether either is worth the trouble? [Tomcat 5.5 was end-of-lifed|http://tomcat.apache.org/tomcat-55-eol.html] two years ago now.
Short of any strong objections I propose we drop support for this container going forward to better focus on Tomcat 6, 7 and 8. Anyone still using Tomcat 5.5 with Arquillian could continue to do so with [org.jboss.arquillian.container:arquillian-tomcat-managed-5.5:1.0.0.CR7|ht...] or earlier.
> Drop Tomcat 5.5 support
> ------------------------
>
> Key: ARQ-1853
> URL: https://issues.jboss.org/browse/ARQ-1853
> Project: Arquillian
> Issue Type: Task
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Reporter: Ian Brandt
> Priority: Optional
>
> I'm working on further DRY'ing up the Tomcat container code, continuing the work done in ARQ-598 and ARQ-600. The Tomcat 5.5 managed container is the only Tomcat 5.5.x container that has been requested or implemented (per ARQ-597), and it's a bit different from the others:
> * Tomcat 5.5.x implements the [the Servlet 2.4 spec|http://tomcat.apache.org/whichversion.html]. The earliest Arquillian protocol is [Servlet 2.5|https://docs.jboss.org/author/display/ARQ/Servlet+2.5]. While the Arquillian Servlet 2.5 protocol has been shown to work with Tomcat 5.5.x, the test archives themselves should really be Servlet 2.4-based, but that introduced a dependency conflict on the Servlet APIs.
> * It's not supported by any version of Weld, which means its injection tests and related dependencies are different from those of every other Tomcat container implementation.
> I'm finding these subtle differences are introducing impediments to sharing test and POM code between this particular container implementation and all the others. With extra effort I'm sure I can achieve some degree of reuse, and otherwise this container could just fork it's own code, but I have to question whether either is worth the trouble? [Tomcat 5.5 was end-of-lifed|http://tomcat.apache.org/tomcat-55-eol.html] two years ago now.
> Short of any strong objections I propose we drop support for this container going forward to better focus on Tomcat 6, 7 and 8. Anyone still using Tomcat 5.5 with Arquillian could continue to do so with [org.jboss.arquillian.container:arquillian-tomcat-managed-5.5:1.0.0.CR7|ht...] or earlier.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (ARQ-1853) Drop Tomcat 5.5 support
by Ian Brandt (JIRA)
[ https://issues.jboss.org/browse/ARQ-1853?page=com.atlassian.jira.plugin.s... ]
Ian Brandt reassigned ARQ-1853:
-------------------------------
Assignee: Ian Brandt
> Drop Tomcat 5.5 support
> ------------------------
>
> Key: ARQ-1853
> URL: https://issues.jboss.org/browse/ARQ-1853
> Project: Arquillian
> Issue Type: Task
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Reporter: Ian Brandt
> Assignee: Ian Brandt
> Priority: Optional
>
> I'm working on further DRY'ing up the Tomcat container code, continuing the work done in ARQ-598 and ARQ-600. The Tomcat 5.5 managed container is the only Tomcat 5.5.x container that has been requested or implemented (per ARQ-597), and it's a bit different from the others:
> * Tomcat 5.5.x implements the [the Servlet 2.4 spec|http://tomcat.apache.org/whichversion.html]. The earliest Arquillian protocol is [Servlet 2.5|https://docs.jboss.org/author/display/ARQ/Servlet+2.5]. While the Arquillian Servlet 2.5 protocol has been shown to work with Tomcat 5.5.x, the test archives themselves should really be Servlet 2.4-based, but that introduced a dependency conflict on the Servlet APIs.
> * It's not supported by any version of Weld, which means its injection tests and related dependencies are different from those of every other Tomcat container implementation.
> I'm finding these subtle differences are introducing impediments to sharing test and POM code between this particular container implementation and all the others. With extra effort I'm sure I can achieve some degree of reuse, and otherwise this container could just fork it's own code, but I have to question whether either is worth the trouble? [Tomcat 5.5 was end-of-lifed|http://tomcat.apache.org/tomcat-55-eol.html] two years ago now.
> Short of any strong objections I propose we drop support for this container going forward to better focus on Tomcat 6, 7 and 8. Anyone still using Tomcat 5.5 with Arquillian could continue to do so with [org.jboss.arquillian.container:arquillian-tomcat-managed-5.5:1.0.0.CR7|ht...] or earlier.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (ARQ-1853) Drop Tomcat 5.5 support
by Ian Brandt (JIRA)
Ian Brandt created ARQ-1853:
-------------------------------
Summary: Drop Tomcat 5.5 support
Key: ARQ-1853
URL: https://issues.jboss.org/browse/ARQ-1853
Project: Arquillian
Issue Type: Task
Components: Tomcat Containers
Affects Versions: tomcat_1.0.0.CR7
Reporter: Ian Brandt
Priority: Optional
I'm making a big push to further DRY up the Tomcat container code, continuing the work done in ARQ-598 and ARQ-600. The Tomcat 5.5 managed container is the only Tomcat 5.5.x container that has been requested or implemented (per ARQ-597), and it's a bit different from the others:
* Tomcat 5.5.x implements the [the Servlet 2.4 spec|http://tomcat.apache.org/whichversion.html]. The earliest Arquillian protocol is [Servlet 2.5|https://docs.jboss.org/author/display/ARQ/Servlet+2.5]. While the Arquillian Servlet 2.5 protocol has been shown to work with Tomcat 5.5.x, the test archives themselves should really be Servlet 2.4-based, but that introduced a dependency conflict on the Servlet APIs.
* It's not supported by any version of Weld, which means its injection tests and related dependencies are different from those of every other Tomcat container implementation.
I'm finding these subtle differences are introducing impediments to sharing test and POM code between this particular container implementation and all the others. With extra effort I'm sure I can achieve some degree of reuse, and otherwise this container could just fork it's own code, but I have to question whether either is worth the trouble? [Tomcat 5.5 was end-of-lifed|http://tomcat.apache.org/tomcat-55-eol.html] two years ago now.
Short of any strong objections I propose we drop support for this container going forward to better focus on Tomcat 6, 7 and 8. Anyone still using Tomcat 5.5 with Arquillian could continue to do so with [org.jboss.arquillian.container:arquillian-tomcat-managed-5.5:1.0.0.CR7|ht...] or earlier.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (ARQ-1789) Add tomcat 8 managed and remote container adapters
by Ian Brandt (JIRA)
[ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.s... ]
Ian Brandt updated ARQ-1789:
----------------------------
Summary: Add tomcat 8 managed and remote container adapters (was: Add tomcat 8 managed and/or remote container adapters)
> Add tomcat 8 managed and remote container adapters
> --------------------------------------------------
>
> Key: ARQ-1789
> URL: https://issues.jboss.org/browse/ARQ-1789
> Project: Arquillian
> Issue Type: Feature Request
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Reporter: Peter Butkovic
> Assignee: Ian Brandt
> Fix For: tomcat_1.0.0.Final
>
>
> I'd like to see managed and/or remote support for tomcat 8 available in arquillian.
> As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (ARQ-1789) Add tomcat 8 managed and/or remote container adapters
by Ian Brandt (JIRA)
[ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.s... ]
Ian Brandt updated ARQ-1789:
----------------------------
Summary: Add tomcat 8 managed and/or remote container adapters (was: add tomcat 8 managed and/or remote container adapters)
> Add tomcat 8 managed and/or remote container adapters
> -----------------------------------------------------
>
> Key: ARQ-1789
> URL: https://issues.jboss.org/browse/ARQ-1789
> Project: Arquillian
> Issue Type: Feature Request
> Components: Tomcat Containers
> Affects Versions: tomcat_1.0.0.CR7
> Reporter: Peter Butkovic
> Assignee: Ian Brandt
> Fix For: tomcat_1.0.0.Final
>
>
> I'd like to see managed and/or remote support for tomcat 8 available in arquillian.
> As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months