March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBBUILD-166) Need way to run just one unit test from the build

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-166?page=all ] Paul Gier updated JBBUILD-166: ------------------------------ Affects Version/s: MavenBuild 1.2 Assignee: Paul Gier There are a few ways to run a single test with a maven based build. A single test can be run using the surefire plugin with this command: mvn -Dtest=org.jboss.MyTest test More info here: http://maven.apache.org/plugins/maven-surefire-plugin/howto.html > Need way to run just one unit test from the build > ------------------------------------------------- > > Key: JBBUILD-166 > URL: http://jira.jboss.com/jira/browse/JBBUILD-166 > Project: JBoss Build System > Issue Type: Feature Request > Affects Versions: MavenBuild 1.2 > Reporter: walkerrl > Assigned To: Paul Gier > Priority: Optional > > This issue is concerned with making sure that within the new build system (i.e. maven2), that there is a way for projects, which use the new build system and follow its guidelines, to kick-off unit tests one at a time. The assumption is that the configuration of the correct classpath along with kicking off junit tests placed in a standard directory, should be the responsibility of the build system, since it is an aspect common to building and testing virtually all projects. This issue just deals with adding the requirement of being able to run a single unit-test on a project using the build system. > If this feature is already available within the build system, then usage information is all that is required. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-326) JBossRetro missing getDeclaredAnnotations; getAnnotations implementation is deficient

by David Lloyd (JIRA)

JBossRetro missing getDeclaredAnnotations; getAnnotations implementation is deficient ------------------------------------------------------------------------------------- Key: JBBUILD-326 URL: http://jira.jboss.com/jira/browse/JBBUILD-326 Project: JBoss Build System Issue Type: Bug Components: JBossRetro Affects Versions: JBossRetro-1.0.4.GA Reporter: David Lloyd Priority: Minor Fix For: JBossRetro-1.0.5.GA I put in a fix to JBossRetro to add support for getDeclaredAnnotations on Method, Field, Constructor, and AccessibleObject. In doing this I realized that getAnnotations seems to be doing what getDeclaredAnnotations is supposed to be doing; according to the JDK javadocs, getAnnotations is supposed to return inherited annotations as well as declared annotations, whereas getDeclaredAnnotations only returns annotations on the specific object. I committed a change to implement getDeclaredAnnotations which essentially duplicates the current getAnnotations behavior, but someone may want to go in and enhance getAnnotations. I'm attaching the patch that I committed in case I'm wrong and someone wants to revert it. -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Closed: (JBBUILD-58) Cleanup of Common Module

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-58?page=all ] Paul Gier closed JBBUILD-58. ---------------------------- Resolution: Out of Date > Cleanup of Common Module > ------------------------ > > Key: JBBUILD-58 > URL: http://jira.jboss.com/jira/browse/JBBUILD-58 > Project: JBoss Build System > Issue Type: Task > Reporter: Ryan Campbell > > From Scott: > There is a lot of unused utility classes along with obsolete functionality that is duplicating the jdk 1.4 behavior that I would like to get cleaned up jboss4.0+. Examples of such classes are: > org.jboss.util.Coercible and all of org.jboss.util.coerce > org.jboss.util.DirectoryBuilder > org.jboss.util.MethodHashing > org.jboss.util.Mu* > org.jboss.util.collection.* much of this is now duplicate functionality > org.jboss.net.sockets.RMI* is an unused experiement in multiplexing > org.jboss.net.sockets.Timeout* is now obsolete functionality supported by the JDK sockets > org.jboss.util.property.* is mostly unused > org.jboss.util.stream.* > org.jboss.xml.* should be incorported into the org.jboss.xml.* jbossxb framework at some point > Before proceeding, modify this description with the precise list of classes to remove and get approval from affected developers. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-4) Thirdparty module management

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-4?page=all ] Paul Gier closed JBBUILD-4. --------------------------- Resolution: Out of Date > Thirdparty module management > ---------------------------- > > Key: JBBUILD-4 > URL: http://jira.jboss.com/jira/browse/JBBUILD-4 > Project: JBoss Build System > Issue Type: Bug > Reporter: Scott M Stark > Fix For: JBossBuild-1.1 RC1 > > > The management of the thirdparty jars in terms of duplication, version, licenses needs to be a natural part of the build system. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2299) OutOfMemory error when repetatively deploying and undeploying with 10 minute interval

by Kenny MacLeod (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2299?page=comments#action_12356366 ] Kenny MacLeod commented on JBAS-2299: ------------------------------------- The relevent issues on the ASF JIRA would appear to be: http://issues.apache.org/jira/browse/BEANUTILS-59 http://issues.apache.org/jira/browse/BEANUTILS-156 One is marked as fix for 1.8.0, the other as "later than 1.8.0". Not promising :-( > OutOfMemory error when repetatively deploying and undeploying with 10 minute interval > ------------------------------------------------------------------------------------- > > Key: JBAS-2299 > URL: http://jira.jboss.com/jira/browse/JBAS-2299 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3RC2 > Environment: WinXP SP2, JBoss 4.0.3RC2, JDK 1.4.2_07 > Reporter: Amar Syed > Assigned To: Clebert Suconic > Fix For: JBossAS-4.2.1.CR1 > > Attachments: Data.txt, SampleApp.ear > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Using a manual copy and delete mechanism with the server\default\deploy folder the sample ear (attached) caused an outofmemory error eventually after 90 repetitions. > The min and max heap settings were configured as : -Xms128m -Xmx512m > The time delay after dropping/deploying the ear at each repetition was set to 10 minutes after which the ear is deleted/undeployed followed by a 10 second sleep till the next deploy cycle. > I find this behaviour strange because http://jira.jboss.com/jira/browse/JBAS-1319 is supposed to have fixed this issue. > The lines from the server.log surrounding the java.lang.OutOfMemoryError are as follows: > 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null > 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@e51e50, cl=org.jboss.mx.loading.UnifiedClassLoader3@c90207{ url=null ,addedOrder=0} > 2005-09-24 06:04:33,057 ERROR [org.apache.commons.digester.Digester] Begin event threw error > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] StandardWrapper.Throwable > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] Servlet /XMPVXE0Partion/VXE1_ContentTestService threw load() exception > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,072 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null > The following two jars were added to the server\default\lib folder. > commons-validator.jar --- version 1.1.3 > struts.jar ---- version 1.2.4 -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-915) Clustered SFSB cache should not preload from the cache loader

by Brian Stansberry (JIRA)

Clustered SFSB cache should not preload from the cache loader ------------------------------------------------------------- Key: EJBTHREE-915 URL: http://jira.jboss.com/jira/browse/EJBTHREE-915 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.0 CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 4.2.0 CR2 Preloading the cache is causing conflicts with region activation, since the preload happens before the region is activated (and thus pollutes the in memory cache, causing the activation to fail.) In any case, preloading doesn't make sense for the SFSB cache; any state on disk would be passivated sessions that had been in use on another node; they are only useful in memory if the client fails over. No point aggressively bringing them into memory. Fix is to remove the <preload>/</preload> element from the ejb3-clustered-sfsbcache-service.xml file. An open question is why there are nodes to be preloaded. StatefulTreeCache.stop() should be causing them to be deleted, and starting the cache shouldn't be bringing over any state transfer. Perhaps some file lock is preventing the node deletion? -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-735) Package config save to parser and provide error reports, and cache

by Michael Neale (JIRA)

Package config save to parser and provide error reports, and cache ------------------------------------------------------------------ Key: JBRULES-735 URL: http://jira.jboss.com/jira/browse/JBRULES-735 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBBUILD-271) EJB3x pom

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-271?page=comments#action_12356321 ] Carlo de Wolf commented on JBBUILD-271: --------------------------------------- The ejb3x classes have been moved to javaee project ejb-api module. The remaining ejb-api classes from the old j2ee module have been merged. > EJB3x pom > --------- > > Key: JBBUILD-271 > URL: http://jira.jboss.com/jira/browse/JBBUILD-271 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Carlo de Wolf > Fix For: MavenBuild 2.0 > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBBUILD-274) J2EE pom

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-274?page=comments#action_12356320 ] Carlo de Wolf commented on JBBUILD-274: --------------------------------------- There is a new project 'javaee' to contain all the JavaEE API classes. > J2EE pom > -------- > > Key: JBBUILD-274 > URL: http://jira.jboss.com/jira/browse/JBBUILD-274 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: MavenBuild 2.0 > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-841) Only allow classes which implement Pool in PoolClass annotation

by Carlo de Wolf (JIRA)

Only allow classes which implement Pool in PoolClass annotation --------------------------------------------------------------- Key: EJBTHREE-841 URL: http://jira.jboss.com/jira/browse/EJBTHREE-841 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Minor Fix For: EJB 3.0 RC10 - FD -- 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

19 years, 3 months

2
3
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 March 2007