Samigo should generate its temp directory automatically from system properties
GENERAL
TESTING
GENERAL
TESTING
Description
relates to
Activity
Show:

Matthew Jones March 2, 2015 at 3:15 PM
The was basically incorporated by

Peter Knoop April 18, 2007 at 7:12 AM
This issue was reported against Nightly/SVN-Trunk after 2.3.1 was released. It is still unresolved at this point, therefore, it is most likely affecting 2.4.0 as well, and Affects Version is being updated to the current 2.4 tag (2.4.0.010) to reflect this.
Java already has a platform independent way to find
the system temp directory. Lets use it to do the "right" thing by
default.
http://java.sun.com/j2se/1.5.0/docs/api/java/lang/
System.html#getProperties()
java.io.tempdir Default temp file path
Find the system temp directory, then generate your working directory
beneath it based on something unique (i.e. server_id+GUID) so that
multiple instances of Sakai that run on the same OS do not have a
chance of stepping on each others' temp files.
You can always have a property available to overwrite this value with
something should the SA want to specify the place where samigo does
its temporary stuff. However I think we can get big points in the
area of User Delight for not requiring folks to worry about things
like this out of the box.
Bonus points for cleaning up the files when you are done with them.