forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-462) Projects need to be able to override plugin installation directory
Date Sun, 06 Mar 2005 15:21:18 GMT
The following comment has been added to this issue:

     Author: Dave Brondsema
    Created: Sun, 6 Mar 2005 9:21 AM
I think this should actually be really easy :-)

In ~/ I set forrest.plugins-dir=${user.home}/.forrest/plugins and downloading
works fine, but those plugins aren't used when forrest is run.

Two places I think we need to change are:
* main/webapp/WEB-INF/xconf/forrest-core.xconf to use @forrest.plugins-dir@ instead of @forrest.home@/build/plugins
* main/targest/webapp.xml to use forrest.plugins-dir instead of build.plugins-dir

However, even after these changes the user's plugins are not used.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-462
    Summary: Projects need to be able to override plugin installation directory
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Forrest

   Reporter: Ross Gardler

    Created: Sun, 6 Mar 2005 5:19 AM
    Updated: Sun, 6 Mar 2005 9:21 AM

If Forrest is installed in a multi-user environemnt then each user should still have their
own version of the plugins. This is because they may need a different version to different
users (not an issue right now as there is only one version of each plugin, however, this will
not always be the case.

In this situation the user should be able to change change the location of the Forrest plugins
directory on a per project basis.

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