[ 
http://jira.dspace.org/jira/browse/DS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Donohue updated DS-516:
---------------------------

    Attachment: DS-516-v4Tim.patch

There are two minor bugs on Windows in DS-516-v3.patch :

(1) dspace.bat needs to have "@echo off" as the first command in the file 
(similar to dsrun.bat file) -- otherwise Windows prints out every command 
before running it (which just looks ugly/confusing)

(2) dsrun.bat's @calll command needs to be:

@call dspace.bat dsrun %*

(Just remove the "org.dspace.app.launcher.ScriptLauncher", as it is already 
called by dspace.bat)

Just in case the fixes above are not clear, I've attached a DS-516-v4Tim.patch 
file which makes these two minor fixes to the original DS-516v3.patch file.  
(It also cleans up the inline comments/license in the *.bat files a bit)

After making those two minor fixes, everything works like a charm on Windows.  
As an example, I can run both of these commands successfully, and both produce 
the same results:

dspace export -t ITEM -i 10 -d C:\tmp -n 1    (New-style Command)
dsrun org.dspace.app.itemexport.ItemExport -t ITEM -i 10 -d C:\tmp -n 1  
(Old-style Command)

I've tried this for several commands (exporting, generating sitemaps, 
reindexing, etc.) and it all seems to work great.

> DSRUN does not start Service Manager
> ------------------------------------
>
>                 Key: DS-516
>                 URL: http://jira.dspace.org/jira/browse/DS-516
>             Project: DSpace 1.x
>          Issue Type: Bug
>          Components: DSpace API
>    Affects Versions: 1.6.0
>            Reporter: Mark Diggory
>            Assignee: Stuart Lewis
>             Fix For: 1.6.1
>
>         Attachments: DS-516-v2.patch, DS-516-v3.patch, DS-516-v4Tim.patch, 
> dsrun.patch
>
>
> I'll also comment you'll want to use the "dspace" CLI script to launch 
> executions rather than "dsrun" as the DSpace services framework need to be 
> started properly before updates happen to services.
> Comment to the developers... We rather missed this in our architecture of the 
> new execution environment.  We may want to consider removing dsrun or 
> enabling a Main wrapper around it similar to the "dspace" shell runner so 
> that the Spring/Services framework is properly started.  An alternative would 
> be to make "dspace" more flexible to support passing Classnames directly to 
> it in the same manner as "dsrun".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------

_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to