You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Cyriaque Dupoirieux (JIRA)" <ji...@apache.org> on 2006/08/11 12:06:14 UTC
[jira] Commented: (FOR-742) trouble accessing unversioned plugin
for a released version of Forrest, e.g. projectInfo
[ http://issues.apache.org/jira/browse/FOR-742?page=comments#action_12427486 ]
Cyriaque Dupoirieux commented on FOR-742:
-----------------------------------------
Can I close this, because I don't know what I can do more than the fallback mecanism which is now in place :
Forrest uses a fall back mecanism to find the plugins to install for a project.
For an unversionned plugin, Forrest tries to get it from :
1. different local sources directories (project.required.plugins.src property)
2. if not found : the remote site in the forrest version directory
3. if not found : the remote site (with no forrest version directory)
For a versionned plugin, Forrest tries to get :
1. the versionned plugin from different local sources directories (project.required.plugins.src property)
2. if not found : the versionned plugin from the remote site in the forrest version directory
3. if not found : the unversionned plugin in different local sources directory (project.required.plugins.src property again)
4. if not found : the unversionned plugin from the remote site in the forrest version directory
5. if not found : the remote site (with no forrest version directory)
> trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
> ----------------------------------------------------------------------------------------
>
> Key: FOR-742
> URL: http://issues.apache.org/jira/browse/FOR-742
> Project: Forrest
> Issue Type: Bug
> Components: Plugins (general issues)
> Affects Versions: 0.8-dev, 0.7
> Reporter: David Crossley
> Assigned To: Cyriaque Dupoirieux
> Priority: Critical
> Fix For: 0.8-dev
>
>
> The plugin retrieval and deployment process are not quite correct. Recently the projectInfo plugin had its version number incremented and the "unversioned" plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant plugin.
> The solution is discussed here:
> http://marc.theaimsgroup.com/?t=113176328300002
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira