headers
David Crossley (JIRA | 1 May 2010 08:25
Picon
Favicon

[jira] Commented: (FOR-1123) use Apache Ivy for dependency management


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

David Crossley commented on FOR-1123:
-------------------------------------

Another useful forrest-dev thread, where Carsten explains that Forrest does not need to use Maven just
because Cocoon uses Maven.

Re: cocoon 2.2, dispatcher and blocks
http://thread.gmane.org/gmane.text.xml.forrest.devel/25135/focus=25155
2007-11-07

> use Apache Ivy for dependency management
> ----------------------------------------
>
>                 Key: FOR-1123
>                 URL: https://issues.apache.org/jira/browse/FOR-1123
>             Project: Forrest
>          Issue Type: Task
>          Components: Compile
>            Reporter: David Crossley
>
> Some time ago we decided to use Ivy. Work was commenced in a branch, but lost momentum. We decided to
commence in our trunk, and expand its use gradually.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 1 May 2010 08:45
Picon
Favicon

[jira] Created: (FOR-1191) Cocoon Blocks need separate release procedure

Cocoon Blocks need separate release procedure
---------------------------------------------

                 Key: FOR-1191
                 URL: https://issues.apache.org/jira/browse/FOR-1191
             Project: Forrest
          Issue Type: Sub-task
          Components: Other
            Reporter: David Crossley

Some Cocoon Blocks have started in the Forrest whiteboard.

These need a well-defined release procedure, voting, and such.

Anything that goes beyond this developer group needs to be properly released.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 1 comment |
headers
David Crossley (JIRA | 1 May 2010 08:51
Picon
Favicon

[jira] Commented: (FOR-1191) Cocoon Blocks need separate release procedure


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

David Crossley commented on FOR-1191:
-------------------------------------

Some links:

More info at http://apache.org/dev/#releases                                                                                   
Especially: http://apache.org/dev/release.html#what

Re: Release-related issues
http://thread.gmane.org/gmane.text.xml.forrest.devel/27517/focus=27529
2009-12-07

Re: cocoon 2.2, dispatcher and blocks
http://thread.gmane.org/gmane.text.xml.forrest.devel/25135/focus=25155
2007-11-07

> Cocoon Blocks need separate release procedure
> ---------------------------------------------
>
>                 Key: FOR-1191
>                 URL: https://issues.apache.org/jira/browse/FOR-1191
>             Project: Forrest
>          Issue Type: Sub-task
>          Components: Other
>            Reporter: David Crossley
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley (JIRA | 1 May 2010 08:59
Picon
Favicon

[jira] Created: (FOR-1192) Cocoon Blocks need specific mention of licenses and notices for supporting products

Cocoon Blocks need specific mention of licenses and notices for supporting products
-----------------------------------------------------------------------------------

                 Key: FOR-1192
                 URL: https://issues.apache.org/jira/browse/FOR-1192
             Project: Forrest
          Issue Type: Sub-task
          Components: Project administration
            Reporter: David Crossley

The rest of Forrest uses a manual license system where we have a *.license.txt file for each supporting
product and we add its license to top-level LICENSE.txt and any required notices in NOTICE.txt (See FOR-855).

These Cocoon Blocks will need to follow that system until we get a better overall way of handling it.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 0 comments |
headers
Forrestbot | 1 May 2010 16:18
Picon

ForrestBot build for forrest-docs FAILED

Automated build for forrest-docs FAILED
Log attached.

----------
Forrestbot run ended at 01 May 02:18 PM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
----------

     [echo] 
          ....... Forrest render START 2010-05-01 02:10:09
          ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-docs
        

check-java-version:
     [echo] This is apache-forrest-0.9-dev
     [echo] Using Java 1.5 from /usr/jdk/instances/jdk1.5.0/jre
     [echo] Using Apache Ant version 1.7.1 compiled on September 26 2008 from /export/opt/forrest-trunk/tools/ant

init-props:
    [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-docs/tmp

echo-settings-condition:

echo-settings:

check-skin:

init-proxy:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Forrestbot | 4 May 2010 04:15
Picon

ForrestBot build for forrest-docs FAILED

Automated build for forrest-docs FAILED
Log attached.

----------
Forrestbot run ended at 04 May 02:15 AM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
----------

     [echo] 
          ....... Forrest render START 2010-05-04 02:10:10
          ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-docs
        

check-java-version:
     [echo] This is apache-forrest-0.9-dev
     [echo] Using Java 1.5 from /usr/jdk/instances/jdk1.5.0/jre
     [echo] Using Apache Ant version 1.7.1 compiled on September 26 2008 from /export/opt/forrest-trunk/tools/ant

init-props:
    [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-docs/tmp

echo-settings-condition:

echo-settings:

check-skin:

init-proxy:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Forrestbot | 4 May 2010 22:13
Picon

ForrestBot build for forrest-docs FAILED

Automated build for forrest-docs FAILED
Log attached.

----------
Forrestbot run ended at 04 May 08:13 PM
Using Forrest 0.9-dev
Forrestbot administrator: Forrest developers
----------

     [echo] 
          ....... Forrest render START 2010-05-04 08:10:06
          ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-docs
        

check-java-version:
     [echo] This is apache-forrest-0.9-dev
     [echo] Using Java 1.5 from /usr/jdk/instances/jdk1.5.0/jre
     [echo] Using Apache Ant version 1.7.1 compiled on September 26 2008 from /export/opt/forrest-trunk/tools/ant

init-props:
    [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-docs/tmp

echo-settings-condition:

echo-settings:

check-skin:

init-proxy:
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Crossley | 5 May 2010 03:19
Picon
Favicon

issues with PDF plugin (Was: For input string: ":0")

(Moved from "user" list. Please see background in thread
Subject: For input string: ":0"
http://thread.gmane.org/gmane.text.xml.forrest.user/4903)

more below ...

Richard Suematsu wrote:
> 
> Ok, I must be doing something wrong because I tried this on my mac at
> home and I get the same error.  Let me just verify one thing -- I
> should be checking out forrest from here:
> 
> svn co http://svn.apache.org/repos/asf/forrest/trunk forrest

Yes, correct.

> I turned on debugging on the log and nothing obvious came out like an
> exception.

My memory is failing. I can get raised logging for forrest
in general, but not getting pdf log messages. How is it done?

>  I did get a userconfig is null error in the middle of a
> bunch of stuff.  Is this a clue?

It is configured as null. It is optional.

Because the updated PDF Plugin has not been properly
deployed to the Forrest website, you can only view its
documentation locally:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sjur Moshagen | 7 May 2010 13:59
Picon

ElemTemplateElement error: carry-body-attribs caused by r887050

Hello all,

I'm not able to build my site anymore, due to the following error:

X [0]                                     linkmap.html	BROKEN: ElemTemplateElement error: carry-body-attribs

I was finally able to track down the cause of the error being the commit r887050. I haven't identified this
earlier since I hadn't been updating my Forrest instance in a while, and then didn't have time to track down
the error earlier.

Tracking down ... that's kind of an overstatement, since the actual bug is not found. The thing is, this bug
does NOT display using a regular seed. I can only trigger this bug using my own site. And this commit was a
massive one, with 47 files being modified. But grepping for carry-body-attribs, there are only two
matches among the modified files:

a83-245-189-120:main sjur$ grep -r 'carry-body-attribs' * | grep -v '\.svn' | cut -d':' -f1 | sort -u
webapp/skins/common/xslt/html/document-to-html.xsl  <--- not modified
webapp/skins/common/xslt/html/site-to-xhtml.xsl     <--- not modified
webapp/skins/pelt/xslt/html/document-to-html.xsl
webapp/skins/pelt/xslt/html/site-to-xhtml.xsl

and the only changes to these two files are:

a83-245-189-120:main sjur$ svn diff -c 887050 webapp/skins/pelt/xslt/html/document-to-html.xsl
Index: webapp/skins/pelt/xslt/html/document-to-html.xsl
===================================================================
--- webapp/skins/pelt/xslt/html/document-to-html.xsl	(revision 887049)
+++ webapp/skins/pelt/xslt/html/document-to-html.xsl	(revision 887050)
 <at>  <at>  -20,7 +20,7  <at>  <at> 
 imported document-to-html.xsl for details.
(Continue reading)

Permalink | Reply | 12 comments |
headers
David Crossley | 12 May 2010 00:48
Picon
Favicon

Subversion client configuration (Was: svn commit: r941344 ...common/html/helper-copyover.contract.xml

Thorsten, it seems that your Subversion client has configuration problems.
Missing eol-style and should not be executable.

See:
http://apache.org/dev/#svn
http://apache.org/dev/version-control.html#https-svn-config

-David

> Author: thorsten
> Date: Wed May  5 15:28:14 2010
> New Revision: 941344
> 
> URL: http://svn.apache.org/viewvc?rev=941344&view=rev
> Log:
> adding helper to copy the input
> 
> Added:
>    
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/resource/themer/themes/common/html/helper-copyover.contract.xml
  (with props)
> 
> Added: forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/resource/themer/themes/common/html/helper-copyover.contract.xml
> URL: http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/resource/themer/themes/common/html/helper-copyover.contract.xml?rev=941344&view=auto
> ==============================================================================
> ---
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/resource/themer/themes/common/html/helper-copyover.contract.xml (added)
>
[snip ]
>
(Continue reading)

Permalink | Reply | 1 comment |

Gmane