June 2016 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-498) Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific class

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-498?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-498: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/199 > Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific class > ------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-498 > URL: https://issues.jboss.org/browse/MODCLUSTER-498 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > This has been polluting the API for a while now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-497) ModClusterConfig#setAdvertiseInterface(java.lang.String) should not have been deprecated as it's used by Tomcat modeller

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-497?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-497: -------------------------------------- Description: This may be causing some confusions in JWS. > ModClusterConfig#setAdvertiseInterface(java.lang.String) should not have been deprecated as it's used by Tomcat modeller > ------------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-497 > URL: https://issues.jboss.org/browse/MODCLUSTER-497 > Project: mod_cluster > Issue Type: Bug > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > This may be causing some confusions in JWS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-497) ModClusterConfig#setAdvertiseInterface(java.lang.String) should not have been deprecated as it's used by Tomcat modeller

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-497?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-497: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 > ModClusterConfig#setAdvertiseInterface(java.lang.String) should not have been deprecated as it's used by Tomcat modeller > ------------------------------------------------------------------------------------------------------------------------ > > Key: MODCLUSTER-497 > URL: https://issues.jboss.org/browse/MODCLUSTER-497 > Project: mod_cluster > Issue Type: Bug > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > This may be causing some confusions in JWS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-498) Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific class

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-498?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-498: -------------------------------------- Summary: Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific class (was: Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific object) > Extract Tomcat modeler specific methods from ModClusterConfig into separate Tomcat-specific class > ------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-498 > URL: https://issues.jboss.org/browse/MODCLUSTER-498 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > This has been polluting the API for a while now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-485: -------------------------------------- Labels: CI (was: ci) > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since, taking master into account support for legacy containers has been dropped so now we have: > * jdk7 + 8 and everything in default (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-485: -------------------------------------- Labels: ci (was: CI) > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since, taking master into account support for legacy containers has been dropped so now we have: > * jdk7 + 8 and everything in default (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-485: -------------------------------------- Labels: (was: ci) > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since, taking master into account support for legacy containers has been dropped so now we have: > * jdk7 + 8 and everything in default (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-485: -------------------------------------- Fix Version/s: 2.0.0.Alpha1 > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: ci > Fix For: 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since, taking master into account support for legacy containers has been dropped so now we have: > * jdk7 + 8 and everything in default (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-485: -------------------------------------- Component/s: Core & Container Integration (Java) > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: ci > Fix For: 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since, taking master into account support for legacy containers has been dropped so now we have: > * jdk7 + 8 and everything in default (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-485) Move CI to Travis

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-485?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-485: -------------------------------------- Labels: ci (was: ) > Move CI to Travis > ----------------- > > Key: MODCLUSTER-485 > URL: https://issues.jboss.org/browse/MODCLUSTER-485 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: ci > Fix For: 2.0.0.Alpha1 > > > -I ran into this while adding support for Tomcat 9.- > -What the CI should be testing, give the number of JDKs and different container versions that we support, we should build with respective jdks and versions:- > -jdk6 + mvn verify -PTC6- > -jdk7 + mvn verify -PTC7- > -jdk7 + mvn verify -PAS7- > -jdk8 + mvn verify -PTC8- > -jdk7/8 + mvn verify- > The situation has changed since, taking master into account support for legacy containers has been dropped so now we have: > * jdk7 + 8 and everything in default (excludes Tomcat 9) -> 3 combos on travis > * jdk 8 + Tomcat 9 -> 1 combo on travis > See http://tomcat.apache.org/whichversion.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues June 2016