November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-290) Make src/build.xml work

by Kabir Khan (JIRA)

Make src/build.xml work ----------------------- Key: JBAOP-290 URL: http://jira.jboss.com/jira/browse/JBAOP-290 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 Should be part of the dist and it should be possible to build the full aop/aspects releases and run some of the tests -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
13
0 / 0

[JBoss JIRA] Created: (JBAOP-453) maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath

by Anders Andersen (JIRA)

maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath ---------------------------------------------------------------------------------- Key: JBAOP-453 URL: http://jira.jboss.com/jira/browse/JBAOP-453 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Environment: maven 2 Reporter: Anders Andersen In order to use the plugin I have to add the following dependencies to the client artifact dependency list. <dependency> <groupId>org.jboss.maven.plugins</groupId> <artifactId>maven-jbossaop-plugin</artifactId> <version>1.0-SNAPSHOT</version> </dependency> <dependency> <groupId>jboss</groupId> <artifactId>jboss-aop</artifactId> <version>2.0.0.alpha2</version> </dependency> <dependency> <groupId>jboss</groupId> <artifactId>jboss-common</artifactId> <version>4.0.2</version> </dependency> <dependency> <groupId>concurrent</groupId> <artifactId>concurrent</artifactId> <version>1.3.4</version> </dependency> This is relative wrong, because all maven internal artifacts ends up being nested dependent om the runtime artifact. See lists below. I think the statement cl.addArguments(new String[] { "-cp", createClassPathList(project.getArtifacts())}); is wrong. I tried to include only project.getPluginArtifacts(), but it gave me a NPE So I am not 100% sure what the code solution should be but it is not good to having maven artifacts in the resulting dependency list of the client-artifact list: (resulting depenency list) The ** marked should not be there **/Users/aka/.m2/repository/org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.jar /Users/aka/.m2/repository/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414.jar /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-opends/2.6.1-SNAPSHOT/portal-test-opends-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/isorelax/isorelax/20020414/isorelax-20020414.jar /Users/aka/.m2/repository/jgroups/jgroups-all/2.2.7/jgroups-all-2.2.7.jar /Users/aka/.m2/repository/jboss/jboss-common/4.0.2/jboss-common-4.0.2.jar /Users/aka/.m2/repository/org/jboss/server/jboss-xml-binding/5.0.0.Alpha/jboss-xml-binding-5.0.0.Alpha.jar /Users/aka/.m2/repository/jboss/jboss-cache/1.2.2/jboss-cache-1.2.2.jar /Users/aka/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar /Users/aka/.m2/repository/jboss/jboss-j2se/200504122039/jboss-j2se-200504122039.jar /Users/aka/.m2/repository/jboss/jbossha/4.0.2/jbossha-4.0.2.jar /Users/aka/.m2/repository/jboss/jboss-minimal/4.0.2/jboss-minimal-4.0.2.jar /Users/aka/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar /Users/aka/.m2/repository/org/jboss/server/jboss-common-client/4.0.4.GA/jboss-common-client-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/server/portal-server/2.6.1-SNAPSHOT/portal-server-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/server/jboss-saaj/4.0.4.GA/jboss-saaj-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/server/jboss-system/4.0.4.GA/jboss-system-4.0.4.GA.jar /Users/aka/.m2/repository/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar /Users/aka/.m2/repository/org/jboss/portal/core/portal-core/2.6.1-SNAPSHOT/portal-core-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/jboss/javassist/3.4.ga/javassist-3.4.ga.jar /Users/aka/.m2/repository/org/jboss/portal/test/portal-test/2.6.1-SNAPSHOT/portal-test-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/format/portal-format/2.6.1-SNAPSHOT/portal-format-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.jar /Users/aka/.m2/repository/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar /Users/aka/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar /Users/aka/.m2/repository/jboss/jboss-system/4.0.2/jboss-system-4.0.2.jar /Users/aka/.m2/repository/javax/mail/mail/1.4/mail-1.4.jar /Users/aka/.m2/repository/hibernate/hibernate/3.2.0/hibernate-3.2.0.jar /Users/aka/.m2/repository/jboss/jboss-j2ee/4.0.4.GA/jboss-j2ee-4.0.4.GA.jar /Users/aka/.m2/repository/jaxen/jaxen/1.0-FCS/jaxen-1.0-FCS.jar /Users/aka/.m2/repository/org/jboss/portal/server/portal-server-test-framework/2.6.1-SNAPSHOT/portal-server-test-framework-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.jar **/Users/aka/.m2/repository/org/apache/maven/maven-project/2.0.2/maven-project-2.0.2.jar /Users/aka/.m2/repository/org/jboss/server/jboss-microcontainer/4.0.4.GA/jboss-microcontainer-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/common/portal-common/2.6.1-SNAPSHOT/portal-common-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/selenium/selenium-java-client-driver/0.0/selenium-java-client-driver-0.0.jar /Users/aka/.m2/repository/javax/portlet/portlet-api/1.0/portlet-api-1.0.jar /Users/aka/.m2/repository/org/jboss/portal/theme/portal-theme/2.6.1-SNAPSHOT/portal-theme-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.jar /Users/aka/.m2/repository/saxpath/saxpath/1.0-FCS/saxpath-1.0-FCS.jar /Users/aka/.m2/repository/org/jboss/server/jboss/4.0.4.GA/jboss-4.0.4.GA.jar /Users/aka/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar /Users/aka/.m2/repository/wsdl4j/wsdl4j/1.5.1/wsdl4j-1.5.1.jar /Users/aka/.m2/repository/concurrent/concurrent/1.3.4/concurrent-1.3.4.jar /Users/aka/.m2/repository/jboss/jboss-backport-concurrent/2.1.0.GA/jboss-backport-concurrent-2.1.0.GA.jar /Users/aka/.m2/repository/org/jboss/server/jbosssx/4.0.4.GA/jbosssx-4.0.4.GA.jar /Users/aka/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar /Users/aka/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar /Users/aka/.m2/repository/trove/trove/1.1-beta-5/trove-1.1-beta-5.jar /Users/aka/.m2/repository/jboss/jboss-aop/2.0.0.alpha2/jboss-aop-2.0.0.alpha2.jar **/Users/aka/.m2/repository/org/apache/maven/maven-model/2.0.2/maven-model-2.0.2.jar /Users/aka/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar /Users/aka/.m2/repository/log4j/log4j/1.2.8/log4j-1.2.8.jar /Users/aka/.m2/repository/bsh/bsh/1.3.0/bsh-1.3.0.jar /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet/2.6.1-SNAPSHOT/portal-portlet-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/jboss/jboss-aspect-library/1.5/jboss-aspect-library-1.5.jar /Users/aka/.m2/repository/org/jboss/portal/portlet-server/portal-portlet-server/2.6.1-SNAPSHOT/portal-portlet-server-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/server/jboss-jmx/4.0.4.GA/jboss-jmx-4.0.4.GA.jar /Users/aka/.m2/repository/org/apache/myfaces/myfaces-impl/1.1.1/myfaces-impl-1.1.1.jar /Users/aka/.m2/repository/org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.jar /Users/aka/.m2/repository/jboss/jboss-aop/jboss-aop/1.5.0.GA/jboss-aop-1.5.0.GA.jar /Users/aka/.m2/repository/org/jboss/portal/common/portal-common-junit/2.6.1-SNAPSHOT/portal-common-junit-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar **/Users/aka/.m2/repository/org/apache/maven/maven-profile/2.0.2/maven-profile-2.0.2.jar /Users/aka/.m2/repository/org/visigoths/freemaker/freemarker/2.3.9/freemarker-2.3.9.jar /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-agent/2.6.1-SNAPSHOT/portal-test-agent-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar /Users/aka/.m2/repository/org/jboss/server/jboss-dependency/4.0.4.GA/jboss-dependency-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/portlet-federation/portal-portlet-federation/2.6.1-SNAPSHOT/portal-portlet-federation-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/msv/msv/20020414/msv-20020414.jar /Users/aka/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar /Users/aka/.m2/repository/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar /Users/aka/.m2/repository/slide/webdavlib/2.0/webdavlib-2.0.jar **/Users/aka/.m2/repository/org/jboss/maven/plugins/maven-jbossaop-plugin/1.0-SNAPSHOT/maven-jbossaop-plugin-1.0-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/web/portal-web/2.6.1-SNAPSHOT/portal-web-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/apache/myfaces/myfaces-api/1.1.1/myfaces-api-1.1.1.jar /Users/aka/.m2/repository/org/jboss/portal/wsrp/portal-wsrp-gen/2.6.1-SNAPSHOT/portal-wsrp-gen-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar /Users/aka/.m2/repository/org/jboss/portal/jems/portal-jems/2.6.1-SNAPSHOT/portal-jems-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/registration/portal-registration/2.6.1-SNAPSHOT/portal-registration-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/server/jboss-jaxrpc/4.0.4.GA/jboss-jaxrpc-4.0.4.GA.jar /Users/aka/.m2/repository/org/jboss/portal/security/portal-security/2.6.1-SNAPSHOT/portal-security-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/api/portal-api/2.6.1-SNAPSHOT/portal-api-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/codehaus/cargo/cargo-core-uberjar/0.8/cargo-core-uberjar-0.8.jar /Users/aka/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar /Users/aka/.m2/repository/dom4j/dom4j/1.4/dom4j-1.4.jar /Users/aka/.m2/repository/org/jboss/portal/identity/portal-identity/2.6.1-SNAPSHOT/portal-identity-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/common/explode-common/2.6.1-SNAPSHOT/explode-common-2.6.1-SNAPSHOT.jar /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet-test-framework/2.6.1-SNAPSHOT/portal-portlet-test-framework-2.6.1-SNAPSHOT.jar **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.2/plexus-utils-1.4.2.jar /Users/aka/.m2/repository/jboss/jnpserver/3.2.3/jnpserver-3.2.3.jar /Users/aka/.m2/repository/opends/opends/0.0/opends-0.0.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

5
22
0 / 0

[JBoss JIRA] Created: (JBAS-3815) Deployment Level Principal-Role Mapping passed to authorization layer

by Anil Saldhana (JIRA)

Deployment Level Principal-Role Mapping passed to authorization layer --------------------------------------------------------------------- Key: JBAS-3815 URL: http://jira.jboss.com/jira/browse/JBAS-3815 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta Since the JBoss 4.0.x days, the deployment level rolename to principal set mapping is available in the meta data, but there was no usage of this in the authorization layer. There is a need for this information to be passed to the authorization manager/mapping layer. Affects the ejb3, ejb21 and web layers [jboss.xml,jboss-web.xml and jboss-app.xml] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-3921) Merge JBCLUSTER-150 fixes with 4.0.5.GA tag

by Vivek Lakshmanan (JIRA)

Merge JBCLUSTER-150 fixes with 4.0.5.GA tag ------------------------------------------- Key: JBAS-3921 URL: http://jira.jboss.com/jira/browse/JBAS-3921 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Vivek Lakshmanan Assigned To: Brian Stansberry Fixes from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798 need merging into a branch off the 4.0.5GA tag so they can be picked up by the patch process. No tag needs to be made on this branch as long as the branch's head satisfactorily fixes the JBCLUSTER-150 issues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-3934) Backport JBAS-3460 to Branch_4_2

by Brian Stansberry (JIRA)

Backport JBAS-3460 to Branch_4_2 -------------------------------- Key: JBAS-3934 URL: http://jira.jboss.com/jira/browse/JBAS-3934 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry The additions to jboss-web.xml should be backported. My inclination is not to remove the default snapshot mode/interval config from the Tomcat SAR config though, as 4.2 is not a major release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-162) VFS fails to parse manifest Class-Path correctly

by Scott M Stark (JIRA)

VFS fails to parse manifest Class-Path correctly ------------------------------------------------ Key: JBMICROCONT-162 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-162 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0_CR1 The org.jboss.test.web.test.WebIntegrationUnitTestCase.testWarManifest in jbossas is currently failing due to the vfs failing to parse the war manifest classpath correctly: 2007-03-26 17:45:10,464 DEBUG [org.jboss.deployers.plugins.deployment.MainDeployerImpl] Add deployment context: vfsfile:/home/svn/JBossHead/jboss-head/testsuite/output/lib/manifest-web.ear 2007-03-26 17:45:10,466 DEBUG [org.jboss.virtual.VFSUtils] Manifest Class-Path entry jbosstest-web-util.jar ignored for manifest-web.war reason=java.io.FileNotFoundException: JarHandler@501036129[path= context=file:/home/svn/JBossHead/jboss-head/testsuite/output/lib/manifest-web.ear real=file:/home/svn/JBossHead/jboss-head/testsuite/output/lib/manifest-web.ear] has no child: il.jar 2007-03-26 17:45:10,489 DEBUG [org.jboss.virtual.VFSUtils] Manifest Class-Path entry jbosstest-web-util.jar ignored for manifest-web.war reason=java.io.FileNotFoundException: JarHandler@501036129[path= context=file:/home/svn/JBossHead/jboss-head/testsuite/output/lib/manifest-web.ear real=file:/home/svn/JBossHead/jboss-head/testsuite/output/lib/manifest-web.ear] has no child: il.jar 2007-03-26 17:45:10,489 DEBUG [org.jboss.deployers.plugins.deployment.MainDeployerImpl] Scheduling deployment: vfsfile:/home/svn/JBossHead/jboss-head/testsuite/output/lib/manifest-web.ear -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4378) Update the management CRUD usecases

by Scott M Stark (JIRA)

Update the management CRUD usecases ----------------------------------- Key: JBAS-4378 URL: http://jira.jboss.com/jira/browse/JBAS-4378 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services, Management services Reporter: Scott M Stark Assigned To: Charles Crouch Fix For: JBossAS-5.0.0.Beta3 A container task for the defining the management CRUD usecases for Beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4762) Make distributable webapps depend on the clustering cache

by Brian Stansberry (JIRA)

Make distributable webapps depend on the clustering cache --------------------------------------------------------- Key: JBAS-4762 URL: http://jira.jboss.com/jira/browse/JBAS-4762 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 In 4.x, in the all config the JBossWeb service itself depends on the jboss.cache:service=TomcatClusteringCache mbean. In AS 5 this is not viable, as the relevant bean is the TomcatDeployer, which can't/shouldn't depend on a deploy folder service like the cache. In any case, it's really the <distributable/> webapps that depend on the cache, not the deployer. The TomcatDeployer should be adding a dependency on the cache to deployments where WebMetaData.getDistributable() is true (probably in superclass AbstractWarDeployer.deployWebModule()). A problem with this dependency-based approach is it breaks the current "feature" whereby apps marked <distributable/> can be deployed in the default config. When this is done, the 4.x deployment code detects the absence of the cache and falls back on using the standard non-distributable session manager. That won't work if we introduce a deployment dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-798) Implement quick Client.removeListener() for polled callbacks, part 2

by Ron Sigal (JIRA)

Implement quick Client.removeListener() for polled callbacks, part 2 -------------------------------------------------------------------- Key: JBREM-798 URL: http://jira.jboss.com/jira/browse/JBREM-798 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) This issue is a continuation of JBREM-757. There are two additions: 1. The unit tests org.jboss.test.remoting.transport.http.timeout.HttpQuickDisconnectTestCase and org.jboss.test.remoting.transport.socket.timeout.SocketQuickDisconnectTestCase did not properly test the the quick version of org.jboss.remoting.Client.removeListener() in the case of polled callbacks. 2. The facility should be tested for the RMI transport when per invocation timeouts are implemented for that transport. (See JBREM-701.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-800) Adjust timout values to avoid cruisecontrol failures

by Ron Sigal (JIRA)

Adjust timout values to avoid cruisecontrol failures ---------------------------------------------------- Key: JBREM-800 URL: http://jira.jboss.com/jira/browse/JBREM-800 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) It seems that some tests fail on cruisecontrol because a busy machine causes timout deadlines to be missed. For example, http://cruisecontrol.jboss.com/cc/artifacts/jboss-remoting-testsuite-1.4/... This issue will be an umbrella issue to cover adjusting timeout values. If a test continues to fail despite updated timeout values, it will need a JIRA issue of its own. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
4
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 November 2007