forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Resolved: (FOR-406) plugins writing to forrest build dir
Date Fri, 10 Dec 2004 00:04:29 GMT

   The following issue has been resolved as FIXED.

   Resolver: Ross Gardler
       Date: Thu, 9 Dec 2004 6:04 PM

Plugin temporary files are now written to the projects temp directory (rather than a new directory
as we original proposed). This will work if the plugin is installed, however, if it has never
been installed then the build will still fail due to not having write acess.

We could make the plugins install into the project directory, but this will duplicate versions
of the plugin on the users hard drive. Instead I have improved the failure message, it now
asks the user to have the system admin install the plugin for them and gives instructions
on how to do this.

I've marked this issue fixed, but not closed it - please test in your environment and close
if it works.
View the issue:

Here is an overview of the issue:
        Key: FOR-406
    Summary: plugins writing to forrest build dir
       Type: Bug

     Status: Resolved
   Priority: Minor
 Resolution: FIXED

    Project: Forrest
             Plugins (general issues)
   Fix Fors:

   Assignee: Ross Gardler
   Reporter: Dave Brondsema

    Created: Tue, 7 Dec 2004 6:29 PM
    Updated: Thu, 9 Dec 2004 6:04 PM

If the user executing forrest without write permissions to $FORREST_HOME an error like the
following occurs:

/home/dpb2/forrest/main/targets/plugins.xml:185: Failed to copy /home/dpb2/forrest/main/var/initial_plugins_sitemap.xmap
to /home/dpb2/forrest/build/plugins/input.xmap due to /home/dpb2/forrest/build/plugins/input.xmap
(Permission denied) and I couldn't delete the corrupt /home/dpb2/forrest/build/plugins/input.xmap

Shouldn't input.xmap go in ${project.home}?

This is different than FOR-356.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message