September 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1851) Update Selenium to 2.43.0

by Pavol Pitonak (JIRA)

Pavol Pitonak created ARQ-1851: ---------------------------------- Summary: Update Selenium to 2.43.0 Key: ARQ-1851 URL: https://issues.jboss.org/browse/ARQ-1851 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Affects Versions: drone_1.3.1.Final Reporter: Pavol Pitonak Update to latest Selenium - 2.43.0 supporting new versions of browsers, e.g. Firefox 31 ESR -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1850) Setup static analysis/reporting options for Arquillian projects

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1850?page=com.atlassian.jira.plugin.s... ] Ian Brandt updated ARQ-1850: ---------------------------- Assignee: Aslak Knutsen > Setup static analysis/reporting options for Arquillian projects > --------------------------------------------------------------- > > Key: ARQ-1850 > URL: https://issues.jboss.org/browse/ARQ-1850 > Project: Arquillian > Issue Type: Feature Request > Components: Build Infrastructure > Reporter: Ian Brandt > Assignee: Aslak Knutsen > > It would be nice to add static analysis and reporting options to the current build infrastructure. There is already CI support via CloudBees [DEV@Cloud service|https://arquillian.ci.cloudbees.com/]. They also offer an integrated [Sonar as a service|https://developer.cloudbees.com/bin/view/DEV/Sonar] option that Arquillian modules could leverage. Also if the builds published the Maven Sites that would allow for [further reporting|http://www.sonarqube.org/maven-site-sonar-or-both-of-them/]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1850) Setup static analysis/reporting options for Arquillian projects

by Ian Brandt (JIRA)

Ian Brandt created ARQ-1850: ------------------------------- Summary: Setup static analysis/reporting options for Arquillian projects Key: ARQ-1850 URL: https://issues.jboss.org/browse/ARQ-1850 Project: Arquillian Issue Type: Feature Request Components: Build Infrastructure Reporter: Ian Brandt It would be nice to add static analysis and reporting options to the current build infrastructure. There is already CI support via CloudBees [DEV@Cloud service|https://arquillian.ci.cloudbees.com/]. They also offer an integrated [Sonar as a service|https://developer.cloudbees.com/bin/view/DEV/Sonar] option that Arquillian modules could leverage. Also if the builds published the Maven Sites that would allow for [further reporting|http://www.sonarqube.org/maven-site-sonar-or-both-of-them/]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.s... ] Ian Brandt updated ARQ-1847: ---------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: tomcat_1.0.0.Final Resolution: Done Added some basic unit tests and merged: https://github.com/arquillian/arquillian-container-tomcat/commit/4dc65d10... > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1849) GlassFish container already boostrapped

by Razvan Petre (JIRA)

Razvan Petre created ARQ-1849: --------------------------------- Summary: GlassFish container already boostrapped Key: ARQ-1849 URL: https://issues.jboss.org/browse/ARQ-1849 Project: Arquillian Issue Type: Bug Components: Configuration Affects Versions: 1.1.5.Final Reporter: Razvan Petre after upgrading from 1.1.3.Final to 1.1.5.Final, was not able to run all the test in Eclipse... any ideas? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.s... ] Stephen Coy updated ARQ-1847: ----------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/27 > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1848) Tomcat managed containers should start and stop Tomcat using the standard run scripts

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-1848?page=com.atlassian.jira.plugin.s... ] Stephen Coy commented on ARQ-1848: ---------------------------------- Normally I don't like calling scripts that invoke java from a java program. However there is some merit in this approach in this instance. I do feel that it should wait until post 1.0.0.Final though. The whole tomcat-container codebase is due for some substantial refactoring just to get rid of code duplication. > Tomcat managed containers should start and stop Tomcat using the standard run scripts > ------------------------------------------------------------------------------------- > > Key: ARQ-1848 > URL: https://issues.jboss.org/browse/ARQ-1848 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > The [standard Tomcat run scripts|http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt] contain a fair little bit of logic and features: > * Multiple instance support (requiring the proper merging of resources from {{CATALINA_BASE}} and {{CATALINA_HOME}}). > * Logging configuration. > * Running with or without a security manager. > * Support for configuration in the 'setenv' script. > * Endorsed and temp directory configuration. > * Launching with JPDA related configuration. > * OS variant and TTY related configuration on UNIX. > By building the Java command to launch Tomcat directly the current {{CommonTomcatManagedContainer}} forgoes the standard implementation of all this. There is a growing history of bug reports and feature requests that suggest this may not be the best approach: > * ARQ-628 - Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > * ARQ-866 - Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > * ARQ-1650 - Managed container bypasses tomcat jul setup > * ARQ-1843 - Tomcat managed container ignores javaHome configuration > * ARQ-1846 - Support configuration of the Tomcat system classpath from managed containers > * ARQ-1847 - Support specifying JMX RMI server port > Rather than reinventing the wheel here, we should just launch and stop Tomcat with the standard run script for the current OS, exposing it's environment variable-driven configuration via arquillian.xml and the {{CommonTomcatManagedConfiguration}}. This will: > * Add all the missing features and logic. > * Be simpler and presumably cheaper to maintain over trying to mirror the standard scripts. > * Encourage better fidelity between managed containers and their production counterparts (e.g. identical {{CATALINA_BASE}} and {{CATALINA_HOME}} merging, as well as setenv script support). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1848) Tomcat managed containers should start and stop Tomcat using the standard run scripts

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1848?page=com.atlassian.jira.plugin.s... ] Ian Brandt commented on ARQ-1848: --------------------------------- Given that we're on CR7, and this will entail a significant change to the arquillian.xml options for the Tomcat managed containers, I'm going to code this on a branch for review and discussion. I believe this is something that we should do before declaring the managed containers 1.0.0.Final, but others may feel differently. > Tomcat managed containers should start and stop Tomcat using the standard run scripts > ------------------------------------------------------------------------------------- > > Key: ARQ-1848 > URL: https://issues.jboss.org/browse/ARQ-1848 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > The [standard Tomcat run scripts|http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt] contain a fair little bit of logic and features: > * Multiple instance support (requiring the proper merging of resources from {{CATALINA_BASE}} and {{CATALINA_HOME}}). > * Logging configuration. > * Running with or without a security manager. > * Support for configuration in the 'setenv' script. > * Endorsed and temp directory configuration. > * Launching with JPDA related configuration. > * OS variant and TTY related configuration on UNIX. > By building the Java command to launch Tomcat directly the current {{CommonTomcatManagedContainer}} forgoes the standard implementation of all this. There is a growing history of bug reports and feature requests that suggest this may not be the best approach: > * ARQ-628 - Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > * ARQ-866 - Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > * ARQ-1650 - Managed container bypasses tomcat jul setup > * ARQ-1843 - Tomcat managed container ignores javaHome configuration > * ARQ-1846 - Support configuration of the Tomcat system classpath from managed containers > * ARQ-1847 - Support specifying JMX RMI server port > Rather than reinventing the wheel here, we should just launch and stop Tomcat with the standard run script for the current OS, exposing it's environment variable-driven configuration via arquillian.xml and the {{CommonTomcatManagedConfiguration}}. This will: > * Add all the missing features and logic. > * Be simpler and presumably cheaper to maintain over trying to mirror the standard scripts. > * Encourage better fidelity between managed containers and their production counterparts (e.g. identical {{CATALINA_BASE}} and {{CATALINA_HOME}} merging, as well as setenv script support). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1846) Support configuration of the Tomcat system classpath from managed containers

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1846?page=com.atlassian.jira.plugin.s... ] Ian Brandt commented on ARQ-1846: --------------------------------- This would be made obsolete by ARQ-1848. > Support configuration of the Tomcat system classpath from managed containers > ---------------------------------------------------------------------------- > > Key: ARQ-1846 > URL: https://issues.jboss.org/browse/ARQ-1846 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > In some rare cases, such as customization of Tomcat's internal logging, it may prove useful to augment or change the [system classpath used to start Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html]. Currently the managed containers hard code the Tomcat default configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1846) Support configuration of the Tomcat system classpath from managed containers

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1846?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1846 stopped by Ian Brandt. --------------------------------------- > Support configuration of the Tomcat system classpath from managed containers > ---------------------------------------------------------------------------- > > Key: ARQ-1846 > URL: https://issues.jboss.org/browse/ARQ-1846 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > In some rare cases, such as customization of Tomcat's internal logging, it may prove useful to augment or change the [system classpath used to start Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html]. Currently the managed containers hard code the Tomcat default configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2014