On 14 May 2010 13:43, Mark H. Wood mw...@iupui.edu wrote:
Closing could be part of the release process. When a fix is
incorporated into a release, the issue should be closed. To revisit it
after a release, a new issue should be linked to the old. But I
wouldn't want to do that without an
[
http://jira.dspace.org/jira/browse/DS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11436#action_11436
]
Tim Donohue commented on DS-524:
Andrea,
I still don't understand why we shouldn't allow DSpace System
[
http://jira.dspace.org/jira/browse/DS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11437#action_11437
]
Robin Taylor commented on DS-524:
-
My tuppence worth :-
If possible I would like us to avoid adding
[
http://jira.dspace.org/jira/browse/DS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Trimble closed DS-523.
--
Documentation Status: Complete or Committed (was: Needed)
Resolution: Fixed
Step 9 moved to
[
http://jira.dspace.org/jira/browse/DS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11439#action_11439
]
Jeffrey Trimble commented on DS-572:
Before closing, Stuart, you have a good example, but it's not
The primary requirement is that it be in the Maven Central or other
repositories that we use. JDOM is only at 1.1 in the maven central repository.
You can search that repository here.
http://mvnrepository.com/artifact/org.jdom/jdom
http://mvnrepository.com/artifact/jdom/jdom
You'll need to
[
http://jira.dspace.org/jira/browse/DS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11440#action_11440
]
Jeffrey Trimble commented on DS-534:
So, in essence there are TWO approaches to importing non-QDC
[
http://jira.dspace.org/jira/browse/DS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11442#action_11442
]
Keith Gilbertson commented on DS-534:
-
They are intended to be used together.
Any values for
[
http://jira.dspace.org/jira/browse/DS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11444#action_11444
]
Keith Gilbertson commented on DS-534:
-
I have some errors in my last comment that made this unclear.
[
http://jira.dspace.org/jira/browse/DS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11445#action_11445
]
Stuart Lewis commented on DS-572:
-
Hi Jeff,
Thanks for looking at this. I'm not sure - if you think it
I would say something like the database config / connection string would be
the only thing that *needs* to stay in the configs.
So if everything else moved to the DB, then that could be easily/safely
modified in an admin section of the user interface, by the admin user.
Somewhat like modifying
[
http://jira.dspace.org/jira/browse/DS-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Shepherd updated DS-397:
Fix Version/s: (was: 1.6.1)
Taking 1.6.1 off as Fix Version until the problem is confirmed to still exist
[
http://jira.dspace.org/jira/browse/DS-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Shepherd updated DS-463:
Fix Version/s: (was: 1.6.1)
Taking 1.6.1 off as a Fix Version as this issue is more of an improvement
than a
Hi, everyone :
I'm using dspace 1.6.0 in the form of xmlui. when interent is connected,
everything is OK. But when it is disconnected , I meet these problem when I
start up tomcat:
Exception sending context initialized event to listener instance of class
14 matches
Mail list logo
