July 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-153) Add support for Microsoft Word document metadata

by Randall Hauch (JIRA)

Add support for Microsoft Word document metadata ------------------------------------------------ Key: DNA-153 URL: http://jira.jboss.com/jira/browse/DNA-153 Project: DNA Issue Type: Sub-task Components: Sequencers Reporter: Randall Hauch Fix For: 0.2 -- 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

15 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (DNA-88) Incorporate JCR TCK tests

by Randall Hauch (JIRA)

Incorporate JCR TCK tests ------------------------- Key: DNA-88 URL: http://jira.jboss.com/jira/browse/DNA-88 Project: DNA Issue Type: Sub-task Reporter: Randall Hauch -- 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

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (DNA-174) Should ensure single versions required for 3rd-party dependencies within same classloader

by Johnny Verhaeg (JIRA)

Should ensure single versions required for 3rd-party dependencies within same classloader ----------------------------------------------------------------------------------------- Key: DNA-174 URL: http://jira.jboss.com/jira/browse/DNA-174 Project: DNA Issue Type: Task Components: Development Environment Affects Versions: 0.1 Reporter: Johnny Verhaeg Priority: Minor Fix For: 0.2 We should write a script that will be executed after the build and produce some reports indicating: - The list of 3rd-party dependencies, both direct & indirect - Any potential conflicts in dependency versions between projects or other dependencies - A tree of non-test-related dependencies by project Developers would then need only to add classloader knowledge into the mix when handling dependency version conflict resolution. It would be nice if the resulting reports could be accessed in the same manner as build & test results via Hudson. -- 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

15 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (DNA-181) Consolidate security, messages, and progress within the ExecutionContext and make framework consistent in its use and passing of this context

by Johnny Verhaeg (JIRA)

Consolidate security, messages, and progress within the ExecutionContext and make framework consistent in its use and passing of this context --------------------------------------------------------------------------------------------------------------------------------------------- Key: DNA-181 URL: https://jira.jboss.org/jira/browse/DNA-181 Project: DNA Issue Type: Feature Request Components: API, SPI Affects Versions: 0.1 Reporter: Johnny Verhaeg Fix For: 0.2 We are already passing around an ExecutionContext to various parts of the DNA framework, and in some places a progress monitor that in turn contains problems encountered (as of DNA-75). We're now looking into security information that also needs to be passed around during login and execution, and it's now evident that a better way to handle all of these information types would be to consolidate all of it within the execution context and make it the common "token" that is consistently passed between all framework components, including the SPI. Messages, progress, security, etc., should always be dealt with in relation to a particular context, and contexts may be hierarchical in nature. For example, the messages, problems, and progress for a particular operation should be recorded in a manner that ties them to that operation's execution within whatever context it occurred, which will have been initiated as part of a broader context, that being either a higher-level or composite operation or, at the very least, within the context of the client's session. Recording information in this manner should make it easier to audit, debug, providing complex logging facilities, etc. "Problems" should be treated more generically as simply "Messages", allowing the framework much for flexibility to handle context-specific information, such as messages specific to an operation or executed command. The entire logging framework can then work off of these messages rather than leaving it to SPI implementors to determine when something should be logged, added as a problem/message, or both. The framework contains only a few other types of information, none of which should be dangerous to pass around, and any of which can be further protected if necessary via context wrappers that may, for instance, return immutable versions of that information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-84) Use quotes consistently in I18n localization property files

by Randall Hauch (JIRA)

Use quotes consistently in I18n localization property files ----------------------------------------------------------- Key: DNA-84 URL: http://jira.jboss.com/jira/browse/DNA-84 Project: DNA Issue Type: Task Reporter: Randall Hauch Assigned To: Randall Hauch Priority: Minor Fix For: 0.2 We appear to be using single quotes and double quotes in our localization messages. Single quotes are used by MessageFormat (which we're not using), but we should use double quotes to be more consistent. -- 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

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-186) Remove ProgressMonitor from StreamSequencer.sequence signature

by Johnny Verhaeg (JIRA)

Remove ProgressMonitor from StreamSequencer.sequence signature -------------------------------------------------------------- Key: DNA-186 URL: https://jira.jboss.org/jira/browse/DNA-186 Project: DNA Issue Type: Sub-task Reporter: Johnny Verhaeg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (DNA-185) Modify SequencerContext to extend ExecutionContext

by Johnny Verhaeg (JIRA)

Modify SequencerContext to extend ExecutionContext -------------------------------------------------- Key: DNA-185 URL: https://jira.jboss.org/jira/browse/DNA-185 Project: DNA Issue Type: Sub-task Reporter: Johnny Verhaeg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-104) Sequence Powerpoint files

by Randall Hauch (JIRA)

Sequence Powerpoint files ------------------------- Key: DNA-104 URL: http://jira.jboss.com/jira/browse/DNA-104 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Fix For: Future Releases Create a sequencer that extracts the content from Excel spreadsheets. Consider using Apache POI (http://poi.apache.org/index.html) to access the Excel files. -- 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

15 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (DNA-71) Document development tools and environment

by Randall Hauch (JIRA)

Document development tools and environment ------------------------------------------ Key: DNA-71 URL: http://jira.jboss.com/jira/browse/DNA-71 Project: DNA Issue Type: Task Components: Documentation Affects Versions: 0.1 Reporter: Randall Hauch Fix For: 0.2 We need to document how to set up the Maven Integration for Eclipse plugin. Apparently there's a newer version which defaults to generating the targets in a separate location (e.g., "targetEclipse"). We need to document this, emphasizing that having the Maven Eclipse plugin needs to work the same way that the command line 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

15 years, 7 months

1
9
0 / 0

[JBoss JIRA] Created: (DNA-103) Sequence Excel files

by Randall Hauch (JIRA)

Sequence Excel files -------------------- Key: DNA-103 URL: http://jira.jboss.com/jira/browse/DNA-103 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Fix For: Future Releases Create a sequencer that extracts the content from Excel spreadsheets. Consider using Apache POI (http://poi.apache.org/index.html) to access the Excel files. -- 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

15 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues July 2008