You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Ron Blaschke (JIRA)" <ji...@apache.org> on 2005/06/19 13:39:19 UTC
[jira] Created: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
-------------------------------------------------------------------------------
Key: FOR-547
URL: http://issues.apache.org/jira/browse/FOR-547
Project: Forrest
Type: Bug
Components: Core operations
Versions: 0.7-dev
Environment: Windows XP, SP2
Ant 1.6.5
Forrest 0.7rc1
Reporter: Ron Blaschke
Priority: Minor
I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
Here's the relevant conversation from forrest-dev.
Ron Blaschke wrote:
> Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
>>Ron Blaschke wrote:
>>
>>>Unable to retrieve the ${plugin.name} plugin.
>>>
>>>Two noteworthy things: Calling "forrest init-plugins" installs the
>>>plugin sucessfully. And the error message says "${plugin.name}",
>>>instead of the real name of the plugin.
>
>>The two things are related. It looks like that the {plugin.name} is not
>>being set for some reason (and I guess {versioned.name} is not set either.
>
>>These are set in the init-plugins target of targets/plugins.xml
>
> I ran my build.xml with "ant -d," and found the following:
>
> Setting ro project property: plugin.name -> ${plugin.name}
> Setting ro project property: plugin.version -> ${plugin.version}
> Setting ro project property: versioned.name ->
> org.apache.forrest.plugin.input.projectInfo
Actually that is as expected. The {plugin.name} and {plugin.version}
values are set by a regexp looking for the the version number. Since
there is no version number in the plugin required the regexp fails and
so no value for the property. The rest of the script tries to get the
{versioned.name} plugin. If it fails it falls back to the unversioned
plugin.
This explains why the error message shows ${plugin.name}, I've changed
that to use the {versioned.name} so at least it will give a more
meaningful error.
> "forrest -d" says:
>
> Setting ro project property: plugin.name ->
> org.apache.forrest.plugin.input.projectInfo
> Setting ro project property: plugin.version ->
> Setting ro project property: versioned.name ->
> org.apache.forrest.plugin.input.projectInfo
This I don't understand. The bechaviour should be the same as above. The
relevant portion of the ANT script is at line 337 of targets/plugins.xml
> My forrest.properties says this:
>
> project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> org.apache.forrest.plugin.input.simplifiedDocbook
I assume you get the same behaviour with simplifiedDocbook?
> Out of curiosity, I added the plugin version.
>
> project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> org.apache.forrest.plugin.input.simplifiedDocbook
>
> The debug trace of my build.xml changes to the following, and the
> plugin is successfully installed.
>
> Setting ro project property: plugin.name ->
> org.apache.forrest.plugin.input.projectInfo
> Setting ro project property: plugin.version -> 0.1
> Setting ro project property: versioned.name ->
> org.apache.forrest.plugin.input.projectInfo-0.1
This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314226 ]
Ross Gardler commented on FOR-547:
----------------------------------
Please, by my guest.
On a broader level, *anyone* is welcome to tackle *any* unassigned issue in our tracker. All help is greatly appreciated.
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7-dev
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling
forrest via Ant (forrest.build.xml:site)
Posted by "Ben Litchfield (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12369244 ]
Ben Litchfield commented on FOR-547:
------------------------------------
Potentially related to some issues people are describing here, I had an issue where I used ANT integration and my build.xml already had an 'init' target defined so the forrest one was not getting called, which meant that a bunch of forrest properties were not getting set correctly.
https://issues.apache.org/jira/browse/FOR-823
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "Ron Blaschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314204 ]
Ron Blaschke commented on FOR-547:
----------------------------------
Sorry about the link, looks like it got truncated.
Yes, the issue still exists with rc3. The simple workaround is to call "forrest init-plugins", which installs the plugins correctly.
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7-dev
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "Ron Blaschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314950 ]
Ron Blaschke commented on FOR-547:
----------------------------------
The problem seems to be caused by ant-contrib-1.0b1. Once I removed the jar from my classpath, the ant script worked fine. Even better, ant-contrib-1.0b2 doesn't seem to cause any problems.
It can easily reproduced by copying ant-contrib-1.0b1.jar to %FORREST_HOME%\lib\endorsed, any running forrest init-plugins, with a plugin missing.
I guess the FAQ should contain a warning for ant-contrib-1.0b1, and this issue can be closed.
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314195 ]
David Crossley commented on FOR-547:
------------------------------------
Your intial report was for release candidate rc1 which had known problems. Do you still see issues with rc3?
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7-dev
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314194 ]
David Crossley commented on FOR-547:
------------------------------------
That link is broken, so here ...
http://marc.theaimsgroup.com/?t=111896538200004
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7-dev
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "Ron Blaschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314224 ]
Ron Blaschke commented on FOR-547:
----------------------------------
Should I tackle this issue? You probably have more important things to worry about. ;-)
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7-dev
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "Ron Blaschke (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314004 ]
Ron Blaschke commented on FOR-547:
----------------------------------
Here's the thread in the mailing list archive.
http://mail-archives.apache.org/mod_mbox/forrest-dev/200506.mbox/%3c1324704355.20050616231233@rblasch.org%3e
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7-dev
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314209 ]
Ross Gardler commented on FOR-547:
----------------------------------
Thanks for the workaround Ron.
I've looked into this issue a little, it appears to be some strange side effect of using "ant" instead of "forrest". I'm starting to think it is actually a bug in ANT not Forrest, but cannot confirm that yet.
> Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
> -------------------------------------------------------------------------------
>
> Key: FOR-547
> URL: http://issues.apache.org/jira/browse/FOR-547
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7-dev
> Environment: Windows XP, SP2
> Ant 1.6.5
> Forrest 0.7rc1
> Reporter: Ron Blaschke
> Priority: Minor
>
> I have an Ant script, which imports forrest.build.xml. When calling the site target with a missing plugin, the install fails. But "forrest init-plugins" works fine. Also, using versioned plugins works, using the Ant script and "forrest init-plugins"..
> Here's the relevant conversation from forrest-dev.
> Ron Blaschke wrote:
> > Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
> >>Ron Blaschke wrote:
> >>
> >>>Unable to retrieve the ${plugin.name} plugin.
> >>>
> >>>Two noteworthy things: Calling "forrest init-plugins" installs the
> >>>plugin sucessfully. And the error message says "${plugin.name}",
> >>>instead of the real name of the plugin.
> >
> >>The two things are related. It looks like that the {plugin.name} is not
> >>being set for some reason (and I guess {versioned.name} is not set either.
> >
> >>These are set in the init-plugins target of targets/plugins.xml
> >
> > I ran my build.xml with "ant -d," and found the following:
> >
> > Setting ro project property: plugin.name -> ${plugin.name}
> > Setting ro project property: plugin.version -> ${plugin.version}
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> Actually that is as expected. The {plugin.name} and {plugin.version}
> values are set by a regexp looking for the the version number. Since
> there is no version number in the plugin required the regexp fails and
> so no value for the property. The rest of the script tries to get the
> {versioned.name} plugin. If it fails it falls back to the unversioned
> plugin.
> This explains why the error message shows ${plugin.name}, I've changed
> that to use the {versioned.name} so at least it will give a more
> meaningful error.
> > "forrest -d" says:
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version ->
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo
> This I don't understand. The bechaviour should be the same as above. The
> relevant portion of the ANT script is at line 337 of targets/plugins.xml
> > My forrest.properties says this:
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> I assume you get the same behaviour with simplifiedDocbook?
> > Out of curiosity, I added the plugin version.
> >
> > project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
> > org.apache.forrest.plugin.input.simplifiedDocbook
> >
> > The debug trace of my build.xml changes to the following, and the
> > plugin is successfully installed.
> >
> > Setting ro project property: plugin.name ->
> > org.apache.forrest.plugin.input.projectInfo
> > Setting ro project property: plugin.version -> 0.1
> > Setting ro project property: versioned.name ->
> > org.apache.forrest.plugin.input.projectInfo-0.1
> This looks like the behaviour expected.
--
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