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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Brian M Dube (JIRA)]

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

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

For now I have created a symlink /var/www/forrest -> /home/forrest/htdocs with 
redirection in /var/www/index.html.

The links in ~forrest/htdocs are broken using this approach, but the pull 
request to modify our puppet configuration is proving more difficult than I 
thought.

The initial change we need is minor, a simple adjustment to docroot-related 
settings compared to the defaults ( 
https://github.com/puppetlabs/puppetlabs-apache/tree/1.6.0#docroot-1 ). The 
problem is that this would be an incomplete solution without also managing the 
forrest role account through puppet. I've been hanging around #asfinfra to ask 
the best way to manage role accounts.

> 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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Created] (FOR-1254) Update documentation for project virtual machine

[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] [Closed] (FOR-1228) I'd like to "help" develop on this project ... currently a java developer...

[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] [Assigned] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

[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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Commented] (FOR-1251) ensure that the new ASF machine for forrest-zones jail works as expected

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

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

[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)

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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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:

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:

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

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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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) ) (И, И). 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) )(И, И). Её маленький 
> вариант таких проблем не имеет. Буква отображается в виде символов. Прошу 
> прощения за мой английский язык.

--
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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
> 
>
> 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) ) (И, И). 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) )(И, И). Её маленький 
> вариант таких проблем не имеет. Буква отображается в виде символов. Прошу 
> прощения за мой английский язык.

--
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

[Brian M Dube (JIRA)]

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

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

Patch reviewed and applied. Thanks.

> 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  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] Closed: (FOR-1224) xslt transformation of resume2.xml generates invalid fo file

[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  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] Updated: (FOR-1224) xslt transformation of resume2.xml generates invalid fo file

[Brian M Dube (JIRA)]

 [ 
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  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] Resolved: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD

[Brian M Dube (JIRA)]

 [ 
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] Closed: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD

[Brian M Dube (JIRA)]

 [ 
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] Updated: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD

[Brian M Dube (JIRA)]

 [ 
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] Commented: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Brian M Dube (JIRA)]

 [ 
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] Assigned: (FOR-1223) example delivered with resume plugin needs fixing to conform to DTD

[Brian M Dube (JIRA)]

 [ 
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] Issue Comment Edited: (FOR-1222) Upgrade packaged Jetty

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Commented: (FOR-1221) Upgrade packaged Batik

[Brian M Dube (JIRA)]

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

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

Some discussion:

http://s.apache.org/93Z
Subject: Upgrading Batik
Date: 7 Jan 2011

> 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] Commented: (FOR-1222) Upgrade packaged Jetty

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

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

[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] Created: (FOR-1221) Upgrade packaged Batik

[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] Updated: (FOR-922) update all docs that explain sitemap fragments

[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] Assigned: (FOR-922) update all docs that explain sitemap fragments

[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

[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.

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

[Brian M Dube (JIRA)]

 [ 
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

[Brian M Dube (JIRA)]

 [ 
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
> ---
>
> 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] Commented: (FOR-752) Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Issue Comment Edited: (FOR-752) Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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. (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. (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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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. (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] Updated: (FOR-922) update all docs that explain sitemap fragments

[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.

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

[Brian M Dube (JIRA)]

 [ 
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.

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

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Created: (FOR-1217) Monitor plugin documentation builds

[Brian M Dube (JIRA)]

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] Created: (FOR-1216) Zone documentation references Solaris

[Brian M Dube (JIRA)]

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] Commented: (FOR-1179) zone server machine going to be updated OS soon: re-establish the forrestbot instance

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Commented: (FOR-1061) svn update is very slow on our zone server

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Issue Comment Edited: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Commented: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] Commented: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111

[Brian M Dube (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-1214) Fix Dispatcher documentation: old org.apache.forrest.themes.core

[Brian M Dube (JIRA)]

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

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

grep results for themes.core:

src/documentation/content/xdocs/dispatcher-glossary.xml:
Hooks are applied currently in the themes.core plugin as
src/documentation/content/xdocs/int/index.xml:  a) custom implementation of 
the themes.core plugin
src/documentation/content/xdocs/int/index.xml:  b) themes.core plugin
src/documentation/content/xdocs/how/howto-dispatcher-quickstart.xml:
,org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core
src/documentation/content/xdocs/how/howto-dispatcher-quickstart.xml:  
FORREST_HOME/whiteboard/plugins/org.apache.forrest.themes.core
src/documentation/content/xdocs/how/howto-dispatcher-quickstart.xml:  
space. Forrest finds the default contract in its core (the themes.core
src/documentation/content/xdocs/how/howto-dispatcher-contracts.xml:  
org.apache.forrest.plugin.themes.core/themes/common/html/blank.ft.


> Fix Dispatcher documentation: old org.apache.forrest.themes.core
> 
>
> Key: FOR-1214
> URL: https://issues.apache.org/jira/browse/FOR-1214
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugin: internal.dispatcher, Plugin: themes.core
>Affects Versions: 0.9-dev
>Reporter: David Crossley
>
> The Dispatcher plugin documentation still refers to the old 
> "org.apache.forrest.themes.core"

-- 
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

[Brian M Dube (JIRA)]

 [ 
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] Assigned: (FOR-1168) Sample pages that fail validation

[Brian M Dube (JIRA)]

 [ 
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

[Brian M Dube (JIRA)]

 [ 
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] Updated: (FOR-1212) Building documentation creates spurious directory tree in project.xdocs-dir/images

[Brian M Dube (JIRA)]

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

Brian M Dube updated FOR-1212:
--

Description: 
Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle Java 
6, files are written to:

$GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallery/src/documentation/content/xdocs/images/gallery/demo

The full path to $FORREST_HOME is expanded, that is, in the above example 
insert the full /path/to/forrest/ where it says $FORREST_HOME.

  was:
Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle Java 
6, files are written to:

$GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallerysrc/documentation/content/xdocs/images/gallery/demo

The full path to $FORREST_HOME is expanded, that is, in the above example 
insert the full /path/to/forrest/ where it says $FORREST_HOME.


> Building documentation creates spurious directory tree in 
> project.xdocs-dir/images
> --
>
> Key: FOR-1212
> URL: https://issues.apache.org/jira/browse/FOR-1212
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugin: input.PhotoGallery
>Affects Versions: 0.9-dev
>Reporter: Brian M Dube
>
> Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle 
> Java 6, files are written to:
> $GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallery/src/documentation/content/xdocs/images/gallery/demo
> The full path to $FORREST_HOME is expanded, that is, in the above example 
> insert the full /path/to/forrest/ where it says $FORREST_HOME.

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

[jira] Created: (FOR-1212) Building documentation creates spurious directory tree in project.xdocs-dir/images

[Brian M Dube (JIRA)]

Building documentation creates spurious directory tree in 
project.xdocs-dir/images
--

 Key: FOR-1212
 URL: https://issues.apache.org/jira/browse/FOR-1212
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.PhotoGallery
Affects Versions: 0.9-dev
Reporter: Brian M Dube


Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle Java 
6, files are written to:

$GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallerysrc/documentation/content/xdocs/images/gallery/demo

The full path to $FORREST_HOME is expanded, that is, in the above example 
insert the full /path/to/forrest/ where it says $FORREST_HOME.

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

[jira] Commented: (FOR-1175) when building static site, copy skin files only if they have been modified since the last static site build

[Brian M Dube (JIRA)]

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

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

http://ant.apache.org/manual/Types/selectors.html

Thank you for pointing out the broken link.

> when building static site, copy skin files only if they have been modified 
> since the last static site build
> ---
>
> Key: FOR-1175
> URL: https://issues.apache.org/jira/browse/FOR-1175
> Project: Forrest
>  Issue Type: Improvement
>  Components: Launch 'forrest'
>Affects Versions: 0.9-dev
>Reporter: Brolin Empey
>Priority: Minor
>
> Years ago, I asked about this issue on the user mailing list:
> 
> AFAIK, nothing has changed since then.  I want to report the issue here so it 
> does not get forgotten.
> Anyway:
> When I rebuild my static site, the "skin" directory seems to be copied 
> unconditionally to the build/site/ directory.  This means that, because the 
> local files have been rewritten and consequently have newer modification 
> times than the remote files, skin/ is uploaded each time I use lftp's reverse 
> mirror function to publish changes to my public Web site, even if nothing in 
> the skin has changed.
> The Ant target that copies the non-generated content to build/site/ should be 
> changed to copy files (including skin files) only if the source file has 
> changed.  Maybe rsync could be used to copy non-generated content.
> If no one fixes this issue, I may use oDesk to hire someone to fix the issue. 
>  I have already had success with using oDesk to hire Michal Sciubidlo to fix 
> Mozilla.org bug 269728.  I have hired Michal again to fix Mozilla.org bug 
> 178506.

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

[jira] Created: (FOR-1211) input.PhotoGallery does not build on OpenJDK

[Brian M Dube (JIRA)]

input.PhotoGallery does not build on OpenJDK


 Key: FOR-1211
 URL: https://issues.apache.org/jira/browse/FOR-1211
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.PhotoGallery
Affects Versions: 0.9-dev
Reporter: Brian M Dube
Priority: Minor


Building input.PhotoGallery with OpenJDK fails due to missing interface methods 
com.sun.image.codec.jpeg.JPEGDecodeParam.getWidth() and 
com.sun.image.codec.jpeg.JPEGDecodeParam.getHeight(). Also 13 warnings about 
com.sun internal API.

Is there public API suitable for this?

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

[jira] Resolved: (FOR-1137) empty jar files are built for plugins even if they have no java code

[Brian M Dube (JIRA)]

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

Brian M Dube resolved FOR-1137.
---

   Resolution: Fixed
Fix Version/s: 0.9-dev

Lazy consensus to last change assumed. Removed FIXME notes and updated plugin 
template build file to include the new property in a comment.

> empty jar files are built for plugins even if they have no java code
> 
>
> Key: FOR-1137
> URL: https://issues.apache.org/jira/browse/FOR-1137
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugins (general issues)
>Affects Versions: 0.8, 0.9-dev
>Reporter: David Crossley
>Priority: Minor
> Fix For: 0.9-dev
>
>
> In $FORREST_HOME/plugins/build.xml file, the test for "java_exists" around 
> line 90 is not sufficient. The pluginTemplate now has an empty default 
> directory stucture for "src/java" with only a readme.txt file. So we get an 
> almost-empty jar file. Need to test for presence of files other than 
> top-level readme.txt
> Not a problem, just clutter.

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

[jira] Closed: (FOR-1137) empty jar files are built for plugins even if they have no java code

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-1137.
-


> empty jar files are built for plugins even if they have no java code
> 
>
> Key: FOR-1137
> URL: https://issues.apache.org/jira/browse/FOR-1137
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugins (general issues)
>Affects Versions: 0.8, 0.9-dev
>Reporter: David Crossley
>Priority: Minor
> Fix For: 0.9-dev
>
>
> In $FORREST_HOME/plugins/build.xml file, the test for "java_exists" around 
> line 90 is not sufficient. The pluginTemplate now has an empty default 
> directory stucture for "src/java" with only a readme.txt file. So we get an 
> almost-empty jar file. Need to test for presence of files other than 
> top-level readme.txt
> Not a problem, just clutter.

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

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

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-922:
--

Getting closer in r992179.

> 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
> 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] Commented: (FOR-922) update all docs that explain sitemap fragments

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-922:
--

The fragments in sitemap-ref.xml and howto-custom-html-source.xml look current 
to me now.

forrest.xmap.html and sitemap.xmap.html (from a previous comment) are from 
Forrest 0.7, so I don't think these need anything.

> 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
> 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] Commented: (FOR-985) the plugins 'test' target does not local deploy its required plugins

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-985:
--

Using output.pdf I get the same results, broken todo and changes.

But using input.PhotoGallery as the test, the plugin doesn't build for me with 
OpenJDK 6. 13 warnings about Sun proprietary API and 2 errors: can't find 
com.sun.image.codec.jpeg.JPEGDecodeParam.getWidth() and 
com.sun.image.codec.jpeg.JPEGDecodeParam.getHeight().

> the plugins 'test' target does not local deploy its required plugins
> 
>
> Key: FOR-985
> URL: https://issues.apache.org/jira/browse/FOR-985
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugins (general issues)
>Affects Versions: 0.8, 0.9-dev
>Reporter: David Crossley
> Fix For: 0.9-dev
>
>
> >For some reason our plugin 'test' Ant target only
> >
> >does a local deploy of the actual plugin that it is  
> >
> >tesing and not the other plugins that are required   
> >
> >by this plugin.
> See thread: plugins 'test' target April 13 when testing RC1.

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

[jira] Commented: (FOR-95) indirect linking and anchors/fragment identifiers

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-95:
-

Is this fully supported and resolved now?

> indirect linking and anchors/fragment identifiers
> -
>
> Key: FOR-95
> URL: https://issues.apache.org/jira/browse/FOR-95
> Project: Forrest
>  Issue Type: Improvement
>  Components: Core operations
>Affects Versions: 0.6, 0.7, 0.8
>Reporter: Richard Cao
>
> I would be nice if Forrest supported anchors with indirect linking. That is, 
> something like this: . (or something 
> similar, like )
> If somepage pointed to somepage.html, then the resultant link would be 
> somepage.html#someanchor.
> Using the above link currently fails with an "invalid xpath" error since 
> "somepage#someanchor" is not a valid qname.

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

[jira] Resolved: (FOR-338) Document Content could be shown in frames

[Brian M Dube (JIRA)]

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

Brian M Dube resolved FOR-338.
--

Resolution: Won't Fix

Frames are deprecated, no?

They are at least handled separately in modular XHTML.

> Document Content could be shown in frames
> -
>
> Key: FOR-338
> URL: https://issues.apache.org/jira/browse/FOR-338
> Project: Forrest
>  Issue Type: New Feature
>  Components: Core operations
>Reporter: Joerg Woost
> Attachments: forrest.zip, screenshot-1.jpg, setFrame.js
>
>
> The navigations, header and footer must not scroll out of the users sight, if 
> he wants to read the document.
> So i use a frame to show the document-content inside the window
> unfortunally there are some things to do, i am not to firm in, so i give you 
> a little idea, how it works and what should be done

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

[jira] Commented: (FOR-1129) Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'

[Brian M Dube (JIRA)]

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

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

Is seeding sites as a subtree within the Forrest installation supported? 
Recommended?

> Cannot get variable 'plugin.xmap.output' in expression 
> '{lm:plugin.xmap.output}'
> 
>
> Key: FOR-1129
> URL: https://issues.apache.org/jira/browse/FOR-1129
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.8
>Reporter: Paul O'Connell
> Attachments: seed.txt, site.txt
>
>
> I extracted forrest 0.8 on windows xp, and ran the 'site' and 'seed' 
> operations using the java 1.5.0_12 jre. I expectrd a default site to be 
> created, but got the following error. After posting to the forrest mail 
> group, it was recommended that i raise an issue.

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

[jira] Closed: (FOR-1094) Ant target "validate-stylesheets" is broken

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-1094.
-


> Ant target "validate-stylesheets" is broken
> ---
>
> Key: FOR-1094
> URL: https://issues.apache.org/jira/browse/FOR-1094
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.9-dev
>Reporter: David Crossley
> Fix For: 0.9-dev
>
>
> In main/targets/validate.xml the "validate-stylesheets" target does nothing. 
> Seems that the property "stylesheets.present" in target "validation-props" 
> might not be set.

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

[jira] Resolved: (FOR-1094) Ant target "validate-stylesheets" is broken

[Brian M Dube (JIRA)]

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

Brian M Dube resolved FOR-1094.
---

   Resolution: Fixed
Fix Version/s: 0.9-dev

> Ant target "validate-stylesheets" is broken
> ---
>
> Key: FOR-1094
> URL: https://issues.apache.org/jira/browse/FOR-1094
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.9-dev
>Reporter: David Crossley
> Fix For: 0.9-dev
>
>
> In main/targets/validate.xml the "validate-stylesheets" target does nothing. 
> Seems that the property "stylesheets.present" in target "validation-props" 
> might not be set.

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

[jira] Commented: (FOR-325) Building in Windows98

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-325:
--

Windows 98 support. Close?

> Building in Windows98
> -
>
> Key: FOR-325
> URL: https://issues.apache.org/jira/browse/FOR-325
> Project: Forrest
>  Issue Type: Improvement
>  Components: Compile
> Environment: Windows 98
>Reporter: Senen de Diego
>Priority: Minor
> Attachments: w98tcdiff.txt
>
>
> As it is, is not possible to build forrest in Windows 98, because command.com 
> shell doesn't permit an equal "=" sign in batch variables.
> I've done a patch to build forrest in Windows 98 using TakeCommand as shell. 
> Take Command is not free but it's the only one I've found to do that. There 
> is a free shell, 4DOS, from the same firma (jpsoft) but it has a limitation 
> of 511 charactars for command, which make it useless for this.
> I've suggest also a couple of changes:
> Stop dupplicating commands, both for Windows_NT and WINNT values of 
> %OS%. 
> Stop calling forrestpath.bat and appendcp.bat from within a FOR loop (there 
> is already a loop in both batch files so I think the first loop isn't 
> necessary).

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

[jira] Resolved: (FOR-385) Profiled access list controlled documents

[Brian M Dube (JIRA)]

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

Brian M Dube resolved FOR-385.
--

Resolution: Won't Fix

The solution appears to have been worked out by the reporter. It's documented 
but the issue hasn't been touched in the years since its creation.

> Profiled access list controlled documents
> -
>
> Key: FOR-385
> URL: https://issues.apache.org/jira/browse/FOR-385
> Project: Forrest
>  Issue Type: New Feature
>  Components: Core operations, Plugin: input.simplifiedDocbook
>Affects Versions: 0.7
> Environment: Windows XP
>Reporter: Alex Batlin
>Priority: Minor
>
> With DocBook, I am able to specify element roles. DocBook profiling XSLs can 
> then be used to produce documents based on say a user profile. This is very 
> valuable if you provide a website to both users and support staff as you can 
> generate a version of the document suitable for each user role profile.
> It would be great, if forrest can be extended with user name and password 
> login feature, user to role/group/any-other-profile mapping feature (in 
> effect access control) and profile-based document generation (for both 
> content documents and tabs|site.xmls).
> Here is a content use-case:
> 1. a some-tool.xml DocBook document contains two sections, one applicable to 
> any user (DocBook role attribute = "user;support") and one that is applicable 
> to just support staff (attribute="support"). 
> 2. a mapping file should exist that maps say guest and joe.user to user 
> roles, whilst joe.support is mapped to support role.
> 3. when guest or joe.user want to view some-tool.html or .pdf file, the xml 
> file is profiled and only section 1 is included in the output, whilst when 
> joe.support views the same document, section 1 and 2 are included.
> Here is a navigation use-case (using concepts from previos use case):
> 1. another-tool.xml DocBook document should only be seen by support role 
> staff, so a new attribute is required in sites and tabs.xml files, say role 
> to again provide profiling.
> 2. so when joe.user views the website, another-tool.html|pdf link is not even 
> presented, but joe.support sees the link.
> Here is the original email thread:
> -Original Message-
> From: Ross Gardler [mailto:rgard...@apache.org] 
> Sent: 21 November 2004 13:49
> To: dev@forrest.apache.org
> Subject: Re: Dynamic or Static Access Control Lists
> Thorsten Scherler wrote:
> > El dom, 21-11-2004 a las 09:13, Alex Batlin escribió:
> > 
> >>Has anyone configured Forrest to allow user to provide userid and
> >>password, and then generated documents based on their role/group.
> >>Document elements can then be tagged with role/group. I am thinking of
> >>the way profiling is done in DocCook.
> > 
> > 
> > No, not AFAIK, but it should be quite easy.
> > 
> > I will need auth as well pretty soon for profiling. You can either beat
> > me by sending a patch or hang in there and wait (I guess end of the
> > year) till I implemend it.
> > 
> > Basicly you have to do the following for auth, protected docs and
> > profiling:
> > 1) create a dir where the protected docs go
> > 2) create a auth pipeline where you start the session
> > 3) add profiling to the session in your profiling
> > 4) change your skin pipelines to display the profiled content
> > 
> > Can you open an enhancement issue and add this to it. This way it will not 
> > get lost.
> There are a number of authorisation blocks in Cocoon. Take a look at the 
> Cocoon docs and their wiki for examples. If you fancy having a go at 
> implementing this before it reaches the top of Throsten's ToDo list we 
> will be happy to advise on the best approach.
> Ross

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

[jira] Updated: (FOR-385) Profiled access list controlled documents

[Brian M Dube (JIRA)]

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

Brian M Dube updated FOR-385:
-

Component/s: (was: Compile)
 Plugin: input.simplifiedDocbook
 Core operations
   Priority: Minor  (was: Major)

> Profiled access list controlled documents
> -
>
> Key: FOR-385
> URL: https://issues.apache.org/jira/browse/FOR-385
> Project: Forrest
>  Issue Type: New Feature
>  Components: Core operations, Plugin: input.simplifiedDocbook
>Affects Versions: 0.7
> Environment: Windows XP
>Reporter: Alex Batlin
>Priority: Minor
>
> With DocBook, I am able to specify element roles. DocBook profiling XSLs can 
> then be used to produce documents based on say a user profile. This is very 
> valuable if you provide a website to both users and support staff as you can 
> generate a version of the document suitable for each user role profile.
> It would be great, if forrest can be extended with user name and password 
> login feature, user to role/group/any-other-profile mapping feature (in 
> effect access control) and profile-based document generation (for both 
> content documents and tabs|site.xmls).
> Here is a content use-case:
> 1. a some-tool.xml DocBook document contains two sections, one applicable to 
> any user (DocBook role attribute = "user;support") and one that is applicable 
> to just support staff (attribute="support"). 
> 2. a mapping file should exist that maps say guest and joe.user to user 
> roles, whilst joe.support is mapped to support role.
> 3. when guest or joe.user want to view some-tool.html or .pdf file, the xml 
> file is profiled and only section 1 is included in the output, whilst when 
> joe.support views the same document, section 1 and 2 are included.
> Here is a navigation use-case (using concepts from previos use case):
> 1. another-tool.xml DocBook document should only be seen by support role 
> staff, so a new attribute is required in sites and tabs.xml files, say role 
> to again provide profiling.
> 2. so when joe.user views the website, another-tool.html|pdf link is not even 
> presented, but joe.support sees the link.
> Here is the original email thread:
> -Original Message-
> From: Ross Gardler [mailto:rgard...@apache.org] 
> Sent: 21 November 2004 13:49
> To: dev@forrest.apache.org
> Subject: Re: Dynamic or Static Access Control Lists
> Thorsten Scherler wrote:
> > El dom, 21-11-2004 a las 09:13, Alex Batlin escribió:
> > 
> >>Has anyone configured Forrest to allow user to provide userid and
> >>password, and then generated documents based on their role/group.
> >>Document elements can then be tagged with role/group. I am thinking of
> >>the way profiling is done in DocCook.
> > 
> > 
> > No, not AFAIK, but it should be quite easy.
> > 
> > I will need auth as well pretty soon for profiling. You can either beat
> > me by sending a patch or hang in there and wait (I guess end of the
> > year) till I implemend it.
> > 
> > Basicly you have to do the following for auth, protected docs and
> > profiling:
> > 1) create a dir where the protected docs go
> > 2) create a auth pipeline where you start the session
> > 3) add profiling to the session in your profiling
> > 4) change your skin pipelines to display the profiled content
> > 
> > Can you open an enhancement issue and add this to it. This way it will not 
> > get lost.
> There are a number of authorisation blocks in Cocoon. Take a look at the 
> Cocoon docs and their wiki for examples. If you fancy having a go at 
> implementing this before it reaches the top of Throsten's ToDo list we 
> will be happy to advise on the best approach.
> Ross

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

[jira] Commented: (FOR-385) Profiled access list controlled documents

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-385:
--

The locations have changed, but the information is still around:

http://www.batlin.com/forrest/profiling.html

http://www.batlin.com/forrest/blocks.html

> Profiled access list controlled documents
> -
>
> Key: FOR-385
> URL: https://issues.apache.org/jira/browse/FOR-385
> Project: Forrest
>  Issue Type: New Feature
>  Components: Compile
>Affects Versions: 0.7
> Environment: Windows XP
>Reporter: Alex Batlin
>
> With DocBook, I am able to specify element roles. DocBook profiling XSLs can 
> then be used to produce documents based on say a user profile. This is very 
> valuable if you provide a website to both users and support staff as you can 
> generate a version of the document suitable for each user role profile.
> It would be great, if forrest can be extended with user name and password 
> login feature, user to role/group/any-other-profile mapping feature (in 
> effect access control) and profile-based document generation (for both 
> content documents and tabs|site.xmls).
> Here is a content use-case:
> 1. a some-tool.xml DocBook document contains two sections, one applicable to 
> any user (DocBook role attribute = "user;support") and one that is applicable 
> to just support staff (attribute="support"). 
> 2. a mapping file should exist that maps say guest and joe.user to user 
> roles, whilst joe.support is mapped to support role.
> 3. when guest or joe.user want to view some-tool.html or .pdf file, the xml 
> file is profiled and only section 1 is included in the output, whilst when 
> joe.support views the same document, section 1 and 2 are included.
> Here is a navigation use-case (using concepts from previos use case):
> 1. another-tool.xml DocBook document should only be seen by support role 
> staff, so a new attribute is required in sites and tabs.xml files, say role 
> to again provide profiling.
> 2. so when joe.user views the website, another-tool.html|pdf link is not even 
> presented, but joe.support sees the link.
> Here is the original email thread:
> -Original Message-
> From: Ross Gardler [mailto:rgard...@apache.org] 
> Sent: 21 November 2004 13:49
> To: dev@forrest.apache.org
> Subject: Re: Dynamic or Static Access Control Lists
> Thorsten Scherler wrote:
> > El dom, 21-11-2004 a las 09:13, Alex Batlin escribió:
> > 
> >>Has anyone configured Forrest to allow user to provide userid and
> >>password, and then generated documents based on their role/group.
> >>Document elements can then be tagged with role/group. I am thinking of
> >>the way profiling is done in DocCook.
> > 
> > 
> > No, not AFAIK, but it should be quite easy.
> > 
> > I will need auth as well pretty soon for profiling. You can either beat
> > me by sending a patch or hang in there and wait (I guess end of the
> > year) till I implemend it.
> > 
> > Basicly you have to do the following for auth, protected docs and
> > profiling:
> > 1) create a dir where the protected docs go
> > 2) create a auth pipeline where you start the session
> > 3) add profiling to the session in your profiling
> > 4) change your skin pipelines to display the profiled content
> > 
> > Can you open an enhancement issue and add this to it. This way it will not 
> > get lost.
> There are a number of authorisation blocks in Cocoon. Take a look at the 
> Cocoon docs and their wiki for examples. If you fancy having a go at 
> implementing this before it reaches the top of Throsten's ToDo list we 
> will be happy to advise on the best approach.
> Ross

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

[jira] Closed: (FOR-1115) Change links from mygroup.org, myproj.mygroup.org, myhost.com, mydomain to example.org per RFC 2606

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-1115.
-

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

> Change links from mygroup.org, myproj.mygroup.org, myhost.com, mydomain to 
> example.org per RFC 2606
> ---
>
> Key: FOR-1115
> URL: https://issues.apache.org/jira/browse/FOR-1115
> Project: Forrest
>  Issue Type: Improvement
>  Components: Documentation and website, Plugin: internal.dispatcher, 
> seed (fresh-site), Skins (general issues)
>Affects Versions: 0.8, 0.9-dev
>Reporter: Brian M Dube
>Priority: Trivial
> Fix For: 0.9-dev
>
>
> Skins, dispatcher, and the seed sites contain default links to mygroup.org. 
> This domain is registered. It appears to be a squatter, but it exists 
> nonetheless. Perhaps these links should be changed to one of the domains 
> provided by RFC 2606.

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

[jira] Reopened: (FOR-1115) Change links from mygroup.org, myproj.mygroup.org, myhost.com, mydomain to example.org per RFC 2606

[Brian M Dube (JIRA)]

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

Brian M Dube reopened FOR-1115:
---

  Assignee: Brian M Dube

Add foo.com to the list

> Change links from mygroup.org, myproj.mygroup.org, myhost.com, mydomain to 
> example.org per RFC 2606
> ---
>
> Key: FOR-1115
> URL: https://issues.apache.org/jira/browse/FOR-1115
> Project: Forrest
>  Issue Type: Improvement
>  Components: Documentation and website, Plugin: internal.dispatcher, 
> seed (fresh-site), Skins (general issues)
>Affects Versions: 0.8, 0.9-dev
>Reporter: Brian M Dube
>Assignee: Brian M Dube
>Priority: Trivial
> Fix For: 0.9-dev
>
>
> Skins, dispatcher, and the seed sites contain default links to mygroup.org. 
> This domain is registered. It appears to be a squatter, but it exists 
> nonetheless. Perhaps these links should be changed to one of the domains 
> provided by RFC 2606.

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

[jira] Closed: (FOR-1000) Use locationmap to resolve XSL imports in skins

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-1000.
-

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

Please review the locationmap naming scheme and documentation changes.

> Use locationmap to resolve XSL imports in skins
> ---
>
> Key: FOR-1000
> URL: https://issues.apache.org/jira/browse/FOR-1000
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>Affects Versions: 0.8, 0.9-dev
>Reporter: Brian M Dube
>Priority: Minor
> Fix For: 0.9-dev
>
>
> To create a custom skin that imports stylesheets from common, for example by 
> copying pelt and modifying it for a project, it is also necessary to copy the 
> common skin because the xsl:import calls use relative paths. The imports can 
> be done with the help of the locationmap.

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

[jira] Updated: (FOR-1000) Use locationmap to resolve XSL imports in skins

[Brian M Dube (JIRA)]

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

Brian M Dube updated FOR-1000:
--

Affects Version/s: 0.9-dev

> Use locationmap to resolve XSL imports in skins
> ---
>
> Key: FOR-1000
> URL: https://issues.apache.org/jira/browse/FOR-1000
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>Affects Versions: 0.8, 0.9-dev
>Reporter: Brian M Dube
>Assignee: Brian M Dube
>Priority: Minor
> Fix For: 0.9-dev
>
>
> To create a custom skin that imports stylesheets from common, for example by 
> copying pelt and modifying it for a project, it is also necessary to copy the 
> common skin because the xsl:import calls use relative paths. The imports can 
> be done with the help of the locationmap.

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

[jira] Commented: (FOR-1000) Use locationmap to resolve XSL imports in skins

[Brian M Dube (JIRA)]

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

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

The rewrites are done in r887050. I have not yet updated the documentation.

I used something like this:
$ grep -r --exclude-dir=\.svn xsl:import main/webapp/skins \
| awk -F : '{ print $1 }' \
| xargs sed -i 
's_../../../common/xslt/.*/\(.*\)-to-\(.*\)\.xsl_lm://transform.skin.common.\2.\1-to-\2_'

and a slightly different version for the css. Changes to the naming scheme I 
used are fine by me.

There are a few files that may need to be handled separately:
$ grep -r --exclude-dir=\.svn xsl:import . | grep -v lm
./common/images/rc.svg.xslt:  
./common/images/dc.svg.xslt:  
./leather-dev/xslt/xml/contract.xsl:  
./leather-dev/xslt/xml/ft-to-xhtml.xsl:  

> Use locationmap to resolve XSL imports in skins
> ---
>
> Key: FOR-1000
> URL: https://issues.apache.org/jira/browse/FOR-1000
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>Affects Versions: 0.8
>Reporter: Brian M Dube
>Assignee: Brian M Dube
>Priority: Minor
> Fix For: 0.9-dev
>
>
> To create a custom skin that imports stylesheets from common, for example by 
> copying pelt and modifying it for a project, it is also necessary to copy the 
> common skin because the xsl:import calls use relative paths. The imports can 
> be done with the help of the locationmap.

-- 
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-1000) Use locationmap to resolve XSL imports in skins

[Brian M Dube (JIRA)]

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

Brian M Dube edited comment on FOR-1000 at 12/1/09 3:56 AM:


I just made a quick test and it worked.

Next:
1) Devise a naming scheme for main/webapp/locationmap-transforms.xml
2) Replace all the relative skin imports with the locationmap pattern from step 
1
3) Update documentation regarding custom skins

If I don't get to it by tomorrow evening, it'll be a few weeks before I can.

  was (Author: brian):
I just made a quick test and it worked.

Next:
1) Devise a naming scheme for main/webapp/locationmap-transforms.xml
2) Replace all the relative skin imports with the locationmap pattern from step 
1

If I don't get to it by tomorrow evening, it'll be a few weeks before I can.
  
> Use locationmap to resolve XSL imports in skins
> ---
>
> Key: FOR-1000
> URL: https://issues.apache.org/jira/browse/FOR-1000
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>Affects Versions: 0.8
>Reporter: Brian M Dube
>Assignee: Brian M Dube
>Priority: Minor
> Fix For: 0.9-dev
>
>
> To create a custom skin that imports stylesheets from common, for example by 
> copying pelt and modifying it for a project, it is also necessary to copy the 
> common skin because the xsl:import calls use relative paths. The imports can 
> be done with the help of the locationmap.

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

[jira] Assigned: (FOR-1000) Use locationmap to resolve XSL imports in skins

[Brian M Dube (JIRA)]

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

Brian M Dube reassigned FOR-1000:
-

Assignee: Brian M Dube

> Use locationmap to resolve XSL imports in skins
> ---
>
> Key: FOR-1000
> URL: https://issues.apache.org/jira/browse/FOR-1000
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>Affects Versions: 0.8
>Reporter: Brian M Dube
>Assignee: Brian M Dube
>Priority: Minor
> Fix For: 0.9-dev
>
>
> To create a custom skin that imports stylesheets from common, for example by 
> copying pelt and modifying it for a project, it is also necessary to copy the 
> common skin because the xsl:import calls use relative paths. The imports can 
> be done with the help of the locationmap.

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

[jira] Commented: (FOR-1000) Use locationmap to resolve XSL imports in skins

[Brian M Dube (JIRA)]

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

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

I just made a quick test and it worked.

Next:
1) Devise a naming scheme for main/webapp/locationmap-transforms.xml
2) Replace all the relative skin imports with the locationmap pattern from step 
1

If I don't get to it by tomorrow evening, it'll be a few weeks before I can.

> Use locationmap to resolve XSL imports in skins
> ---
>
> Key: FOR-1000
> URL: https://issues.apache.org/jira/browse/FOR-1000
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>Affects Versions: 0.8
>Reporter: Brian M Dube
>Priority: Minor
> Fix For: 0.9-dev
>
>
> To create a custom skin that imports stylesheets from common, for example by 
> copying pelt and modifying it for a project, it is also necessary to copy the 
> common skin because the xsl:import calls use relative paths. The imports can 
> be done with the help of the locationmap.

-- 
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

[Brian M Dube (JIRA)]

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

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

Hehe, yes, I saw you there when I was looking for things to do. When this comes 
around, let us know if we can help prepare for the upgrade. I started to make 
copies of parts of /export, but I noticed most of the structures were svn 
checkouts, so I stopped.

> 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] Commented: (FOR-1179) zone server machine going to be updated OS soon: re-establish the forrestbot instance

[Brian M Dube (JIRA)]

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

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

forrest.z.a.o has been up 47 days (longer than this issue). When is this 
scheduled?

A listing of which filesystem? I can help with this with more detail.

I've tried following infrastructure in the past, but it was too much traffic 
for me.

> 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] Resolved: (FOR-1181) feeder plugin documentation should be clearer

[Brian M Dube (JIRA)]

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

Brian M Dube resolved FOR-1181.
---

   Resolution: Fixed
Fix Version/s: 0.9-dev
 Assignee: (was: Brian M Dube)

Applied in r834348 with thanks.

Please create patches from $FORREST_HOME. Then the context is known by the 
patch file alone.

> feeder plugin documentation should be clearer
> -
>
> Key: FOR-1181
> URL: https://issues.apache.org/jira/browse/FOR-1181
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.feeder
>Affects Versions: 0.9-dev
>Reporter: Vicent
> Fix For: 0.9-dev
>
> Attachments: index_patch
>
>
> The documentation explaining how to use the feeder plugin available at 
> http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/index.html
> is not very clear. A patch is provided for trunk revision r832303.

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

[jira] Closed: (FOR-1181) feeder plugin documentation should be clearer

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-1181.
-


> feeder plugin documentation should be clearer
> -
>
> Key: FOR-1181
> URL: https://issues.apache.org/jira/browse/FOR-1181
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.feeder
>Affects Versions: 0.9-dev
>Reporter: Vicent
> Fix For: 0.9-dev
>
> Attachments: index_patch
>
>
> The documentation explaining how to use the feeder plugin available at 
> http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/index.html
> is not very clear. A patch is provided for trunk revision r832303.

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

[jira] Updated: (FOR-1181) feeder plugin documentation should be clearer

[Brian M Dube (JIRA)]

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

Brian M Dube updated FOR-1181:
--

Other Info:   (was: [Patch available])

> feeder plugin documentation should be clearer
> -
>
> Key: FOR-1181
> URL: https://issues.apache.org/jira/browse/FOR-1181
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.feeder
>Affects Versions: 0.9-dev
>Reporter: Vicent
> Fix For: 0.9-dev
>
> Attachments: index_patch
>
>
> The documentation explaining how to use the feeder plugin available at 
> http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/index.html
> is not very clear. A patch is provided for trunk revision r832303.

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

[jira] Closed: (FOR-1182) Add a new site to the list of sites using dispatcher

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-1182.
-


> Add a new site to the list of sites using dispatcher
> 
>
> Key: FOR-1182
> URL: https://issues.apache.org/jira/browse/FOR-1182
> Project: Forrest
>  Issue Type: Task
>  Components: Documentation and website
>Affects Versions: 0.9-dev
>Reporter: Vicent
> Fix For: 0.9-dev
>
> Attachments: live-sites.xml.diff
>
>
> Add the www.vitables.org website to the list of sites using dispatcher 
> http://forrest.apache.org/live-sites.html

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

[jira] Resolved: (FOR-1182) Add a new site to the list of sites using dispatcher

[Brian M Dube (JIRA)]

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

Brian M Dube resolved FOR-1182.
---

   Resolution: Fixed
Fix Version/s: 0.9-dev
 Assignee: (was: Brian M Dube)

Added in r834342. Thanks.

> Add a new site to the list of sites using dispatcher
> 
>
> Key: FOR-1182
> URL: https://issues.apache.org/jira/browse/FOR-1182
> Project: Forrest
>  Issue Type: Task
>  Components: Documentation and website
>Affects Versions: 0.9-dev
>Reporter: Vicent
> Fix For: 0.9-dev
>
> Attachments: live-sites.xml.diff
>
>
> Add the www.vitables.org website to the list of sites using dispatcher 
> http://forrest.apache.org/live-sites.html

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

[jira] Updated: (FOR-1182) Add a new site to the list of sites using dispatcher

[Brian M Dube (JIRA)]

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

Brian M Dube updated FOR-1182:
--

Other Info:   (was: [Patch available])

> Add a new site to the list of sites using dispatcher
> 
>
> Key: FOR-1182
> URL: https://issues.apache.org/jira/browse/FOR-1182
> Project: Forrest
>  Issue Type: Task
>  Components: Documentation and website
>Affects Versions: 0.9-dev
>Reporter: Vicent
> Fix For: 0.9-dev
>
> Attachments: live-sites.xml.diff
>
>
> Add the www.vitables.org website to the list of sites using dispatcher 
> http://forrest.apache.org/live-sites.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-1182) Add a new site to the list of sites using dispatcher

[Brian M Dube (JIRA)]

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

Brian M Dube reassigned FOR-1182:
-

Assignee: Brian M Dube

> Add a new site to the list of sites using dispatcher
> 
>
> Key: FOR-1182
> URL: https://issues.apache.org/jira/browse/FOR-1182
> Project: Forrest
>  Issue Type: Task
>  Components: Documentation and website
>Affects Versions: 0.9-dev
>Reporter: Vicent
>Assignee: Brian M Dube
> Attachments: live-sites.xml.diff
>
>
> Add the www.vitables.org website to the list of sites using dispatcher 
> http://forrest.apache.org/live-sites.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-1181) feeder plugin documentation should be clearer

[Brian M Dube (JIRA)]

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

Brian M Dube reassigned FOR-1181:
-

Assignee: Brian M Dube

> feeder plugin documentation should be clearer
> -
>
> Key: FOR-1181
> URL: https://issues.apache.org/jira/browse/FOR-1181
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.feeder
>Affects Versions: 0.9-dev
>Reporter: Vicent
>Assignee: Brian M Dube
> Attachments: index_patch
>
>
> The documentation explaining how to use the feeder plugin available at 
> http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/index.html
> is not very clear. A patch is provided for trunk revision r832303.

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

[jira] Commented: (FOR-1175) when building static site, copy skin files only if they have been modified since the last static site build

[Brian M Dube (JIRA)]

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

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

rsync is a great solution, but it is manual. Don't count on Ant to handle this 
for you because there is no Java implementation of rsync. The incredible tool 
you mention will help show that Java efforts on the rsync front have fallen 
short.

> when building static site, copy skin files only if they have been modified 
> since the last static site build
> ---
>
> Key: FOR-1175
> URL: https://issues.apache.org/jira/browse/FOR-1175
> Project: Forrest
>  Issue Type: Improvement
>  Components: Launch 'forrest'
>Affects Versions: 0.9-dev
>Reporter: Brolin Empey
>Priority: Minor
>
> Years ago, I asked about this issue on the user mailing list:
> 
> AFAIK, nothing has changed since then.  I want to report the issue here so it 
> does not get forgotten.
> Anyway:
> When I rebuild my static site, the "skin" directory seems to be copied 
> unconditionally to the build/site/ directory.  This means that, because the 
> local files have been rewritten and consequently have newer modification 
> times than the remote files, skin/ is uploaded each time I use lftp's reverse 
> mirror function to publish changes to my public Web site, even if nothing in 
> the skin has changed.
> The Ant target that copies the non-generated content to build/site/ should be 
> changed to copy files (including skin files) only if the source file has 
> changed.  Maybe rsync could be used to copy non-generated content.
> If no one fixes this issue, I may use oDesk to hire someone to fix the issue. 
>  I have already had success with using oDesk to hire Michal Sciubidlo to fix 
> Mozilla.org bug 269728.  I have hired Michal again to fix Mozilla.org bug 
> 178506.

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

[jira] Closed: (FOR-611) add Technicat to live site page

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-611.



> add Technicat to live site page
> ---
>
> Key: FOR-611
> URL: https://issues.apache.org/jira/browse/FOR-611
> Project: Forrest
>  Issue Type: Wish
>  Components: Documentation and website
>Affects Versions: 0.7
>Reporter: Phil Chu
>Assignee: Diwaker Gupta
>Priority: Trivial
> Fix For: 0.8
>
>
> Please feel free to add the Technicat, LLC web site, 
> http://www.technicat.com/ to the Forrest live sites page.
> I have been using Forrest to build the Technicat site for nearly two years, 
> now, from 0.5-0.7, moving from Windows to Linux to MacOS. Great system!
> Also, if you want to inquire, I have acquaintance who uses Forrest for the 
> Blumenfeld Maso web site, http://www.blumenfeld-maso.com/
> -Phil

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

[jira] Closed: (FOR-842) Tigris skin meta support

[Brian M Dube (JIRA)]

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

Brian M Dube closed FOR-842.



> Tigris skin meta support
> 
>
> Key: FOR-842
> URL: https://issues.apache.org/jira/browse/FOR-842
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>Affects Versions: 0.7, 0.8
>Reporter: Brian M Dube
>Priority: Trivial
> Attachments: tigris.patch
>
>
> Add support for meta tags in xdoc input documents.

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

[jira] Commented: (FOR-211) whole-site html and pdf: broken ext links

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-211:
--

At this point I'm not running any specific tests, only building our docs 
because the patch makes changes in site-author.

It seems the patch has become outdated with respect to trunk. Yes, the virtual 
targets do not exist on disk; but the pipelines which generate their content 
are failing and causing the error shown above. I may have more time this 
weekend.

> whole-site html and pdf: broken ext links
> -
>
> Key: FOR-211
> URL: https://issues.apache.org/jira/browse/FOR-211
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.6
>Reporter: David Crossley
> Fix For: 0.9-dev
>
> Attachments: links-HEAD.txt, links-patched.txt, 
> wholesite_pdftab_patch4.txt
>
>
> In the the generated site.html all of the external links are broken (i.e. the 
> href attributes are like ... error:#ext:forrest).

-- 
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-211) whole-site html and pdf: broken ext links

[Brian M Dube (JIRA)]

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

Brian M Dube edited comment on FOR-211 at 4/23/09 8:06 PM:
---


  wholesite.html
  pdf-tab.html
  wholesite.pdf
  pdf-tab.pdf


It still breaks for me. Are you running 'forrest' in $FORREST_HOME/site-author?

  was (Author: brian):

  wholesite.html
  pdf-tab.html
  wholesite.pdf
  pdf-tab.pdf


It still breaks for me. Are you running 'forrest build' in 
$FORREST_HOME/site-author?
  
> whole-site html and pdf: broken ext links
> -
>
> Key: FOR-211
> URL: https://issues.apache.org/jira/browse/FOR-211
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.6
>Reporter: David Crossley
> Fix For: 0.9-dev
>
> Attachments: links-HEAD.txt, links-patched.txt, 
> wholesite_pdftab_patch4.txt
>
>
> In the the generated site.html all of the external links are broken (i.e. the 
> href attributes are like ... error:#ext:forrest).

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

[jira] Commented: (FOR-211) whole-site html and pdf: broken ext links

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-211:
--


  wholesite.html
  pdf-tab.html
  wholesite.pdf
  pdf-tab.pdf


It still breaks for me. Are you running 'forrest build' in 
$FORREST_HOME/site-author?

> whole-site html and pdf: broken ext links
> -
>
> Key: FOR-211
> URL: https://issues.apache.org/jira/browse/FOR-211
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.6
>Reporter: David Crossley
> Fix For: 0.9-dev
>
> Attachments: links-HEAD.txt, links-patched.txt, 
> wholesite_pdftab_patch4.txt
>
>
> In the the generated site.html all of the external links are broken (i.e. the 
> href attributes are like ... error:#ext:forrest).

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

[jira] Commented: (FOR-211) whole-site html and pdf: broken ext links

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-211:
--

I've reverted the patch in r766976.

Our docs fail to build with these changes in place and I don't have time this 
evening to do anything other than revert.

> whole-site html and pdf: broken ext links
> -
>
> Key: FOR-211
> URL: https://issues.apache.org/jira/browse/FOR-211
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.6
>Reporter: David Crossley
> Fix For: 0.9-dev
>
> Attachments: links-HEAD.txt, links-patched.txt, 
> wholesite_pdftab_patch3.txt
>
>
> In the the generated site.html all of the external links are broken (i.e. the 
> href attributes are like ... error:#ext:forrest).

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

[jira] Commented: (FOR-211) whole-site html and pdf: broken ext links

[Brian M Dube (JIRA)]

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

Brian M Dube commented on FOR-211:
--

Committed revision 766959.

I'm not up to speed with this issue, but I've applied the patch and thank you 
for your patience. I tested briefly and found no regressions. Please test.

> whole-site html and pdf: broken ext links
> -
>
> Key: FOR-211
> URL: https://issues.apache.org/jira/browse/FOR-211
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations
>Affects Versions: 0.6
>Reporter: David Crossley
> Fix For: 0.9-dev
>
> Attachments: links-HEAD.txt, links-patched.txt, 
> wholesite_pdftab_patch3.txt
>
>
> In the the generated site.html all of the external links are broken (i.e. the 
> href attributes are like ... error:#ext:forrest).

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

[jira] Commented: (FOR-1147) the JavaScript external files should be referenced in body not head of html

[Brian M Dube (JIRA)]

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

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

I mean where script tags are allowed in a document. The way I read it, XHTML 
specifies head as the only parent for script elements. HTML 4 was more relaxed 
about their placement.

> the JavaScript external files should be referenced in body not head of html
> ---
>
> Key: FOR-1147
> URL: https://issues.apache.org/jira/browse/FOR-1147
> Project: Forrest
>  Issue Type: Sub-task
>  Components: Plugin: internal.dispatcher
>Affects Versions: 0.9-dev
>Reporter: David Crossley
>
> Optimisation guidelines suggest to declare the *.js files towards the end of 
> the "body" rather than from the "head". This will delay these http requests 
> and so lets the "head" be loaded more quickly.

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