April 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Resolved: (DNA-27) I18n framework should not throw exceptions for duplicate or missing messages

by Johnny Verhaeg (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-27?page=all ] Johnny Verhaeg resolved DNA-27. ------------------------------- Resolution: Done Added convenience methods to project I18n classes, and tests for each to ensure they have no localization problems. Also moved CommonI18nTest to correct package. > I18n framework should not throw exceptions for duplicate or missing messages > ---------------------------------------------------------------------------- > > Key: DNA-27 > URL: http://jira.jboss.com/jira/browse/DNA-27 > Project: DNA > Issue Type: Task > Components: Common > Reporter: Randall Hauch > Assigned To: Johnny Verhaeg > Priority: Minor > Fix For: 0.1 > > > Currently, the I18n framework checks for duplicate or missing messages in the property files. This check is very nice to have, but throwing an exception often causes problems in many different tests. Given that some of these tests may wrap the exception thrown by the I18n class, some of these failures can be very difficult to track down. > It would be better to have each I18n class (e.g., "CoreI18n") record the problems, and to create a test case for each of these classes. The test case can verify that there are no problems. Then, if there is a problem in a properties file, the test will fail while other tests (that don't necessarily care so much about missing or duplicate messages) won't. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-27) I18n framework should not throw exceptions for duplicate or missing messages

by Johnny Verhaeg (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-27?page=comments#action_12410425 ] Johnny Verhaeg commented on DNA-27: ----------------------------------- Re-designed I18n to store text and instance-specific problems within instances. Corrected some synchronization- and exception-related bugs. Changed terminology related to localization. Supplied many more tests, including for other locales. > I18n framework should not throw exceptions for duplicate or missing messages > ---------------------------------------------------------------------------- > > Key: DNA-27 > URL: http://jira.jboss.com/jira/browse/DNA-27 > Project: DNA > Issue Type: Task > Components: Common > Reporter: Randall Hauch > Assigned To: Johnny Verhaeg > Priority: Minor > Fix For: 0.1 > > > Currently, the I18n framework checks for duplicate or missing messages in the property files. This check is very nice to have, but throwing an exception often causes problems in many different tests. Given that some of these tests may wrap the exception thrown by the I18n class, some of these failures can be very difficult to track down. > It would be better to have each I18n class (e.g., "CoreI18n") record the problems, and to create a test case for each of these classes. The test case can verify that there are no problems. Then, if there is a problem in a properties file, the test will fail while other tests (that don't necessarily care so much about missing or duplicate messages) won't. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-27) I18n framework should not throw exceptions for duplicate or missing messages

by Johnny Verhaeg (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-27?page=comments#action_12410424 ] Johnny Verhaeg commented on DNA-27: ----------------------------------- Changed I18n to store errors encountered during the load of localization files in a global map rather than throwing exceptions, allowing these to be handled at a later time without hindering other current development. > I18n framework should not throw exceptions for duplicate or missing messages > ---------------------------------------------------------------------------- > > Key: DNA-27 > URL: http://jira.jboss.com/jira/browse/DNA-27 > Project: DNA > Issue Type: Task > Components: Common > Reporter: Randall Hauch > Assigned To: Johnny Verhaeg > Priority: Minor > Fix For: 0.1 > > > Currently, the I18n framework checks for duplicate or missing messages in the property files. This check is very nice to have, but throwing an exception often causes problems in many different tests. Given that some of these tests may wrap the exception thrown by the I18n class, some of these failures can be very difficult to track down. > It would be better to have each I18n class (e.g., "CoreI18n") record the problems, and to create a test case for each of these classes. The test case can verify that there are no problems. Then, if there is a problem in a properties file, the test will fail while other tests (that don't necessarily care so much about missing or duplicate messages) won't. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Work started: (DNA-23) Create example sequencer

by Randall Hauch (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-23?page=all ] Work on DNA-23 started by Randall Hauch. > Create example sequencer > ------------------------ > > Key: DNA-23 > URL: http://jira.jboss.com/jira/browse/DNA-23 > Project: DNA > Issue Type: Sub-task > Components: Documentation, Examples > Reporter: Randall Hauch > Assigned To: Randall Hauch > Fix For: 0.1 > > > Ideas include a Maven 2 POM file sequencer, or one that extracts image metadata. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (DNA-54) Set up continuous integration with Hudson

by Randall Hauch (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-54?page=all ] Randall Hauch resolved DNA-54. ------------------------------ Resolution: Done > Set up continuous integration with Hudson > ----------------------------------------- > > Key: DNA-54 > URL: http://jira.jboss.com/jira/browse/DNA-54 > Project: DNA > Issue Type: Task > Components: Testing > Reporter: Randall Hauch > Assigned To: Randall Hauch > Priority: Critical > Fix For: 0.1 > > > Set up continuous integration of the codebase using JBoss' Hudson 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-54) Set up continuous integration with Hudson

by Randall Hauch (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-54?page=comments#action_12410104 ] Randall Hauch commented on DNA-54: ---------------------------------- The continuous integration job is available at http://hudson.jboss.org/hudson/job/DNA%20continuous%20on%20JDK1.5/, and the nightly is available at http://hudson.jboss.org/hudson/job/DNA%20nightly%20integration%20on%20JDK... > Set up continuous integration with Hudson > ----------------------------------------- > > Key: DNA-54 > URL: http://jira.jboss.com/jira/browse/DNA-54 > Project: DNA > Issue Type: Task > Components: Testing > Reporter: Randall Hauch > Assigned To: Randall Hauch > Priority: Critical > Fix For: 0.1 > > > Set up continuous integration of the codebase using JBoss' Hudson 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-54) Set up continuous integration with Hudson

by Randall Hauch (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-54?page=comments#action_12410088 ] Randall Hauch commented on DNA-54: ---------------------------------- The builds are now being published, and the first build is in the publishing queue. > Set up continuous integration with Hudson > ----------------------------------------- > > Key: DNA-54 > URL: http://jira.jboss.com/jira/browse/DNA-54 > Project: DNA > Issue Type: Task > Components: Testing > Reporter: Randall Hauch > Assigned To: Randall Hauch > Priority: Critical > Fix For: 0.1 > > > Set up continuous integration of the codebase using JBoss' Hudson 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-54) Set up continuous integration with Hudson

by Randall Hauch (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-54?page=comments#action_12410086 ] Randall Hauch commented on DNA-54: ---------------------------------- Added two new builds to Hudson. One build represents the continuous integration tests, and it polls SVN for changes every 15 minutes and runs "mvn clean package". The other build represents a nightly run of the unit and integration tests, and this is scheduled to run "mvn clean integration-test" every morning at 3AM (regardless of changes). Note that recent changes to the "dna-integration-tests" project mean that all the JUnit tests in that project only run during the "integration-test" phase. > Set up continuous integration with Hudson > ----------------------------------------- > > Key: DNA-54 > URL: http://jira.jboss.com/jira/browse/DNA-54 > Project: DNA > Issue Type: Task > Components: Testing > Reporter: Randall Hauch > Assigned To: Randall Hauch > Priority: Critical > Fix For: 0.1 > > > Set up continuous integration of the codebase using JBoss' Hudson 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Work started: (DNA-54) Set up continuous integration with Hudson

by Randall Hauch (JIRA)

[ http://jira.jboss.com/jira/browse/DNA-54?page=all ] Work on DNA-54 started by Randall Hauch. > Set up continuous integration with Hudson > ----------------------------------------- > > Key: DNA-54 > URL: http://jira.jboss.com/jira/browse/DNA-54 > Project: DNA > Issue Type: Task > Components: Testing > Reporter: Randall Hauch > Assigned To: Randall Hauch > Priority: Critical > Fix For: 0.1 > > > Set up continuous integration of the codebase using JBoss' Hudson 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (DNA-57) Refactor codebase to clearly and cleanly separate SPI and API

by Randall Hauch (JIRA)

Refactor codebase to clearly and cleanly separate SPI and API ------------------------------------------------------------- Key: DNA-57 URL: http://jira.jboss.com/jira/browse/DNA-57 Project: DNA Issue Type: Task Components: Common, Connectors, Maven Classloader, Sequencers Affects Versions: 0.1 Reporter: Randall Hauch Assigned To: Randall Hauch Priority: Critical Fix For: 0.1 The existing structure of the codebase is not conducive for reusable interfaces in the API, nor does it cleanly separate the interfaces and classes that should be implemented/extended. We need to specifically identify the SPI classes (e.g., sequencers, connectors, etc.) and any APIs (e.g., configuration, DnaService, etc.). Also, if it's possible, collapse some of the projects or at least reorganize to prevent proliferation. -- 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, 1 month

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues April 2008