from:"Brian M Dube"


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

Brian M Dube commented on FOR-1251:
---

Fixed in https://github.com/apache/infrastructure-puppet/pull/16.

Waiting for next puppet update.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected


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

Brian M Dube commented on FOR-1251:
---

A few more changes in addition to that pull request and now we're in business.

Docroot is now /var/www/forrest with ownership forrest_role:www-data.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected


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

Brian M Dube commented on FOR-1251:
---

Things are somewhat configured for user forrest_role now, with some uncommitted 
changes in ~forrest_role/config. A crontab is back in place but the forrestbot 
items are commented out. I can't tell what files are expected to be present for 
the run-forrestbot.sh calls to function properly.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected


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

Brian M Dube commented on FOR-1251:
---

Changes committed in r1710883 and r1710885.

Forrestbot items in crontab reactivated.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

2015-09-16 Thread Brian M Dube (JIRA)


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

Brian M Dube commented on FOR-1251:
---

I had symlinked our vhost DocumentRoot /var/www to ~forrest/htdocs but the next 
automatic puppet run blew away the symlink and recreated the empty directory 
/var/www.

We can create a pull request to change our DocumentRoot in puppet, but what 
I've done for now is change the user:group of /var/www to forrest:forrest and 
'svn checkout' the zone/htdocs repository there, with a symlink as 
~forrest/htdocs back to /var/www. As long as puppet doesn't change the 
ownership of /var/www then I think this will work without a pull request.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

2015-09-16 Thread Brian M Dube (JIRA)


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

Brian M Dube commented on FOR-1251:
---

Puppet does manage ownership of /var/www. So the proposed fix in my last 
comment will not work without a pull request.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

2015-09-15 Thread Brian M Dube (JIRA)


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

Brian M Dube commented on FOR-1251:
---

Be aware, the scripts in ~forrest/config are somewhat broken at the moment. 
Since it is a svn working copy, you can see what has been changed.

An approach for the future would be to source the binary paths from one 
canonical script or just ensure that $PATH enforces the correct choices when 
using bare binary names.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FOR-1228) I'd like to "help" develop on this project ... currently a java developer...

2015-09-13 Thread Brian M Dube (JIRA)


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

Brian M Dube closed FOR-1228.
-
Resolution: Invalid

If this isn't spam, join us on the mailing list to help with the project.

> I'd like to "help"  develop on this project ... currently a java developer...
> -
>
> Key: FOR-1228
> URL: https://issues.apache.org/jira/browse/FOR-1228
> Project: Forrest
>  Issue Type: Task
>  Components: Other
>Reporter: forrTann
>Priority: Minor
> Fix For: 0.12
>
>
> I'd like someone to email me in order to begin helping on this project.
> thx



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FOR-1254) Update documentation for project virtual machine

2015-09-13 Thread Brian M Dube (JIRA)

Brian M Dube created FOR-1254:
-

 Summary: Update documentation for project virtual machine
 Key: FOR-1254
 URL: https://issues.apache.org/jira/browse/FOR-1254
 Project: Forrest
  Issue Type: Task
  Components: zones.a.o administration
Reporter: Brian M Dube
Priority: Minor


Find all documentation referencing FreeBSD jails and Solaris zones and update 
it for the new virtual machine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

2015-09-08 Thread Brian M Dube (JIRA)


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

Brian M Dube commented on FOR-1251:
---

The paths in ~forrest/config/*.sh scripts need to be updated to work in the new 
environment.

I'm disabling the forrest user crontab on the old zone at this time.

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

2015-09-08 Thread Brian M Dube (JIRA)


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

Brian M Dube reassigned FOR-1251:
-

Assignee: Brian M Dube

> ensure that the new ASF machine for forrest-zones jail works as expected
> 
>
> Key: FOR-1251
> URL: https://issues.apache.org/jira/browse/FOR-1251
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: David Crossley
>Assignee: Brian M Dube
>
> ASF Infra are decommissioning "sigyn" which hosts the Forrest project's build 
> and demo server.
> We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

2015-04-08 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486304#comment-14486304
 ] 

Brian M Dube commented on FOR-1251:
---

The packages and vm specs look fine to me.

 ensure that the new ASF machine for forrest-zones jail works as expected
 

 Key: FOR-1251
 URL: https://issues.apache.org/jira/browse/FOR-1251
 Project: Forrest
  Issue Type: Task
  Components: zones.a.o administration
Reporter: David Crossley

 ASF Infra are decommissioning sign which hosts the Forrest project's build 
 and demo server.
 We have asked for a new VM via the issue INFRA-9093.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: svn commit: r1641160 - /forrest/trunk/site-author/skinconf.xml

2014-11-23 Thread Brian M Dube

On 11/22/2014 09:40 PM, rgard...@apache.org wrote:
 Author: rgardler
 Date: Sun Nov 23 05:40:38 2014
 New Revision: 1641160
 
 URL: http://svn.apache.org/r1641160
 Log:
 Updte MOTD to latest release version, Feb 2011 was quite some time ago :-)

Hi Ross, good to see you again,

It was a long time ago, but v0.9 of 2011 is still the current release
version.

-Brian

 Modified:
 forrest/trunk/site-author/skinconf.xml
 
 Modified: forrest/trunk/site-author/skinconf.xml
 URL: 
 http://svn.apache.org/viewvc/forrest/trunk/site-author/skinconf.xml?rev=1641160r1=1641159r2=1641160view=diff
 ==
 --- forrest/trunk/site-author/skinconf.xml (original)
 +++ forrest/trunk/site-author/skinconf.xml Sun Nov 23 05:40:38 2014
 @@ -104,7 +104,7 @@ See main/fresh-site/src/documentation/sk
motd
  motd-option pattern=index.html starts-with=true
motd-page location=page
 -7 February 2011 : Forrest-0.9 released
 +Latest release: Forrest-0.10
/motd-page
motd-page-urlhttp://forrest.apache.org/mirrors.cgi/motd-page-url
  /motd-option

Re: the forrest.zones jail needs attention

2014-09-14 Thread Brian M Dube

On 09/14/2014 02:08 AM, David Crossley wrote:
 On Wed, Mar 05, 2014 at 04:20:58PM -0800, Brian M Dube wrote:
 On 03/02/2014 11:45 PM, User Forrest wrote:
 At forrest.zones.apache.org

 svn update failed

 See logfile: /home/forrest/config/update-forrest-trunk-2014030307.log

 This is an SSL error. I tried to fix it by installing the port which 
 contains the root CA certificates, but that failed.

 It also looks like the certificate can be manually accepted (presumably 
 once suffices) by the forrest user.
 
 I presume that someone needs to log in, switch to the 'forrest' user [2],
 and probably also do 'svn upgrade' in the relevant directory.

This is done.

-Brian

 Some notes are here:
 [1] https://forrest.apache.org/zone.html
 [2] http://svn.apache.org/repos/asf/forrest/zone/README.txt
 [3] http://www.apache.org/dev/machines.html#jails-tlps (our jail in on sigyn).
 
 I cannot do this at this stage, so hopefully Brian can.
 
 -David

[jira] [Closed] (FOR-1247) Configuration required to override and use X509 from crypto file for Decryption

2014-06-26 Thread Brian M Dube (JIRA)


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

Brian M Dube closed FOR-1247.
-

Resolution: Invalid

No response from reporter. Appears to be filed for the wrong project.

 Configuration required to override and use X509 from crypto file for 
 Decryption
 ---

 Key: FOR-1247
 URL: https://issues.apache.org/jira/browse/FOR-1247
 Project: Forrest
  Issue Type: Improvement
  Components: Core operations
Affects Versions: 0.6
Reporter: Balakrishnan Nagaraja
 Attachments: ws4j - Issue.txt


 When the soap response contains KeyInfo tag, then Key processor extracts 
 X509 cert from SOAP Body. Some times, the servers does not send them. 
 If the Key Info tag is not present, then Key processor extract the cert from 
 the crypto. 
 So need a parameter to over ride to have key processor use the crypto 
 configuration for decryption. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

ApacheCon CFP closes June 25

2014-06-10 Thread Brian M Dube

Apache Forrest enthusiasts,

As you may be aware, ApacheCon will be held this year in Budapest, on
November 17-23. (See http://apachecon.eu for more info.)

The Call For Papers for that conference is still open, but will be
closing soon. We need your talk proposals, to represent Forrest at
ApacheCon. We need all kinds of talks - deep technical talks, hands-on
tutorials, introductions for beginners, or case studies about the
awesome stuff you're doing with Forrest.

Please consider submitting a proposal, at
http://events.linuxfoundation.org//events/apachecon-europe/program/cfp

Thanks!

[jira] [Commented] (FOR-1247) Configuration required to override and use X509 from crypto file for Decryption

2014-05-02 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988373#comment-13988373
 ] 

Brian M Dube commented on FOR-1247:
---

Is this filed for the correct project?

 Configuration required to override and use X509 from crypto file for 
 Decryption
 ---

 Key: FOR-1247
 URL: https://issues.apache.org/jira/browse/FOR-1247
 Project: Forrest
  Issue Type: Improvement
  Components: Core operations
Affects Versions: 0.6
Reporter: Balakrishnan Nagaraja
 Attachments: ws4j - Issue.txt


 When the soap response contains KeyInfo tag, then Key processor extracts 
 X509 cert from SOAP Body. Some times, the servers does not send them. 
 If the Key Info tag is not present, then Key processor extract the cert from 
 the crypto. 
 So need a parameter to over ride to have key processor use the crypto 
 configuration for decryption. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: forrest.zones.a.o : svn update failed

2014-03-05 Thread Brian M Dube


On 03/02/2014 11:45 PM, User Forrest wrote:

At forrest.zones.apache.org

svn update failed

See logfile: /home/forrest/config/update-forrest-trunk-2014030307.log


This is an SSL error. I tried to fix it by installing the port which 
contains the root CA certificates, but that failed.


It also looks like the certificate can be manually accepted (presumably 
once suffices) by the forrest user.


-Brian

[jira] [Commented] (FOR-1234) Dispatcher caches too eagerly

2012-07-15 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414738#comment-13414738
 ] 

Brian M Dube commented on FOR-1234:
---

There is a workaround mentioned in the dispatcher quickstart documentation. 
That is, in your structurer file, to remove the cache settings from:

forrest:structurer xmlns:forrest=http://apache.org/forrest/templates/1.0;
xmlns:jx=http://apache.org/cocoon/templates/jx/1.0;
jx:cache-key=#{$cocoon/parameters/getRequest}

jx:cache-validity=${Packages.org.apache.excalibur.source.impl.validity.NOPValidity()}

to:

forrest:structurer xmlns:forrest=http://apache.org/forrest/templates/1.0;
xmlns:jx=http://apache.org/cocoon/templates/jx/1.0;


 Dispatcher caches too eagerly
 -

 Key: FOR-1234
 URL: https://issues.apache.org/jira/browse/FOR-1234
 Project: Forrest
  Issue Type: Bug
  Components: Whiteboard: Dispatcher (stax)
Affects Versions: 0.9, 0.10-dev
Reporter: Børre Gaup

 When editing content pages in forrest I can't see the changes in the web 
 browser when refreshing the page. I have to restart forrest to see any 
 changes of the content in the browser.
 Here are two threads on the issue:
 http://thread.gmane.org/gmane.text.xml.forrest.user/5034
 http://thread.gmane.org/gmane.text.xml.forrest.devel/27855

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Commented] (FOR-1234) Dispatcher caches too eagerly

2012-07-15 Thread Brian M Dube

On 07/15/2012 12:03 PM, Brian M Dube (JIRA) wrote:
 
 [ 
 https://issues.apache.org/jira/browse/FOR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414738#comment-13414738
  ] 
 
 Brian M Dube commented on FOR-1234:
 ---
 
 There is a workaround mentioned in the dispatcher quickstart documentation. 
 That is, in your structurer file, to remove the cache settings from:
 
 forrest:structurer xmlns:forrest=http://apache.org/forrest/templates/1.0;
 xmlns:jx=http://apache.org/cocoon/templates/jx/1.0;
 jx:cache-key=#{$cocoon/parameters/getRequest}
 
 jx:cache-validity=${Packages.org.apache.excalibur.source.impl.validity.NOPValidity()}
 
 to:
 
 forrest:structurer xmlns:forrest=http://apache.org/forrest/templates/1.0;
 xmlns:jx=http://apache.org/cocoon/templates/jx/1.0;

It seems the documentation for this plugin is not available on the
Forrest website. Is 'ant deploy-docs' from the plugin directory the
correct thing to do?

Brian

Re: [VOTE] re-release version 0.9

2012-04-14 Thread Brian M Dube

+1
md5$ 2bc9e0b220f8ec5bc1f228dbc3023e0e apache-forrest-0.9-sources.tar.gz

-Brian

Re: problem with our forrest.zones.apache.org

2012-04-05 Thread Brian M Dube

On 04/05/2012 07:03 PM, Brian M Dube wrote:
 On 04/04/2012 09:51 PM, David Crossley wrote:
 The Forrest jail web server is not reachable.
 For http://forrest.zones.apache.org/
 ... The connection has timed out

 Someone needs to ssh in and see what is happening.
 
 I've restarted httpd and it is again serving requests. I don't have much
 time to investigate, but I did find this:
 
 [Tue Mar 06 10:11:48 2012] [notice] caught SIGTERM, shutting down
 
 I don't immediately see a cause for that and I'm out of time for today.

I didn't look at the date in that log message closely enough. That's
when the jail last booted. So httpd has apparently been down since then.

 
 -Brian
 
 http://forrest.apache.org/zone.html

 -David

Re: [jira] Subscription: FOR-open-with-patch

2011-12-11 Thread Brian M Dube

Hi,

Does anyone else get the list below automatically emailed? I don't
remember subscribing to it, and I don't see where to turn it off in Jira.

-Brian

On 12/11/2011 04:30 AM, j...@apache.org wrote:
 Issue Subscription
 Filter: FOR-open-with-patch (10 issues)
 Subscriber: rgardler
 
 Key Summary
 FOR-652 CSS Style Sheets need cleanup, optimization and better naming of 
 elements
 https://issues.apache.org/jira/browse/FOR-652
 FOR-211 whole-site html and pdf: broken ext links
 https://issues.apache.org/jira/browse/FOR-211
 FOR-412 use CSS for displaying list of Changes
 https://issues.apache.org/jira/browse/FOR-412
 FOR-969 Add sensible site navigation in DOAP plugin
 https://issues.apache.org/jira/browse/FOR-969
 FOR-355 Improved PDF configurability (e.g., TOC, Page Numbers, logo)
 https://issues.apache.org/jira/browse/FOR-355
 FOR-998 [PATCH] Resolve empty cells.
 https://issues.apache.org/jira/browse/FOR-998
 FOR-311 OOo Headings bug causes Forrest to fail
 https://issues.apache.org/jira/browse/FOR-311
 FOR-934 i18n language override menu
 https://issues.apache.org/jira/browse/FOR-934
 FOR-280 gather index terms from documents to create index page with links
 https://issues.apache.org/jira/browse/FOR-280
 FOR-795 Navigation bars for easy access in long documents
 https://issues.apache.org/jira/browse/FOR-795

[jira] [Closed] (FOR-1229) add Techsol to list of example skinned Web sites

2011-10-21 Thread Brian M Dube (Closed) (JIRA)


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

Brian M Dube closed FOR-1229.
-

Resolution: Fixed

Added example site. Thanks.

 add Techsol to list of example skinned Web sites
 

 Key: FOR-1229
 URL: https://issues.apache.org/jira/browse/FOR-1229
 Project: Forrest
  Issue Type: Task
  Components: Example Sites
Reporter: Brolin Empey

 URL: http://techsol.ca/
 Name: Technical Solutions Inc. DBA Techsol
 Catch phrase: Techsol is a North American (NAFTA) corporation providing 
 low-cost outsourcing of your embedded product, or ZigBee wireless adapter, 
 design and board fabrication.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (FOR-1230) add Techsol's Medallion System to list of example skinned Web sites

2011-10-21 Thread Brian M Dube (Closed) (JIRA)


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

Brian M Dube closed FOR-1230.
-

Resolution: Fixed

Added example site. Thanks.

 add Techsol's Medallion System to list of example skinned Web sites
 ---

 Key: FOR-1230
 URL: https://issues.apache.org/jira/browse/FOR-1230
 Project: Forrest
  Issue Type: Task
  Components: Example Sites
Reporter: Brolin Empey

 URL: http://medallionsystem.com/
 Name: Techsol's Medallion System
 Catch phrase: Techsol's embedded computer products division specialises on 
 Linux on ARM technology.
 Techsol's Medallion System should be listed after Techsol because it 
 references Techsol.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FOR-1227) Not correctly displayed Cyrillic

2011-08-17 Thread Brian M Dube (JIRA)

[
https://issues.apache.org/jira/browse/FOR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086786#comment-13086786
]

Brian M Dube commented on FOR-1227:
---

Can you tell what code point is being used for И in your file? When I view a
hex dump of a source file that works for me, 0xd098 corresponds to И in my
file. Is it the same for you?

You're on Win 7; are you using Cygwin to run Forrest?

Not correctly displayed Cyrillic

Key: FOR-1227
URL: https://issues.apache.org/jira/browse/FOR-1227
Project: Forrest
Issue Type: Bug
Components: XML grammars validation
Affects Versions: 0.9
Reporter: Aleksander
Priority: Minor
Attachments: screenshot-1.jpg

Eng:
Hello dear developers. Not correctly displayed only one letter in the
Cyrillic alphabet - capital letter И (
http://en.wikipedia.org/wiki/I_(Cyrillic) ) (#1048;, #x0418;). Her small
version has no such problems. The letter appears as a character. I apologize
for my English.
Rus:
Здравствуйте уважаемые разработчики. Не корректно отображается всего одна
буква в кириллице - заглавная буква И (
http://en.wikipedia.org/wiki/I_(Cyrillic) )(#1048;, #x0418;). Её маленький
вариант таких проблем не имеет. Буква отображается в виде символов. Прошу
прощения за мой английский язык.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FOR-1227) Not correctly displayed Cyrillic

2011-08-12 Thread Brian M Dube (JIRA)

[
https://issues.apache.org/jira/browse/FOR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084136#comment-13084136
]

Brian M Dube commented on FOR-1227:
---

Hello, this letter appears correctly for me on Linux OpenJDK 6. Curious that
only one letter is affected.

Not correctly displayed Cyrillic

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: forrest-osgi

2011-06-25 Thread Brian M Dube

On Fri, Jun 24, 2011 at 04:38:25PM -0400, Tim Williams wrote:
 I finally checked this out and ran into a couple snags.
 
 o) I had to create empty ./src/test directories in all the bundle
 packages.  I didn't look into it as I just wanted to get running.  If
 that's correct, I'm happy to check it in.

It does appear I broke the build before I had to move on to other
things. Sorry about that. The build process could be improved to check
for these directories, but checking them in gets it done, too.

 o) It seemed to want forrest.build.xml in $FORREST_HOME/main instead
 of directly in $FORREST_HOME

I've run into that when forrest/bin/forrest gets called instead of
whiteboard/forrest-osgi/bin/forrest, due to $FORREST_HOME or $PATH not
being reset for forrest-osgi work.

Thanks for looking at it.

-Brian

Re: Getting started with submodules

2011-06-25 Thread Brian M Dube

On Wed, May 18, 2011 at 06:59:05PM -0700, Brian M Dube wrote:
 I have some of the build working with Apache EasyAnt (for
 forrest-osgi). If there is a response on their list, I'll follow up
 with some questions and pursue it further.

There was a response.

Date: Mon, 6 Jun 2011 17:19:01 +0200
Subject: Re: Getting started with submodules
Message-ID: BANLkTi=1mkfj3vckf6noybdbejs3dub...@mail.gmail.com

The solution is likely to involve writing a new OSGi plugin for Apache
EasyAnt. I won't have the time to investigate that option for a while.

-Brian

Re: Getting started with submodules

2011-05-18 Thread Brian M Dube

I have some of the build working with Apache EasyAnt (for
forrest-osgi). If there is a response on their list, I'll follow up
with some questions and pursue it further.

-Brian

managing dependencies

2011-05-18 Thread Brian M Dube

On Sat, Apr 30, 2011 at 04:44:52PM +1000, David Crossley wrote:
 We are going to have the continued problem of management
 of dependencies and supporting products.
 
 There is the new project EasyAnt coming through the
 Apache Incubator. 

I've joined their dev list and I'm experimenting with the product,
with some success.

I see that Cocoon 2.1.11 and blocks are available in Maven
repositories and thus accessible to Ivy / EasyAnt. Is stepping back to
that version from 2.1.12-dev an acceptable approach if it means a
dependency management tool could be used? Thoughts?

-Brian

Getting started with submodules

2011-05-15 Thread Brian M Dube

Hello,

I'm experimenting with EasyAnt for the OSGi implementation of Apache
Forrest [1] which consists of about a dozen submodules. Right now each
submodule contains its own Ant build file which can be called directly
or from build.xml at [1].

The submodule build files use the bnd task to create OSGi bundles from
the sources. Is this setup a good candidate for EasyAnt? Is a plugin
already available for creating OSGi bundles?

-Brian

[1] https://svn.apache.org/repos/asf/forrest/trunk/whiteboard/forrest-osgi/

Re: git-svn and svn properties (Re: svn commit: r1096401)

2011-04-30 Thread Brian M Dube

On Tue, Apr 26, 2011 at 03:59:44PM +1000, David Crossley wrote:
 Brian M Dube wrote:
   Author: bdube
   Date: Mon Apr 25 02:56:52 2011
   New Revision: 1096401
   
   URL: http://svn.apache.org/viewvc?rev=1096401view=rev
   Log:
   Follow r1096394 (git-svn) with svn:ignore and svn:eol-style
  
  Does anyone know a better way?
 
 The infrastructure-dev mail list is for
 discussion of future tools etc. Various topics
 releated to git are happening. 
 
 http://apache.org/dev/infra-mail.html

Ah, from that discussion I learned that git-svn is supposed to use and
respect the configuration settings of my svn installation. I found
that my settings had lost the additions from

http://www.apache.org/dev/svn-eol-style.txt

at some point. I've added these again and I'll see how it goes the
next time I commit with new files.

-Brian

Re: svn commit: r1097721 - /forrest/trunk/whiteboard/forrest-osgi/conf/default-forrest.properties

2011-04-29 Thread Brian M Dube

On Fri, Apr 29, 2011 at 08:11:17AM -, cross...@apache.org wrote:
 Modified:
 forrest/trunk/whiteboard/forrest-osgi/conf/default-forrest.properties
 
 -project.content-dir=src/documentation
 +project.content-dir=docs/src/documentation

Hmm was something not working correctly for you? docs is one project,
with its own forrest.properties; why this change in the default file?

-Brian

Re: new whiteboard experiment, OSGi style

2011-04-28 Thread Brian M Dube

On Thu, Apr 28, 2011 at 07:47:35PM +1000, David Crossley wrote:
 Wow, Brian, very exiting. I have read though the
 docs and will investigate soon.

Great, thanks. I'll gladly expand the documentation based on any
questions.

-Brian

Re: new whiteboard experiment, OSGi style

2011-04-26 Thread Brian M Dube

On Mon, Apr 25, 2011 at 10:08:22PM -0700, Brian M Dube wrote:
 On Sun, Apr 24, 2011 at 07:20:09PM -0700, Brian M Dube wrote:
  There is a new whiteboard experiment in r1096394.
 
 It seems there are still issues with Java 5. Java 6 works for me on
 Ubuntu.

Now Java 5 works for me.

-Brian

Re: new whiteboard experiment, OSGi style

2011-04-25 Thread Brian M Dube

On Sun, Apr 24, 2011 at 07:20:09PM -0700, Brian M Dube wrote:
 There is a new whiteboard experiment in r1096394.
 
 It is briefly documented in whiteboard/forrest-osgi/docs. Note that
 the Forrest project in docs is a normal 0.9 or 0.10-dev project. You
 do not need forrest-osgi to read it.

It seems there are still issues with Java 5. Java 6 works for me on
Ubuntu.

-Brian

new whiteboard experiment, OSGi style

2011-04-24 Thread Brian M Dube

There is a new whiteboard experiment in r1096394. [1]

It is briefly documented in whiteboard/forrest-osgi/docs. Note that
the Forrest project in docs is a normal 0.9 or 0.10-dev project. You
do not need forrest-osgi to read it.

-Brian

[1] http://svn.apache.org/viewvc?view=revisionrevision=1096394

git-svn and svn properties (Re: svn commit: r1096401)

2011-04-24 Thread Brian M Dube

On Mon, Apr 25, 2011 at 02:56:54AM -, bd...@apache.org wrote:
 Author: bdube
 Date: Mon Apr 25 02:56:52 2011
 New Revision: 1096401
 
 URL: http://svn.apache.org/viewvc?rev=1096401view=rev
 Log:
 Follow r1096394 (git-svn) with svn:ignore and svn:eol-style

Does anyone know a better way?

-Brian

Re: motd question

2011-04-02 Thread Brian M Dube

On Fri, Apr 01, 2011 at 12:52:41PM +0200, Vicent Mas wrote:
 Hi,
 
 I'm trying to add a motd pane only to the main page of my dispatcher website. 
 Adding the following lines to my pelt-html.content.panel.xml makes the pane 
 to 
 appear in every index.html page of the website:
 
 forrest:contract name=content-motd-page
   forrest:property name=content-motd-page
 motd
   motd-option pattern=index.html
 motd-title/motd-title
 motd-page location=altMy message here./motd-page
   /motd-option
 /motd
   /forrest:property
 /forrest:contract
 
 I've changed the filename of the main page of my website following the
 answer to question 2.13 of the FAQ:
 
 http://forrest.apache.org/docs_0_100/faq.html#defaultStartPage
 
 but I'd rather prefer to achieve my goal giving a proper path to the pattern 
 option of the motd contract. The problem is that the index.xml of the main 
 page is directly under the xdocs folder and I don't know how to be more 
 specific and tell forrest that I don't want the motd to be applied to the 
 index 
 pages of subdirectories under  xdocs. Could someone tell me how to do it, 
 please?

The motd contract uses the XSLT contains() function to determine
whether the motd is displayed for a given path. It does not appear
that the contains() function is intelligent enough to do what you
want. Also, a brief search shows a general lack of support for regular
expressions in XSLT 1.0.

Perhaps the motd could be injected via the Cocoon pipeline, where
regular expressions are supported.

-Brian

Re: Locationmap rewrite example, perhaps zone network glitch

2011-03-28 Thread Brian M Dube

On Fri, Mar 18, 2011 at 05:47:17PM +1100, David Crossley wrote:
Brian M Dube wrote:
David Crossley wrote:
Forrestbot wrote:
[ snip ]
[java] X [0]
/home/forrest/config/forrestbot-trunk/sources/forrest-seed/src/documentation/content/xdocs/rewrite.index
BROKEN: No pipeline matched request:
/home/forrest/config/forrestbot-trunk/sources/forrest-seed/src/documentation/content/xdocs/rewrite.index
[java] java.lang.NullPointerException
[java] at
org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
[ snip ]

I don't know what causes these occasional failures.
Could it be a network glitch on the zone server.
Can Forrest handle it better.
Need to look into the Cocoon logfiles on our zone server.

Need to look soon after the failure, or we temporarily suspend log
pruning. I hadn't noticed how short-lived the logs are until I went to
check on this and noticed the last failure is already pruned.

I updated the f.a.o/zone.html doc to better explain the log files.
Yes the Cocoon ones are of course re-generated on each hourly run.
Perhaps we could add some post-processing to $CONFIG/run-forrestbot.sh
to save the Cocoon logs if there is a non-successful build.

I see nothing revealing in the logs from the last failure.

I modified a local seed to try this link rewriting example with a name
that is known not to resolve to IP, and the failure mode is the same
as we are seeing with the zone. An occasional DNS issue?

Also, the NPE quoted above is resolved for me by adding one check for
null to the Cocoon source. Why it is null for our use case and not for
Cocoon's, I haven't investigated.

-Brian

Re: Locationmap rewrite example, perhaps zone network glitch

2011-03-17 Thread Brian M Dube

On Thu, Feb 24, 2011 at 05:30:48PM +1100, David Crossley wrote:
 Forrestbot wrote:
  [ snip ]
   [java] X [0] 
  /home/forrest/config/forrestbot-trunk/sources/forrest-seed/src/documentation/content/xdocs/rewrite.index
BROKEN: No pipeline matched request: 
  /home/forrest/config/forrestbot-trunk/sources/forrest-seed/src/documentation/content/xdocs/rewrite.index
   [java] java.lang.NullPointerException
   [java] at 
  org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
  [ snip ]
 
 I don't know what causes these occasional failures.
 Could it be a network glitch on the zone server.
 Can Forrest handle it better.
 Need to look into the Cocoon logfiles on our zone server.

Need to look soon after the failure, or we temporarily suspend log
pruning. I hadn't noticed how short-lived the logs are until I went to
check on this and noticed the last failure is already pruned.

-Brian

 -David

[jira] Closed: (FOR-1224) xslt transformation of resume2.xml generates invalid fo file

2011-03-01 Thread Brian M Dube (JIRA)

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

Brian M Dube closed FOR-1224.
-

Resolution: Fixed
Fix Version/s: 0.10-dev

xslt transformation of resume2.xml generates invalid fo file

Key: FOR-1224
URL: https://issues.apache.org/jira/browse/FOR-1224
Project: Forrest
Issue Type: Bug
Components: Plugin: input.Resume
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Priority: Minor
Fix For: 0.10-dev

Attachments: patch.txt

I have customized my web site to include the file resume2.xml from the trunk
I am using forrest-0.9 and I am attempting to transform resume2.xml in jetty
into PDF by clicking on the link with the PDF icon.
I have installed the resume plugin by copying the resume plugin of trunk into
the folder $FORREST_HOME/whiteboard/plugins . There is a tiny potential
version mismatch as my FORREST_HOME is version 0.9 and the plugin is from
trunk.
At the startup of forrest I see this message : No locationmap provided for
plugin org.apache.forrest.plugin.input.Resume
I can see in html the resume2, but once I click on the link for PDF I see
this message : INTERNAL SERVER ERROR ... Error(Unknown location): fo:inline
is not a valid child element of fo:list-block.
I think somewhere in the documentation of forrest there is a paragraph
explaining how to debug transformations, and I googled the error above, some
people say that it happens when an empty ul/ tag is generated in a
transformation ? Not sure.
resume.xml can be transformed into PDF properly.
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.Resume/src/documentation/content/xdocs/resume2.xml

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (FOR-1224) xslt transformation of resume2.xml generates invalid fo file

2011-03-01 Thread Brian M Dube (JIRA)

[
https://issues.apache.org/jira/browse/FOR-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001297#comment-13001297
]

Brian M Dube commented on FOR-1224:
---

Patch reviewed and applied. Thanks.

xslt transformation of resume2.xml generates invalid fo file

Attachments: patch.txt

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] Resolved: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD

2011-02-28 Thread Brian M Dube

On Sun, Feb 27, 2011 at 03:14:22PM -0500, Antoine Levy-Lambert wrote:
 Hello Brian,

Hello,

 In fact there I might enter another bug report, concerning the fact that
 fop chokes on fo output from the resume plugin - at least in one use
 case.

Ah, there is an issue there. Are you familiar with requesting
intermediate formats from Forrest? To get the intermediate xdoc
(resume converted to xdoc in this case), request for example
http://localhost:/resume2.xml which looks ok to me. But then the
fo, http://localhost:/resume2.fo, has issues. I haven't been able
to confirm whether the issue comes from the resume plugin or the pdf
plugin. But thank you for calling this to attention.

 Also, I wonder whether a locationmap.xml under
 whiteboard/plugins/org.apache.plugin/input.Resume is needed ?

The message that no locationmap is present is informational, if I
remember correctly, and is not cause for alarm.

-Brian

 Regards,
 
 Antoine

Re: [jira] Resolved: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD

2011-02-28 Thread Brian M Dube

On Mon, Feb 28, 2011 at 08:15:23PM -0800, Brian M Dube wrote:
 On Sun, Feb 27, 2011 at 03:14:22PM -0500, Antoine Levy-Lambert wrote:
  Hello Brian,
 
 Hello,
 
  In fact there I might enter another bug report, concerning the fact that
  fop chokes on fo output from the resume plugin - at least in one use
  case.
 
 Ah, there is an issue there. Are you familiar with requesting
 intermediate formats from Forrest? To get the intermediate xdoc
 (resume converted to xdoc in this case), request for example
 http://localhost:/resume2.xml which looks ok to me. But then the
 fo, http://localhost:/resume2.fo, has issues. I haven't been able
 to confirm whether the issue comes from the resume plugin or the pdf
 plugin. But thank you for calling this to attention.

Sorry, whether resume or common skin stylesheet.

-Brian

  Also, I wonder whether a locationmap.xml under
  whiteboard/plugins/org.apache.plugin/input.Resume is needed ?
 
 The message that no locationmap is present is informational, if I
 remember correctly, and is not cause for alarm.
 
 -Brian
 
  Regards,
  
  Antoine

[jira] Assigned: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD


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

Brian M Dube reassigned FOR-1223:
-

Assignee: Brian M Dube

 example delivered with resume plugin needs fixing to conform to DTD
 ---

 Key: FOR-1223
 URL: https://issues.apache.org/jira/browse/FOR-1223
 Project: Forrest
  Issue Type: Bug
  Components: Plugins: Potential new
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Assignee: Brian M Dube
Priority: Trivial
 Attachments: patch.txt


 example delivered with resume plugin does not conform with the DTD

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD


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

Brian M Dube updated FOR-1223:
--

Component/s: (was: Plugins: Potential new)
 Plugin: input.Resume

 example delivered with resume plugin needs fixing to conform to DTD
 ---

 Key: FOR-1223
 URL: https://issues.apache.org/jira/browse/FOR-1223
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.Resume
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Assignee: Brian M Dube
Priority: Trivial
 Attachments: patch.txt


 example delivered with resume plugin does not conform with the DTD

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD


[ 
https://issues.apache.org/jira/browse/FOR-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1320#comment-1320
 ] 

Brian M Dube commented on FOR-1223:
---

Patch applied with thanks. I also added some other maintenance changes with the 
patch.

 example delivered with resume plugin needs fixing to conform to DTD
 ---

 Key: FOR-1223
 URL: https://issues.apache.org/jira/browse/FOR-1223
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.Resume
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Assignee: Brian M Dube
Priority: Trivial
 Fix For: 0.10-dev

 Attachments: patch.txt


 example delivered with resume plugin does not conform with the DTD

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD


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

Brian M Dube updated FOR-1223:
--

Fix Version/s: 0.10-dev
   Other Info:   (was: [Patch available])

 example delivered with resume plugin needs fixing to conform to DTD
 ---

 Key: FOR-1223
 URL: https://issues.apache.org/jira/browse/FOR-1223
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.Resume
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Assignee: Brian M Dube
Priority: Trivial
 Fix For: 0.10-dev

 Attachments: patch.txt


 example delivered with resume plugin does not conform with the DTD

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD


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

Brian M Dube closed FOR-1223.
-


 example delivered with resume plugin needs fixing to conform to DTD
 ---

 Key: FOR-1223
 URL: https://issues.apache.org/jira/browse/FOR-1223
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.Resume
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Priority: Trivial
 Fix For: 0.10-dev

 Attachments: patch.txt


 example delivered with resume plugin does not conform with the DTD

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD


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

Brian M Dube resolved FOR-1223.
---

Resolution: Fixed
  Assignee: (was: Brian M Dube)

 example delivered with resume plugin needs fixing to conform to DTD
 ---

 Key: FOR-1223
 URL: https://issues.apache.org/jira/browse/FOR-1223
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.Resume
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Priority: Trivial
 Fix For: 0.10-dev

 Attachments: patch.txt


 example delivered with resume plugin does not conform with the DTD

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-1224) xslt transformation of resume2.xml generates invalid fo file


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

Brian M Dube updated FOR-1224:
--

Component/s: (was: Plugins: Potential new)
 Plugin: input.Resume

 xslt transformation of resume2.xml generates invalid fo file
 

 Key: FOR-1224
 URL: https://issues.apache.org/jira/browse/FOR-1224
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.Resume
Affects Versions: 0.10-dev
Reporter: Antoine Levy-Lambert
Priority: Minor

 I have customized my web site to include the file resume2.xml from the trunk 
 I am using forrest-0.9 and I am attempting to transform resume2.xml in jetty 
 into PDF by clicking on the link with the PDF icon.
 I have installed the resume plugin by copying the resume plugin of trunk into 
 the folder $FORREST_HOME/whiteboard/plugins . There is a tiny potential 
 version mismatch as my FORREST_HOME is version 0.9 and the plugin is from 
 trunk.
 At the startup of forrest I see this message : No locationmap provided for 
 plugin org.apache.forrest.plugin.input.Resume
 I can see in html the resume2, but once I click on the link for PDF I see 
 this message : INTERNAL SERVER ERROR ... Error(Unknown location): fo:inline 
 is not a valid child element of fo:list-block.
 I think somewhere in the documentation of forrest there is a paragraph 
 explaining how to debug transformations, and I googled the error above, some 
 people say that it happens when an empty ul/ tag is generated in a 
 transformation ? Not sure.
 resume.xml can be transformed into PDF properly.
 http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.Resume/src/documentation/content/xdocs/resume2.xml

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (FOR-1222) Upgrade packaged Jetty

2011-02-12 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993858#comment-12993858
 ] 

Brian M Dube commented on FOR-1222:
---

The Ant task was not as helpful. I didn't use it with the upgrade.

To do:
 - upgrading notes, any custom configuration file will need to be upgraded
 - investigate Jetty 7

 Upgrade packaged Jetty
 --

 Key: FOR-1222
 URL: https://issues.apache.org/jira/browse/FOR-1222
 Project: Forrest
  Issue Type: Improvement
  Components: Launch 'forrest run'
Affects Versions: 0.10-dev
Reporter: Brian M Dube

 The packaged version of Jetty can be upgraded.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Issue Comment Edited: (FOR-1222) Upgrade packaged Jetty

2011-02-12 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993858#comment-12993858
 ] 

Brian M Dube edited comment on FOR-1222 at 2/12/11 9:19 AM:


The Ant task was not as helpful. I didn't use it with the upgrade.

To do:
 - upgrading notes, any custom configuration file will need to be upgraded
 - investigate Jetty 7
 - tune configuration: there is output available when starting Jetty like with 
the old version, but it is not being displayed with 'forrest run'
 - tune configuration: logging, tmp file space

  was (Author: brian):
The Ant task was not as helpful. I didn't use it with the upgrade.

To do:
 - upgrading notes, any custom configuration file will need to be upgraded
 - investigate Jetty 7
  
 Upgrade packaged Jetty
 --

 Key: FOR-1222
 URL: https://issues.apache.org/jira/browse/FOR-1222
 Project: Forrest
  Issue Type: Improvement
  Components: Launch 'forrest run'
Affects Versions: 0.10-dev
Reporter: Brian M Dube

 The packaged version of Jetty can be upgraded.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[RT] Forrest v1.0

2011-02-12 Thread Brian M Dube

Do we have a set of enumerated requirements for Forrest v1.0? Can or
should the next release fit these requirements? Thoughts?

I'm trying to avoid in this thread the community health discussion
that is likely to arise; not suppress that discussion, just a
preference for a different thread.

-Brian

[jira] Created: (FOR-1221) Upgrade packaged Batik

2011-02-08 Thread Brian M Dube (JIRA)

Upgrade packaged Batik
--

 Key: FOR-1221
 URL: https://issues.apache.org/jira/browse/FOR-1221
 Project: Forrest
  Issue Type: Improvement
  Components: Core operations
Affects Versions: 0.10-dev
Reporter: Brian M Dube


The packaged version of Batik can be upgraded.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (FOR-1222) Upgrade packaged Jetty

2011-02-08 Thread Brian M Dube (JIRA)

Upgrade packaged Jetty
--

 Key: FOR-1222
 URL: https://issues.apache.org/jira/browse/FOR-1222
 Project: Forrest
  Issue Type: Improvement
  Components: Launch 'forrest run'
Affects Versions: 0.10-dev
Reporter: Brian M Dube


The packaged version of Jetty can be upgraded.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (FOR-1222) Upgrade packaged Jetty

2011-02-08 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992330#comment-12992330
 ] 

Brian M Dube commented on FOR-1222:
---

There is a Jetty Ant task available with version 6.1.26 that looks promising. I 
am investigating this.

I have not looked at Jetty 7 (version 7+ moved from codehaus to eclipse).

 Upgrade packaged Jetty
 --

 Key: FOR-1222
 URL: https://issues.apache.org/jira/browse/FOR-1222
 Project: Forrest
  Issue Type: Improvement
  Components: Launch 'forrest run'
Affects Versions: 0.10-dev
Reporter: Brian M Dube

 The packaged version of Jetty can be upgraded.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: progress with release 0.9

2011-02-07 Thread Brian M Dube

On Tue, Feb 08, 2011 at 12:22:08PM +1100, David Crossley wrote:
 I will now proceed with the remainder of the release plan
 to actually get it out there and announced. That will take
 some time.

Is the code freeze until the announcement?

-Brian

Re: [VOTE] please review release candidate then vote

2011-02-06 Thread Brian M Dube

On Tue, Feb 01, 2011 at 02:47:08PM +1100, David Crossley wrote:
 For Windows get *.zip (md5sum c04600e8befeaf005d5e4b9d6c8034f9)
 For UNIX get *.tar.gz (md5sum ea58a078e3861d4dfc8bf3296a53a5f8)

+1

md5sum$ ea58a078e3861d4dfc8bf3296a53a5f8  apache-forrest-0.9.tar.gz

Thanks all.

-Brian

Re: svn commit: r1065468 - /forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.skos/resources/stylesheets/glossaryBundle-to-index.all.xsl

2011-02-05 Thread Brian M Dube

On Mon, Jan 31, 2011 at 02:11:58AM -, cross...@apache.org wrote:
 Author: crossley
 Date: Mon Jan 31 02:11:58 2011
 New Revision: 1065468
 
 URL: http://svn.apache.org/viewvc?rev=1065468view=rev
 Log:
 There was something strange with the xml declaration line for this file.
 
 Modified:
 
 forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.skos/resources/stylesheets/glossaryBundle-to-index.all.xsl

Just for reference, that was the Unicode byte order marker [1].

-Brian

[1] http://unicode.org/faq/utf_bom.html

Re: [VOTE] please review release candidate then vote

2011-02-02 Thread Brian M Dube

Basic tests work for me on Linux with both Sun Java 5 and OpenJDK 6.

-Brian

Re: JIRA down, need to handle poor response

2011-01-30 Thread Brian M Dube

On Mon, Jan 31, 2011 at 10:19:08AM +1100, David Crossley wrote:
[snip]
 This is because JIRA is down.
 
 Previously we just got no response, so forrest treated it differently.
 
 Behind-the-scenes forrest is doing a request for a certain JIRA
 report and transforming the result.
 
 Because for our site-author docs build we have internal validation [1][2]
 configured to be happening, we detect this error in this way.
[snip]
 I assume that our xsl stylesheet needs tweaks to handle such
 unexpected content.

There is an attempt in r1065442 [3]. Can anyone confirm whether the
maintenance message is hand-crafted each time, or starts from a known
template? That would make the stylesheet less brittle. With this
revision, the body content is taken as is and produces an invalid
intermediate document, but the final result is usable.

-Brian

 [1] http://forrest.apache.org/howto-dev.html#debug-validation
 Using Cocoon Validation Transformers
 
 [2] http://forrest.apache.org/howto-dev.html#validate-intermediate
 Validate all intermediate xml content

[3] http://svn.apache.org/viewvc?view=revisionrevision=1065442

 -David

Plus signs in a/@name (was Re: svn commit: r1061643 - in /forrest/site: docs_0_90/changes.html docs_0_90/changes.rss docs_0_90/changes.xml docs_0_90/skins.html docs_0_90/upgrading_09.html dtdx/documen

2011-01-23 Thread Brian M Dube

On Thu, Jan 20, 2011 at 10:10:15PM -0800, Brian M Dube wrote:
  -a href=#Changes+to+Build-N1034CChanges to Build/a
  +a href=#Changes+to+Build-N10355Changes to Build/a
 
  -a href=#Changes+to+the+Code+Base-N10356Changes to the Code Base/a
  +a href=#Changes+to+the+Code+Base-N1035FChanges to the Code Base/a
 
  -a href=#Changes+to+Documentation-N106D3Changes to Documentation/a
  +a href=#Changes+to+Documentation-N106DCChanges to Documentation/a
 
  -a href=#Contributors+to+this+release-N10875Contributors to this 
  release/a
  +a href=#Contributors+to+this+release-N1087EContributors to this 
  release/a
 
 ...
 
 Perhaps a change similar to r1061144 should happen here. Also I think
 there is discussion about '+' being invalid in these attributes. I'll
 have to search for that discussion later.

I'm not finding that discussion. The '+' is allowed in places like
a/@name for HTML 4.01 Transitional, but not in XHTML 1.0 Strict. I
think that is what I was remembering.

-Brian

input.projectInfo update (was Re: svn commit: r1061643 - in /forrest/site: docs_0_90/changes.html docs_0_90/changes.rss docs_0_90/changes.xml docs_0_90/skins.html docs_0_90/upgrading_09.html dtdx/docu

2011-01-23 Thread Brian M Dube

On Fri, Jan 21, 2011 at 05:32:52PM +1100, David Crossley wrote:
 Brian M Dube wrote:
   -a href=#Changes+to+Build-N1034CChanges to Build/a
   +a href=#Changes+to+Build-N10355Changes to Build/a
  
   -a href=#Changes+to+the+Code+Base-N10356Changes to the Code Base/a
   +a href=#Changes+to+the+Code+Base-N1035FChanges to the Code Base/a
  
   -a href=#Changes+to+Documentation-N106D3Changes to Documentation/a
   +a href=#Changes+to+Documentation-N106DCChanges to Documentation/a
  
   -a href=#Contributors+to+this+release-N10875Contributors to this 
   release/a
   +a href=#Contributors+to+this+release-N1087EContributors to this 
   release/a
  
  ...
  
  Perhaps a change similar to r1061144 should happen here.
 
 I was wondering about that. This is in the projectInfo plugin.
 Perhaps use the release version number instead.

In r1062562, sections now have an explicit @id built from @context and
@version.

-Brian

 -David

Re: svn commit: r1061643 - in /forrest/site: docs_0_90/changes.html docs_0_90/changes.rss docs_0_90/changes.xml docs_0_90/skins.html docs_0_90/upgrading_09.html dtdx/document-v13.pdf dtdx/document-v20

2011-01-20 Thread Brian M Dube

 -a href=#Changes+to+Build-N1034CChanges to Build/a
 +a href=#Changes+to+Build-N10355Changes to Build/a

 -a href=#Changes+to+the+Code+Base-N10356Changes to the Code Base/a
 +a href=#Changes+to+the+Code+Base-N1035FChanges to the Code Base/a

 -a href=#Changes+to+Documentation-N106D3Changes to Documentation/a
 +a href=#Changes+to+Documentation-N106DCChanges to Documentation/a

 -a href=#Contributors+to+this+release-N10875Contributors to this 
 release/a
 +a href=#Contributors+to+this+release-N1087EContributors to this 
 release/a

...

Perhaps a change similar to r1061144 should happen here. Also I think
there is discussion about '+' being invalid in these attributes. I'll
have to search for that discussion later.

-Brian

[jira] Assigned: (FOR-922) update all docs that explain sitemap fragments

2011-01-17 Thread Brian M Dube (JIRA)


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

Brian M Dube reassigned FOR-922:


Assignee: (was: Brian M Dube)

 update all docs that explain sitemap fragments
 --

 Key: FOR-922
 URL: https://issues.apache.org/jira/browse/FOR-922
 Project: Forrest
  Issue Type: Sub-task
  Components: Documentation and website
Affects Versions: 0.9-dev
Reporter: David Crossley
 Fix For: 0.9-dev


 There are various documents that explain parts of the sitemaps. Some of these 
 mention pathnames, some have actual fragments of code copied from sitemaps. 
 All of this needs to be updated to reflect the current sitemaps.
 The sitemaps were recently updated to use locationmap, some sitemaps were 
 simplified, filenames were changed, e.g. document2html.xsl to 
 document-to-html.xsl
 These changes need to be reflected in the current docs.

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

[jira] Updated: (FOR-922) update all docs that explain sitemap fragments

2011-01-17 Thread Brian M Dube (JIRA)


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

Brian M Dube updated FOR-922:
-

Fix Version/s: (was: 0.9-dev)
   0.10

I have less time for this than I thought. Pushing off.

 update all docs that explain sitemap fragments
 --

 Key: FOR-922
 URL: https://issues.apache.org/jira/browse/FOR-922
 Project: Forrest
  Issue Type: Sub-task
  Components: Documentation and website
Affects Versions: 0.9-dev
Reporter: David Crossley
 Fix For: 0.10


 There are various documents that explain parts of the sitemaps. Some of these 
 mention pathnames, some have actual fragments of code copied from sitemaps. 
 All of this needs to be updated to reflect the current sitemaps.
 The sitemaps were recently updated to use locationmap, some sitemaps were 
 simplified, filenames were changed, e.g. document2html.xsl to 
 document-to-html.xsl
 These changes need to be reflected in the current docs.

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

[jira] Updated: (FOR-922) update all docs that explain sitemap fragments

2011-01-16 Thread Brian M Dube (JIRA)


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

Brian M Dube updated FOR-922:
-

Issue Type: Sub-task  (was: Task)
Parent: FOR-874

 update all docs that explain sitemap fragments
 --

 Key: FOR-922
 URL: https://issues.apache.org/jira/browse/FOR-922
 Project: Forrest
  Issue Type: Sub-task
  Components: Documentation and website
Affects Versions: 0.9-dev
Reporter: David Crossley
Assignee: Brian M Dube
 Fix For: 0.9-dev


 There are various documents that explain parts of the sitemaps. Some of these 
 mention pathnames, some have actual fragments of code copied from sitemaps. 
 All of this needs to be updated to reflect the current sitemaps.
 The sitemaps were recently updated to use locationmap, some sitemaps were 
 simplified, filenames were changed, e.g. document2html.xsl to 
 document-to-html.xsl
 These changes need to be reflected in the current docs.

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

Re: svn commit: r1059492 - /forrest/site/jiraclient_apache.license

2011-01-15 Thread Brian M Dube

On Sun, Jan 16, 2011 at 05:48:06AM -, bd...@apache.org wrote:
 Author: bdube
 Date: Sun Jan 16 05:48:05 2011
 New Revision: 1059492
 
 URL: http://svn.apache.org/viewvc?rev=1059492view=rev
 Log:
 Remove file deployed by mistake
 
 Removed:
 forrest/site/jiraclient_apache.license

This is not a sensitive file. I have an email from ALM Works with
permission to post publicly the ASF license for their Jira Client
product. It was just deployed by accident.

I'm trying to get used to git-svn, sorry for the noise.

Brian

Revised dates (was [Proposal] Release Plan for Forrest 0.90)

2011-01-11 Thread Brian M Dube

On Tue, Dec 07, 2010 at 04:59:06PM +1100, David Crossley wrote:
 The proposed milestones are:
 
 [1] end of vote on Release Plan
 Monday 2010-12-20 at 22:00 UTC
 http://www.timeanddate.com/worldclock/fixedtime.html?day=20month=12year=2010hour=22min=0sec=0p1=0
 
 [2] create initial release candidate, start testing
 Monday 2011-01-10 at 22:00 UTC
 http://www.timeanddate.com/worldclock/fixedtime.html?day=10month=1year=2011hour=22min=0sec=0p1=0

 [3] create final release candidate if necessary
 Saturday 2011-01-15 at 22:00 UTC
 http://www.timeanddate.com/worldclock/fixedtime.html?day=15month=1year=2011hour=22min=0sec=0p1=0

 [4] end of vote on final release candidate and commence the upload phase
 Monday 2011-01-17 at 22:00 UTC (i.e. planned release date)
 http://www.timeanddate.com/worldclock/fixedtime.html?day=17month=1year=2011hour=22min=0sec=0p1=0

[2] create initial release candidate, start testing
Revised: Monday 2011-01-31 at 22:00 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?day=31month=1year=2011hour=22min=0sec=0p1=0

[3] create final release candidate if necessary
Revised: Saturday 2011-02-05 at 22:00 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?day=5month=2year=2011hour=22min=0sec=0p1=0

[4] end of vote on final release candidate and commence the upload phase
Revised: Monday 2011-02-07 at 22:00 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?day=7month=2year=2011hour=22min=0sec=0p1=0


Revisions look correct and acceptable?

-Brian

[jira] Commented: (FOR-752) Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs directory


[ 
https://issues.apache.org/jira/browse/FOR-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980566#action_12980566
 ] 

Brian M Dube commented on FOR-752:
--

Breakpoint hit: thread=main, java.io.File.mkdirs(), line=1,145 bci=0

main[1] dump this.path
 this.path = /tmp/seed/build/webapp/WEB-INF/logs
main[1] where
  [1] java.io.File.mkdirs (File.java:1,145)
  [2] org.apache.log.output.io.FileTarget.openFile (FileTarget.java:103)
  [3] org.apache.log.output.io.FileTarget.init (FileTarget.java:55)
  [4] org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget 
(FileTargetFactory.java:164)
  [5] org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget 
(FileTargetFactory.java:145)
  [6] org.apache.avalon.excalibur.logger.DefaultLogTargetManager.configure 
(DefaultLogTargetManager.java:92)
  [7] org.apache.avalon.framework.container.ContainerUtil.configure 
(ContainerUtil.java:201)
  [8] org.apache.avalon.excalibur.logger.LogKitLoggerManager.setupTargetManager 
(LogKitLoggerManager.java:457)
  [9] org.apache.avalon.excalibur.logger.LogKitLoggerManager.configure 
(LogKitLoggerManager.java:403)
  [10] org.apache.cocoon.bean.CocoonWrapper.initialize (CocoonWrapper.java:144)
  [11] org.apache.cocoon.bean.CocoonBean.initialize (CocoonBean.java:102)
  [12] org.apache.cocoon.Main.main (Main.java:320)


 Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs 
 directory
 ---

 Key: FOR-752
 URL: https://issues.apache.org/jira/browse/FOR-752
 Project: Forrest
  Issue Type: Bug
  Components: Tool: Forrestbot
Affects Versions: 0.7, 0.8, 0.9-dev
Reporter: Richard Calmbach
Priority: Minor
 Fix For: 0.10


 When running Forrestbot with the default value for property build.work-dir 
 (namely work/${ant.project.name}), project.build-dir is set to the same 
 value and consequently, project.webapp is set to 
 work/${ant.project.name}/webapp. However, one of the two logs directories 
 continues to be created at build/webapp/WEB-INF/logs, suggesting that 
 somewhere a hardcoded value is used instead of ${project.webapp}. The mkdir 
 command for this logs directory is not in any of the Ant build files in the 
 Forrest distribution; it must be in one of the Java classes, probably in a 
 class related to logging. I forced an I/O failure by turning off all 
 permissions on build/webapp and running forrest -f build.xml build. This 
 yielded a stacktrace that originated 7 calls before:
 org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget(FileTargetFactory.java:160)
 The remaining 7 invokations were not displayed (just ... 7 more).
 The upshot of this bug is that running forrest -f build.xml clean misses 
 the logs directory in the unexpected location. My workaround right now is 
 to use a custom clean-all target that depends on clean and that deletes 
 the spurious build/webapp directory.

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

[jira] Issue Comment Edited: (FOR-752) Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs directory


[ 
https://issues.apache.org/jira/browse/FOR-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980566#action_12980566
 ] 

Brian M Dube edited comment on FOR-752 at 1/12/11 12:33 AM:


I included this stacktrace because I thought it showed the directory being 
created in a different part of the code, but I didn't read the issue 
description closely enough. Leaving it in since the original description is 
truncated.

  [1] java.io.File.mkdirs (File.java:1,145)
  [2] org.apache.log.output.io.FileTarget.openFile (FileTarget.java:103)
  [3] org.apache.log.output.io.FileTarget.init (FileTarget.java:55)
  [4] org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget 
(FileTargetFactory.java:164)
  [5] org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget 
(FileTargetFactory.java:145)
  [6] org.apache.avalon.excalibur.logger.DefaultLogTargetManager.configure 
(DefaultLogTargetManager.java:92)
  [7] org.apache.avalon.framework.container.ContainerUtil.configure 
(ContainerUtil.java:201)
  [8] org.apache.avalon.excalibur.logger.LogKitLoggerManager.setupTargetManager 
(LogKitLoggerManager.java:457)
  [9] org.apache.avalon.excalibur.logger.LogKitLoggerManager.configure 
(LogKitLoggerManager.java:403)
  [10] org.apache.cocoon.bean.CocoonWrapper.initialize (CocoonWrapper.java:144)
  [11] org.apache.cocoon.bean.CocoonBean.initialize (CocoonBean.java:102)
  [12] org.apache.cocoon.Main.main (Main.java:320)


  was (Author: brian):
Breakpoint hit: thread=main, java.io.File.mkdirs(), line=1,145 bci=0

main[1] dump this.path
 this.path = /tmp/seed/build/webapp/WEB-INF/logs
main[1] where
  [1] java.io.File.mkdirs (File.java:1,145)
  [2] org.apache.log.output.io.FileTarget.openFile (FileTarget.java:103)
  [3] org.apache.log.output.io.FileTarget.init (FileTarget.java:55)
  [4] org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget 
(FileTargetFactory.java:164)
  [5] org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget 
(FileTargetFactory.java:145)
  [6] org.apache.avalon.excalibur.logger.DefaultLogTargetManager.configure 
(DefaultLogTargetManager.java:92)
  [7] org.apache.avalon.framework.container.ContainerUtil.configure 
(ContainerUtil.java:201)
  [8] org.apache.avalon.excalibur.logger.LogKitLoggerManager.setupTargetManager 
(LogKitLoggerManager.java:457)
  [9] org.apache.avalon.excalibur.logger.LogKitLoggerManager.configure 
(LogKitLoggerManager.java:403)
  [10] org.apache.cocoon.bean.CocoonWrapper.initialize (CocoonWrapper.java:144)
  [11] org.apache.cocoon.bean.CocoonBean.initialize (CocoonBean.java:102)
  [12] org.apache.cocoon.Main.main (Main.java:320)

  
 Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs 
 directory
 ---

 Key: FOR-752
 URL: https://issues.apache.org/jira/browse/FOR-752
 Project: Forrest
  Issue Type: Bug
  Components: Tool: Forrestbot
Affects Versions: 0.7, 0.8, 0.9-dev
Reporter: Richard Calmbach
Priority: Minor
 Fix For: 0.10


 When running Forrestbot with the default value for property build.work-dir 
 (namely work/${ant.project.name}), project.build-dir is set to the same 
 value and consequently, project.webapp is set to 
 work/${ant.project.name}/webapp. However, one of the two logs directories 
 continues to be created at build/webapp/WEB-INF/logs, suggesting that 
 somewhere a hardcoded value is used instead of ${project.webapp}. The mkdir 
 command for this logs directory is not in any of the Ant build files in the 
 Forrest distribution; it must be in one of the Java classes, probably in a 
 class related to logging. I forced an I/O failure by turning off all 
 permissions on build/webapp and running forrest -f build.xml build. This 
 yielded a stacktrace that originated 7 calls before:
 org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget(FileTargetFactory.java:160)
 The remaining 7 invokations were not displayed (just ... 7 more).
 The upshot of this bug is that running forrest -f build.xml clean misses 
 the logs directory in the unexpected location. My workaround right now is 
 to use a custom clean-all target that depends on clean and that deletes 
 the spurious build/webapp directory.

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

[jira] Commented: (FOR-752) Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs directory


[ 
https://issues.apache.org/jira/browse/FOR-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980579#action_12980579
 ] 

Brian M Dube commented on FOR-752:
--

This seems to work. It's the same idea as Mathieu's proposed change, but it 
avoids changing the visibility of ForrestConfUtils.getSystemProperty().

Index: main/java/org/apache/forrest/log/ForrestLogTargetFactory.java
===
--- main/java/org/apache/forrest/log/ForrestLogTargetFactory.java   
(revision 1057988)
+++ main/java/org/apache/forrest/log/ForrestLogTargetFactory.java   
(working copy)
@@ -42,7 +42,7 @@
 
 if(!projectHome.startsWith(ForrestConfUtils.defaultHome)){
 DefaultContext newContext = new DefaultContext(context);
-newContext.put(context-root,projectHome + /build/webapp);
+newContext.put(context-root, 
ForrestConfUtils.getProjectWebappHome());
 currentContext = newContext;
 }
 } catch (Exception e) {
Index: main/java/org/apache/forrest/conf/ForrestConfUtils.java
===
--- main/java/org/apache/forrest/conf/ForrestConfUtils.java (revision 
1057988)
+++ main/java/org/apache/forrest/conf/ForrestConfUtils.java (working copy)
@@ -89,6 +89,10 @@
 return contextHome;
 }
 
+public static String getProjectWebappHome() {
+  return getSystemProperty(project.webapp);
+}
+
 /**
  * For backwards compatibility, alias old skin names to new ones. This must
  * be kept in sync with aliasing in forrest.build.xml/init-props


 Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs 
 directory
 ---

 Key: FOR-752
 URL: https://issues.apache.org/jira/browse/FOR-752
 Project: Forrest
  Issue Type: Bug
  Components: Tool: Forrestbot
Affects Versions: 0.7, 0.8, 0.9-dev
Reporter: Richard Calmbach
Priority: Minor
 Fix For: 0.10


 When running Forrestbot with the default value for property build.work-dir 
 (namely work/${ant.project.name}), project.build-dir is set to the same 
 value and consequently, project.webapp is set to 
 work/${ant.project.name}/webapp. However, one of the two logs directories 
 continues to be created at build/webapp/WEB-INF/logs, suggesting that 
 somewhere a hardcoded value is used instead of ${project.webapp}. The mkdir 
 command for this logs directory is not in any of the Ant build files in the 
 Forrest distribution; it must be in one of the Java classes, probably in a 
 class related to logging. I forced an I/O failure by turning off all 
 permissions on build/webapp and running forrest -f build.xml build. This 
 yielded a stacktrace that originated 7 calls before:
 org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget(FileTargetFactory.java:160)
 The remaining 7 invokations were not displayed (just ... 7 more).
 The upshot of this bug is that running forrest -f build.xml clean misses 
 the logs directory in the unexpected location. My workaround right now is 
 to use a custom clean-all target that depends on clean and that deletes 
 the spurious build/webapp directory.

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

[jira] Updated: (FOR-752) Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs directory

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

Brian M Dube updated FOR-752:
-

Other Info: (was: [Patch available])

Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs
directory
---

Key: FOR-752
URL: https://issues.apache.org/jira/browse/FOR-752
Project: Forrest
Issue Type: Bug
Components: Tool: Forrestbot
Affects Versions: 0.7, 0.8, 0.9-dev
Reporter: Richard Calmbach
Priority: Minor
Fix For: 0.9-dev

When running Forrestbot with the default value for property build.work-dir
(namely work/${ant.project.name}), project.build-dir is set to the same
value and consequently, project.webapp is set to
work/${ant.project.name}/webapp. However, one of the two logs directories
continues to be created at build/webapp/WEB-INF/logs, suggesting that
somewhere a hardcoded value is used instead of ${project.webapp}. The mkdir
command for this logs directory is not in any of the Ant build files in the
Forrest distribution; it must be in one of the Java classes, probably in a
class related to logging. I forced an I/O failure by turning off all
permissions on build/webapp and running forrest -f build.xml build. This
yielded a stacktrace that originated 7 calls before:
org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget(FileTargetFactory.java:160)
The remaining 7 invokations were not displayed (just ... 7 more).
The upshot of this bug is that running forrest -f build.xml clean misses
the logs directory in the unexpected location. My workaround right now is
to use a custom clean-all target that depends on clean and that deletes
the spurious build/webapp directory.

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

[jira] Closed: (FOR-752) Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs directory

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

Brian M Dube closed FOR-752.

Resolution: Fixed
Fix Version/s: (was: 0.10)
0.9-dev

Contributed patch applied with thanks.

Forrestbot build workstage creates spurious build/webapp/WEB-INF/logs
directory
---

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

[jira] Updated: (FOR-922) update all docs that explain sitemap fragments

2011-01-09 Thread Brian M Dube (JIRA)


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

Brian M Dube updated FOR-922:
-

Assignee: Brian M Dube

 update all docs that explain sitemap fragments
 --

 Key: FOR-922
 URL: https://issues.apache.org/jira/browse/FOR-922
 Project: Forrest
  Issue Type: Task
  Components: Documentation and website
Affects Versions: 0.9-dev
Reporter: David Crossley
Assignee: Brian M Dube
 Fix For: 0.9-dev


 There are various documents that explain parts of the sitemaps. Some of these 
 mention pathnames, some have actual fragments of code copied from sitemaps. 
 All of this needs to be updated to reflect the current sitemaps.
 The sitemaps were recently updated to use locationmap, some sitemaps were 
 simplified, filenames were changed, e.g. document2html.xsl to 
 document-to-html.xsl
 These changes need to be reflected in the current docs.

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

Re: Upgrading Batik

2011-01-09 Thread Brian M Dube

On Sat, Jan 08, 2011 at 12:44:13PM +1100, David Crossley wrote:
 Brian M Dube wrote:
  The Jing discussion reminded me of upgrading Batik. We currently
  package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did
  Cocoon or Forrest build a custom jar out of the modules that Batik
  ships?
 
 Forrest would have obtained that as-is from Cocoon
 at the time of an etc/cocoon_upgrade process.
 
 The svn log over in the Cocoon branch shows that it was
 Antonio (2005-05-23) who commited it there. This gave me some
 search clues and so found this around our 0.6 release:
 
 http://s.apache.org/qx8
 Subject: Re: REsizing batik to a minimum for us.
 Date: May 27, 2004
 
 -David

I see. Thanks.

Creating a batik-all-1.7.jar and copying it to forrest/lib/core in
place of 1.6 causes problems which I'm having trouble diagnosing. I've
also tried rebuilding the cocoon-batik-block against Batik 1.7, and it
didn't help.

I'll try a few more things, but this update may not make it into the
release. Help is welcome.

-Brian

Re: Plugin documentation review status

2011-01-08 Thread Brian M Dube

On Sun, Jan 02, 2011 at 01:22:53PM +1100, David Crossley wrote:
 Brian M Dube wrote:
 
  Does automatic testing of plugin documentation already take place
  somewhere? If not, I'm a willing volunteer to set something up.
 
 Not yet. Something that we have wondered about doing.
 
 That would be good.
 
 We have the forrest zones server, so we can add anything there.
 Using actual forrestbot might be overkill.
 See forrest.a.o/zone.html and $SVN/forrest/zone/README.html
 
 -David

I didn't speak up during the zone transition, so it doesn't appear
that I have access to set this up on the new zone.

But I can test ideas locally for now.

-Brian

[jira] Commented: (FOR-1061) svn update is very slow on our zone server


[ 
https://issues.apache.org/jira/browse/FOR-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979196#action_12979196
 ] 

Brian M Dube commented on FOR-1061:
---

Is this an issue with the new zone?

 svn update is very slow on our zone server
 --

 Key: FOR-1061
 URL: https://issues.apache.org/jira/browse/FOR-1061
 Project: Forrest
  Issue Type: Task
  Components: zones.a.o administration
Reporter: David Crossley

 We are seeing Forrestbot failures. This is because our hourly 'svn update' 
 and rebuild of Forrest is sometimes   
  
 taking an extraordinary long time. Therefore it interrupts forrestbot jobs 
 that happen later in the hour. It seems to be a network or IO issue.

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

[jira] Commented: (FOR-1179) zone server machine going to be updated OS soon: re-establish the forrestbot instance


[ 
https://issues.apache.org/jira/browse/FOR-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979197#action_12979197
 ] 

Brian M Dube commented on FOR-1179:
---

Resolved on the new zone?

 zone server machine going to be updated OS soon: re-establish the forrestbot 
 instance
 -

 Key: FOR-1179
 URL: https://issues.apache.org/jira/browse/FOR-1179
 Project: Forrest
  Issue Type: Task
  Components: zones.a.o administration
Reporter: David Crossley

 The zones.apache.org is going to be having its machine and OS updated soon.
 We need to plan for migration of our forrestbot installation.
 Most of the config is in SVN, and some info is at 
 http://forrest.apache.org/zone.html
 Need to get a listing of the filesystem structure, and copy of the crontab. 

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

[jira] Created: (FOR-1216) Zone documentation references Solaris

Zone documentation references Solaris
-

 Key: FOR-1216
 URL: https://issues.apache.org/jira/browse/FOR-1216
 Project: Forrest
  Issue Type: Bug
  Components: zones.a.o administration
Affects Versions: 0.9-dev
Reporter: Brian M Dube
Priority: Minor


http://forrest.apache.org/zone.html references Solaris, and other parts may 
also need to be updated to reflect the latest configuration.

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

[jira] Created: (FOR-1217) Monitor plugin documentation builds

Monitor plugin documentation builds
---

 Key: FOR-1217
 URL: https://issues.apache.org/jira/browse/FOR-1217
 Project: Forrest
  Issue Type: Bug
  Components: zones.a.o administration
Affects Versions: 0.9-dev
Reporter: Brian M Dube


The documentation for the various plugins is not regularly built and checked 
for errors. It is very easy to let this slip far enough behind that fixes 
become difficult.

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

[jira] Commented: (FOR-1217) Monitor plugin documentation builds


[ 
https://issues.apache.org/jira/browse/FOR-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979200#action_12979200
 ] 

Brian M Dube commented on FOR-1217:
---

Some discussion:

http://s.apache.org/lf
Subject: Plugin documentation review status
Date: Jan 1, 2011

 Monitor plugin documentation builds
 ---

 Key: FOR-1217
 URL: https://issues.apache.org/jira/browse/FOR-1217
 Project: Forrest
  Issue Type: Bug
  Components: zones.a.o administration
Affects Versions: 0.9-dev
Reporter: Brian M Dube

 The documentation for the various plugins is not regularly built and checked 
 for errors. It is very easy to let this slip far enough behind that fixes 
 become difficult.

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

[jira] Closed: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111


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

Brian M Dube closed FOR-1215.
-

   Resolution: Fixed
Fix Version/s: (was: 0.10)
   0.9-dev

Fixed with rebuilt Cocoon Validation block.

 The optional use of Cocoon Validation Transformers fails with Jing-2009
 ---

 Key: FOR-1215
 URL: https://issues.apache.org/jira/browse/FOR-1215
 Project: Forrest
  Issue Type: Bug
  Components: XML grammars  validation
Affects Versions: 0.9-dev
Reporter: David Crossley
 Fix For: 0.9-dev


 The optional use of Cocoon Validation Transformers is explained here:
 http://forrest.apache.org/howto-dev.html#debug-validation
 http://forrest.apache.org/howto-dev.html#validate-intermediate
 FOR-1172 enable validation of the internal xml
 This works okay with Jing-20081028
 However with the current release of Jing-2009 it fails with this message:
 ...
 * [178/93]  [93/135]  0.886s 10.0Kb  linkmap.validation-start.xml
 * [179/92]  [0/0] 0.089s 0b  
 docs_0_90/howto/howto-buildPlugin.validation.xml
 Exception in thread main java.lang.NoSuchFieldError: ENTITY_RESOLVER
   at 
 org.apache.cocoon.components.validation.jing.JingSchemaParser.parseSchema(JingSchemaParser.java:79)
   at 
 org.apache.cocoon.components.validation.impl.AbstractValidator.getSchema(AbstractValidator.java:410)

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

Upgrading Batik

2011-01-07 Thread Brian M Dube

The Jing discussion reminded me of upgrading Batik. We currently
package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did
Cocoon or Forrest build a custom jar out of the modules that Batik
ships?

-Brian

[jira] Commented: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111

2011-01-06 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978626#action_12978626
 ] 

Brian M Dube commented on FOR-1215:
---

It works to build the Cocoon Validation Block with Jing-2009 on the class 
path. No changes are necessary to the source code in the block.

Do we need a validation block that works with multiple versions of Jing, or is 
the goal to upgrade Jing?

 The optional use of Cocoon Validation Transformers fails with Jing-2009
 ---

 Key: FOR-1215
 URL: https://issues.apache.org/jira/browse/FOR-1215
 Project: Forrest
  Issue Type: Bug
  Components: XML grammars  validation
Affects Versions: 0.9-dev
Reporter: David Crossley
 Fix For: 0.10


 The optional use of Cocoon Validation Transformers is explained here:
 http://forrest.apache.org/howto-dev.html#debug-validation
 http://forrest.apache.org/howto-dev.html#validate-intermediate
 FOR-1172 enable validation of the internal xml
 This works okay with Jing-20081028
 However with the current release of Jing-2009 it fails with this message:
 ...
 * [178/93]  [93/135]  0.886s 10.0Kb  linkmap.validation-start.xml
 * [179/92]  [0/0] 0.089s 0b  
 docs_0_90/howto/howto-buildPlugin.validation.xml
 Exception in thread main java.lang.NoSuchFieldError: ENTITY_RESOLVER
   at 
 org.apache.cocoon.components.validation.jing.JingSchemaParser.parseSchema(JingSchemaParser.java:79)
   at 
 org.apache.cocoon.components.validation.impl.AbstractValidator.getSchema(AbstractValidator.java:410)

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

[jira] Commented: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111

2011-01-06 Thread Brian M Dube (JIRA)


[ 
https://issues.apache.org/jira/browse/FOR-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978660#action_12978660
 ] 

Brian M Dube commented on FOR-1215:
---

I'll describe what I did since I'm not at all up to speed with
Cocoon. Using Cocoon's BRANCH_2_1_X at r1056175, I swapped out the
included Jing (20030619) with 2009 and updated lib/jars.xml to
reflect that change. Then I excluded all blocks but validation and
built Cocoon. I tested Forrest with the block built against the newer
Jing and validation worked without error.

If the validation block as shipped by Forrest requires any kind of
configuration, I missed that step. But if not, it looks like Jing and
the validation block can be upgraded together without issue.


 The optional use of Cocoon Validation Transformers fails with Jing-2009
 ---

 Key: FOR-1215
 URL: https://issues.apache.org/jira/browse/FOR-1215
 Project: Forrest
  Issue Type: Bug
  Components: XML grammars  validation
Affects Versions: 0.9-dev
Reporter: David Crossley
 Fix For: 0.10


 The optional use of Cocoon Validation Transformers is explained here:
 http://forrest.apache.org/howto-dev.html#debug-validation
 http://forrest.apache.org/howto-dev.html#validate-intermediate
 FOR-1172 enable validation of the internal xml
 This works okay with Jing-20081028
 However with the current release of Jing-2009 it fails with this message:
 ...
 * [178/93]  [93/135]  0.886s 10.0Kb  linkmap.validation-start.xml
 * [179/92]  [0/0] 0.089s 0b  
 docs_0_90/howto/howto-buildPlugin.validation.xml
 Exception in thread main java.lang.NoSuchFieldError: ENTITY_RESOLVER
   at 
 org.apache.cocoon.components.validation.jing.JingSchemaParser.parseSchema(JingSchemaParser.java:79)
   at 
 org.apache.cocoon.components.validation.impl.AbstractValidator.getSchema(AbstractValidator.java:410)

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

[jira] Issue Comment Edited: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111

2011-01-06 Thread Brian M Dube (JIRA)

[
https://issues.apache.org/jira/browse/FOR-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978660#action_12978660
]

Brian M Dube edited comment on FOR-1215 at 1/7/11 2:14 AM:
---

I'll describe what I did since I'm not at all up to speed with
Cocoon. Using Cocoon's BRANCH_2_1_X at r1056175, I swapped out the
included Jing (20030619) with 2009 and updated lib/jars.xml to
reflect that change. Then I excluded all blocks but validation and
built Cocoon. I tested Forrest with the block built against the newer
Jing and validation worked without error (with the newer Jing also on Forrest's
class path in place of our version).

If the validation block as shipped by Forrest requires any kind of
configuration, I missed that step. But if not, it looks like Jing and
the validation block can be upgraded together without issue.

was (Author: brian):
I'll describe what I did since I'm not at all up to speed with
Cocoon. Using Cocoon's BRANCH_2_1_X at r1056175, I swapped out the
included Jing (20030619) with 2009 and updated lib/jars.xml to
reflect that change. Then I excluded all blocks but validation and
built Cocoon. I tested Forrest with the block built against the newer
Jing and validation worked without error.

If the validation block as shipped by Forrest requires any kind of
configuration, I missed that step. But if not, it looks like Jing and
the validation block can be upgraded together without issue.

The optional use of Cocoon Validation Transformers fails with Jing-2009
---

Key: FOR-1215
URL: https://issues.apache.org/jira/browse/FOR-1215
Project: Forrest
Issue Type: Bug
Components: XML grammars validation
Affects Versions: 0.9-dev
Reporter: David Crossley
Fix For: 0.10

The optional use of Cocoon Validation Transformers is explained here:
http://forrest.apache.org/howto-dev.html#debug-validation
http://forrest.apache.org/howto-dev.html#validate-intermediate
FOR-1172 enable validation of the internal xml
This works okay with Jing-20081028
However with the current release of Jing-2009 it fails with this message:
...
* [178/93] [93/135] 0.886s 10.0Kb linkmap.validation-start.xml
* [179/92] [0/0] 0.089s 0b
docs_0_90/howto/howto-buildPlugin.validation.xml
Exception in thread main java.lang.NoSuchFieldError: ENTITY_RESOLVER
at
org.apache.cocoon.components.validation.jing.JingSchemaParser.parseSchema(JingSchemaParser.java:79)
at
org.apache.cocoon.components.validation.impl.AbstractValidator.getSchema(AbstractValidator.java:410)

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

[jira] Assigned: (FOR-1168) Sample pages that fail validation


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

Brian M Dube reassigned FOR-1168:
-

Assignee: (was: Gavin)

Removing assignment to emeritus member.

 Sample pages that fail validation
 -

 Key: FOR-1168
 URL: https://issues.apache.org/jira/browse/FOR-1168
 Project: Forrest
  Issue Type: Bug
  Components: Documentation and website, Plugin: internal.dispatcher
Affects Versions: 0.9-dev
Reporter: Gavin
 Fix For: 0.10


 The main 'sample.html' passes validation fine, however some other pages fail 
 xhtml 1.0 strict validation. Mainly due to the use of the + symbol in name 
 anchors. Not a problem for sites validating to HTML4.01.
 These pages include (but check for more)
 samples-b/usemap.html
 samples-b/xinclude.html
 samples-b/static.html
 samples-b/linking.html
 samples-b/howto-wowto.html
 samples-b/embedded_html.html
 samples-b/ascii-art.html
 locationmap/index.html
 samples-c/subdir/index.html
 samples-c/showonlywhenselected/page1.html
 samples-c/showonlywhenselected/page2.html
 pluginDocs/plugins_0_90/index.html

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

[jira] Assigned: (FOR-1183) Forrestbar search of Jira issues broken, perhaps changed Jira search syntax


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

Brian M Dube reassigned FOR-1183:
-

Assignee: (was: Gavin)

Removing assignment to emeritus member.

 Forrestbar search of Jira issues broken, perhaps changed Jira search syntax
 ---

 Key: FOR-1183
 URL: https://issues.apache.org/jira/browse/FOR-1183
 Project: Forrest
  Issue Type: Bug
  Components: Tool: Forrestbar
Reporter: David Crossley

 When searching our Jira Issues using Forrestbar, the upgraded ASF Jira now 
 seems to intercede with smart query. However, it seems to lose our search 
 terms, and just finds all Forrest issues. Perhaps the Jira search syntax has 
 changed.

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

[jira] Closed: (FOR-1213) remove required plugin org.apache.forrest.themes.core from various plugin forrest.properties


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

Brian M Dube closed FOR-1213.
-

   Resolution: Fixed
Fix Version/s: 0.9-dev

Updated affected forrest.properties files.

 remove required plugin org.apache.forrest.themes.core from various plugin 
 forrest.properties
 

 Key: FOR-1213
 URL: https://issues.apache.org/jira/browse/FOR-1213
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: internal.dispatcher, Plugin: themes.core
Affects Versions: 0.9-dev
Reporter: David Crossley
 Fix For: 0.9-dev


 The plugin org.apache.forrest.themes.core resources moved to the DIspatcher 
 plugin.
 Various plugin websites are already using the Dispatcher, and so need their 
 project.required.plugins changed to remove themes.core
  

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

[jira] Commented: (FOR-1214) Fix Dispatcher documentation: old org.apache.forrest.themes.core