Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[udig-devel] [jira] Created: (UDIG-288) wrong pref cache spot

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/UDIG-288

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: UDIG-288
    Summary: wrong pref cache spot
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: uDIG
   Fix Fors:
             UDIG 0.9
   Versions:
             UDIG 0.8

   Assignee: 
   Reporter: David Zwiers

    Created: Fri, 25 Feb 2005 1:44 PM
    Updated: Fri, 25 Feb 2005 1:44 PM
Environment: I also had this on both linux and XP with java 5.0, eclipse M4, M5

Description:
(10:37:19) acuster: why's uDig trying to modify /etc/ ?
(10:37:22) acuster: Feb 25, 2005 1:36:48 PM java.util.prefs.FileSystemPreferences syncWorld
(10:37:22) acuster: WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException: /etc/.java/.systemPrefs/org create failed.
(10:37:52) acuster: ~/.uDig/ would make more sense
(10:38:09) acuster: adding a dot file to /etc/ is *evil*
(10:38:30) rgould: Interesting
(10:39:43) polio: I'm not convinced it's not part of the referencing spi stuff ... it appeared right after we switched to the new crs and developement of additional epsg factory started
(10:40:28) polio: on the other hand could also be the rcp ... but I'm fairly sure we are not doing this on purpose. I will make a jira for it
(10:40:38) polio: thanks acuster


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



Back to the top