Yes, we discovered this the other day when working on a installation
without networking enabled. It is caused because EhCache is trying to
enable an RMI port for distributed caching.
You can disable this by overriding the dspace-services cache configuration file.
place the following in
[dspace-s
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
org.dspace.servicemanag
[
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
[
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
and
Hi all,
Today is the agreed date for the code freeze on DSpace 1.6.1.
The week from now until 21st May is to enable thorough testing of all the
changes we've committed, without the dspace-1_6_x branch changing significantly
while we do it.
This means:
- New JIRA issues won't be reviewed for in
On May 14, 2010, at 12:53 PM, Mark H. Wood wrote:
> On Fri, May 14, 2010 at 02:17:01PM +, Tim Donohue (JIRA) wrote:
>> (Sidenote: Eventually, someday, I feel we should move the majority of all
>> configurations to the Admin UI -- so that there's no need to stop/start
>> Tomcat/DSpace every
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 set
[
http://jira.dspace.org/jira/browse/DS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11445#action_11445
]
Stuart Lewis commented on DS-572:
-
Hi Jeff,
Thanks for looking at this. I'm not sure - if you think it
On Fri, May 14, 2010 at 02:17:01PM +, Tim Donohue (JIRA) wrote:
> (Sidenote: Eventually, someday, I feel we should move the majority of all
> configurations to the Admin UI -- so that there's no need to stop/start
> Tomcat/DSpace every time you need to modify dspace.cfg. However, in order to
[
http://jira.dspace.org/jira/browse/DS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11443#action_11443
]
Jeffrey Trimble commented on DS-534:
Very good. So this "metadata_[schema].xml" file is the registr
[
http://jira.dspace.org/jira/browse/DS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11442#action_11442
]
Keith Gilbertson commented on DS-534:
-
They are intended to be used together.
Any values for meta
[
http://jira.dspace.org/jira/browse/DS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11440#action_11440
]
Jeffrey Trimble commented on DS-534:
So, in essence there are TWO approaches to importing non-QDC da
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 mot
[
http://jira.dspace.org/jira/browse/DS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Trimble closed DS-507.
--
Documentation Status: Complete or Committed (was: In Description)
Resolution: Fixed
Documentati
[
http://jira.dspace.org/jira/browse/DS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11439#action_11439
]
Jeffrey Trimble commented on DS-572:
Before closing, Stuart, you have a good example, but it's not i
[
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 end
[
http://jira.dspace.org/jira/browse/DS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11437#action_11437
]
Robin Taylor commented on DS-524:
-
My tuppence worth :-
If possible I would like us to avoid adding any
[
http://jira.dspace.org/jira/browse/DS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11436#action_11436
]
Tim Donohue commented on DS-524:
Andrea,
I still don't understand why we shouldn't allow DSpace System
On 14 May 2010 13:43, Mark H. Wood 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 intermediate
Automated or not, I think it would be good for some who are not
developers to trawl JIRA regularly and keep asking, "whatever happened
to Issue X?" Developers don't always set priorities the way others
would. Anybody can put together a team to do this.
--
Mark H. Wood, Lead System Programmer
On Thu, May 13, 2010 at 05:52:28PM +0100, Graham Triggs wrote:
> I'm actually not a fan of the Closed status. Having worked with Jira in a
> number of cases where I've needed to re-organise issues after they've been
> worked on - either to add some additional categorisation, re-organisation of
> pr
On Thu, May 13, 2010 at 04:21:31PM +0100, TAYLOR Robin wrote:
> My understanding of these steps would be...
>
> Received - A new issue that has yet to be reviewed.
> Open - Reviewed and not immediately closed. As things stand
> the issue may or may not be assigned to
23 matches
Mail list logo
