April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-633) TS: Make container JVM --enable-assertions configurable.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-633?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3702 to WFLY-633: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-633 (was: AS7-3702) Component/s: (was: Test Suite) Fix Version/s: (was: 7.1.1.Final) > TS: Make container JVM --enable-assertions configurable. > --------------------------------------------------------- > > Key: WFLY-633 > URL: https://issues.jboss.org/browse/WFLY-633 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Optional > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Arquillian's AS7 container has a property: > {code} > <property name="enableAssertions">false</property> > {code} > And it's true by default. > Let's make it configurable. > {code} > <jvm.args.enableAssertions></jvm.args.enableAssertions> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-632) TS: Check how JDBC drivers are copied

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-632?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3377 to WFLY-632: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-632 (was: AS7-3377) Component/s: (was: Test Suite) Fix Version/s: (was: EAP 6.1.0.Alpha (7.2.0.Final)) > TS: Check how JDBC drivers are copied > ------------------------------------- > > Key: WFLY-632 > URL: https://issues.jboss.org/browse/WFLY-632 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Honza Brázdil > > I created some initial impl, but that copies drivers to deployments/. > The preferred way for TS harness is to create a module, since the other way is easy to do manually in case if interrest. > What's specially needed to check is that the driver and DB config ends up in all instances of multi-node modules (cluster, multinode, etc.). > https://community.jboss.org/wiki/DataSourceConfigurationInAS7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-635) TS: Fix XSLT transformations (namespaces problem)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-635?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3778 to WFLY-635: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-635 (was: AS7-3778) Component/s: (was: Test Suite) Fix Version/s: (was: 7.1.1.Final) > TS: Fix XSLT transformations (namespaces problem) > ------------------------------------------------- > > Key: WFLY-635 > URL: https://issues.jboss.org/browse/WFLY-635 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Original Estimate: 2 days > Remaining Estimate: 2 days > > Applying the standard XSLT copy template, > {code:xml} > <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > xmlns:ds="urn:jboss:domain:datasources:1.0" > xmlns="urn:jboss:domain:1.1" > version="1.0"> > <xsl:template match="@*|node()"> > <xsl:copy> > <xsl:apply-templates select="@*|node()"/> > </xsl:copy> > </xsl:template> > {code} > to the JBoss AS 7 standalone.xml, leads to loss of parameters: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?><server xmlns="urn:jboss:domain:1.1"> > <extensions> > <extension/> > <extension/> > {code} > instead of > {code:xml} > <?xml version="1.0" encoding="UTF-8"?><server xmlns="urn:jboss:domain:1.1"> > <extensions> > <extension module="org.jboss.as.clustering.infinispan"/> > <extension module="org.jboss.as.configadmin"/> > {code} > It's something namespace-related because ds:... attribs ARE copied: > {code:xml} > <subsystem> > <datasources> > <ds:datasource xmlns:ds="urn:jboss:domain:1.1" jndi-name="java:jboss/datasources/ExampleDS" > pool-name="MSQL" > enabled="true" > jta="true" > use-java-context="true"> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-636) TS: parametrize surefire test.redirectTestOutputToFile property

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-636?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3813 to WFLY-636: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-636 (was: AS7-3813) Component/s: (was: Test Suite) Fix Version/s: (was: 7.1.1.Final) > TS: parametrize surefire test.redirectTestOutputToFile property > --------------------------------------------------------------- > > Key: WFLY-636 > URL: https://issues.jboss.org/browse/WFLY-636 > Project: WildFly > Issue Type: Sub-task > Reporter: Dominik Pospisil > Assignee: Ondrej Zizka > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-637) TS: Pass node0, node1 to <ant ...> since inheritAll="true" doesn't work.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-637?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3840 to WFLY-637: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-637 (was: AS7-3840) Component/s: (was: Test Suite) Fix Version/s: (was: 7.1.1.Final) > TS: Pass node0, node1 to <ant ...> since inheritAll="true" doesn't work. > ------------------------------------------------------------------------ > > Key: WFLY-637 > URL: https://issues.jboss.org/browse/WFLY-637 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-628) TS: Way to build with a clean local repo.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-628?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-2997 to WFLY-628: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-628 (was: AS7-2997) Component/s: (was: Test Suite) > TS: Way to build with a clean local repo. > ----------------------------------------- > > Key: WFLY-628 > URL: https://issues.jboss.org/browse/WFLY-628 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > This can be done either by using an empty local repo, setting it in settings.xml, > {code} > <settings> > <localRepository>mvn-repo</localRepository> > ... > {code} > or by using the dependency:purge-local-repository goal in a profile: > {code} > <profile> > <id>cleanRepo.profile</id> > <activation><property><name>cleanRepo</name></property></activation> > <build> > <plugins> > <plugin> > <artifactId>maven-dependency-plugin</artifactId> > <goals><goal>purge-local-repository</goal></goals> > </plugin> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>build-helper-maven-plugin</artifactId> > <version>1.7</version> > <executions> <execution> > <id>remove-old-installers</id> > <goals><goal>remove-project-artifact</goal></goals> > <configuration> <removeAll>true</removeAll> </configuration> > </execution> </executions> > </plugin> > </plugins> > </build> > </profile> > {code} > However first can only be done in settings.xml, and not in a profile, and the later can be done with `mvn dependency:purge-local-repository build-helper:remove-project-artifact -Dbuildhelper.removeAll`. > So it's not to be done in the testsuite itself. Resolving. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-626) TS: Database switch (in datasources)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-626?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-2989 to WFLY-626: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-626 (was: AS7-2989) Component/s: (was: Test Suite) Fix Version/s: (was: 7.1.0.Final) > TS: Database switch (in datasources) > ------------------------------------ > > Key: WFLY-626 > URL: https://issues.jboss.org/browse/WFLY-626 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > This is how Hibernate did it: > https://github.com/hibernate/hibernate-core/blob/3.6/hibernate-parent/pom... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-627) TS: -Djboss.dist=... has no effect, /build/target/jboss-as* is always used

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-627?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-2996 to WFLY-627: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-627 (was: AS7-2996) Component/s: (was: Test Suite) Fix Version/s: (was: 7.1.1.Final) > TS: -Djboss.dist=... has no effect, /build/target/jboss-as* is always used > --------------------------------------------------------------------------- > > Key: WFLY-627 > URL: https://issues.jboss.org/browse/WFLY-627 > Project: WildFly > Issue Type: Sub-task > Reporter: Ivo Studensky > Assignee: Ondrej Zizka > Priority: Critical > Labels: test-dev-blocker > Original Estimate: 1 week, 2 days > Time Spent: 1 week, 3 days > Remaining Estimate: 0 minutes > > Please check the usage of -Djboss.dist parameter provided from the command line. It seems the testsuite does not take it and still uses jboss.dist as defined in testsuite/pom.xml#<properties>. Looks like maven properties are a bit different than system properties, read for example the following: > http://maven.40175.n5.nabble.com/Overriding-properties-from-command-line-... > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-629) TS: Find a way to retain same value of property with ${basedir} in submodules.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-629?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3122 to WFLY-629: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-629 (was: AS7-3122) Component/s: (was: Test Suite) > TS: Find a way to retain same value of property with ${basedir} in submodules. > ------------------------------------------------------------------------------ > > Key: WFLY-629 > URL: https://issues.jboss.org/browse/WFLY-629 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > John Casey: > {quote} > Can you explain exactly how the ${basedir} property will be used? This matters, because expression resolution happens two different ways, once for POM interpolation and again for plugin parameter injection. For more information on the differences, you can play with an expression plugin I built: http://github.com/jdcasey/expression-maven-plugin (see the README for information on using it). > {quote} > We need to refer to ${basedir} for two purposes: > 1) To be able to pass important directories to the tests, for example: > * AS project root dir > * Testsuite root dir (to access global resources) > * Integration testsuite root dir (to access int. ts. resources) > In this case, we need to be able to define the value in parent pom and retain it for sub-modules. > 2) For various operations (plugin executions) which are defined in parent pom, but inherited in sub-modules. > In this case, we really need to have it done using relative paths, e.g. ${basedir}/src/config/arquillian . > In both cases, ${basedir} is used for plugins configuration. > John Casey: > {quote} > I've written a plugin called org.commonjava.maven.plugins:directory-maven-plugin that has goals: > * execution-root = Resolves to the directory where maven was invoked > * directory-of = uses a <project/> configuration with groupId and artifactId to find another project in the current session, and returns its basedir > * highest-basedir = traverses the parent hierarchies of all current projects, up until it finds a parent that has been resolved instead of loaded locally. Then, it sorts these basedir paths and returns the one closest to the filesystem root. If the top two hits (highest results) are not nested within one another, it will fail. > I'd expect you to use something like these to pin down a particular project basedir reference, and inject it consistently into each project in the session. It may be that you actually need something like a combination of the last two, to reference a particular parent project that was loaded from disk (but may not be in the current session per se). If so, that's another easy one to write. > The plugin is here: > http://github.com/jdcasey/directory-maven-plugin > You can take a look at the README.md for more information. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-631) TS: Make commons-lang3, commons-io and commons-codec available in tests.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-631?page=com.atlassian.jira.plugin.s... ] Jason Greene moved AS7-3306 to WFLY-631: ---------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-631 (was: AS7-3306) Affects Version/s: (was: 7.1.0.CR1b) Component/s: (was: Test Suite) > TS: Make commons-lang3, commons-io and commons-codec available in tests. > ------------------------------------------------------------------------ > > Key: WFLY-631 > URL: https://issues.jboss.org/browse/WFLY-631 > Project: WildFly > Issue Type: Sub-task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > To relieve people from writing methods like toHex(), defaultIfNull() and escapeHtml(), > I'd like to add commons-lang3, commons-io and commons-codec. > These are de-facto standard, well tested, mostly thread-safe. > For tests running in server, these would still need to be packaged into the deployment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013