headers
David Crossley (JIRA | 5 Mar 2013 16:45
Picon
Favicon

[jira] [Commented] (FOR-1193) output.pdf plugin uses special Forrest version of the Cocoon FOP Block, Cocoon-2.1 now has upgraded


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

David Crossley commented on FOR-1193:
-------------------------------------

Our special stuff is not needed anymore. The Cocoon FOP Block has been upgraded to use FOP-1.0 (See COCOON-2295).

So far only done in our "update_cocoon_2.1.12" branch.

We should also be able to upgrade to FOP-1.1

> output.pdf plugin uses special Forrest version of the Cocoon FOP Block, Cocoon-2.1 now has upgraded
> ---------------------------------------------------------------------------------------------------
>
>                 Key: FOR-1193
>                 URL: https://issues.apache.org/jira/browse/FOR-1193
>             Project: Forrest
>          Issue Type: Task
>          Components: Core operations, Plugin: output.pdf
>    Affects Versions: 0.9
>            Reporter: David Crossley
>             Fix For: 0.10-dev
>
>
> Recently the Cocoon-2.1 FOP Block was updated, so we might be able to remove our home-grown version.
> See
>  https://issues.apache.org/jira/browse/COCOON-2289
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 5 Mar 2013 16:19
Picon
Favicon

[jira] [Commented] (FOR-1240) Upgrade packaged Cocoon to 2.1.12


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

David Crossley commented on FOR-1240:
-------------------------------------

https://svn.apache.org/repos/asf/forrest/branches/update_cocoon_2.1.12

Following $FORREST_HOME/etc/cocoon_upgrade/

Not yet done Step 8 or Step 9.

The branch is ready now for people to do further improvements and bug fixing.

When the Cocoon release happens then we can follow the upgrade process again.

> Upgrade packaged Cocoon to 2.1.12
> ---------------------------------
>
>                 Key: FOR-1240
>                 URL: https://issues.apache.org/jira/browse/FOR-1240
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Core operations
>    Affects Versions: 0.10-dev
>            Reporter: David Crossley
>            Priority: Critical
>             Fix For: 0.10-dev
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 5 Mar 2013 16:15
Picon
Favicon

[jira] [Updated] (FOR-1241) round corner PNGs are not being generated in the "update_cocoon_2.1.12" branch


     [
https://issues.apache.org/jira/browse/FOR-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-1241:
--------------------------------

    Attachment: error.txt

Attached is "error.txt" being the trace from one of the corner images.

> round corner PNGs are not being generated in the "update_cocoon_2.1.12" branch
> ------------------------------------------------------------------------------
>
>                 Key: FOR-1241
>                 URL: https://issues.apache.org/jira/browse/FOR-1241
>             Project: Forrest
>          Issue Type: Bug
>          Components: Skins (general issues)
>    Affects Versions: 0.10-dev
>            Reporter: David Crossley
>             Fix For: 0.10-dev
>
>         Attachments: error.txt
>
>
> The generation of the round corner PNGs is not happening in the "update_cocoon_2.1.12" branch:
> "java.lang.ClassCastException: org.apache.batik.dom.GenericElement"

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 5 Mar 2013 16:11
Picon
Favicon

[jira] [Created] (FOR-1241) round corner PNGs are not being generated in the "update_cocoon_2.1.12" branch

David Crossley created FOR-1241:
-----------------------------------

             Summary: round corner PNGs are not being generated in the "update_cocoon_2.1.12" branch
                 Key: FOR-1241
                 URL: https://issues.apache.org/jira/browse/FOR-1241
             Project: Forrest
          Issue Type: Bug
          Components: Skins (general issues)
    Affects Versions: 0.10-dev
            Reporter: David Crossley
             Fix For: 0.10-dev

The generation of the round corner PNGs is not happening in the "update_cocoon_2.1.12" branch:
"java.lang.ClassCastException: org.apache.batik.dom.GenericElement"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 5 Mar 2013 09:08
Picon
Favicon

[jira] [Commented] (FOR-1240) Upgrade packaged Cocoon to 2.1.12


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

David Crossley commented on FOR-1240:
-------------------------------------

I upgraded my Forrest to use current Cocoon-2.1.12-dev and it seems okay (see the abovementioned thread).
This also had upgraded FOP, Batik, etc.

Going to make a branch in Forrest SVN to do this upgrade, then follow on after the Cocoon release.

> Upgrade packaged Cocoon to 2.1.12
> ---------------------------------
>
>                 Key: FOR-1240
>                 URL: https://issues.apache.org/jira/browse/FOR-1240
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Core operations
>    Affects Versions: 0.10-dev
>            Reporter: David Crossley
>            Priority: Critical
>             Fix For: 0.10-dev
>
>
> Cocoon is now preparing to release 2.1.12
> Forrest is already using an older in-development version, so it should be straight-forward.
> Upgrading our dependencies provides a good test of Cocoon and our interactions with it. It would be good
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kristian Waagan (JIRA | 25 Jan 2013 12:13
Picon
Favicon

[jira] [Commented] (FOR-915) changes with PNGs generated on different platforms


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

Kristian Waagan commented on FOR-915:
-------------------------------------

Apache Derby is having this problem for its site, but we've learned to work around it by simply reverting the
changed PNGs after site generation.

> changes with PNGs generated on different platforms
> --------------------------------------------------
>
>                 Key: FOR-915
>                 URL: https://issues.apache.org/jira/browse/FOR-915
>             Project: Forrest
>          Issue Type: Bug
>          Components: Core operations, Skins (general issues)
>    Affects Versions: 0.8, 0.9, 0.10-dev
>            Reporter: Thorsten Scherler
>             Fix For: 0.10-dev
>
>         Attachments: corner-comparison.png, corner.svg
>
>
> http://marc.theaimsgroup.com/?t=115450117900002&r=1&w=2
> > > Modified:
> > >     forrest/site/committed-1.png
> > >     forrest/site/live-sites.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sjur Moshagen | 24 Jan 2013 22:01
Picon

Javascript mime type

Hello,

In the file '$FORREST_HOME/main/webapp/resources.xmap' there's the following match:

      <map:match pattern="**skin/**.js">
        <map:read src="{lm:skin.js.{2}}" mime-type="application/x-javascript" />
      </map:match>

x-javascript looks kind of strange and old. This is what wikipedia has to say about javascript mime type (http://en.wikipedia.org/wiki/Internet_media_type):

«• application/javascript: ECMAScript/JavaScript; Defined in RFC 4329 (equivalent to
application/ecmascript but with looser processing rules) It is not accepted in IE 8 or earlier -
text/javascript is accepted but it is defined as obsolete in RFC 4329. The "type" attribute of the
<script> tag inHTML5 is optional. In practice, ***omitting the media type of JavaScript programs is the
most interoperable solution,*** since all browsers have always assumed the correct default even before HTML5.»

(my emphasis)

If there are no objections, I will just remove the mime type from that (and similar) match(es).

Sjur
Permalink | Reply | 5 comments |
headers
Gump | 23 Jan 2013 05:35
Picon
Favicon

[GUMP <at> vmgump]: Project forrest-test-basic (in module forrest) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project forrest-test-basic has an issue affecting its community integration.
This issue affects 3 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - forrest-test :  Apache Forrest software is a publishing framework that trans...
    - forrest-test-basic :  Apache Forrest software is a publishing framework that trans...
    - forrest-test-deploy-plugins :  Apache Forrest software is a publishing framework that trans...

Full details are available at:
    http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason build failed

The following work was performed:
http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/gump_work/build_forrest_forrest-test-basic.html
Work Name: build_forrest_forrest-test-basic (Type: Build)
Work ended in a state of : Failed
Elapsed: 11 secs
Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true
-Dbuild.sysclasspath=only
-Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sjur Moshagen | 18 Jan 2013 14:04
Picon

Deploying wiki plugin (I can't)

Hello all,

Could some developer be kind and run 'ant deploy' in
$FORREST_HOME/plugins/org.apache.forrest.plugin.input.wiki/ ? I have issues with my own instance
of Forrest, and am not able to get a clean deploy through. There should be no issues with the plugin though.

I need the latest dev version of that plugin online as soon as possible, so that I can start to rely on the
availability of the new features for my colleagues.

Thanks a lot in advance,
Sjur
Permalink | Reply | 1 comment |
headers
Sjur Moshagen | 15 Jan 2013 20:49
Picon

Suggested changes to wiki plugin

Hi all,

I needed to fix some bugs (or missing features) in the wiki plugin, to better cope with the jspwiki format. So
far I have only stored the changes locally in my project folder (thus the previous commit to fix the
locationmap for finding resource files). Now I would like to move the changes to the plugin, but there are
one change that I would like feedback on before I do this.

The changes I have made are these:

* I added support for formatting and links within table cells, so that tables now should behave as the
jspwiki spec [1] says
* I added support for definition lists (terms + definition), but *NOT* in accordance with the jspwiki spec

The reason for not following the spec was that I could not get the Chaperon grammar (which is used to parse the
jspwiki document and convert it to xml) to accept the syntax used by jspwiki. I don't know why, but to me it
looks like a bug in the Chaperon lexer.

The jspwiki syntax is:

; Term : definition

My syntax is:

#; Term
##: definition

Not as elegant, but it works, and my implementation allows for links, formatting and breaks within the
definition (which should be in accordance with the jspwiki syntax).

Now the question(s):
(Continue reading)

Permalink | Reply | 3 comments |
headers
David Crossley (JIRA | 11 Jan 2013 06:24
Picon
Favicon

[jira] [Commented] (FOR-1235) Gump cannot find plugins


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

David Crossley commented on FOR-1235:
-------------------------------------

See r1425266 which added a "gump-plugins" target to our build which deploys the needed plugins. Declare
any future others here.

See r1425427 which forces gump to use those.

                
> Gump cannot find plugins
> ------------------------
>
>                 Key: FOR-1235
>                 URL: https://issues.apache.org/jira/browse/FOR-1235
>             Project: Forrest
>          Issue Type: Bug
>          Components: Compile, Plugins (general issues)
>    Affects Versions: 0.10-dev
>            Reporter: David Crossley
>
> Apache Gump has trouble finding our plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
(Continue reading)

Permalink | Reply | 0 comments |

Gmane