You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "David Crossley (JIRA)" <ji...@apache.org> on 2011/01/09 11:15:45 UTC

[jira] Commented: (FOR-1187) upgraded PDF plugin was not deployed properly

    [ https://issues.apache.org/jira/browse/FOR-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979286#action_12979286 ] 

David Crossley commented on FOR-1187:
-------------------------------------

In this case it does not actually matter. The PDF plugin is the only plugin that is shipped as source along with a Forrest release. So forrest uses its own local version and all is okay.

I tested with a Forrest-0.8 release and with a Forrest-0.7 release (remember with 0.7 to declare the specific ...pdf-0.1 version of the plugin in the project's forrest.properties file) and pdf production does work properly.

Also did a test with a fresh Forrest-0.8 release, by removing the local plugins/org.apache.forrest.plugin.output.pdf directory. The seed site build then proceeded as expected: downloaded the old currently deployed plugin from f.a.o from the plugins/0.8 directory, and the PDFs are okay.

So i think that what is now needed, is to deploy a versioned (0.2) zip from an old svn trunk. I will keep notes of what i do because i am a bit unsure about plugin deployment process. It is good to practice on this PDF plugin, as per paragraph 1 of this comment.



> upgraded PDF plugin was not deployed properly
> ---------------------------------------------
>
>                 Key: FOR-1187
>                 URL: https://issues.apache.org/jira/browse/FOR-1187
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugin: output.pdf
>    Affects Versions: 0.7, 0.8
>            Reporter: David Crossley
>            Assignee: David Crossley
>             Fix For: 0.9-dev
>
>
> Around January 2008 the PDF plugin was upgraded, gaining functionality that was only relevant to forrest-0.9-dev. It was re-deployed without changing the version numbers in the plugin descriptor.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.