January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1862) Better reports configuration for JBossUnit maven plugin

by Boleslaw Dawidowicz (JIRA)

Better reports configuration for JBossUnit maven plugin -------------------------------------------------------- Key: JBPORTAL-1862 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1862 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz In JBossUnit maven plugin you can now only configure reports globally. It should be possible to to define it per testsuite the same way as in ant plugin -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1861) With JBossUnit ant plugin in some cases on test error reports are not generated

by Boleslaw Dawidowicz (JIRA)

With JBossUnit ant plugin in some cases on test error reports are not generated ------------------------------------------------------------------------------- Key: JBPORTAL-1861 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1861 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz In some situations when tests doesn't run properly there is no trace for it as even reports are not generated. I don't have any way to reproduce it at the moment and will try to describe it better later. If test framework has problems to bootstrap, build plugins should fail the build. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1860) Optional build fail in JBossUnit maven and ant plugins

by Boleslaw Dawidowicz (JIRA)

Optional build fail in JBossUnit maven and ant plugins ------------------------------------------------------ Key: JBPORTAL-1860 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1860 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz In "the maven way" when test doesn't pass whole build fail. It should be optional to make both JBoss Unit plugins behave the same. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1859) Make JBossUnit maven plugin react on maven.skip.test property

by Boleslaw Dawidowicz (JIRA)

Make JBossUnit maven plugin react on maven.skip.test property ------------------------------------------------------------- Key: JBPORTAL-1859 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1859 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Make JBossUnit maven plugin react on maven.skip.test property to skip test phase same way as surfire does. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2011) Make table auto-creation create SERIAL columns with Postgresql when using auto-increment feature

by Dr. Richard Li (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2011?page=comments#action_12393813 ] Dr. Richard Li commented on JBAS-2011: -------------------------------------- No need to do a patch, you can create the serial field using jbosscmp-jdbc.xml: {code:xml} <entity> <ejb-name>TestObject</ejb-name> <cmp-field> <field-name>pk</field-name> <jdbc-type>BIGINT</jdbc-type> <sql-type>bigserial</sql-type> <auto-increment/> </cmp-field> <entity-command name="postgresql-fetch-seq"/> </entity> {code} > Make table auto-creation create SERIAL columns with Postgresql when using auto-increment feature > ------------------------------------------------------------------------------------------------ > > Key: JBAS-2011 > URL: http://jira.jboss.com/jira/browse/JBAS-2011 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: CMP service > Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final > Environment: FreeBSD, JBoss 4.0.2, Postgresql > Reporter: Jonathan Chen > Priority: Optional > Attachments: patch-serial-autoinc > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > If the auto-increment feature is enabled for Postgresql tables, the tables will not be created with the SERIAL attribute. > A patch to fix this (against 4.0.2, 4.0.3) without invoking post-creation commands is available at: > http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/java/jboss4/files/... > Basically, the patch breaks down the <auto-increment-template> from 1 substitution to 3 substitutions. This allows the field creation for serial fields in Postgresql (and Informix) to be specified in detail. The patch includes corrections for databases to use the extended format. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-207) Intercept direct access to Nodes

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-207?page=all ] Manik Surtani resolved JBCACHE-207. ----------------------------------- Resolution: Done > Intercept direct access to Nodes > -------------------------------- > > Key: JBCACHE-207 > URL: http://jira.jboss.com/jira/browse/JBCACHE-207 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.3 > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.1.0.GA > > > Node.put() currently doesn't pass through an interceptor chain, therefore cache loading, locking, modification recording etc is not provided. > If we want to continue offering navigation via Nodes, we will need to support direct modifications to Nodes. > Idea is to have a (singleton) interceptor chain for *all* nodes and reuse existing interceptors -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-931) Move to JBossAOP rather than hand-wiring interceptor chain for JBoss Cache

by Manik Surtani (JIRA)

Move to JBossAOP rather than hand-wiring interceptor chain for JBoss Cache -------------------------------------------------------------------------- Key: JBCACHE-931 URL: http://jira.jboss.com/jira/browse/JBCACHE-931 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA This should be a seamless change for end-users, and backward compat should be maintained. -- 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

16 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1219) Refactor logic implementation of interceptors

by Manik Surtani (JIRA)

Refactor logic implementation of interceptors --------------------------------------------- Key: JBCACHE-1219 URL: http://jira.jboss.com/jira/browse/JBCACHE-1219 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Mircea Markus Fix For: 2.2.0.GA The current interceptor implementations are pretty messy, unreadable and hard to maintain, with lots of switches and casts from an args array. The goal of this task is to create a SwitchedInterceptor, an abstract class that extends Interceptor, which would perform a switch() and call no-op handlers which can be overridden by subclasses such as the PessimisticLockInterceptor, etc. The benefit is that the implementation interceptors are easier to follow through, read and refactor. Another benefit is that the switched interceptor can take care of extracting method call parameters and pass them to the handlers - making them typed. -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSER-103) JBossObjectInputStream.resolveObject() is not supported

by David Lloyd (JIRA)

JBossObjectInputStream.resolveObject() is not supported ------------------------------------------------------- Key: JBSER-103 URL: http://jira.jboss.com/jira/browse/JBSER-103 Project: JBoss Serialization Issue Type: Feature Request Reporter: David Lloyd Assigned To: Clebert Suconic Priority: Minor JBossObjectInputStream.resolveObject() is not supported on the read side, but JBossObjectOutputStream.replaceObject() is supported. These two methods are often used together. Please add support for resolveObject() on the reading side. -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1339) Debugging: Breakpoints are only considered for code with variables

by Michael Zimmermann (JIRA)

Debugging: Breakpoints are only considered for code with variables ------------------------------------------------------------------ Key: JBRULES-1339 URL: http://jira.jboss.com/jira/browse/JBRULES-1339 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.3 Environment: Linux (Kubunut 7.10), Current Eclipse 3.2.x, Drools 4.0.3 Reporter: Michael Zimmermann In my installation breakpoints in drl files are only recognized if there is any variable involved. Here is a small example 1) Works ok, while debugging the application stops at the breakpoint in System.out.println() rule "TestRule" when eval (1==1) then int i = 1; System.out.println("Breakpoint ok" +i); end 2) The breakpoint in System.out.println() is ignored. The rule fires nevertheless.... rule "TestRule" when eval (1==1) then int i = 1; System.out.println("Breakpoint ignored"); end Tested via the Debug > As > Drools -- 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

16 years, 4 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008