September 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-324) Create publishing-related decorators that can be attached to workspace-related views

by Johnny Verhaeg (JIRA)

Create publishing-related decorators that can be attached to workspace-related views ------------------------------------------------------------------------------------ Key: DNA-324 URL: https://jira.jboss.org/jira/browse/DNA-324 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 We may want to model our approach after SCM repository plug-ins, while making sure we don't conflict with those plug-ins or "over-decorate". -- 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

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (DNA-320) Create connection management view

by Johnny Verhaeg (JIRA)

Create connection management view --------------------------------- Key: DNA-320 URL: https://jira.jboss.org/jira/browse/DNA-320 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 To create and maintain connections to one or more repositories deployed in a container -- 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

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (DNA-322) Create context menu and menu bar items tied to publishing actions

by Johnny Verhaeg (JIRA)

Create context menu and menu bar items tied to publishing actions ----------------------------------------------------------------- Key: DNA-322 URL: https://jira.jboss.org/jira/browse/DNA-322 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 -- 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

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (DNA-530) ClasspathLocalizationRepository Should Not Use Thread Context Class Loader

by Dan Florian (JIRA)

ClasspathLocalizationRepository Should Not Use Thread Context Class Loader -------------------------------------------------------------------------- Key: DNA-530 URL: https://jira.jboss.org/jira/browse/DNA-530 Project: DNA Issue Type: Bug Components: Common Affects Versions: 0.6 Environment: Ubuntu 9.04 Reporter: Dan Florian Assignee: Dan Florian Fix For: 0.7 Ran Eclipse with JBoss MetaMatrix Designer installed as well as the DNA Eclipse plugin. At startup MetaMatrix sets the current thread's context class loader. This was causing a problem (stack overflow) in I18N class used by the DNA Eclipse plugin. ClasspathLocalizationRepository should always use it's own class loader. -- 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-529) Upgrade to Lucene 2.9

by Randall Hauch (JIRA)

Upgrade to Lucene 2.9 --------------------- Key: DNA-529 URL: https://jira.jboss.org/jira/browse/DNA-529 Project: DNA Issue Type: Thirdparty Change Components: JCR Affects Versions: 0.7 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.7 Lucene 2.9 was just released, and includes a whole host of new features. Lucene 3.0 should be released soon as basically a 2.9 minus deprecations, so if that comes out soon we should probably just jump to that. Lucene 2.9 is not yet in the JBoss Maven repository, so that needs to be done and will be a fair amount of work (considering all the many different modules that make up Lucene). -- 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

14 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-528) Loading Additional Mimetypes Via Stream Does Not Work in MimeTypeUtil

by Dan Florian (JIRA)

Loading Additional Mimetypes Via Stream Does Not Work in MimeTypeUtil --------------------------------------------------------------------- Key: DNA-528 URL: https://jira.jboss.org/jira/browse/DNA-528 Project: DNA Issue Type: Bug Components: Common Affects Versions: 0.6 Environment: Ubuntu 9.04 Reporter: Dan Florian Assignee: Dan Florian Fix For: 0.7 Custom extension to mimetype mappings are not available after load. I'm calling the static load(InputStream, Map) method and passing the resultant Map into the MimeTypeUtil constructor. However none of the mappings are available to the MimeTypeUtil object. -- 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-527) JcrSingleValuePropertyTest's Date Test Fails On Ubuntu

by Dan Florian (JIRA)

JcrSingleValuePropertyTest's Date Test Fails On Ubuntu ------------------------------------------------------ Key: DNA-527 URL: https://jira.jboss.org/jira/browse/DNA-527 Project: DNA Issue Type: Bug Components: Graph, Testing Affects Versions: 0.6 Environment: Ubuntu 9.04 Reporter: Dan Florian Assignee: Dan Florian Fix For: 0.7 The "shouldProvideDate" test fails due to differences in the toString() values of the Calendar objects. Removing the asserts that check the toString(), the length of the toString(), and the Calendars will allow the test to pass. With these 3 assert removed the test is still checking the milliseconds of the date and the type which is sufficient. The Calendar test is failing because one calendar has an id of "GMT" while the other one is using "UTC." -- 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-524) JcrValueTest Fails Due To Timezone

by Dan Florian (JIRA)

JcrValueTest Fails Due To Timezone ---------------------------------- Key: DNA-524 URL: https://jira.jboss.org/jira/browse/DNA-524 Project: DNA Issue Type: Bug Components: Testing Affects Versions: 0.6 Environment: Ubuntu 9.04 Reporter: Dan Florian Assignee: Dan Florian Fix For: 0.7 JcrValueTest has 2 failures: 1. shouldProvideDateForDouble fails with this error: java.lang.AssertionError: Expected: is <java.util.GregorianCalendar[time=0,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="US/Central",offset=-21600000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=US/Central,offset=-21600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=1969,MONTH=11,WEEK_OF_YEAR=1,WEEK_OF_MONTH=5,DAY_OF_MONTH=31,DAY_OF_YEAR=365,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=6,HOUR_OF_DAY=18,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-21600000,DST_OFFSET=0]> got: <java.util.GregorianCalendar[time=0,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="America/Chicago",offset=-21600000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=America/Chicago,offset=-21600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=1969,MONTH=11,WEEK_OF_YEAR=1,WEEK_OF_MONTH=5,DAY_OF_MONTH=31,DAY_OF_YEAR=365,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=6,HOUR_OF_DAY=18,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-21600000,DST_OFFSET=0]> at org.junit.Assert.assertThat(Assert.java:502) at org.junit.Assert.assertThat(Assert.java:492) at org.jboss.dna.jcr.JcrValueTest.shouldProvideDateForDouble(JcrValueTest.java:159) 2. shouldProvideDateForLong fails with this error: java.lang.AssertionError: Expected: is <java.util.GregorianCalendar[time=0,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="US/Central",offset=-21600000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=US/Central,offset=-21600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=1969,MONTH=11,WEEK_OF_YEAR=1,WEEK_OF_MONTH=5,DAY_OF_MONTH=31,DAY_OF_YEAR=365,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=6,HOUR_OF_DAY=18,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-21600000,DST_OFFSET=0]> got: <java.util.GregorianCalendar[time=0,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="America/Chicago",offset=-21600000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=America/Chicago,offset=-21600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=1969,MONTH=11,WEEK_OF_YEAR=1,WEEK_OF_MONTH=5,DAY_OF_MONTH=31,DAY_OF_YEAR=365,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=6,HOUR_OF_DAY=18,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-21600000,DST_OFFSET=0]> at org.junit.Assert.assertThat(Assert.java:502) at org.junit.Assert.assertThat(Assert.java:492) at org.jboss.dna.jcr.JcrValueTest.shouldProvideDateForLong(JcrValueTest.java:192) Tests are failing because expected timezone is "US/Central" and actual timezone is "America/Chicago." Changing the test to tests to check the milliseconds allows the tests to pass. -- 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-525) Configure connection information for QA databases

by Randall Hauch (JIRA)

Configure connection information for QA databases ------------------------------------------------- Key: DNA-525 URL: https://jira.jboss.org/jira/browse/DNA-525 Project: DNA Issue Type: Task Components: Testing Affects Versions: 0.7 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.7 DNA-521 added the infrastructure for testing multiple databases, but didn't put in the correct connection information on the QA databases because we didn't yet have databases set up. Now that we do have these databases, we have to update the connection information in the parent POM.xml. -- 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-521) Define infrastructure for testing with multiple DBMSes

by Randall Hauch (JIRA)

Define infrastructure for testing with multiple DBMSes ------------------------------------------------------ Key: DNA-521 URL: https://jira.jboss.org/jira/browse/DNA-521 Project: DNA Issue Type: Task Affects Versions: 0.6 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.7 We need to support easily testing the different aspects of DNA (primarily integration testing, but including the JPA connector testing) on different DBMS systems. There are several ways of doing this, but one seemingly attractive way is to define a Maven profile for each DBMS to define the dependencies, custom repositories for drivers, and Maven properties that define the database connection information. Each project can then be done in a database-agnostic manner, where database-related information (e.g., connection properties, driver names, etc.) can be placed in a property file within the project's "/src/test/resources" area and defined in terms of the Maven properties. Then the Maven build (or just test runs) can be executed by supplying the desired DBMS profile; ideally, the normal build process would be completed, and then the tests can be run using the different DBMS profiles. The jBPM4 project defines the profiles in their parent POM [1], while the Hibernate project defines them is their "testsuite" project's POM [2]. I actually like how jBPM defines it in the parent POM, but I like how Hibernate's POM defines and organizes their profiles. Also note Hibernate's use of one DBMS profile (currently HSQLDB) as the default, meaning that all tests would normally pick that up. Also, an example of a Hibernate test resource file that picks up the Maven properties is at [3]. [1] https://anonsvn.jboss.org/repos/jbpm/jbpm4/trunk/pom.xml [2] https://anonsvn.jboss.org/repos/hibernate/core/trunk/testsuite/pom.xml [3] https://anonsvn.jboss.org/repos/hibernate/core/trunk/testsuite/src/test/r... -- 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

14 years, 7 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues September 2009