August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-462) Verify the validity of the artifacts generated by the new build

by Ovidiu Feodorov (JIRA)

Verify the validity of the artifacts generated by the new build --------------------------------------------------------------- Key: JBMESSAGING-462 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-462 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 Make sure the jboss-messaging.jar manifest is correctly generated, and also the version of a new built server is correctly reported. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-463) Completely get rid of commented out jboss.aspects.lib references build-messaging.xml

by Ovidiu Feodorov (JIRA)

Completely get rid of commented out jboss.aspects.lib references build-messaging.xml ------------------------------------------------------------------------------------ Key: JBMESSAGING-463 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-463 Project: JBoss Messaging Issue Type: Sub-task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.Alpha1 -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3461) Resolve the failures in the ClusteredSSO unit tests

by Brian Stansberry (JIRA)

Resolve the failures in the ClusteredSSO unit tests --------------------------------------------------- Key: JBAS-3461 URL: http://jira.jboss.com/jira/browse/JBAS-3461 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-4.0.5.CR1 -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-464) log4j output format differs from the CVS version

by Ovidiu Feodorov (JIRA)

log4j output format differs from the CVS version ------------------------------------------------ Key: JBMESSAGING-464 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-464 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.Alpha1 The log4j output for tests doesn't seem to be what it was before: [junit] main 18:50:46,984 INFO [ServerSessionEndpoint] Received message:JBossMessage[256]:PERSISTENT. It is most likely due to not including the right log4j in the tests.execution.classpath. Ivestigate this. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-475) Old build-related tasks

by Ovidiu Feodorov (JIRA)

Old build-related tasks ----------------------- Key: JBMESSAGING-475 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-475 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-175) Unnecessary junit.timeout2 used by tests/build.xml

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-175?page=all ] Ovidiu Feodorov closed JBMESSAGING-175. --------------------------------------- Resolution: Done Assignee: Ovidiu Feodorov (was: Tim Fox) Reverted. > Unnecessary junit.timeout2 used by tests/build.xml > -------------------------------------------------- > > Key: JBMESSAGING-175 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-175 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Instead of using junit.timeout2 we should figure out why the normal timeout is not picked up in Tim's case. Revert to using junit.timeout. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-150) TCK sould test Messaging, and not JBossMQ, by default

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-150?page=all ] Ovidiu Feodorov reassigned JBMESSAGING-150: ------------------------------------------- Assignee: Prabhat Jha (was: Ovidiu Feodorov) > TCK sould test Messaging, and not JBossMQ, by default > ----------------------------------------------------- > > Key: JBMESSAGING-150 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-150 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Priority: Minor > Fix For: 1.2.1 > > > Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. > See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. > All TCK-related Messaging configuration files and build scripts are in https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to j2eetck-mods. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-89) Repository reorganization

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-89?page=all ] Ovidiu Feodorov updated JBMESSAGING-89: --------------------------------------- Comment: was deleted > Repository reorganization > ------------------------- > > Key: JBMESSAGING-89 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-89 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The current JBoss Messaging CVS module (jboss-head/jms) contains unused directories and files, byproducts of alpha development and refactoring. > Clean-up the module and keep only what is necessary. > Rename the current "messaging" module "jbossmq", and change "jms" to "messaging" -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-89) Repository reorganization

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-89?page=all ] Ovidiu Feodorov closed JBMESSAGING-89. -------------------------------------- Resolution: Done > Repository reorganization > ------------------------- > > Key: JBMESSAGING-89 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-89 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The current JBoss Messaging CVS module (jboss-head/jms) contains unused directories and files, byproducts of alpha development and refactoring. > Clean-up the module and keep only what is necessary. > Rename the current "messaging" module "jbossmq", and change "jms" to "messaging" -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-150) TCK sould test Messaging, and not JBossMQ, by default

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-150?page=all ] Ovidiu Feodorov updated JBMESSAGING-150: ---------------------------------------- Description: Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. All TCK-related Messaging configuration files and build scripts are in https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to j2eetck-mods. was: Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. > TCK sould test Messaging, and not JBossMQ, by default > ----------------------------------------------------- > > Key: JBMESSAGING-150 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-150 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > > Modify j2eetck-mods so when Vendor Implementation config is built, it will include by default Messaging, and not MQ. Testing Messaging shouldn't require any other additional steps. > See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of affairs. > All TCK-related Messaging configuration files and build scripts are in https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to j2eetck-mods. -- 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, 11 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 August 2006