You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Web Maestro Clay <th...@gmail.com> on 2006/04/20 07:38:26 UTC
Problem with plugin 'is not available in the build dir'
I'm having problems getting plugins working. I was able to use it
previously, but I can no longer even run `forrest init-plugins`.
Q: If it was working before, what have you done to make it stop working?
A: I started making modifications to the ODT plugin's stylesheets.
While testing I noticed it wasn't working. After searching the
archives, I decided to try checking out a fresh copy from svn.
Unfortunately (after changing $FORREST_HOME to point to the fresh svn
checkout) I receive the same error.
Without further ado, here's the error (along w some extra fluff...)
[clay@Clays-PB trafxs]$ echo $FORREST_HOME
/Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk
[clay@Clays-PB trafxs]$ pwd
/Users/clay/Sites/trafxs
[clay@Clays-PB trafxs]$ forrest init-plugins
Apache Forrest. Run 'forrest -projecthelp' to list options
Buildfile: /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/
forrest.build.xml
init-props:
echo-settings:
init-plugins:
Created dir: /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/
build/plugins
Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
--------------------------------------------------------------
Installing plugin: org.apache.forrest.plugin.input.odt
--------------------------------------------------------------
check-plugin:
org.apache.forrest.plugin.input.odt is not available in the build dir
init-props:
echo-settings:
init-proxy:
fetch-plugins-descriptors:
Deleting 2 files from /Users/clay/Sites/trafxs/build/tmp
Fetching plugins descriptor: http://forrest.apache.org/plugins/
plugins.xml
Getting: http://forrest.apache.org/plugins/plugins.xml
....
last modified = Fri Feb 24 01:07:16 PST 2006
Fetching plugins descriptor: http://forrest.apache.org/plugins/
whiteboard-plugins.xml
Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
....
last modified = Thu Apr 06 00:54:56 PDT 2006
Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml.
Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-
plugins.xml.
fetch-plugin:
Processing /Users/clay/Sites/trafxs/build/tmp/plugins-1.xml to /Users/
clay/Sites/trafxs/build/tmp/pluginlist2fetchbuild.xml
Loading stylesheet /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/
trunk/main/var/pluginlist2fetch.xsl
findPlugin:
Processing /Users/clay/Sites/trafxs/build/tmp/plugins-2.xml to /Users/
clay/Sites/trafxs/build/tmp/pluginlist2fetchbuild.xml
Loading stylesheet /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/
trunk/main/var/pluginlist2fetch.xsl
findPlugin:
unpack-plugin:
ERROR
=====
Unable to retrieve the org.apache.forrest.plugin.input.odt plugin.
There may be more information about the reason for this in output
above. The usual cause is that Forrest has been unable to download
the plugin descriptor file that indicates where this plugin is to be
downloaded from. If you are behind a firewall then set the proxy.host
and proxy.port values in the forrest.properties file.
You may also like to check the value of the
forrest.plugins.descriptors property in the forrest.properties file
and ensure that the locations indicated by that value are accessible
(note there should be no spaces in this property).
If all else fails you can can manually install the plugins you need
by downloading the install bundles (see
http://forrest.apache.org/pluginDocs/plugins_0_70/index.html) and
unpacking
them into FORREST_HOME/build/plugins.
Note that once the plugins have been installed, they will not need
to be installed again unless you delete them or wish to upgrade them.
BUILD FAILED
/Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/targets/
plugins.xml:389: The following error occurred while executing this line:
/Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/targets/
plugins.xml:410: The following error occurred while executing this line:
/Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/targets/
plugins.xml:110: Unable to install required plugins. See error
messages above for more detail.
Total time: 10 seconds
[clay@Clays-PB trafxs]$
Clay Leeds
the.webmaestro@gmail.com
My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet
Re: Problem with plugin 'is not available in the build dir'
Posted by Ross Gardler <rg...@apache.org>.
Cyriaque Dupoirieux wrote:
> le 20/04/2006 10:02 Ross Gardler a écrit :
>
>> Cyriaque Dupoirieux wrote:
>>
>>> le 20/04/2006 07:38 Web Maestro Clay a écrit :
>>>
>>>> I'm having problems getting plugins working. I was able to use it
>>>> previously, but I can no longer even run `forrest init-plugins`.
>>>>
>>>> Q: If it was working before, what have you done to make it stop
>>>> working?
>>>> A: I started making modifications to the ODT plugin's stylesheets.
>>>> While testing I noticed it wasn't working. After searching the
>>>> archives, I decided to try checking out a fresh copy from svn.
>>>> Unfortunately (after changing $FORREST_HOME to point to the fresh
>>>> svn checkout) I receive the same error.
>>>
>>>
>>> The plugin is not defined in any of plugins descriptor file because
>>> it have never been deployed in the forrest site.
>>
>>
>> Correct evaluation (i.e. not in the whiteboard plugin descriptor
>> file), wrong reason.
>
> Right,
>
>>
>> All plugins should appear in the descriptor file. These entries must
>> be added manually at this time There is an issue to generate them from
>> the plugin build information, I've done about 50% of the work towards
>> this, but not found the time for the other 50% yet.
>
> Maybe I can help on this, it's
> http://issues.apache.org/jira/browse/FOR-532 but I cannot see your svn
> submissions...
[I've set the reply-to field to the dev list - this has moved on now]
Sorry, must have forgot to but the issue number in the commits.
From memory all I have done is make the necessary information available
in the build.xml and added some hooks to the plugin deployment code.
What needs to be done now is (off the top of my head):
- XSL to create a plugins descriptor from the build.xml information
- add a sitemap match to create a plugin descriptor
- change sitemap match for plugins.xml files in core to aggregate each
descriptor in to the complete descriptor file
>> Why not just add it to the whiteboard descriptor file?
>
> Of course, but a commiter must do this.
Or a user supplies a patch.
> BTW, we still miss several plugins declaration like
> org.apache.forrest.plugin.output.php and org.apache.forrest.themes.core.
> Do I add them ?
I see no reason for keeping any plugins out. If you do add them then you
should deploy the descriptor (I think it is "ant deploy-descriptor", but
may be wrong).
Ross
Re: Problem with plugin 'is not available in the build dir'
Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.
le 20/04/2006 10:02 Ross Gardler a écrit :
> Cyriaque Dupoirieux wrote:
>> le 20/04/2006 07:38 Web Maestro Clay a écrit :
>>
>>> I'm having problems getting plugins working. I was able to use it
>>> previously, but I can no longer even run `forrest init-plugins`.
>>>
>>> Q: If it was working before, what have you done to make it stop
>>> working?
>>> A: I started making modifications to the ODT plugin's stylesheets.
>>> While testing I noticed it wasn't working. After searching the
>>> archives, I decided to try checking out a fresh copy from svn.
>>> Unfortunately (after changing $FORREST_HOME to point to the fresh
>>> svn checkout) I receive the same error.
>>
>> The plugin is not defined in any of plugins descriptor file because
>> it have never been deployed in the forrest site.
>
> Correct evaluation (i.e. not in the whiteboard plugin descriptor
> file), wrong reason.
Right,
>
> All plugins should appear in the descriptor file. These entries must
> be added manually at this time There is an issue to generate them from
> the plugin build information, I've done about 50% of the work towards
> this, but not found the time for the other 50% yet.
Maybe I can help on this, it's
http://issues.apache.org/jira/browse/FOR-532 but I cannot see your svn
submissions...
>
>> Two solutions :
>> First the simple one :
>>
>> cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.odt//
>> $FORREST_HOME/tools/ant/bin/ant local-deploy
>>
>> Second, much more complicated but no need of further local-deployment :
>> Define the plugin in a file of your choice (let's say
>> MyPluginsDescriptor.xml)
>
> Why not just add it to the whiteboard descriptor file?
Of course, but a commiter must do this.
BTW, we still miss several plugins declaration like
org.apache.forrest.plugin.output.php and org.apache.forrest.themes.core.
Do I add them ?
Salutations,
Cyriaque,
>
> Ross
>
>
Re: Problem with plugin 'is not available in the build dir'
Posted by Thorsten Scherler <th...@apache.org>.
El jue, 20-04-2006 a las 14:52 -0700, Clay Leeds escribió:
> On Apr 20, 2006, at 1:02 AM, Ross Gardler wrote:
> > Cyriaque Dupoirieux wrote:
> >> le 20/04/2006 07:38 Web Maestro Clay a écrit :
> >>> I'm having problems getting plugins working. I was able to use it
> >>> previously, but I can no longer even run `forrest init-plugins`.
> >>>
> >>> Q: If it was working before, what have you done to make it stop
> >>> working?
> >>> A: I started making modifications to the ODT plugin's
> >>> stylesheets. While testing I noticed it wasn't working. After
> >>> searching the archives, I decided to try checking out a fresh
> >>> copy from svn. Unfortunately (after changing $FORREST_HOME to
> >>> point to the fresh svn checkout) I receive the same error.
> >> The plugin is not defined in any of plugins descriptor file
> >> because it have never been deployed in the forrest site.
> >
> > Correct evaluation (i.e. not in the whiteboard plugin descriptor
> > file), wrong reason.
> >
> > All plugins should appear in the descriptor file. These entries
> > must be added manually at this time There is an issue to generate
> > them from the plugin build information, I've done about 50% of the
> > work towards this, but not found the time for the other 50% yet.
> >
> >> Two solutions :
> >> First the simple one :
> >> cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.odt//
> >> $FORREST_HOME/tools/ant/bin/ant local-deploy
> >> Second, much more complicated but no need of further local-
> >> deployment :
> >> Define the plugin in a file of your choice (let's say
> >> MyPluginsDescriptor.xml)
> >
> > Why not just add it to the whiteboard descriptor file?
> >
> > Ross
>
> Thank you both! I've added it to the whiteboard descriptor file. I
> was going to submit a PATCH to whiteboard-plugins.xml, but I've just
> noticed an OpenDocument plugin (I thought that was what I was working
> on! :-). As that question is mildly off-topic I'll ask about it.
>
Well just do svn st in the whiteboard dir or have a look at
http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/ and
you find out that it is your plugin (that you were working on). ;)
salu2
> BTW, in case I or someone else needs this info Cyriaque meant for me
> to go here:
> cd $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.input.odt
>
> (in Cyriaque's haste to help, 'whiteboard/' was omitted)...
>
> Clay Leeds
> webmaestro@mac.com
>
> My religion is simple. My religion is kindness.
> -- HH Dalai Lama of Tibet
>
>
>
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: Problem with plugin 'is not available in the build dir'
Posted by Clay Leeds <we...@mac.com>.
On Apr 20, 2006, at 1:02 AM, Ross Gardler wrote:
> Cyriaque Dupoirieux wrote:
>> le 20/04/2006 07:38 Web Maestro Clay a écrit :
>>> I'm having problems getting plugins working. I was able to use it
>>> previously, but I can no longer even run `forrest init-plugins`.
>>>
>>> Q: If it was working before, what have you done to make it stop
>>> working?
>>> A: I started making modifications to the ODT plugin's
>>> stylesheets. While testing I noticed it wasn't working. After
>>> searching the archives, I decided to try checking out a fresh
>>> copy from svn. Unfortunately (after changing $FORREST_HOME to
>>> point to the fresh svn checkout) I receive the same error.
>> The plugin is not defined in any of plugins descriptor file
>> because it have never been deployed in the forrest site.
>
> Correct evaluation (i.e. not in the whiteboard plugin descriptor
> file), wrong reason.
>
> All plugins should appear in the descriptor file. These entries
> must be added manually at this time There is an issue to generate
> them from the plugin build information, I've done about 50% of the
> work towards this, but not found the time for the other 50% yet.
>
>> Two solutions :
>> First the simple one :
>> cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.odt//
>> $FORREST_HOME/tools/ant/bin/ant local-deploy
>> Second, much more complicated but no need of further local-
>> deployment :
>> Define the plugin in a file of your choice (let's say
>> MyPluginsDescriptor.xml)
>
> Why not just add it to the whiteboard descriptor file?
>
> Ross
Thank you both! I've added it to the whiteboard descriptor file. I
was going to submit a PATCH to whiteboard-plugins.xml, but I've just
noticed an OpenDocument plugin (I thought that was what I was working
on! :-). As that question is mildly off-topic I'll ask about it.
BTW, in case I or someone else needs this info Cyriaque meant for me
to go here:
cd $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.input.odt
(in Cyriaque's haste to help, 'whiteboard/' was omitted)...
Clay Leeds
webmaestro@mac.com
My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet
Re: Problem with plugin 'is not available in the build dir'
Posted by Ross Gardler <rg...@apache.org>.
Cyriaque Dupoirieux wrote:
> le 20/04/2006 07:38 Web Maestro Clay a écrit :
>
>> I'm having problems getting plugins working. I was able to use it
>> previously, but I can no longer even run `forrest init-plugins`.
>>
>> Q: If it was working before, what have you done to make it stop working?
>> A: I started making modifications to the ODT plugin's stylesheets.
>> While testing I noticed it wasn't working. After searching the
>> archives, I decided to try checking out a fresh copy from svn.
>> Unfortunately (after changing $FORREST_HOME to point to the fresh svn
>> checkout) I receive the same error.
>
> The plugin is not defined in any of plugins descriptor file because it
> have never been deployed in the forrest site.
Correct evaluation (i.e. not in the whiteboard plugin descriptor file),
wrong reason.
All plugins should appear in the descriptor file. These entries must be
added manually at this time There is an issue to generate them from the
plugin build information, I've done about 50% of the work towards this,
but not found the time for the other 50% yet.
> Two solutions :
> First the simple one :
>
> cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.odt//
> $FORREST_HOME/tools/ant/bin/ant local-deploy
>
> Second, much more complicated but no need of further local-deployment :
> Define the plugin in a file of your choice (let's say
> MyPluginsDescriptor.xml)
Why not just add it to the whiteboard descriptor file?
Ross
Re: Problem with plugin 'is not available in the build dir'
Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.
le 20/04/2006 07:38 Web Maestro Clay a écrit :
> I'm having problems getting plugins working. I was able to use it
> previously, but I can no longer even run `forrest init-plugins`.
>
> Q: If it was working before, what have you done to make it stop working?
> A: I started making modifications to the ODT plugin's stylesheets.
> While testing I noticed it wasn't working. After searching the
> archives, I decided to try checking out a fresh copy from svn.
> Unfortunately (after changing $FORREST_HOME to point to the fresh svn
> checkout) I receive the same error.
The plugin is not defined in any of plugins descriptor file because it
have never been deployed in the forrest site.
Two solutions :
First the simple one :
cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.odt//
$FORREST_HOME/tools/ant/bin/ant local-deploy
Second, much more complicated but no need of further local-deployment :
Define the plugin in a file of your choice (let's say
MyPluginsDescriptor.xml)
Add it to the forrest.plugins.descriptors property in
either your project forrest.properties or your
${user.hume}/forrest.properties
* forrest.plugins.descriptors=http://forrest.apache.org/plugins/plugins.xml,http://forrest.apache.org/plugins/whiteboard-plugins.xml,file:///path/path/path/MyPluginsDescriptor.xml
Salutations,
Cyriaque,
>
> Without further ado, here's the error (along w some extra fluff...)
>
> [clay@Clays-PB trafxs]$ echo $FORREST_HOME
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk
> [clay@Clays-PB trafxs]$ pwd
> /Users/clay/Sites/trafxs
> [clay@Clays-PB trafxs]$ forrest init-plugins
> Apache Forrest. Run 'forrest -projecthelp' to list options
>
> Buildfile:
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/forrest.build.xml
>
>
> init-props:
>
> echo-settings:
>
> init-plugins:
> Created dir:
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/build/plugins
> Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
> Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
> Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
> Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
> Copying 1 file to /Users/clay/Sites/trafxs/build/tmp
>
> --------------------------------------------------------------
> Installing plugin: org.apache.forrest.plugin.input.odt
> --------------------------------------------------------------
>
>
> check-plugin:
> org.apache.forrest.plugin.input.odt is not available in the build dir
>
> init-props:
>
> echo-settings:
>
> init-proxy:
>
> fetch-plugins-descriptors:
> Deleting 2 files from /Users/clay/Sites/trafxs/build/tmp
> Fetching plugins descriptor:
> http://forrest.apache.org/plugins/plugins.xml
> Getting: http://forrest.apache.org/plugins/plugins.xml
> ....
> last modified = Fri Feb 24 01:07:16 PST 2006
> Fetching plugins descriptor:
> http://forrest.apache.org/plugins/whiteboard-plugins.xml
> Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
> ....
> last modified = Thu Apr 06 00:54:56 PDT 2006
> Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml.
> Plugin list loaded from
> http://forrest.apache.org/plugins/whiteboard-plugins.xml.
>
> fetch-plugin:
> Processing /Users/clay/Sites/trafxs/build/tmp/plugins-1.xml to
> /Users/clay/Sites/trafxs/build/tmp/pluginlist2fetchbuild.xml
> Loading stylesheet
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/var/pluginlist2fetch.xsl
>
>
> findPlugin:
> Processing /Users/clay/Sites/trafxs/build/tmp/plugins-2.xml to
> /Users/clay/Sites/trafxs/build/tmp/pluginlist2fetchbuild.xml
> Loading stylesheet
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/var/pluginlist2fetch.xsl
>
>
> findPlugin:
>
> unpack-plugin:
>
> ERROR
> =====
>
> Unable to retrieve the org.apache.forrest.plugin.input.odt plugin.
> There may be more information about the reason for this in output
> above. The usual cause is that Forrest has been unable to download
> the plugin descriptor file that indicates where this plugin is to be
> downloaded from. If you are behind a firewall then set the proxy.host
> and proxy.port values in the forrest.properties file.
>
> You may also like to check the value of the
> forrest.plugins.descriptors property in the forrest.properties file
> and ensure that the locations indicated by that value are accessible
> (note there should be no spaces in this property).
>
> If all else fails you can can manually install the plugins you need
> by downloading the install bundles (see
> http://forrest.apache.org/pluginDocs/plugins_0_70/index.html) and
> unpacking
> them into FORREST_HOME/build/plugins.
>
> Note that once the plugins have been installed, they will not need
> to be installed again unless you delete them or wish to upgrade them.
>
>
> BUILD FAILED
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/targets/plugins.xml:389:
> The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/targets/plugins.xml:410:
> The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/apache/forrest_0.8/trunk/main/targets/plugins.xml:110:
> Unable to install required plugins. See error messages above for more
> detail.
>
> Total time: 10 seconds
> [clay@Clays-PB trafxs]$
>
>
> Clay Leeds
> the.webmaestro@gmail.com
>
> My religion is simple. My religion is kindness.
> -- HH Dalai Lama of Tibet
>
>
>
>