[RESULT] [VOTE] Move Apache Forrest to the Attic

[David Crossley]

With four binding +1 and one non-binding +1, the vote passes to move Apache 
Forrest to the Attic.

The next step is to raise the resolution in the next board report. 
https://attic.apache.org/process.html

-David

On Mon, Nov 11, 2019 at 04:46:31PM +1100, David Crossley wrote:
> The Apache Forrest project has seen little activity for a long time, and 
> there has not been a release since 2011.
> 
> As noted in the quarterly Board reports [1], for years the Forrest PMC has 
> been keeping the project in maintenance mode.
> 
> Recent board reports have indicated a move to the Apache Attic. A thread was 
> commenced on the project mailing lists to provide an opportuntity for people 
> to discuss that possibility and to re-engage [2]. There was no further 
> discussion.
> 
> Note that the project resources would still be available. There would be no 
> further releases. The Apache Forrest PMC would be terminated by Board 
> resolution, and the Apache Attic PMC would instead have the oversight.
> 
> This vote thread is to confirm the desire of the project, being the next step 
> in the Attic process [3].
> 
> The general voting process is explained at the Forrest project guidelines 
> [4]. This situation was not anticipated by the guidelines. So in this case 
> anyone can vote.
> 
> So please vote whether Apache Forrest will be retired and moved to the Attic:
> +1 yes move to the Attic
> -1 the project should continue, and indicates commitment to revitalise the 
> project
> 
> The three outcomes could be:
> 
> A) There are three or more people voting -1, saying that they would instead 
> like the project to continue and agree to be involved.
> In this case, a probable course would be to go via the Apache Incubator [5] 
> to revitalise the community.
> 
> B) The normal positive outcome, with three or more +1 votes.
> C) Insufficent votes indicates a dormant PMC.
> 
> So in those latter cases, the remainder of the Attic process would ensue.
> 
> Also note that even after moving to the Attic, there are processes defined 
> there regarding moving out again.
> 
> The vote will run for one month to be summarised on 11 December.
> 
> 
> [1] https://whimsy.apache.org/board/minutes/Forrest.html
> 
> [2] 
> https://lists.apache.org/thread.html/fda24957e049f10d282037594d2aa61ce9a31cf8fc5313959aa81672@%3Cdev.forrest.apache.org%3E
> Subject: Forrest possibly retiring?
> Date: 2019-06-11
> 
> [3] https://attic.apache.org/process.html
> 
> [4] https://forrest.apache.org/guidelines.html
> 
> [5] https://incubator.apache.org/
> 

Re: [VOTE] Move Apache Forrest to the Attic

[David Crossley]

With four binding +1 and one non-binding +1, the vote passes to move Apache 
Forrest to the Attic.

The next step is to raise the resolution in the next board report. 
https://attic.apache.org/process.html

-David

On Mon, Nov 11, 2019 at 04:46:31PM +1100, David Crossley wrote:
> The Apache Forrest project has seen little activity for a long time, and 
> there has not been a release since 2011.
> 
> As noted in the quarterly Board reports [1], for years the Forrest PMC has 
> been keeping the project in maintenance mode.
> 
> Recent board reports have indicated a move to the Apache Attic. A thread was 
> commenced on the project mailing lists to provide an opportuntity for people 
> to discuss that possibility and to re-engage [2]. There was no further 
> discussion.
> 
> Note that the project resources would still be available. There would be no 
> further releases. The Apache Forrest PMC would be terminated by Board 
> resolution, and the Apache Attic PMC would instead have the oversight.
> 
> This vote thread is to confirm the desire of the project, being the next step 
> in the Attic process [3].
> 
> The general voting process is explained at the Forrest project guidelines 
> [4]. This situation was not anticipated by the guidelines. So in this case 
> anyone can vote.
> 
> So please vote whether Apache Forrest will be retired and moved to the Attic:
> +1 yes move to the Attic
> -1 the project should continue, and indicates commitment to revitalise the 
> project
> 
> The three outcomes could be:
> 
> A) There are three or more people voting -1, saying that they would instead 
> like the project to continue and agree to be involved.
> In this case, a probable course would be to go via the Apache Incubator [5] 
> to revitalise the community.
> 
> B) The normal positive outcome, with three or more +1 votes.
> C) Insufficent votes indicates a dormant PMC.
> 
> So in those latter cases, the remainder of the Attic process would ensue.
> 
> Also note that even after moving to the Attic, there are processes defined 
> there regarding moving out again.
> 
> The vote will run for one month to be summarised on 11 December.
> 
> 
> [1] https://whimsy.apache.org/board/minutes/Forrest.html
> 
> [2] 
> https://lists.apache.org/thread.html/fda24957e049f10d282037594d2aa61ce9a31cf8fc5313959aa81672@%3Cdev.forrest.apache.org%3E
> Subject: Forrest possibly retiring?
> Date: 2019-06-11
> 
> [3] https://attic.apache.org/process.html
> 
> [4] https://forrest.apache.org/guidelines.html
> 
> [5] https://incubator.apache.org/
> 

Re: [VOTE] Move Apache Forrest to the Attic

[David Crossley]

+1 move to the Attic.

-David

On Mon, Nov 11, 2019 at 04:46:31PM +1100, David Crossley wrote:
> The Apache Forrest project has seen little activity for a long time, and 
> there has not been a release since 2011.
> 
> As noted in the quarterly Board reports [1], for years the Forrest PMC has 
> been keeping the project in maintenance mode.
> 
> Recent board reports have indicated a move to the Apache Attic. A thread was 
> commenced on the project mailing lists to provide an opportuntity for people 
> to discuss that possibility and to re-engage [2]. There was no further 
> discussion.
> 
> Note that the project resources would still be available. There would be no 
> further releases. The Apache Forrest PMC would be terminated by Board 
> resolution, and the Apache Attic PMC would instead have the oversight.
> 
> This vote thread is to confirm the desire of the project, being the next step 
> in the Attic process [3].
> 
> The general voting process is explained at the Forrest project guidelines 
> [4]. This situation was not anticipated by the guidelines. So in this case 
> anyone can vote.
> 
> So please vote whether Apache Forrest will be retired and moved to the Attic:
> +1 yes move to the Attic
> -1 the project should continue, and indicates commitment to revitalise the 
> project
> 
> The three outcomes could be:
> 
> A) There are three or more people voting -1, saying that they would instead 
> like the project to continue and agree to be involved.
> In this case, a probable course would be to go via the Apache Incubator [5] 
> to revitalise the community.
> 
> B) The normal positive outcome, with three or more +1 votes.
> C) Insufficent votes indicates a dormant PMC.
> 
> So in those latter cases, the remainder of the Attic process would ensue.
> 
> Also note that even after moving to the Attic, there are processes defined 
> there regarding moving out again.
> 
> The vote will run for one month to be summarised on 11 December.
> 
> 
> [1] https://whimsy.apache.org/board/minutes/Forrest.html
> 
> [2] 
> https://lists.apache.org/thread.html/fda24957e049f10d282037594d2aa61ce9a31cf8fc5313959aa81672@%3Cdev.forrest.apache.org%3E
> Subject: Forrest possibly retiring?
> Date: 2019-06-11
> 
> [3] https://attic.apache.org/process.html
> 
> [4] https://forrest.apache.org/guidelines.html
> 
> [5] https://incubator.apache.org/
> 

[VOTE] Move Apache Forrest to the Attic

[David Crossley]

The Apache Forrest project has seen little activity for a long time, and there 
has not been a release since 2011.

As noted in the quarterly Board reports [1], for years the Forrest PMC has been 
keeping the project in maintenance mode.

Recent board reports have indicated a move to the Apache Attic. A thread was 
commenced on the project mailing lists to provide an opportuntity for people to 
discuss that possibility and to re-engage [2]. There was no further discussion.

Note that the project resources would still be available. There would be no 
further releases. The Apache Forrest PMC would be terminated by Board 
resolution, and the Apache Attic PMC would instead have the oversight.

This vote thread is to confirm the desire of the project, being the next step 
in the Attic process [3].

The general voting process is explained at the Forrest project guidelines [4]. 
This situation was not anticipated by the guidelines. So in this case anyone 
can vote.

So please vote whether Apache Forrest will be retired and moved to the Attic:
+1 yes move to the Attic
-1 the project should continue, and indicates commitment to revitalise the 
project

The three outcomes could be:

A) There are three or more people voting -1, saying that they would instead 
like the project to continue and agree to be involved.
In this case, a probable course would be to go via the Apache Incubator [5] to 
revitalise the community.

B) The normal positive outcome, with three or more +1 votes.
C) Insufficent votes indicates a dormant PMC.

So in those latter cases, the remainder of the Attic process would ensue.

Also note that even after moving to the Attic, there are processes defined 
there regarding moving out again.

The vote will run for one month to be summarised on 11 December.


[1] https://whimsy.apache.org/board/minutes/Forrest.html

[2] 
https://lists.apache.org/thread.html/fda24957e049f10d282037594d2aa61ce9a31cf8fc5313959aa81672@%3Cdev.forrest.apache.org%3E
Subject: Forrest possibly retiring?
Date: 2019-06-11

[3] https://attic.apache.org/process.html

[4] https://forrest.apache.org/guidelines.html

[5] https://incubator.apache.org/

Re: History - packaging, and the 0.9 release

[David Crossley]

One other discrepancy which would need to be fixed before the 0.10 release.

The distribution archives are not complete.

The listing here only contains the convenience package as explained below:
http://archive.apache.org/dist/forrest/0.9/

It needs to also have a copy of the 0.9 re-release as explained below,
especially the actual "*-sources" package.

The complete set of files are available at:
http://archive.apache.org/dist/forrest/
but they were not copied to the 0.9 space.

Perhaps there was a glitch with the archiving process around that time.

-David


On Tue, Aug 07, 2018 at 01:23:05PM +1000, David Crossley wrote:
> I did some archeology detective work to find how we ended up with three 
> separate release packages.
> 
> Aside: Way too much time wandering around broken email archives, grrr.
> With some of the links, i at least used the Apache URL Shortener to go via the
> Gmane message-id service. I found that some links to there do still work.
> However, if they have gone then we should be able to get the message-id from
> the Shortener (i thought that it was by appending "?action=display", but no)
> and then use some other email archive to lookup with the message-id.
> Surely lists.apache.org can do that but i cannot find how.
> 
> So on our download page we link to two separate packages:
> 
> apache-forrest-0.9-sources.tar.gz
> apache-forrest-0.9-dependencies.tar.gz
> 
> Yet the $FORREST_HOME/main/build.xml only generates apache-forrest-0.9.tar.gz
> 
> Our "How_to_release" doc does not mention the separate "*-sources" and 
> "*.dependencies" packages.
> 
> Looking behind the scenes at:
> http://archive.apache.org/dist/forrest/
> Shows that the "*-sources" and "*.dependencies" packages are dated 2012-11-21
> and the other one is dated earlier at 2011-02-01.
> 
> The date 2011-02-01 is our original 0.9 release date.
> 
> The source of our download mirrors page was edited around 2012-04-20
> to link to those separate packages.
> 
> Going back to the mail archives around March April 2012 shows that we needed
> to re-release 0.9:
>   Date: Thu, 29 Mar 2012 17:55:13 +1100
>   From: David Crossley 
>   To: dev@forrest.apache.org
>   Subject: [Proposal] re-release 0.9 with proper source code package
>   Message-ID: <20120329065513.GA6677@igg.local>
> See its linked message from Roy that:
>> ... jar files of dependencies -- they are NOT our product and they
>> MUST NOT be present in the source code package that is voted on for 
> release.
> 
> We did our original release of apache-forrest-0.9.tar.gz on 2011-02-01
> then followed up with a proper "sources-only" release on 2012-04-19.
> 
> Note that the "How_to_release" doc and the main/build.xml have not been 
> updated to do that.
> 
> Why were those packages amended on 2012-11-21?
> I reckon that that is probably this:
>   https://issues.apache.org/jira/browse/FOR-1239
>   utilise svnpubsub for Forrest distribution area
> 
> Then around 2013-11-29 a distribution maintainer asked about the separate 
> packages
> and could we provide a combined one:
>   https://issues.apache.org/jira/browse/FOR-1244
>   "Fat tar" for easier installation
> 
> I did provide the instructions there to enable one of the Forrest PMC to 
> combine the packages into one and deploy that to the dist area.
> I presume that no-one did, otherwise the apache-forrest-0.9.tar.gz
> would have a date newer than the original of 2011-02-01.
> So that is considered to be a convenience archive, but not the one called
> for in FOR-1244.
> 
> Gavin commented yesterday in that FOR-1244 wondering about the release 
> packaging.
> I will link from there to here to help explain.
> 
> Good luck, i hope that this history helps.
> 
> -David
> 

[jira] [Commented] (FOR-1244) "Fat tar" for easier installation

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1244:
-

Ah, no. That is the original convenience archive of the original 0.9 release.

We re-released later with two separate archives (the "*-sources.tar.gz" and the 
"*-dependencies.tar.gz" which are the [A] and [B] referred to above) as can be 
seen on our Downloads page and in that Homebrew formula.

We did not follow through as explained in the comment above to provide a new 
combined file [C].

This message today tries to summarise the history:

Date: Tue, 7 Aug 2018 13:23:05 +1000
From: David Crossley
To: dev at forrest
Subject: History - packaging, and the 0.9 release


> "Fat tar" for easier installation
> -
>
> Key: FOR-1244
> URL: https://issues.apache.org/jira/browse/FOR-1244
> Project: Forrest
>  Issue Type: Improvement
>  Components: Compile
>Reporter: Raymie Stata
>Priority: Major
> Fix For: 0.10-dev
>
>
> I've been writing a Homebrew formula for installing Forrest onto Macs 
> (https://github.com/mxcl/homebrew/pull/24520).  Homebrew doesn't handle the 
> two-tar-file structure of your distribution very well.  Can you publish a 
> "fat-tar" file that combines the contents of both, in addition to the two 
> independent ones?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

History - packaging, and the 0.9 release

[David Crossley]

I did some archeology detective work to find how we ended up with three 
separate release packages.

Aside: Way too much time wandering around broken email archives, grrr.
With some of the links, i at least used the Apache URL Shortener to go via the
Gmane message-id service. I found that some links to there do still work.
However, if they have gone then we should be able to get the message-id from
the Shortener (i thought that it was by appending "?action=display", but no)
and then use some other email archive to lookup with the message-id.
Surely lists.apache.org can do that but i cannot find how.

So on our download page we link to two separate packages:

apache-forrest-0.9-sources.tar.gz
apache-forrest-0.9-dependencies.tar.gz

Yet the $FORREST_HOME/main/build.xml only generates apache-forrest-0.9.tar.gz

Our "How_to_release" doc does not mention the separate "*-sources" and 
"*.dependencies" packages.

Looking behind the scenes at:
http://archive.apache.org/dist/forrest/
Shows that the "*-sources" and "*.dependencies" packages are dated 2012-11-21
and the other one is dated earlier at 2011-02-01.

The date 2011-02-01 is our original 0.9 release date.

The source of our download mirrors page was edited around 2012-04-20
to link to those separate packages.

Going back to the mail archives around March April 2012 shows that we needed
to re-release 0.9:
  Date: Thu, 29 Mar 2012 17:55:13 +1100
  From: David Crossley 
  To: dev@forrest.apache.org
  Subject: [Proposal] re-release 0.9 with proper source code package
  Message-ID: <20120329065513.GA6677@igg.local>
See its linked message from Roy that:
   > ... jar files of dependencies -- they are NOT our product and they
   > MUST NOT be present in the source code package that is voted on for 
release.

We did our original release of apache-forrest-0.9.tar.gz on 2011-02-01
then followed up with a proper "sources-only" release on 2012-04-19.

Note that the "How_to_release" doc and the main/build.xml have not been updated 
to do that.

Why were those packages amended on 2012-11-21?
I reckon that that is probably this:
  https://issues.apache.org/jira/browse/FOR-1239
  utilise svnpubsub for Forrest distribution area

Then around 2013-11-29 a distribution maintainer asked about the separate 
packages
and could we provide a combined one:
  https://issues.apache.org/jira/browse/FOR-1244
  "Fat tar" for easier installation

I did provide the instructions there to enable one of the Forrest PMC to 
combine the packages into one and deploy that to the dist area.
I presume that no-one did, otherwise the apache-forrest-0.9.tar.gz
would have a date newer than the original of 2011-02-01.
So that is considered to be a convenience archive, but not the one called
for in FOR-1244.

Gavin commented yesterday in that FOR-1244 wondering about the release 
packaging.
I will link from there to here to help explain.

Good luck, i hope that this history helps.

-David

Re: Release Manager, Next Release. 0.10

[David Crossley]

Thanks for taking on this job.

-David

[jira] [Updated] (FOR-853) Links: using Jira to manage issues for next release

[David Crossley (JIRA)]

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

David Crossley updated FOR-853:
---
Description: 
We have an incomplete discussion about how to use Jira to assist with 
management of our issues, and a classification method to identify issues for 
the next release, and Jira filters so that we can see important outstanding 
issues at a glance. This needs to be finalised and documented (probably in 
/issues.html)
and also need to document our procedure for release.

Re: planning the 0.8 release (Was: [RT] structurer location and resource types)
http://marc.info/?t=11432466733


  was:
We have an incomplete discussion about how to use Jira to assist with 
management of our issues, and a classification method to identify issues for 
the next release, and Jira filters so that we can see important outstanding 
issues at a glance. This needs to be finalised and documented (probably in 
/issues.html)
and also need to document our procedure for release.

Re: planning the 0.8 release (Was: [RT] structurer location and resource types)
http://marc.theaimsgroup.com/?t=11432466733



> Links: using Jira to manage issues for next release
> ---
>
> Key: FOR-853
> URL: https://issues.apache.org/jira/browse/FOR-853
> Project: Forrest
>  Issue Type: Bug
>  Components: Discussion links to archives, Project administration
>    Reporter: David Crossley
>Priority: Major
>
> We have an incomplete discussion about how to use Jira to assist with 
> management of our issues, and a classification method to identify issues for 
> the next release, and Jira filters so that we can see important outstanding 
> issues at a glance. This needs to be finalised and documented (probably in 
> /issues.html)
> and also need to document our procedure for release.
> Re: planning the 0.8 release (Was: [RT] structurer location and resource 
> types)
> http://marc.info/?t=11432466733



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (FOR-853) Links: using Jira to manage issues for next release

[David Crossley (JIRA)]

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

David Crossley commented on FOR-853:


This is an old issue (but never finalised). The document 
http://forrest.apache.org/procedures/release/How_to_release.html will be the 
most useful at this stage.

> Links: using Jira to manage issues for next release
> ---
>
> Key: FOR-853
> URL: https://issues.apache.org/jira/browse/FOR-853
> Project: Forrest
>  Issue Type: Bug
>  Components: Discussion links to archives, Project administration
>    Reporter: David Crossley
>Priority: Major
>
> We have an incomplete discussion about how to use Jira to assist with 
> management of our issues, and a classification method to identify issues for 
> the next release, and Jira filters so that we can see important outstanding 
> issues at a glance. This needs to be finalised and documented (probably in 
> /issues.html)
> and also need to document our procedure for release.
> Re: planning the 0.8 release (Was: [RT] structurer location and resource 
> types)
> http://marc.theaimsgroup.com/?t=11432466733



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Forrestbot site publishes always include dtd pdf changes

[David Crossley]

A note for the archives:

A glance (there might be more) at the issues for Component "Plugin: output.pdf"
found these two:

https://issues.apache.org/jira/browse/FOR-1077
new CreationDate causes constant differences in output pdf documents

https://issues.apache.org/jira/browse/FOR-1200
stop re-generating PDF documents on Forrest website

-David

On Thu, Jan 25, 2018 at 09:47:59AM +1100, Gavin McDonald wrote:
> 
> 
> > On 25 Jan 2018, at 9:41 am, David Crossley <cross...@apache.org> wrote:
> > 
> > On Mon, Jan 22, 2018 at 10:50:43PM +1100, Gavin McDonald wrote:
> >> As per the subject, I was checking through the forrest svn-site mailing 
> >> list archives [1] and noticed that every time (usually David) publishes 
> >> the Forrest website, two pdf changes to the same two documents (v13 and 
> >> v20) are always published as well - even though they are clearly not part 
> >> of the changes that triggered the publish in the first place.
> >> 
> >> Do we know why? 
> > 
> > Yes. There is some discussion and issues in the archives, but sorry i have 
> > no time to find it.
> 
> ack thanks, after I sent this note a bit of deja vu crept in :)
> 
> > 
> > IIRC, it has something to do with the generation of the PDFs by FOP.
> > It rewrites some metadata (perhaps "date") every time.
> > 
> > As you can see from [1] i just let it deploy anyway.
> 
> ok thanks.
> > 
> > You may find also that there is some generated image that changes for no 
> > apparent reason.
> > This flip-flops depending on the operating system of the person doing the 
> > deployment.
> > We have not seen it for a while, as it has been only me doing the 
> > publishing.
> 
> Ok, lets see what happens when I do it - these days Im on a MAC
> 
> Gav…
> 
> > 
> > -David
> > 
> >> Gav…
> >> 
> >> [1] -  
> >> https://lists.apache.org/list.html?site-...@forrest.apache.org:2017-10 
> >> <https://lists.apache.org/list.html?site-...@forrest.apache.org:2017-10> 
> >> 
> >> 
> 

[jira] [Commented] (FOR-329) doesn't preserve space

[David Crossley (JIRA)]

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

David Crossley commented on FOR-329:


Yes to the other skins. Don't know what is happening with dispatcher. For PDF i 
don't know offhand -- it would need some detective work.


>  doesn't preserve space
> ---
>
> Key: FOR-329
> URL: https://issues.apache.org/jira/browse/FOR-329
> Project: Forrest
>  Issue Type: Bug
>  Components: XML grammars  validation
>Affects Versions: 0.6, 0.8, 0.9, 0.10-dev
> Environment: The sample document, document-v20.html, on the Forrest 
> Apache website viewed from IE 6.0.
>Reporter: asdf
>Assignee: Gavin
>Priority: Minor
>
> Lines 45-48 of src/documentation/content/xdocs/docs/document-v20.xml show a 
> paragraph with white space:
> 45:   46:>With the p xml:space="preserve" attribute, 
> you can declare
> 47:that whitespace shouldbe   preserved, without implying it is 
> in any other
> 48:way special.
> In viewing the document at http://forrest.apache.org/docs/document-v20.html 
> with IE 6.0 I see the following:
> With the  attribute, you can declare that whitespace 
> should be preserved, without implying it is in any other way special.
> Thanks,
> Mark



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Forrestbot site publishes always include dtd pdf changes

[David Crossley]

On Mon, Jan 22, 2018 at 10:50:43PM +1100, Gavin McDonald wrote:
> As per the subject, I was checking through the forrest svn-site mailing list 
> archives [1] and noticed that every time (usually David) publishes the 
> Forrest website, two pdf changes to the same two documents (v13 and v20) are 
> always published as well - even though they are clearly not part of the 
> changes that triggered the publish in the first place.
> 
> Do we know why? 

Yes. There is some discussion and issues in the archives, but sorry i have no 
time to find it.

IIRC, it has something to do with the generation of the PDFs by FOP.
It rewrites some metadata (perhaps "date") every time.

As you can see from [1] i just let it deploy anyway.

You may find also that there is some generated image that changes for no 
apparent reason.
This flip-flops depending on the operating system of the person doing the 
deployment.
We have not seen it for a while, as it has been only me doing the publishing.

-David

> Gav…
> 
> [1] -  https://lists.apache.org/list.html?site-...@forrest.apache.org:2017-10 
>  
> 
> 

[jira] [Commented] (FOR-329) doesn't preserve space

[David Crossley (JIRA)]

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

David Crossley commented on FOR-329:


Following the page: https://forrest.apache.org/docs/changes.html
shows that this was introduced in https://svn.apache.org/r7460

That might assist finding what has changed to CSS since then.

>  doesn't preserve space
> ---
>
> Key: FOR-329
> URL: https://issues.apache.org/jira/browse/FOR-329
> Project: Forrest
>  Issue Type: Bug
>  Components: XML grammars  validation
>Affects Versions: 0.6, 0.8, 0.9, 0.10-dev
> Environment: The sample document, document-v20.html, on the Forrest 
> Apache website viewed from IE 6.0.
>Reporter: asdf
>Priority: Minor
>
> Lines 45-48 of src/documentation/content/xdocs/docs/document-v20.xml show a 
> paragraph with white space:
> 45:   46:>With the p xml:space="preserve" attribute, 
> you can declare
> 47:that whitespace shouldbe   preserved, without implying it is 
> in any other
> 48:way special.
> In viewing the document at http://forrest.apache.org/docs/document-v20.html 
> with IE 6.0 I see the following:
> With the  attribute, you can declare that whitespace 
> should be preserved, without implying it is in any other way special.
> Thanks,
> Mark



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [GitHub] forrest pull request #1: Trivial typo

[David Crossley]

On Tue, Mar 21, 2017 at 07:33:47PM -0700, Brian M Dube wrote:
> On 03/21/2017 05:55 PM, Brian M Dube wrote:
> > On 03/20/2017 08:09 PM, David Crossley wrote:
> >>
> >> Ah, i do not know. There must be some docs at ASF Infra.
> >> I do know that the process has been refined and is ready now.
> >>
> >> We should have sorted ourselves before the first pull request.
> >>
> >> One issue will be that that mirror is way out-of-date. I presume that
> >> it is still from the initial experiment many years ago.
> > 
> > The github mirror is out of date, and it's unclear to me why that is.
> > Github mirrors git://git.apache.org/forrest.git and that in turn is
> > supposed to keep up with our main svn location. But that's not happening.
> 
> It's not happening because once upon a time in our svn history, we had a
> branch name that was allowed by svn but disallowed by git. So now the
> mirroring process with branches enabled cannot continue. Infra has
> disabled branches for our mirror for the time being so that we can at
> least sync svn trunk to git and deal with the current pull request.
> 
> Details at https://issues.apache.org/jira/browse/INFRA-13719
> 
> My chat with infra also answered the question about contributions.
> Membership in the github.com/apache organization does signify that ICLA
> is on file and there is no issue accepting such a user's work.

Fantastic. Thanks for sorting all of that out.

Today i did attempt to find up-to-date documentation to assist us, but
that has consumed all available time. Hope someone else has better luck.

> >> Also we need the notifications to go to our svn@ list, not dev.
> > 
> > Do you mean pull requests like the one below should go to svn@, or just
> > commits?

I confused myself. I meant that commits should go to that list,
and the pull requests do come here to dev.

-David

> It looks like this is handled at the Service Desk under Github Integration.
> 
> https://issues.apache.org/jira/servicedesk/customer/portal/1
> 
> > Brian
> > 
> >> That should have been called "commits" or some such. Perhaps need an alias.
> >>
> >> -David
> >>
> >> On Mon, Mar 20, 2017 at 04:30:16PM -0700, Brian M Dube wrote:
> >>> Thank you, kinow.
> >>>
> >>> So how does this work? I can see that github user kinow is a member of
> >>> the github.com/apache organization. There is also a ki...@apache.org
> >>> with matching name. Is that all we need to know to accept and attribute
> >>> commits from github?
> >>>
> >>> Brian
> >>>
> >>> On 03/19/2017 04:57 AM, kinow wrote:
> >>>> GitHub user kinow opened a pull request:
> >>>>
> >>>> https://github.com/apache/forrest/pull/1
> >>>>
> >>>> Trivial typo
> >>>>
> >>>> 
> >>>>
> >>>> You can merge this pull request into a Git repository by running:
> >>>>
> >>>> $ git pull https://github.com/kinow/forrest trunk
> >>>>
> >>>> Alternatively you can review and apply these changes as the patch at:
> >>>>
> >>>> https://github.com/apache/forrest/pull/1.patch
> >>>>
> >>>> To close this pull request, make a commit to your master/trunk branch
> >>>> with (at least) the following in the commit message:
> >>>>
> >>>> This closes #1
> >>>> 
> >>>> 
> >>>> commit 857a0eaaf8c17c5c17e690258a99905ff29879fa
> >>>> Author: Bruno P. Kinoshita <ki...@users.noreply.github.com>
> >>>> Date:   2017-03-19T11:56:57Z
> >>>>
> >>>> Trivial typo
> >>>>
> >>>> 
> >>>>
> >>>>
> >>>> ---
> >>>> If your project is set up for it, you can reply to this email and have 
> >>>> your
> >>>> reply appear on GitHub as well. If your project does not have this 
> >>>> feature
> >>>> enabled and wishes so, or if the feature is enabled but not working, 
> >>>> please
> >>>> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> >>>> with INFRA.
> >>>> ---
> >>>>
> >>>
> 

Re: [GitHub] forrest pull request #1: Trivial typo

[David Crossley]

Ah, i do not know. There must be some docs at ASF Infra.
I do know that the process has been refined and is ready now.

We should have sorted ourselves before the first pull request.

One issue will be that that mirror is way out-of-date. I presume that
it is still from the initial experiment many years ago.

Also we need the notifications to go to our svn@ list, not dev.
That should have been called "commits" or some such. Perhaps need an alias.

-David

On Mon, Mar 20, 2017 at 04:30:16PM -0700, Brian M Dube wrote:
> Thank you, kinow.
> 
> So how does this work? I can see that github user kinow is a member of
> the github.com/apache organization. There is also a ki...@apache.org
> with matching name. Is that all we need to know to accept and attribute
> commits from github?
> 
> Brian
> 
> On 03/19/2017 04:57 AM, kinow wrote:
> > GitHub user kinow opened a pull request:
> > 
> > https://github.com/apache/forrest/pull/1
> > 
> > Trivial typo
> > 
> > 
> > 
> > You can merge this pull request into a Git repository by running:
> > 
> > $ git pull https://github.com/kinow/forrest trunk
> > 
> > Alternatively you can review and apply these changes as the patch at:
> > 
> > https://github.com/apache/forrest/pull/1.patch
> > 
> > To close this pull request, make a commit to your master/trunk branch
> > with (at least) the following in the commit message:
> > 
> > This closes #1
> > 
> > 
> > commit 857a0eaaf8c17c5c17e690258a99905ff29879fa
> > Author: Bruno P. Kinoshita 
> > Date:   2017-03-19T11:56:57Z
> > 
> > Trivial typo
> > 
> > 
> > 
> > 
> > ---
> > If your project is set up for it, you can reply to this email and have your
> > reply appear on GitHub as well. If your project does not have this feature
> > enabled and wishes so, or if the feature is enabled but not working, please
> > contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> > with INFRA.
> > ---
> > 
> 

mail not showing at lists.apache.org

[David Crossley]

It came to our attention that mail for the svn@ and site-svn@ lists
is being delivered, but not showing at lists.apache.org archives.

I have contacted ASF Infrastructure.

-David

[jira] [Closed] (FOR-244) UTF escapes (entities) in site.xml label attributes makes forrest build fail

[David Crossley (JIRA)]

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

David Crossley closed FOR-244.
--

> UTF escapes (entities) in site.xml label attributes makes forrest build fail
> 
>
> Key: FOR-244
> URL: https://issues.apache.org/jira/browse/FOR-244
> Project: Forrest
>  Issue Type: Bug
>  Components: XML grammars & validation
>Affects Versions: 0.6
>Reporter: johan Eltes
> Fix For: 0.10-dev
>
>
>  in site.xml 
> makes the forrest fail with:  BROKEN: The entity "ouml" was referenced, but 
> not declared.



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

Re: External component and forrest site

[David Crossley]

Brian M Dube wrote:
> Sjur Moshagen wrote:
> > Hello all,
> > 
> > As a follow-up on the previous question, here’s another one:
> > 
> > I need to be able to build a static version of the site. This works fine 
> > _except_ for this editor thing that I added to 
> > $PROJECT_HOME/src/documentation/resources/.
> > 
> > The thing is, that the ant build files are _mimicking_ the xmaps etc, they 
> > are not directly using them. And in this case ant is not copying any (?) of 
> > the files found in that resources dir except for the one linked to in the 
> > html page that contains the editor.

Around line 82 of main/targets/site.xml
it copies only certain project resources, explicitly the images directory.

Perhaps the ability was never completed to copy over certain relevant
other project resources.

> > So:
> > 
> > how can I tell ant that _in this project_ I need to copy everything in 
> > resources/x/ to site/x/?

Perhaps this is indicating that this should be in a plugin.
There is a section at the end of each plugin build.xml file,
that shows how to copy over extra resources.

I only found one that utilises that: the output.htmlArea plugin.
(Not sure about the state of that plugin, but at least useful as an example.)

As a plugin would make it easier to apply to various projects.

> I thought I remembered there being a setting to control this. All I'm
> finding now is:
> 
> https://forrest.apache.org/docs_0_100/howto/howto-asf-mirror.html#link
> and
> https://forrest.apache.org/docs_0_100/faq.html#cli-xconf
> 
> Have you already tried that?
> 
> Brian

And if your project uses Forrestbot to deploy, then that might assist
on a per-project level.

http://forrest.apache.org/tools/forrestbot.html#Workstages
discusses using your own "getlocal.get" workstage.

Another way is shown in our "zone" SVN forrest/zone/config/run-forrestbot.sh
which can copy some stuff before invoking forrest.

-David

[jira] [Closed] (FOR-1256) Add to licensing info for bundled bootstrap, jquery, glyphicons

[David Crossley (JIRA)]

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

David Crossley closed FOR-1256.
---

> Add to licensing info for bundled bootstrap, jquery, glyphicons
> ---
>
> Key: FOR-1256
> URL: https://issues.apache.org/jira/browse/FOR-1256
> Project: Forrest
>  Issue Type: Task
>  Components: Licenses and Notices, Skins (general issues)
>Affects Versions: 0.10-dev
>    Reporter: David Crossley
>Assignee: Sjur N. Moshagen
> Fix For: 0.10-dev
>
>
> As the supporting CSS and JavaScript and fonts for the new "fleece" skin are 
> bundled, we need to adhere to their licensing requirements.



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

[jira] [Closed] (FOR-1257) Enable use of font formats

[David Crossley (JIRA)]

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

David Crossley closed FOR-1257.
---
Resolution: Fixed

Added: r1752365

> Enable use of font formats
> --
>
> Key: FOR-1257
> URL: https://issues.apache.org/jira/browse/FOR-1257
> Project: Forrest
>  Issue Type: New Feature
>  Components: Core operations, Skins (general issues)
>Affects Versions: 0.10-dev
>    Reporter: David Crossley
> Fix For: 0.10-dev
>
>
> The new Bootstrap-based skin "fleece" CSS files have links to ../fonts/*.*
> So the sitemap and locationmap files need to handle them.



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

[jira] [Created] (FOR-1257) Enable use of font formats

[David Crossley (JIRA)]

David Crossley created FOR-1257:
---

 Summary: Enable use of font formats
 Key: FOR-1257
 URL: https://issues.apache.org/jira/browse/FOR-1257
 Project: Forrest
  Issue Type: New Feature
  Components: Core operations, Skins (general issues)
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


The new Bootstrap-based skin "fleece" CSS files have links to ../fonts/*.*

So the sitemap and locationmap files need to handle them.



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

[jira] [Commented] (FOR-1256) Add to licensing info for bundled bootstrap, jquery, glyphicons

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1256:
-

Instead, i reckon that any licenses/* should have link entries in our top-level 
LICENSE file, and any required notices go into our top-level NOTICE file.

> Add to licensing info for bundled bootstrap, jquery, glyphicons
> ---
>
> Key: FOR-1256
> URL: https://issues.apache.org/jira/browse/FOR-1256
> Project: Forrest
>  Issue Type: Task
>  Components: Licenses and Notices, Skins (general issues)
>Affects Versions: 0.10-dev
>    Reporter: David Crossley
>Assignee: Sjur N. Moshagen
> Fix For: 0.10-dev
>
>
> As the supporting CSS and JavaScript and fonts for the new "fleece" skin are 
> bundled, we need to adhere to their licensing requirements.



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

Re: New skin fleece

[David Crossley]

Fantastic.

Forrest indicates trouble finding the "fonts/*" files
(which are linked from the bootstrap css) and the bootstrap*.css.map

This probably needs to be handled by webapp/resources.xmap and
webapp/locationmap-skins.xml

I have tried, but run out of time - away now for a few days.

-David

[jira] [Commented] (FOR-1256) Add to licensing info for bundled bootstrap, jquery, glyphicons

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1256:
-

Follow Justin's fantastic demonstration project at 
https://github.com/justinmclean/ApacheWombat

> Add to licensing info for bundled bootstrap, jquery, glyphicons
> ---
>
> Key: FOR-1256
> URL: https://issues.apache.org/jira/browse/FOR-1256
> Project: Forrest
>  Issue Type: Task
>  Components: Licenses and Notices, Skins (general issues)
>Affects Versions: 0.10-dev
>    Reporter: David Crossley
> Fix For: 0.10-dev
>
>
> As the supporting CSS and JavaScript and fonts for the new "fleece" skin are 
> bundled, we need to adhere to their licensing requirements.



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

[jira] [Created] (FOR-1256) Add to licensing info for bundled bootstrap, jquery, glyphicons

[David Crossley (JIRA)]

David Crossley created FOR-1256:
---

 Summary: Add to licensing info for bundled bootstrap, jquery, 
glyphicons
 Key: FOR-1256
 URL: https://issues.apache.org/jira/browse/FOR-1256
 Project: Forrest
  Issue Type: Task
  Components: Licenses and Notices, Skins (general issues)
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


As the supporting CSS and JavaScript and fonts for the new "fleece" skin are 
bundled, we need to adhere to their licensing requirements.



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

new mail archives interface

[David Crossley]

At the recent ApacheCon conference, the new mail archives interface was 
unveiled.

See https://lists.apache.org/

See the mention at the weekly article "The Apache News Round-up"
https://blogs.apache.org/foundation/entry/the_apache_news_round_up85

See background information about Forrest mail lists:
https://forrest.apache.org/mail-lists.html

-David

[REMINDER] ApacheCon NA 2016 Travel Assistance Applications now open!

[David Crossley]

The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon North America 2016 are now open! This
announcement serves as a purpose for you (pmcs@) to let members of your
community know about both ApacheConNA 2016 and about the TAC assistance to
attend. Could you please forward this announcement to your community,
along  with (if possible) information on how your project is involved in
ApacheCon this year?

We will be supporting ApacheCon NA, Vancouver BC, May 9th - 13th 2016.

TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons. For more info on this years
applications and qualifying criteria please visit the TAC website at <
http://www.apache.org/travel/ >.   Applications are already open, so don't
delay!

*Important dates*...

   - CFP Close: February 12, 2016
   - CFP Notifications: February 29, 2016
   - TAC Applications close:  March 2, 2016
   - Schedule Announced: March 3, 2016

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as required
to efficiently and accurately process your request), this will enable TAC
to announce successful awards shortly afterwards.

As usual TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.

We look forward to greeting many of you in Vancouver, BC in May 2016!

Kind Regards

Lewis

(On behalf of the Travel Assistance Committee)

Re: Title element content in v2 docs

[David Crossley]

I did some net archaeology:

This was initially added to document-v11 DTD around 2003-03-20,
i gather as part of the alignment with xhtml at the time.
Soon after, the DTD changes since Forrest-0.4 were removed
and the new document-v12 was commenced in CVS on 2003-04-24:
http://marc.info/?l=forrest-dev=105115903415487
which did contain a comment about it.

The comment is also listed at the end of our example documents, e.g.:
http://forrest.apache.org/dtdx/document-v20.html#changes-12
viz:
"doc-v12 enhances doc-v11 by relaxing various restrictions that were found to 
be unnecessary.
* Links ((link|jump|fork) and inline elements (br|img|icon|acronym) are allowed 
inside title.
* ..."

-David

Sjur Moshagen wrote:
> Hello all,
> 
> I just noticed a discrepancy between the dtd and the actual rendering in the 
> default (and possibly all) skins for the title element. The DTD says:
> 
> title
> Element name title
> Content model ( #PCDATA | strong | em | code | sub | sup | a | br | 
> img | icon | acronym | map ) *
> Attributes
> idtype: ID
> class type: CDATA
> xml:lang  type: NMTOKEN
> Used inside   header | section
> 
> I then tried to add an img element inside title, but it is removed during the 
> transformations to html. It is there in the intermediate xml:
> 
> 
> 
> OSX
> 
> 
> Question:
> 
> Does this mean that it never has been added to the html rendering (ie various 
> skins/default html transform), or that it really should not be part of the 
> content model for the title element? The same question is valid also for the 
> remaining title subelements.
> 
> Grateful for feedback.
> 
> Sjur
> 
> 

[jira] [Commented] (FOR-1255) back-port features from the "scales" skin to the "pelt" skin

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1255:
-

Added the "Conditional display of menuitems" ("showonlywhenselected") feature 
to pelt skin in http://svn.apache.org/r1716292

> back-port features from the "scales" skin to the "pelt" skin
> 
>
> Key: FOR-1255
> URL: https://issues.apache.org/jira/browse/FOR-1255
> Project: Forrest
>  Issue Type: Improvement
>  Components: Skins (general issues)
>    Affects Versions: 0.10-dev
>Reporter: David Crossley
>
> There are some features, such as menu "showonlywhenselected", that would be 
> good to go back into the main "pelt" skin.



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

[jira] [Created] (FOR-1255) back-port features from the "scales" skin to the "pelt" skin

[David Crossley (JIRA)]

David Crossley created FOR-1255:
---

 Summary: back-port features from the "scales" skin to the "pelt" 
skin
 Key: FOR-1255
 URL: https://issues.apache.org/jira/browse/FOR-1255
 Project: Forrest
  Issue Type: Improvement
  Components: Skins (general issues)
Affects Versions: 0.10-dev
    Reporter: David Crossley


There are some features, such as menu "showonlywhenselected", that would be 
good to go back into the main "pelt" skin.



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

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1251:
-

Wow, thanks so much for your great work.

I reviewed the commits, but not yet investigated the output logs on the vm.

> 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

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1251:
-

Did a quick investigation on the server. Seems to be working. Well done.

I did a little clean-up. There was some remnants of an old "forrest-seed" site 
in ~forrest-role
probably the result of an old mis-configured run.

> 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-1254) Update documentation for project virtual machine

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1254:
-

The GIT URLs to browse the Puppet config is explained in issue INFRA-9093 that 
set up the new vm.

Need to find ASF Infrastructure documentation for getting our changes added.

> Update documentation for project virtual machine
> 
>
> Key: FOR-1254
> URL: https://issues.apache.org/jira/browse/FOR-1254
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: Brian M Dube
>Priority: Minor
>
> Find all documentation referencing FreeBSD jails and Solaris zones and update 
> it for the new virtual machine.



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

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

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1251:
-

So our next priority is to adjust the Puppet config. The location is explained 
in issue INFRA-9093 that set up the new vm.

> 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-1254) Update documentation for project virtual machine

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1254:
-

The current documentation is at http://forrest.apache.org/zone.html
That has some fixme notes and links to some other stuff.

> Update documentation for project virtual machine
> 
>
> Key: FOR-1254
> URL: https://issues.apache.org/jira/browse/FOR-1254
> Project: Forrest
>  Issue Type: Task
>  Components: zones.a.o administration
>Reporter: Brian M Dube
>Priority: Minor
>
> Find all documentation referencing FreeBSD jails and Solaris zones and update 
> it for the new virtual machine.



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

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

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1251:
-

Brian has started some initial work while the new machine was being set up (see 
some notes in INFRA-9093). He will now be away for a while, and i will also be 
busy.

If any Forrest committer wants to help, then i will set you up as a user after 
you add your SSH key via https://id.apache.org/

Brian sent me these notes:
> I haven't really done anything that would need documentation yet, but here's 
> a rough list:
> 
> - created user forrest
> - recreated ~forrest/ structure
> - performed `svn upgrade` where prompted (note upgrade, not update, necessary 
> because the working copy was so old)
> - started to address the crontab and ~forrest/config/*.sh scripts
Do 'svn diff' in the various directories, and incorporate those change to our 
forrest/zone SVN.
> - the active crontab from the old zone and the copy in svn differed, but I 
> don't remember what the differences were
They relate to removing old log files once-per-day. Perhaps this could be 
simplified.
> - I saved a copy of the active crontab on the new vm as ~bdube/cron.forrest
> - there is also ~bdube/forrest.home.tar.bz2 because I didn't want to miss 
> anything that wasn't captured in svn

> 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-1253) consider using the head/link rel=canonical for non-current sets of docs

[David Crossley (JIRA)]

David Crossley created FOR-1253:
---

 Summary: consider using the head/link rel=canonical for 
non-current sets of docs
 Key: FOR-1253
 URL: https://issues.apache.org/jira/browse/FOR-1253
 Project: Forrest
  Issue Type: Improvement
  Components: Plugin: internal.dispatcher, Skins (general issues)
Reporter: David Crossley
 Fix For: 0.10-dev


We have three sets of online documentation: for the current release, for the 
past release, and for the in-development set. Search engines need to be 
assisted to prefer the current set.



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

[jira] [Commented] (FOR-1253) consider using the head/link rel=canonical for non-current sets of docs

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1253:
-

Consider adding the link href=... rel=current to the head of output html for 
the past set of documentation.

Here is one discussion of the situation:
https://moz.com/blog/canonical-url-tag-the-most-important-advancement-in-seo-practices-since-sitemaps

As an example, see the older versions of Apache HTTP Server Documentation
http://httpd.apache.org/docs/
Their mail archives probably have discussion of when they introduced this.

Some factors to consider:

Should the href be a relative url with a leading slash.

Should it be double-slash.

Should we utilise the following redirection facility that we already have in 
place:
http://forrest.apache.org/docs/ redirects to the current set.
http://forrest.apache.org/docs/dev/ redirects to the in-development set.

Verify the .htaccess file.

There is also the documentation for each plugin.

 consider using the head/link rel=canonical for non-current sets of docs
 ---

 Key: FOR-1253
 URL: https://issues.apache.org/jira/browse/FOR-1253
 Project: Forrest
  Issue Type: Improvement
  Components: Plugin: internal.dispatcher, Skins (general issues)
Reporter: David Crossley
 Fix For: 0.10-dev


 We have three sets of online documentation: for the current release, for the 
 past release, and for the in-development set. Search engines need to be 
 assisted to prefer the current set.



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

[jira] [Commented] (FOR-1246) Upgrade packaged Ant to 1.9.x

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1246:
-

There are some notes in $FORREST_HOME/tools/ant/bin/README-forrest-upgrade.txt

 Upgrade packaged Ant to 1.9.x
 -

 Key: FOR-1246
 URL: https://issues.apache.org/jira/browse/FOR-1246
 Project: Forrest
  Issue Type: Improvement
  Components: Core operations
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


 Upgrade our packaged Apache Ant to a recent version.



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

[jira] [Created] (FOR-1252) update licenses to use the new W3C Software and Document Notice and License

[David Crossley (JIRA)]

David Crossley created FOR-1252:
---

 Summary: update licenses to use the new W3C Software and Document 
Notice and License
 Key: FOR-1252
 URL: https://issues.apache.org/jira/browse/FOR-1252
 Project: Forrest
  Issue Type: Task
  Components: Licenses and Notices
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


W3C has a new license. We need to review the supporting products that we use 
that has one of the old licenses. See the list in $FORREST_HOME/LICENSE.txt 
file and related files.



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

[jira] [Updated] (FOR-857) append license files to the top-level LICENSE.txt

[David Crossley (JIRA)]

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

David Crossley updated FOR-857:
---
Component/s: (was: Project administration)
 Licenses and Notices

Added a new JIRA Component Licenses and Notices.

 append license files to the top-level LICENSE.txt
 -

 Key: FOR-857
 URL: https://issues.apache.org/jira/browse/FOR-857
 Project: Forrest
  Issue Type: Bug
  Components: Licenses and Notices
Reporter: David Crossley
 Fix For: 0.10-dev

 Attachments: licer-20100825.pl.gz


 The license files for accompanying external products needs to be appended 
 after the Apache License in the top-level $FORREST_HOME/LICENSE.txt file.
 Perhaps the current discussion on the legal-discuss mailing list will clarify
 http://www.apache.org/foundation/mailinglists.html#foundation-legal



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

[jira] [Updated] (FOR-855) verify the license situation prior to each release

[David Crossley (JIRA)]

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

David Crossley updated FOR-855:
---
Component/s: (was: Project administration)
 Licenses and Notices

 verify the license situation prior to each release
 --

 Key: FOR-855
 URL: https://issues.apache.org/jira/browse/FOR-855
 Project: Forrest
  Issue Type: Bug
  Components: Licenses and Notices
Affects Versions: 0.9, 0.10-dev
Reporter: David Crossley
Assignee: David Crossley
Priority: Blocker
 Fix For: 0.10-dev


 This should be continually happening anyway, but immediately prior to each 
 release we need to verify that our license situation is in order. This issue 
 should not ever be closed, rather just move the Fix for Version on to the 
 next release.
 Here are some of the tasks:
 A) Ensure that all supporting libraries have a corresponding license. 
 Basically every jar file or other external package needs to have a 
 *.license.txt file. Ensure that any license conditions are met, e.g. for some 
 we must add an entry to NOTICE.txt, while for some others we must not. 
 Remember to abide by the ASF guidelines (e.g. nothing more restrictive than 
 the Apache License).
 B) Scan the whole trunk repository to add missing ASF license headers to 
 source files and to ensure that the ASF license headers have not been 
 accidently added to external files. See etc/relicense.txt
 C) Remove any author tags.



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

[jira] [Commented] (FOR-1252) update licenses to use the new W3C Software and Document Notice and License

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1252:
-

See the note at the ASF Legal Discuss mailing list:

Date: Fri, 5 Jun 2015 12:36:13 +0200
From: Sergio Fernández wik...@apache.org
To: d...@marmotta.apache.org, legal-disc...@apache.org
Subject: Fwd: Adoption of new Software and Document License
Message-ID: 
CAOfJQJ1Y+qKoRF=NaLa9COR9J+Y8hDTY+cruREan4zpGvREr=a...@mail.gmail.com
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201506.mbox/%3cCAOfJQJ1Y+qKoRF=NaLa9COR9J+Y8hDTY+cruREan4zpGvREr=a...@mail.gmail.com%3e

 update licenses to use the new W3C Software and Document Notice and License
 ---

 Key: FOR-1252
 URL: https://issues.apache.org/jira/browse/FOR-1252
 Project: Forrest
  Issue Type: Task
  Components: Licenses and Notices
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


 W3C has a new license. We need to review the supporting products that we use 
 that has one of the old licenses. See the list in $FORREST_HOME/LICENSE.txt 
 file and related files.



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

[jira] [Commented] (FOR-1206) Upgrade supporting product concurrent-1.3.4 to backport-util-concurrent

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1206:
-

Still need to consider upgrading to backport-util-concurrent.

 Upgrade supporting product concurrent-1.3.4 to backport-util-concurrent
 ---

 Key: FOR-1206
 URL: https://issues.apache.org/jira/browse/FOR-1206
 Project: Forrest
  Issue Type: Task
  Components: Core operations, Licenses and Notices
Reporter: David Crossley

 As suggested, upgrade the supporting product: lib/core/concurrent-1.3.4.jar 
 to backport-util-concurrent



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

[jira] [Updated] (FOR-1206) Upgrade supporting product concurrent-1.3.4 to backport-util-concurrent

[David Crossley (JIRA)]

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

David Crossley updated FOR-1206:

Component/s: Licenses and Notices

Part of the license issue was handled in

http://svn.apache.org/r1033375
Log Message:
Treat Concurrent as Category B
Issue: FOR-855 FOR-857 FOR-1206

We need to still review http://www.apache.org/legal/resolved.html#concurrent
to ensure that we have met requirements.

 Upgrade supporting product concurrent-1.3.4 to backport-util-concurrent
 ---

 Key: FOR-1206
 URL: https://issues.apache.org/jira/browse/FOR-1206
 Project: Forrest
  Issue Type: Task
  Components: Core operations, Licenses and Notices
Reporter: David Crossley

 As suggested, upgrade the supporting product: lib/core/concurrent-1.3.4.jar 
 to backport-util-concurrent



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

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

[David Crossley]

On Sat, May 09, 2015 at 03:03:35PM +0100, Gavin McDonald wrote:
  On 9 May 2015, at 2:22 pm, User Forrest forr...@forrest.zones.apache.org 
  wrote:
  
  At forrest.zones.apache.org
  
  svn update failed
  
  See logfile: /home/forrest/config/update-forrest-trunk-2015050913.log
 
 The log stated we needed to accept the new cert recently deployed by infra.
 
 Ran the job manually and accepted the cert, all should be well now.
 
 HTH

It does. Thanks.
-David

 Gav…
 
 

Re: a release is needed

[David Crossley]

Speaking as a Forrest developer, i will help out here as much
as i can manage. I would rather spend any available time to
help get a release done, than to help put Forrest into the
Apache Attic. We are in danger of that being the next step.

We need people to recommence participation.

Some early things to do [1]:

Decide which Java version. We really need to move forward.
I, for one, cannot even build and test on the currently specified version.
Would someone else please commence the discussion about that.

Tweak the Ant build system to package Forrest differently.
Remember that recently we needed to repackage the last release
to split it into a core package and a dependencies package.
The build system needs some minor adjustment to effect that,
and also create a convenience package which combines the two.

Upgrade some dependencies, especially core ones such as
Apache Ant and Apache Xerces.

Scan the JIRA issue tracker to see if there is anything that
can be done before release, or that need some discussion to move
them forward.

Review the how to release instructions. We might be able to
make some changes to ease the process. For example, see the first
fixme note: Having the docs packaged with the release is a great
demonstration of Forrest's ability, but it complicates the release
process.

Those are reasonably easy steps, which should start to
re-invigorate this community.

Remember that you do not need to be a committer to help with
a release. Anyone can assist.

-David

On Thu, Jan 22, 2015 at 10:54:42AM +1100, David Crossley wrote:
 As the Chair, i feel the need to remind the project that
 there is a responsibility to release the product.
 
 The procedure is well documented [1]. This has been enhanced
 over the years, improving with each release. Remember that
 it tries to document every step so that it is easier to
 recall each task and to ensure that the process flows
 without hiccups.
 
 [1] http://forrest.apache.org/procedures/release/How_to_release.html
 [2] Last release: 7 February 2011 : Forrest-0.9
 
 -David
 

Re: Experimenting with a bootstrap-based skin

[David Crossley]

On Tue, Feb 10, 2015 at 09:17:54AM +1100, David Crossley wrote:
 On Fri, Feb 06, 2015 at 09:46:32AM +0200, Sjur Moshagen wrote:
  Hello all,
  
  As part of improving our web site, a colleague of mine made a first stab at 
  creating a boostrap based skin. The result can be seen at divvun.no. So far 
  the skin is only in our own svn repo, but if successful, the intention is 
  to make it available to the Forrest community.
 
 Great, this is good news.

If you still want to do that, then it would be a fantastic thing for Forrest.
How can we proceed?

If you cannot just commit it under the terms of your own
Individual Contributor License Agreement (ICLA)
http://www.apache.org/licenses/#clas
or do not have time, then another approach would be that you
or your colleague add the skin to a JIRA issue tracker
http://forrest.apache.org/issues.html
and send in their own ICLA to cover the contribution.

Some other Forrest committer could then add the contribution.

Alternatively as suggested below, your colleague could become
a Forrest committer.

Another alternative is to describe any tips and tricks
that your team needed to do to get this to happen. Then another
Forrest committer could create the new skin.

-David

 Tim also suggested this back in March 2012, and a few of us indicated
 interest. Unfortunately it did not progress. Now you have, so excellent.
 
  Known issues:
  * Several features of Forrest are not yet supported, such as warning and 
  note elements (they will be rendered roughly as regular p elements).
  * most of the menu items and tabs are presently untranslated
  * it has the same inflexibility as other skins (but Dispatcher has turned 
  out to be way to heavy, memory consuming and slow for our purposes, so that 
  is not an option)
  
  BTW, the i18n implementation you find there is a post-processing hack, due 
  to the lack of i18n support in the Cocoon/Forrest CLI. We build the static 
  site once for each locale, and then merge them into one site while 
  injecting the language choice menu.
 
 It is good that such workarounds can happen with Forrest.
 If you have any enhancements or tips for the static i18n documentation,
 then that would be useful:
 http://forrest.zones.apache.org/ft/build/forrest-seed/samples-c/i18n.html
 
 Bertrand commenced some work to improve i18n back in May 2006.
 I am not sure how far that progressed. I do see some open
 issues from that and in the Internationalisation JIRA component.
 There is also the possibility to improve stuff at Cocoon, as the
 2.1 project is still alive.
 
  We need the static version, as Forrest is not stable enough to be run 
  dynamically (at least not in our case).
 
 Would you provide any comments on that aspect in separate threads.
 We should be able to address some of those issues.
 
  Feedback is welcome.
 
 Please suggest any of your colleagues to be committers at Forrest.
 The new skin could be added to the Forrest SVN early, and others
 could assist.
 
 -David
 
  Sjur
  
  

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

[David Crossley (JIRA)]

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

David Crossley updated FOR-1251:

Description: 
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.

  was:
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.


 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)

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

[David Crossley]

Ping ...

-David

On Mon, Mar 30, 2015 at 03:46:52AM +, David Crossley (JIRA) wrote:
 
 [ 
 https://issues.apache.org/jira/browse/FOR-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386146#comment-14386146
  ] 
 
 David Crossley commented on FOR-1251:
 -
 
 At the INFRA-9093 they are asking what additional packages we need. I have 
 added some. Would others please review.
 
 Our documentation is here. It is a little out-of-date, but mostly still 
 relevant.
 https://forrest.apache.org/zone.html
 
  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.

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

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1251:
-

At the INFRA-9093 they are asking what additional packages we need. I have 
added some. Would others please review.

Our documentation is here. It is a little out-of-date, but mostly still 
relevant.
https://forrest.apache.org/zone.html

 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)

early registration for ApacheCon in Austin Texas

[David Crossley]

Dear Apache Forrest enthusiast,

In just a few weeks, we'll be holding ApacheCon in Austin, Texas, and
we'd love to have you in attendance. You can save $300 on admission by
registering NOW, since the early bird price ends on the 21st.

Register at http://s.apache.org/acna2015-reg

ApacheCon this year celebrates the 20th birthday of the Apache HTTP
Server, and we'll have Brian Behlendorf, who started this whole thing,
keynoting for us, and you'll have a chance to meet some of the original
Apache Group, who will be there to celebrate with us.

We've got 7 tracks of great talks, as well as BOFs, the Apache BarCamp,
project-specific hack events, and evening events where you can deepen
your connection with the larger Apache community. See the full schedule
at http://apacheconna2015.sched.org/

And if you have any questions, comments, or just want to hang out with
us before and during the event, follow us on Twitter - @apachecon - or
drop by #apachecon on the Freenode IRC network.

Hope to see you in Austin!

Re: Experimenting with a bootstrap-based skin

[David Crossley]

Wow, this is nice. It seems better than when i looked the other day.

The top-level navigation collapses beautifully when i narrow the browser window.
The second-level tabs are behaving properly.
However not on the front page, for example the Events tab.

Anyway, great stuff.

-David

Re: Experimenting with a bootstrap-based skin

[David Crossley]

On Fri, Feb 06, 2015 at 09:46:32AM +0200, Sjur Moshagen wrote:
 Hello all,
 
 As part of improving our web site, a colleague of mine made a first stab at 
 creating a boostrap based skin. The result can be seen at divvun.no. So far 
 the skin is only in our own svn repo, but if successful, the intention is to 
 make it available to the Forrest community.

Great, this is good news.

Tim also suggested this back in March 2012, and a few of us indicated
interest. Unfortunately it did not progress. Now you have, so excellent.

 Known issues:
 * Several features of Forrest are not yet supported, such as warning and note 
 elements (they will be rendered roughly as regular p elements).
 * most of the menu items and tabs are presently untranslated
 * it has the same inflexibility as other skins (but Dispatcher has turned out 
 to be way to heavy, memory consuming and slow for our purposes, so that is 
 not an option)
 
 BTW, the i18n implementation you find there is a post-processing hack, due to 
 the lack of i18n support in the Cocoon/Forrest CLI. We build the static site 
 once for each locale, and then merge them into one site while injecting the 
 language choice menu.

It is good that such workarounds can happen with Forrest.
If you have any enhancements or tips for the static i18n documentation,
then that would be useful:
http://forrest.zones.apache.org/ft/build/forrest-seed/samples-c/i18n.html

Bertrand commenced some work to improve i18n back in May 2006.
I am not sure how far that progressed. I do see some open
issues from that and in the Internationalisation JIRA component.
There is also the possibility to improve stuff at Cocoon, as the
2.1 project is still alive.

 We need the static version, as Forrest is not stable enough to be run 
 dynamically (at least not in our case).

Would you provide any comments on that aspect in separate threads.
We should be able to address some of those issues.

 Feedback is welcome.

Please suggest any of your colleagues to be committers at Forrest.
The new skin could be added to the Forrest SVN early, and others
could assist.

-David

 Sjur
 
 

[jira] [Commented] (FOR-707) Document i18n features of Forrest

[David Crossley (JIRA)]

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

David Crossley commented on FOR-707:


This was added in http://svn.apache.org/r751566
to the forrest seed-sample site.

 Document i18n features of Forrest
 -

 Key: FOR-707
 URL: https://issues.apache.org/jira/browse/FOR-707
 Project: Forrest
  Issue Type: Task
  Components: Documentation and website, Internationalisation (i18n)
Affects Versions: 0.7, 0.8
Reporter: Ross Gardler
Priority: Critical
 Fix For: 0.9

 Attachments: i18n.xml


 There is next to no documentation about i18n, just a pretty poor FAQ entry 
 that points at an issue that has now been closed.
 Cheche wrote a blog entry on his work:
 http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/
 We could, at the very least use the locationmap to pull this content into our 
 site [OT: I wonder if this could be a way to generate more documentation?)



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

[jira] [Commented] (FOR-707) Document i18n features of Forrest

[David Crossley (JIRA)]

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

David Crossley commented on FOR-707:


The Blog posting by Cheche referred to above is not available at the moment.

There is a copy at the Wayback Machine:
http://web.archive.org/web/*/http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/

 Document i18n features of Forrest
 -

 Key: FOR-707
 URL: https://issues.apache.org/jira/browse/FOR-707
 Project: Forrest
  Issue Type: Task
  Components: Documentation and website, Internationalisation (i18n)
Affects Versions: 0.7, 0.8
Reporter: Ross Gardler
Priority: Critical
 Fix For: 0.9

 Attachments: i18n.xml


 There is next to no documentation about i18n, just a pretty poor FAQ entry 
 that points at an issue that has now been closed.
 Cheche wrote a blog entry on his work:
 http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/
 We could, at the very least use the locationmap to pull this content into our 
 site [OT: I wonder if this could be a way to generate more documentation?)



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

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

[David Crossley (JIRA)]

David Crossley created FOR-1251:
---

 Summary: 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)

a release is needed

[David Crossley]

As the Chair, i feel the need to remind the project that
there is a responsibility to release the product.

The procedure is well documented [1]. This has been enhanced
over the years, improving with each release. Remember that
it tries to document every step so that it is easier to
recall each task and to ensure that the process flows
without hiccups.

[1] http://forrest.apache.org/procedures/release/How_to_release.html
[2] Last release: 7 February 2011 : Forrest-0.9

-David

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

[David Crossley]

I gave up waiting and reverted it. This was also holding up the website 
publishing.

-David

On Tue, Nov 25, 2014 at 06:07:44AM +1100, David Crossley wrote:
 Ross, would you please revert this. I don't understand why you changed it.
 
 -David
 
 On Sun, Nov 23, 2014 at 08:49:19AM -0800, Brian M Dube wrote:
  On 11/22/2014 09:40 PM, rgard...@apache.org wrote:
   Author: rgardler
   Date: Sun Nov 23 05:40:38 2014
   New Revision: 1641160
   
   URL: http://svn.apache.org/r1641160
   Log:
   Updte MOTD to latest release version, Feb 2011 was quite some time ago :-)
  
  Hi Ross, good to see you again,
  
  It was a long time ago, but v0.9 of 2011 is still the current release
  version.
  
  -Brian
  
   Modified:
   forrest/trunk/site-author/skinconf.xml
   
   Modified: forrest/trunk/site-author/skinconf.xml
   URL: 
   http://svn.apache.org/viewvc/forrest/trunk/site-author/skinconf.xml?rev=1641160r1=1641159r2=1641160view=diff
   ==
   --- forrest/trunk/site-author/skinconf.xml (original)
   +++ forrest/trunk/site-author/skinconf.xml Sun Nov 23 05:40:38 2014
   @@ -104,7 +104,7 @@ See main/fresh-site/src/documentation/sk
  motd
motd-option pattern=index.html starts-with=true
  motd-page location=page
   -7 February 2011 : Forrest-0.9 released
   +Latest release: Forrest-0.10
  /motd-page
  
   motd-page-urlhttp://forrest.apache.org/mirrors.cgi/motd-page-url
/motd-option
   
   
 

Re: buildbot failure in ASF Buildbot on forrest-trunk

[David Crossley]

That is the same strangeness that Sjur encountered. Dunno.

-David

On Thu, Nov 27, 2014 at 07:01:30AM +, build...@apache.org wrote:
 The Buildbot has detected a new failure on builder forrest-trunk while 
 building ASF Buildbot. Full details are available at:
 http://ci.apache.org/builders/forrest-trunk/builds/19
 
 Buildbot URL: http://ci.apache.org/
 
 Buildslave for this Build: lares_ubuntu
 
 Build Reason: The AnyBranchScheduler scheduler named 'on-forrest-commit' 
 triggered this build
 Build Source Stamp: [branch forrest/trunk] 1642032
 Blamelist: crossley
 
 BUILD FAILED: failed
 
 Sincerely,
  -The Buildbot
 
 
 

Re: Improving the localisation of the search box

[David Crossley]

I re-generated the whole Forrest website to deploy your changes there.

-David

On Tue, Nov 25, 2014 at 10:21:53PM +0100, Sjur Moshagen wrote:
 25. nov. 2014 kl. 22:14 skrev David Crossley cross...@apache.org:
  
  On Tue, Nov 25, 2014 at 02:46:32PM +0100, Sjur Moshagen wrote:
  With no objections so far, and this being the 0.10-dev code base, I think 
  it is ok to disregard older browsers for now.
  
  That is a good approach.
  
  Yes, i was going to suggest option two too.
 
 Thanks a lot for the feedback :)
 
 Sjur
 

Re: Improving the localisation of the search box

[David Crossley]

On Tue, Nov 25, 2014 at 02:46:32PM +0100, Sjur Moshagen wrote:
 24. nov. 2014 kl. 16:59 skrev Sjur Moshagen sju...@mac.com:
  Question/viewpoints requested:
  
  Is this important enough that we want to find a JS solution for older 
  browsers? I tried one, but couldn’t get it going (that might well be 
  because of my non-existent JS knowledge).
  
  OR:
  
  Would it be ok to drop support for older browsers in this case? It just 
  means that there won’t be any lead text/placeholder text in the search 
  field, it will just be plain white instead.
 
 With no objections so far, and this being the 0.10-dev code base, I think it 
 is ok to disregard older browsers for now.

That is a good approach.

Yes, i was going to suggest option two too.

-David

 Sjur
 

Re: buildbot failure in ASF Buildbot on forrest-trunk

[David Crossley]

On Tue, Nov 25, 2014 at 03:18:39PM +0100, Sjur Moshagen wrote:
 25. nov. 2014 kl. 15:07 skrev build...@apache.org:
  
  The Buildbot has detected a new failure on builder forrest-trunk while 
  building ASF Buildbot. Full details are available at:
 http://ci.apache.org/builders/forrest-trunk/builds/17
  
  Buildbot URL: http://ci.apache.org/
  
  Buildslave for this Build: lares_ubuntu
  
  Build Reason: The AnyBranchScheduler scheduler named 'on-forrest-commit' 
  triggered this build
  Build Source Stamp: [branch forrest/trunk] 1641622
  Blamelist: sjur
  
  BUILD FAILED: failed
  
  Sincerely,
  -The Buildbot
 
 Thank you, Buildbot!
 
 Except that I do not understand what has gone wrong. In the log file for the 
 failed process, the only fail is logged as follows:
 
  program finished with exit code 0
  elapsedTime=0.017328
  program finished with exit code 1
  program finished with exit code 0
 
 The process before (svn --version) ends with a normal exit code, and the same 
 for the following process. That is, one single, anonymous process did not end 
 successfully, but everything else did.
 
 How come?

I do not know either. Something about corrupted xml.

I had a similar problem back on September 14. See the logs above.
The next day it came good all by itself.

If not, then perhaps need to contact Infrastructure.
I am not sure how, but start here:
http://ci.apache.org/#buildbot

-David

 Sjur
 

Re: buildbot failure in ASF Buildbot on forrest-trunk

[David Crossley]

On Tue, Nov 25, 2014 at 10:45:26PM +0100, Sjur Moshagen wrote:
 25. nov. 2014 kl. 22:33 skrev David Crossley cross...@apache.org:
  
  On Tue, Nov 25, 2014 at 03:18:39PM +0100, Sjur Moshagen wrote:
  program finished with exit code 0
  elapsedTime=0.017328
  program finished with exit code 1
  program finished with exit code 0
  
  The process before (svn --version) ends with a normal exit code, and the 
  same for the following process. That is, one single, anonymous process did 
  not end successfully, but everything else did.
  
  How come?
  
  I do not know either. Something about corrupted xml.
  
  I had a similar problem back on September 14. See the logs above.
  The next day it came good all by itself.
 
 Thanks for the follow-up. I am kind of hoping that it will disappear by 
 itself also this time, we’ll see tomorrow.

I just triggered it with another commit, and now it is happy.
No idea why.

-David

  If not, then perhaps need to contact Infrastructure.
  I am not sure how, but start here:
  http://ci.apache.org/#buildbot
 
 Ok.
 
 Sjur
 

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

[David Crossley]

Ross, would you please revert this. I don't understand why you changed it.

-David

On Sun, Nov 23, 2014 at 08:49:19AM -0800, Brian M Dube wrote:
 On 11/22/2014 09:40 PM, rgard...@apache.org wrote:
  Author: rgardler
  Date: Sun Nov 23 05:40:38 2014
  New Revision: 1641160
  
  URL: http://svn.apache.org/r1641160
  Log:
  Updte MOTD to latest release version, Feb 2011 was quite some time ago :-)
 
 Hi Ross, good to see you again,
 
 It was a long time ago, but v0.9 of 2011 is still the current release
 version.
 
 -Brian
 
  Modified:
  forrest/trunk/site-author/skinconf.xml
  
  Modified: forrest/trunk/site-author/skinconf.xml
  URL: 
  http://svn.apache.org/viewvc/forrest/trunk/site-author/skinconf.xml?rev=1641160r1=1641159r2=1641160view=diff
  ==
  --- forrest/trunk/site-author/skinconf.xml (original)
  +++ forrest/trunk/site-author/skinconf.xml Sun Nov 23 05:40:38 2014
  @@ -104,7 +104,7 @@ See main/fresh-site/src/documentation/sk
 motd
   motd-option pattern=index.html starts-with=true
 motd-page location=page
  -7 February 2011 : Forrest-0.9 released
  +Latest release: Forrest-0.10
 /motd-page
 motd-page-urlhttp://forrest.apache.org/mirrors.cgi/motd-page-url
   /motd-option
  
  

Re: The Forrest feels like home

[David Crossley]

On Fri, Nov 14, 2014 at 07:25:51AM +0100, Sjur Moshagen wrote:
 Welcome back!
 
 :)
 
 Sjur
 
  14. nov. 2014 kl. 03:05 skrev Ross Gardler (MS OPEN TECH) 
  ross.gard...@microsoft.com:
  
  It’s been many many years since I was in the Forrest, but it feels like 
  home. Hello folks J

Yes, welcome Ross. It is great to hear.

  I’m re-evaluating Forrest for a small project I have. After searching far 
  and wide there still isn’t a solution for my use case other than Forrest. 
  So I’ve re-subscribed to the dev list, more out fond memories than any 
  intention to contribute again – though if I do use it on this project who 
  knows…
   
  My first comment – damn this community documented Forrest well :-D

It certainly helps to be able to remind ourselves how stuff works.
The email archives are useful too, with discussion about some unresolved issues.

One other thing that might help you to get going again:
https://svn.apache.org/repos/asf/forrest/trunk/etc/review-plugin-deployment.txt

-David

  Ross
 

[jira] [Closed] (FOR-1250) HIVE - Add support for pulling HBase columns with regex matching

[David Crossley (JIRA)]

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

David Crossley closed FOR-1250.
---
Resolution: Invalid

Closed. This is not a Forrest issue.

Please see the Apache Hive project at https://hive.apache.org/

 HIVE - Add support for pulling HBase columns with regex matching
 

 Key: FOR-1250
 URL: https://issues.apache.org/jira/browse/FOR-1250
 Project: Forrest
  Issue Type: Bug
  Components: Other
Reporter: Sucaz Moshe

 Hi, we would like to create table that pulling HBase columns with regex 
 matching. for example:
 CREATE EXTERNAL TABLE XXX(
 key string 
 , DATES  MAPSTRING, BIGINT
 , FLOATS MAPSTRING, DOUBLE  
 , STRINGS MAPSTRING, STRING
 )
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' WITH 
 SERDEPROPERTIES (
 hbase.columns.mapping = :key, FECF:D_[0-9]*, FECF:F_[0-9]*, 
 FECF:C[0-9]*_[0-9]*,
 hbase.table.default.storage.type = binary)
 TBLPROPERTIES (hbase.table.name = XXX);
 currently only prefix work (with hive 0.12.0):
 CREATE EXTERNAL TABLE XXX(
 key string 
 , DATES  MAPSTRING, BIGINT
 , FLOATS MAPSTRING, DOUBLE  
 , STRINGS MAPSTRING, STRING
 )
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' WITH 
 SERDEPROPERTIES (
 hbase.columns.mapping = :key, FECF:D_.*, FECF:F_.*, FECF:C.*,
 hbase.table.default.storage.type = binary)
 TBLPROPERTIES (hbase.table.name = XXX);



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

Re: Building my website with forrest 0.9

[David Crossley]

Also try again the Dispatcher plugin's docs.
It uses the projectInfo plugin and so hopefully it
now works for you too.
  
   The projectInfo plugin fails so the dispatcher plugin fails too.
  
   Yep.
 
  After doing the svn update the dispatcher plugin is built properly and
  I can see the docs on my web browser.
 
  Great. That is because although it uses the projectInfo plugin,
  it does not use those resources that were missing above.
 
Each plugin's own docs (do 'forrest run' there) is supposed
to demonstrate its own features. So you might be able to follow
its setup and apply to your own situation.
 
  Now hopefully you can get further with that.
 
 Unfortunately I've not been able to make my website work with the
 dispatcher. The plugin works now but its documentation is still
 outdated. I'm studying the plugin and trying to find out how it has to
 be used but I'm failing.

Apart from investigating the Dispatcher plugin's own docs,
there are a couple of other recent-ish plugins that use the Dispatcher.
There is a table in the file $FORREST_HOME/etc/review-plugin-deployment.txt
Look for plugins that were added in v0.9 or more and use the Dispatcher,
for example the input.foaf and input.skos plugins.

 This thread is very long so I will ask for
 help in the thread Customizing a website using forrest 0.10-dev and
 dispatcher
 
 Thanks a lot for all your help.

Thanks to you too. Hope that it gets sorted out.

-David

Re: Building my website with forrest 0.9

[David Crossley]

On Tue, Sep 16, 2014 at 10:42:11AM +0200, Vicent Mas wrote:
 On Mon, Sep 15, 2014 at 11:16 AM, David Crossley cross...@apache.org wrote:
  On Mon, Sep 15, 2014 at 10:21:41AM +0200, Vicent Mas wrote:
  On Sun, Sep 14, 2014 at 10:54 AM, David Crossley cross...@apache.org 
  wrote:
   On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
   On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org 
   wrote:
On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
On Thu, Sep 11, 2014 at 4:53 PM, David Crossley 
cross...@apache.org wrote:
 On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 2:54 AM, David Crossley 
 cross...@apache.org wrote:
 
  If that works, then try configuring that sample site
  to use Dispatcher. See its forrest.properties configuration 
  file.
  Then do the 'forrest' command again.

 That fails.

 With the 0.10 version my website is built both with the skinner 
 method
 and with the dispatcher plugin so I think my best option is to 
 use the
 0.10 version and try to find out why the customizations are 
 ignored.

 Thanks again for your help.

 Ah, good that it works with 0.10-dev

 So that confirms https://issues.apache.org/jira/browse/FOR-1188

 Would you please try with the projectInfo plugin.
 It has been difficult to get someone on Windows to confirm
 that it still has that problem.

 cd 
 $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
 Enable it for Dispatcher in forrest.properties, i.e.
 project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
 Then do:
  forrest site
   
It fails for me. The content of the broken-links.xml file is:
   
broken-links
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
   
 [snipped some other similar ones for brevity]
   
/broken-links
   
Sorry for not doing this yesterday. I just forgot about it.
   
Thanks. So it seems like the same problem.
  
   I made the change to the projectInfo plugin today to hopefully
   apply the workaround described in FOR-1108 and FOR-1188.
  
   Would you please do 'svn up' and try that plugin again,
   enabled for the Dispatcher.
 
  Hi,
   it fails again. But the content of  broken-links.xml is much shorter
  now (only 2 errors)::
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)index.html/link
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)/index.html/link
  /broken-links
 
  Ah. This plugin is one of the few that utilises a map:mount
  to include a sub-sitemap (Dispatcher too).
 
  I now made another fix to this plugin to stop mounting
  and just add the pipelines from svnHelp.xmap into input.xmap file.
 
  Before doing 'svn up' would you please try this projectInfo
  docs again, but not enabled for the Dispatcher, i.e. just
  with its default skins. I want to see if the problem was
  only with Dispatcher-enabled sites.
 
 Doing that the broken-links.xml seems to be the same:
 
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)index.html/link
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)/index.html/link
 /broken-links
 
 After doing svn update the built fails with the following errors:
 
 broken-links
   link message

Re: Building my website with forrest 0.9

[David Crossley]

On Mon, Sep 15, 2014 at 10:21:41AM +0200, Vicent Mas wrote:
 On Sun, Sep 14, 2014 at 10:54 AM, David Crossley cross...@apache.org wrote:
  On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
  On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org 
  wrote:
   On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
   On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org 
   wrote:
On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
On Thu, Sep 11, 2014 at 2:54 AM, David Crossley 
cross...@apache.org wrote:

 If that works, then try configuring that sample site
 to use Dispatcher. See its forrest.properties configuration file.
 Then do the 'forrest' command again.
   
That fails.
   
With the 0.10 version my website is built both with the skinner 
method
and with the dispatcher plugin so I think my best option is to use 
the
0.10 version and try to find out why the customizations are ignored.
   
Thanks again for your help.
   
Ah, good that it works with 0.10-dev
   
So that confirms https://issues.apache.org/jira/browse/FOR-1188
   
Would you please try with the projectInfo plugin.
It has been difficult to get someone on Windows to confirm
that it still has that problem.
   
cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
Enable it for Dispatcher in forrest.properties, i.e.
project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
Then do:
 forrest site
  
   It fails for me. The content of the broken-links.xml file is:
  
   broken-links
 link message=C:\Users\Vicente\Apache
   Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
   Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
   Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
   (El nombre de archivo, el nombre de directorio o la sintaxis de la
   etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
  
[snipped some other similar ones for brevity]
  
   /broken-links
  
   Sorry for not doing this yesterday. I just forgot about it.
  
   Thanks. So it seems like the same problem.
 
  I made the change to the projectInfo plugin today to hopefully
  apply the workaround described in FOR-1108 and FOR-1188.
 
  Would you please do 'svn up' and try that plugin again,
  enabled for the Dispatcher.
 
 Hi,
  it fails again. But the content of  broken-links.xml is much shorter
 now (only 2 errors)::
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)index.html/link
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)/index.html/link
 /broken-links

Ah. This plugin is one of the few that utilises a map:mount
to include a sub-sitemap (Dispatcher too).

I now made another fix to this plugin to stop mounting
and just add the pipelines from svnHelp.xmap into input.xmap file.

Before doing 'svn up' would you please try this projectInfo
docs again, but not enabled for the Dispatcher, i.e. just
with its default skins. I want to see if the problem was
only with Dispatcher-enabled sites.

  Also try again the Dispatcher plugin's docs.
  It uses the projectInfo plugin and so hopefully it
  now works for you too.
 
 The projectInfo plugin fails so the dispatcher plugin fails too.

Yep.

  Each plugin's own docs (do 'forrest run' there) is supposed
  to demonstrate its own features. So you might be able to follow
  its setup and apply to your own situation.
 
  By the way, this FAQ explains how to run the plugins docs
  server on the default  port and your project on another port:
  http://forrest.apache.org/docs_0_100/faq.html#run_port
 
 I didn't know it. Thanks for the info
 
   Getting back to your own website.
   Do you use any other plugins, or just Dispatcher?
 
  I use the PDF plugin too, if the site is not built. It seems that the
  dispatcher requires the PDF plugin.
 
 The above lines should read:
 
 I use the PDF plugin too, if *not* the site is not built. It seems that the
 dispatcher requires the PDF plugin.

Yes i figured out what you meant, but i did not understand why.

I see now. It is because the default settings for the Dispatcher
do add a link to *.pdf for each page.

-David

[jira] [Closed] (FOR-1249) Gump trouble because we use head of xmlgraphics-commons but specific fop-1.0

[David Crossley (JIRA)]

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

David Crossley closed FOR-1249.
---
Resolution: Fixed

Gump has been happy for 4 runs now.

 Gump trouble because we use head of xmlgraphics-commons but specific fop-1.0
 

 Key: FOR-1249
 URL: https://issues.apache.org/jira/browse/FOR-1249
 Project: Forrest
  Issue Type: Task
  Components: Core operations
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


 On 2014-08-22 Gump started reporting a problem related to our use of FOP and 
 XML Graphics Commons.
 Workaround this for now by tweaking our Gump Descriptor to use our older 
 package version of xmlgraphics-commons to match our old FOP.



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

Re: buildbot failure in ASF Buildbot on forrest-trunk

[David Crossley]

Help please. Can anyone see what it is complaining about?

-David

On Sun, Sep 14, 2014 at 08:26:03AM +, build...@apache.org wrote:
 The Buildbot has detected a new failure on builder forrest-trunk while 
 building ASF Buildbot.
 Full details are available at:
  http://ci.apache.org/builders/forrest-trunk/builds/5
 
 Buildbot URL: http://ci.apache.org/
 
 Buildslave for this Build: lares_ubuntu
 
 Build Reason: scheduler
 Build Source Stamp: [branch forrest/trunk] 1624808
 Blamelist: crossley
 
 BUILD FAILED: failed
 
 sincerely,
  -The Buildbot
 
 
 

Re: Building my website with forrest 0.9

[David Crossley]

On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
 On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org wrote:
  On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org 
  wrote:
   On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
   On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org 
   wrote:
   
If that works, then try configuring that sample site
to use Dispatcher. See its forrest.properties configuration file.
Then do the 'forrest' command again.
  
   That fails.
  
   With the 0.10 version my website is built both with the skinner method
   and with the dispatcher plugin so I think my best option is to use the
   0.10 version and try to find out why the customizations are ignored.
  
   Thanks again for your help.
  
   Ah, good that it works with 0.10-dev
  
   So that confirms https://issues.apache.org/jira/browse/FOR-1188
  
   Would you please try with the projectInfo plugin.
   It has been difficult to get someone on Windows to confirm
   that it still has that problem.
  
   cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
   Enable it for Dispatcher in forrest.properties, i.e.
   project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
   Then do:
forrest site
 
  It fails for me. The content of the broken-links.xml file is:
 
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
  (El nombre de archivo, el nombre de directorio o la sintaxis de la
  etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
 
   [snipped some other similar ones for brevity]
 
  /broken-links
 
  Sorry for not doing this yesterday. I just forgot about it.
 
  Thanks. So it seems like the same problem.

I made the change to the projectInfo plugin today to hopefully
apply the workaround described in FOR-1108 and FOR-1188.

Would you please do 'svn up' and try that plugin again,
enabled for the Dispatcher.

Also try again the Dispatcher plugin's docs.
It uses the projectInfo plugin and so hopefully it
now works for you too.

Each plugin's own docs (do 'forrest run' there) is supposed
to demonstrate its own features. So you might be able to follow
its setup and apply to your own situation.

By the way, this FAQ explains how to run the plugins docs
server on the default  port and your project on another port:
http://forrest.apache.org/docs_0_100/faq.html#run_port

  Getting back to your own website.
  Do you use any other plugins, or just Dispatcher?
 
 I use the PDF plugin too, if the site is not built. It seems that the
 dispatcher requires the PDF plugin.

I cannot understand why that would be so.

-David

the forrest.zones jail needs attention

[David Crossley]

On Wed, Mar 05, 2014 at 04:20:58PM -0800, Brian M Dube wrote:
 On 03/02/2014 11:45 PM, User Forrest wrote:
 At forrest.zones.apache.org
 
 svn update failed
 
 See logfile: /home/forrest/config/update-forrest-trunk-2014030307.log
 
 This is an SSL error. I tried to fix it by installing the port which 
 contains the root CA certificates, but that failed.
 
 It also looks like the certificate can be manually accepted (presumably 
 once suffices) by the forrest user.

I presume that someone needs to log in, switch to the 'forrest' user [2],
and probably also do 'svn upgrade' in the relevant directory.

Some notes are here:
[1] https://forrest.apache.org/zone.html
[2] http://svn.apache.org/repos/asf/forrest/zone/README.txt
[3] http://www.apache.org/dev/machines.html#jails-tlps (our jail in on sigyn).

I cannot do this at this stage, so hopefully Brian can.

-David

Re: the forrest.zones jail needs attention

[David Crossley]

On Sun, Sep 14, 2014 at 07:08:41PM +1000, David Crossley wrote:
 On Wed, Mar 05, 2014 at 04:20:58PM -0800, Brian M Dube wrote:
  On 03/02/2014 11:45 PM, User Forrest wrote:
  At forrest.zones.apache.org
  
  svn update failed
  
  See logfile: /home/forrest/config/update-forrest-trunk-2014030307.log
  
  This is an SSL error. I tried to fix it by installing the port which 
  contains the root CA certificates, but that failed.
  
  It also looks like the certificate can be manually accepted (presumably 
  once suffices) by the forrest user.
 
 I presume that someone needs to log in, switch to the 'forrest' user [2],
 and probably also do 'svn upgrade' in the relevant directory.
 
 Some notes are here:
 [1] https://forrest.apache.org/zone.html
 [2] http://svn.apache.org/repos/asf/forrest/zone/README.txt
 [3] http://www.apache.org/dev/machines.html#jails-tlps (our jail in on sigyn).
 
 I cannot do this at this stage, so hopefully Brian can.

Of course just ask here if i can help to clarify stuff
such as the locations of jobs, svn workspace, logs, etc.

 -David

Re: the forrest.zones jail needs attention

[David Crossley]

On Sun, Sep 14, 2014 at 02:17:49PM -0700, Brian M Dube wrote:
 On 09/14/2014 02:08 AM, David Crossley wrote:
  On Wed, Mar 05, 2014 at 04:20:58PM -0800, Brian M Dube wrote:
  On 03/02/2014 11:45 PM, User Forrest wrote:
  At forrest.zones.apache.org
 
  svn update failed
 
  See logfile: /home/forrest/config/update-forrest-trunk-2014030307.log
 
  This is an SSL error. I tried to fix it by installing the port which 
  contains the root CA certificates, but that failed.
 
  It also looks like the certificate can be manually accepted (presumably 
  once suffices) by the forrest user.
  
  I presume that someone needs to log in, switch to the 'forrest' user [2],
  and probably also do 'svn upgrade' in the relevant directory.
 
 This is done.

Fantastic. Now we will see what happens when someone makes the next commit.
Our forrest should build itself and do tests. It has been a while.

-David

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

[jira] [Commented] (FOR-1249) Gump trouble because we use head of xmlgraphics-commons but specific fop-1.0

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1249:
-

Our Gump project uses the head of xml-batik and xmlgraphics-commons but 
uses our packaged fop-1.0.jar.

Changing our Gump Descriptor to use our packaged xmlgraphics-commons-1.5.jar.
Done in r1624475.

This may affect the use of head of Batik, lets see.

 Gump trouble because we use head of xmlgraphics-commons but specific fop-1.0
 

 Key: FOR-1249
 URL: https://issues.apache.org/jira/browse/FOR-1249
 Project: Forrest
  Issue Type: Task
  Components: Core operations
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


 On 2014-08-22 Gump started reporting a problem related to our use of FOP and 
 XML Graphics Commons.
 Workaround this for now by tweaking our Gump Descriptor to use our older 
 package version of xmlgraphics-commons to match our old FOP.



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

Re: FOR-1249 xmlgraphics-commons and fop-1.0

[David Crossley]

See https://issues.apache.org/jira/browse/FOR-1249
Gump trouble because we use head of xmlgraphics-commons but specific fop-1.0

-David

On Sat, Aug 23, 2014 at 09:21:31AM +1000, David Crossley wrote:
 Follow through from http://forrest.apache.org/gump.html
 to forrest-test and then the Complete Output File at Gump.
 
 ---
 ...
  [java] * [13/60]   [0/0] 2.19s  0b  samples-b/sample.pdf
  [java] Exception in thread main java.lang.NoSuchMethodError: 
 org.apache.xmlgraphics.xmp.Metadata.mergeInto(Lorg/apache/xmlgraphics/xmp/Metadata;)V
  [java]   at 
 org.apache.fop.render.pdf.PDFRenderingUtil.renderXMPMetadata(PDFRenderingUtil.java:342)
  [java]   at 
 org.apache.fop.render.pdf.PDFDocumentHandler.handleExtensionObject(PDFDocumentHandler.java:294)
 ...
 ---
 
 So something changed recently at XML Graphics that affects our use of FOP.
 The recent commit there is http://svn.apache.org/r1619414
 
 Can anyone see why that would be so?
 
 -David
 
 On Fri, Aug 22, 2014 at 03:59:55AM +, Gump wrote:
  To whom it may engage...
  
  This is an automated request, but not an unsolicited one. For 
  more information please visit http://gump.apache.org/nagged.html, 
  and/or contact the folk at gene...@gump.apache.org.
  
  Project forrest-test has an issue affecting its community integration.
  This issue affects 1 projects.
  The current state of this project is 'Failed', with reason 'Build Timed 
  Out'.
  For reference only, the following projects are affected by this:
  - forrest-test :  Apache Forrest software is a publishing framework 
  that trans...
  
  
  Full details are available at:
  http://vmgump.apache.org/gump/public/forrest/forrest-test/index.html
  
  That said, some information snippets are provided here.
  
  The following annotations (debug/informational/warning/error messages) were 
  provided:
   -INFO- Failed with reason build timed out
  
  
  
  The following work was performed:
  http://vmgump.apache.org/gump/public/forrest/forrest-test/gump_work/build_forrest_forrest-test.html
  Work Name: build_forrest_forrest-test (Type: Build)
  Work ended in a state of : Failed
  Elapsed: 1 hour 1 sec
  Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
  -Dbuild.sysclasspath=only 
  -Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar
   org.apache.tools.ant.Main -verbose 
  -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
  -Dproject.plugins.override=true gump-forrest-test 
  [Working Directory: /srv/gump/public/workspace/forrest/main]
  CLASSPATH: 
  /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-2.1.13-dev.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-asciiart-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-auth-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-batik-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-chaperon-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-fop-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-html-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-linkrewriter-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-lucene-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-profiler-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-template-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-validation-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-xsp-block.jar:/srv/gump/public/workspace/forrest/lib/core/chaperon-2004
   
  0205.jar:/srv/gump/public/workspace/forrest/lib/core/ehcache-core-2.2.0.jar:/srv/gump/public/workspace/forrest/lib/core/jing-2009.jar:/srv/gump/public/workspace/forrest/lib/core/jtidy-04aug2000r7-dev.jar:/srv/gump/public/workspace/forrest/lib/core/nekopull-0.2.4.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-log4j12-1.7.2.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-api-1.7.2.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-6.1.26.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-util-6.1.26.jar:/srv/gump/public/workspace/forrest/build/plugins/lib/fop-1.0.jar:/srv/gump/public/workspace/forrest/build/xml-forrest.jar:/srv/gump/packages/apache-attic/avalon-framework-api-4.3.jar:/srv/gump/packages/apache-attic/avalon-framework-impl-4.3.jar:/srv/gump/packages/apache-attic/excalibur-component-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-datasource-2.2.2.jar:/srv/gump/packages/apache-attic/excalibur-instrument-api-2.2.1.jar:/srv/gump/packages/apach
   
  e-attic/excalibur-logger-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-pool-api-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-pool-impl-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur

Re: Building my website with forrest 0.9

[David Crossley]

On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org wrote:
  On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org 
  wrote:
  
   If that works, then try configuring that sample site
   to use Dispatcher. See its forrest.properties configuration file.
   Then do the 'forrest' command again.
 
  That fails.
 
  With the 0.10 version my website is built both with the skinner method
  and with the dispatcher plugin so I think my best option is to use the
  0.10 version and try to find out why the customizations are ignored.
 
  Thanks again for your help.
 
  Ah, good that it works with 0.10-dev
 
  So that confirms https://issues.apache.org/jira/browse/FOR-1188
 
  Would you please try with the projectInfo plugin.
  It has been difficult to get someone on Windows to confirm
  that it still has that problem.
 
  cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
  Enable it for Dispatcher in forrest.properties, i.e.
  project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
  Then do:
   forrest site
 
 It fails for me. The content of the broken-links.xml file is:
 
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
 (El nombre de archivo, el nombre de directorio o la sintaxis de la
 etiqueta del volumen no son correctos)releaseNotes_0.2.html/link

 [snipped some other similar ones for brevity]

 /broken-links
 
 Sorry for not doing this yesterday. I just forgot about it.

Thanks. So it seems like the same problem.

Getting back to your own website.
Do you use any other plugins, or just Dispatcher?

-David

Re: Customizing a website using forrest 0.10-dev and dispatcher

[David Crossley]

On Fri, Sep 12, 2014 at 10:08:28AM +0200, Vicent Mas wrote:
 On Fri, Sep 12, 2014 at 1:29 AM, David Crossley cross...@apache.org wrote:
  On Thu, Sep 11, 2014 at 06:52:28PM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 5:09 PM, David Crossley cross...@apache.org 
  wrote:
   On Thu, Sep 11, 2014 at 01:48:58PM +0200, Vicent Mas wrote:
   Hi,
  
   I'm trying to build a website with forrest 0.10 and the dispatcher
   plugin. My current problem is that all my customizations are ignored. 
   For
   instance, if I change the copyright in a footer it is not updated. I've 
   used
   the Dispatcher Quickstart (version 0.8 is the most modern version I 
   found) as
   a guide when possible.
  
   Not sure what you mean regarding version 0.8.
 
  I mean this document:
 
  http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.html
 
  Ah. When using the dev version of Forrest, should use the local docs.
 
   The current, but perhaps out-of-date, document is in the plugin's docs.
   Do this:
cd whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher
forrest run
http://localhost:/how/howto-dispatcher-quickstart.html
 
  I've done it but I get a Resource not found error.
 
  That is very strange. It works locally for me.
 
  Perhaps you need to clean your Forrest setup.
  (Of course replace with Windows-specific commands.)
   cd $FORREST_HOME/main
   ./build.sh clean
   ./build.sh
 
  Not sure what is needed to clean the Dispatcher plugin,
  so do this:
   cd 
  $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher
   forrest clean
   $FORREST_HOME/tools/ant/bin/ant clean
 
  Then do:
   forrest run
  which should automatically build and deploy the Dispatcher plugin,
  and the other plugins that it uses, from the local dev sources.
  During that process the get-local Ant task should be indicating
  that it is using the local sources.
 
 No luck. I keep getting a Resource not found error.

Okay. That might be due to its use of the projectInfo plugin
which we think might need tweaking as indicated in FOR-1188.

  Anyway I've found
  the xml version of the document and the content seems to correspond to
  the document I mention above. The document talks about an
  org.apache.forrest.themes.core plugin that I'm unable to find and also
  about a pelt.fv file in that plugin, so I am lost.
 
  Yes, because no-one has managed to update those docs yet.
 
 I see.
 
  As Sjur explained that old supporting plugin is not used anymore.
 
 I don't use that plugin. As I said I used the quickstart document as a
 guide only when possible. IIRC my hierarchy of folders was built
 imitating the contents of the dispatcher plugin folder regarding
 themes.

   (Patches welcome :-)
 
  I wish I was able to patch it :-) Thanks once more for your help.
 
   I am hoping that someone who knows more can help you with
   the rest, e.g. Thorsten, Cyriaque, Brian, etc.
 
 I hope so. As I said I'm really stuck.

In the meantime you might be able to determine where the
Dispatcher is looking for those project resources by investigating
the various *.xmap sitemaps in the top-level of the Dispatcher
plugin and its locationmap.xml file.

There are some debugging techniques listed here:
http://forrest.apache.org/howto-dev.html
and the link to the FAQ
http://forrest.apache.org/docs_0_100/faq.html#version
to report all properties to help with following those sitemaps.

-David

Re: FOR-1249 xmlgraphics-commons and fop-1.0

[David Crossley]

Woops, the xmlgraphics-commons-1.5.jar needed to be explicitly added to the 
forrest-test-basic job.

-David

On Fri, Sep 12, 2014 at 09:07:00PM +, Gump wrote:
 To whom it may engage...
 
 This is an automated request, but not an unsolicited one. For 
 more information please visit http://gump.apache.org/nagged.html, 
 and/or contact the folk at gene...@gump.apache.org.
 
 Project forrest-test-basic has an issue affecting its community integration.
 This issue affects 3 projects.
 The current state of this project is 'Failed', with reason 'Build Timed Out'.
 For reference only, the following projects are affected by this:
 - forrest-test :  Apache Forrest software is a publishing framework that 
 trans...
 - forrest-test-basic :  Apache Forrest software is a publishing framework 
 that trans...
 - forrest-test-deploy-plugins :  Apache Forrest software is a publishing 
 framework that trans...
 
 
 Full details are available at:
 http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/index.html
 
 That said, some information snippets are provided here.
 
 The following annotations (debug/informational/warning/error messages) were 
 provided:
  -INFO- Failed with reason build timed out
 
 
 
 The following work was performed:
 http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/gump_work/build_forrest_forrest-test-basic.html
 Work Name: build_forrest_forrest-test-basic (Type: Build)
 Work ended in a state of : Failed
 Elapsed: 1 hour 2 secs
 Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
 -Dbuild.sysclasspath=only 
 -Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar
  org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
 test-basic 
 [Working Directory: /srv/gump/public/workspace/forrest/main]
 CLASSPATH: 
 /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-2.1.13-dev.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-asciiart-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-auth-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-batik-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-chaperon-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-fop-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-html-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-linkrewriter-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-lucene-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-profiler-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-template-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-validation-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-xsp-block.jar:/srv/gump/public/workspace/forrest/lib/core/chaperon-2004
  
 0205.jar:/srv/gump/public/workspace/forrest/lib/core/ehcache-core-2.2.0.jar:/srv/gump/public/workspace/forrest/lib/core/jing-2009.jar:/srv/gump/public/workspace/forrest/lib/core/nekopull-0.2.4.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-log4j12-1.7.2.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-api-1.7.2.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-6.1.26.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-util-6.1.26.jar:/srv/gump/public/workspace/forrest/build/xml-forrest.jar:/srv/gump/packages/apache-attic/avalon-framework-api-4.3.jar:/srv/gump/packages/apache-attic/avalon-framework-impl-4.3.jar:/srv/gump/packages/apache-attic/excalibur-component-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-datasource-2.2.2.jar:/srv/gump/packages/apache-attic/excalibur-instrument-api-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-logger-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-pool-api-2.2.1.jar:/srv/gump/packages/apache-attic/excalib
  
 

[jira] [Comment Edited] (FOR-1249) Gump trouble because we use head of xmlgraphics-commons but specific fop-1.0

[David Crossley (JIRA)]

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

David Crossley edited comment on FOR-1249 at 9/13/14 12:23 AM:
---

Our Gump project uses the head of xml-batik and xmlgraphics-commons but 
uses our packaged fop-1.0.jar.

Changing our Gump Descriptor to use our packaged xmlgraphics-commons-1.5.jar.
Done in r1624475 and r1624686.

This may affect the use of head of Batik, lets see.


was (Author: crossley):
Our Gump project uses the head of xml-batik and xmlgraphics-commons but 
uses our packaged fop-1.0.jar.

Changing our Gump Descriptor to use our packaged xmlgraphics-commons-1.5.jar.
Done in r1624475.

This may affect the use of head of Batik, lets see.

 Gump trouble because we use head of xmlgraphics-commons but specific fop-1.0
 

 Key: FOR-1249
 URL: https://issues.apache.org/jira/browse/FOR-1249
 Project: Forrest
  Issue Type: Task
  Components: Core operations
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


 On 2014-08-22 Gump started reporting a problem related to our use of FOP and 
 XML Graphics Commons.
 Workaround this for now by tweaking our Gump Descriptor to use our older 
 package version of xmlgraphics-commons to match our old FOP.



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

Re: Building my website with forrest 0.9

[David Crossley]

On Thu, Sep 11, 2014 at 10:54:29AM +1000, David Crossley wrote:
 On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
  Hi,
  
  I've just installed forrest-0.9 with the help of David Crossley (thanks 
  again).
  
  Unfortunately it can't build my website (that I built when 0.9 was the
  developer version).
  With 'forrest run' I get the following error:
  
  Internal Server Error
  Message: null
  Description: No details available.
  Sender: org.apache.cocoon.servlet.CocoonServlet
  Source: Cocoon Servlet
  cause
  
  C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)
  
  request-uri
  /index.html
  
  Request URI
  index.html
 
  If I do a clean, run 'forrest' and read the broken-links.xml file it says:
  
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)linkmap.html/link
  /broken-links
  
  I don't know what to do now. Any ideas?
 
 Those mangled Windows pathnames are certainly a problem.

This Google search: apache forrest mangled Windows
found some relevant past discussion. There is dev list stuff,
plus two issues:
https://issues.apache.org/jira/browse/FOR-1108
 Dispatcher, Cocoon 2.1 and Windows
https://issues.apache.org/jira/browse/FOR-1188
 locationmap or sitemap path broken on Windows, multiple paths concatenated

These sound similar to your problems.

 First thing is to ensure that a default skinned site will work.
 In a new directory, do:
  forrest seed-sample
  forrest
 
 If that works, then try configuring that sample site
 to use Dispatcher. See its forrest.properties configuration file.
 Then do the 'forrest' command again.
 
  Should I try forrest 0.10?
 
 Perhaps that might help.

In the FOR-1188 issue listed above, Sjur seemed to indicate
that using svn trunk (forrest-0.10-dev) did help.

It would be great to finish investigating those issues
and hopefully remove the workarounds.

-David

 I do recall some similar issues in the past.
 I do not use Windows, so it is difficult for me to help.
 Let us hope that one of the other committers that use
 Dispatcher will assist.
 
 -David
 
  TIA
  
  Vicent
  
  PS: I'm using Windows 8.1 (and missing my Ubuntu)
  
  -- 
  Share what you know, learn what you don't.
  

[jira] [Commented] (FOR-1188) locationmap or sitemap path broken on Windows, multiple paths concatenated

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1188:
-

Other related discussion around 23 Mar 2012:
http://s.apache.org/vj

 locationmap or sitemap path broken on Windows, multiple paths concatenated
 --

 Key: FOR-1188
 URL: https://issues.apache.org/jira/browse/FOR-1188
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: internal.dispatcher
Affects Versions: 0.8, 0.9
Reporter: Rajith Gunasinghe
 Fix For: 0.10-dev


 Dear all
 I was going to edit perfectly working plugin 
 org.apache.forrest.plugin.input.projectInfo. Before that i tried to test it 
 using ant test command. Then below bug arrised. I have included 
 antworks-miporter.jar and xml-common-resolver.jar.
 Please help me
 Rajith
 D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.projectInfoant 
 test
 Buildfile: 
 D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.projectIn
 fo\build.xml
 init-build-compiler:
 echo-init:
  [echo]
  [echo]   
 --
  [echo]
  [echo]   Using Apache Ant version 1.8.0 compiled on February 1 2010
  [echo]   Build file 
 D:\Projects\forrest\plugins\org.apache.forrest.plug
 in.input.projectInfo\build.xml
  [echo]   Use 'build.[sh|bat] -projecthelp' to see other options.
  [echo]   Build system home C:\apache-ant-1.8.0
  [echo]   Build number 12
  [echo]   Project Name Forrest plugin build file
  [echo]   Java Version 1.6
  [echo]   Timestamp 201003311350
  [echo]
  [echo]   
 --
  [echo]
 init:
 clean:
[delete] Deleting directory 
 D:\Projects\forrest\build\plugins\org.apache.forr
 est.plugin.input.projectInfo
 compile:
 jar:
 local-deploy:
  [echo] Locally deploying org.apache.forrest.plugin.input.projectInfo
  [copy] Copying 43 files to 
 D:\Projects\forrest\build\plugins\org.apache.for
 rest.plugin.input.projectInfo
 build:
 docs:
  [echo] Building Docs for org.apache.forrest.plugin.input.projectInfo
 check-java-version:
  [echo] This is apache-forrest-0.8
  [echo] Using Java 1.6 from C:\Program Files\Java\jdk1.6.0_18\jre
  [echo] Using Apache Ant version 1.8.0 compiled on February 1 2010 from 
 C:\a
 pache-ant-1.8.0
 init-props:
 echo-settings-condition:
 echo-settings:
 check-skin:
 init-proxy:
 fetch-skins-descriptors:
 fetch-skin:
 unpack-skins:
 init-skins:
 fetch-plugins-descriptors:
  [echo] Fetching plugins descriptor: 
 http://forrest.apache.org/plugins/plugi
 ns.xml
   [get] Getting: http://forrest.apache.org/plugins/plugins.xml
   [get] To: 
 D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.proj
 ectInfo\build\tmp\plugins-1.xml
   [get] local file date : Wed Mar 24 13:38:56 IST 2010
   [get] Not modified - so not downloaded
  [echo] Fetching plugins descriptor: 
 http://forrest.apache.org/plugins/white
 board-plugins.xml
   [get] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
   [get] To: 
 D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.proj
 ectInfo\build\tmp\plugins-2.xml
   [get] local file date : Thu Mar 04 15:05:34 IST 2010
   [get] Not modified - so not downloaded
  [echo] Plugin list loaded from 
 http://forrest.apache.org/plugins/plugins.xm
 l.
  [echo] Plugin list loaded from 
 http://forrest.apache.org/plugins/whiteboard
 -plugins.xml.
 init-plugins:
  [copy] Copying 1 file to 
 D:\Projects\forrest\plugins\org.apache.forrest.plu
 gin.input.projectInfo\build\tmp
  [copy] Copying 1 file to 
 D:\Projects\forrest\plugins\org.apache.forrest.plu
 gin.input.projectInfo\build\tmp
  [copy] Copying 1 file to 
 D:\Projects\forrest\plugins\org.apache.forrest.plu
 gin.input.projectInfo\build\tmp
  [copy] Copying 1 file to 
 D:\Projects\forrest\plugins\org.apache.forrest.plu
 gin.input.projectInfo\build\tmp
  [copy] Copying 1 file to 
 D:\Projects\forrest\plugins\org.apache.forrest.plu
 gin.input.projectInfo\build\tmp
  [echo]
  [echo]   
 --
  [echo]   Installing plugin: 
 org.apache.forrest.plugin.input.projectInfo
  [echo]   
 --
  [echo]
 check-plugin:
  [echo] org.apache.forrest.plugin.input.projectInfo is available in the 
 buil
 d dir. Trying to update it...
 init-props:
 echo-settings-condition:
 echo-settings:
 init-proxy:
 fetch-plugins-descriptors:
 fetch-plugin:
  [echo] Trying to find the description

Re: Building my website with forrest 0.9

[David Crossley]

On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org wrote:
 
  If that works, then try configuring that sample site
  to use Dispatcher. See its forrest.properties configuration file.
  Then do the 'forrest' command again.
 
 That fails.
 
 With the 0.10 version my website is built both with the skinner method
 and with the dispatcher plugin so I think my best option is to use the
 0.10 version and try to find out why the customizations are ignored.
 
 Thanks again for your help.

Ah, good that it works with 0.10-dev

So that confirms https://issues.apache.org/jira/browse/FOR-1188

Would you please try with the projectInfo plugin.
It has been difficult to get someone on Windows to confirm
that it still has that problem.

cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
Enable it for Dispatcher in forrest.properties, i.e.
project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
Then do:
 forrest site

-David

Re: Customizing a website using forrest 0.10-dev and dispatcher

[David Crossley]

On Thu, Sep 11, 2014 at 01:48:58PM +0200, Vicent Mas wrote:
 Hi,
 
 I'm trying to build a website with forrest 0.10 and the dispatcher
 plugin. My current problem is that all my customizations are ignored. For
 instance, if I change the copyright in a footer it is not updated. I've used
 the Dispatcher Quickstart (version 0.8 is the most modern version I found) as
 a guide when possible.

Not sure what you mean regarding version 0.8.

The current, but perhaps out-of-date, document is in the plugin's docs.
Do this:
 cd whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher
 forrest run
 http://localhost:/how/howto-dispatcher-quickstart.html

(Patches welcome :-)

I am hoping that someone who knows more can help you with
the rest, e.g. Thorsten, Cyriaque, Brian, etc.

-David

 The current structure of my website is as follows (best
 read with a monospace font):
 
 forrest
   |-forrest.properties
   |-forrest.properties.dispatcher.properties
   |-forrest.properties.xml
   |-build
   |-src
 |-documentation
  |-Readme.txt
  |-sitemap.xmap
  |-skinconf.xml
  |-classes
  |-conf
  |-translations
  |-content
  |  |-xdocs
  ||-site.xml
  ||-tabs.xml
  ||-index.xml
  ||-files and folders with the website content
  |-resources
|-images
 |-schema
 |-structurer
 |  |-url
 ||-screenshots
 |  |-index.structurer.xml (customize the html view of the
 screenshots/index.html page)
 |
 |-stylesheets
 |-themes
  |-common
  |  |-html
  ||- a bunch of customized contracts
  |-pelt
  |  |-css
  |  |-images
  |  |-panels
  ||-pelt-css.panel.xml
  ||-pelt-html.content.panel.xml
  ||-pelt-html.footer.panel.xml
  ||-pelt-html.head.panel.xml
  ||-pelt-html.header.panel.xml
  ||-pelt-html.leftbar.panel.xml
  ||-pelt-html.nav-main.panel.xml
  ||-pelt-html.panel.xml
  ||-pelt-html.screeshots_head.panel.xml (used in
  |   index.structurer.xml)
  |-common.structurer.xml
  |-pelt.structurer.xml
 
 The content of the $THEMES folder has been copied from
 $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/themer/themes
 in order to customise (adding/removing contracts or using my own contracts)
 how website pages are rendered.
 The $STRUCTURER folder allows to customize a given page differently to the
 bulk of pages.
 
 The above hierarchy worked in the past (when 0.9 was the development
 version) but currently it fails with both 0.9 stable and 0.10 development
 versions:
 - with 0.9 version I get the error explained in one of my previous mails
   (Subject: Building my website with forrest 0.9. Thanks again to
 David Crossley for his help)
 - with 0.10 version my customizations are silently ignored but at least the
   website is displayed
 
 It seems that my best chance is to use forrest 0.10.
 
 Could somebody tell me how should I customise my website with the dispatcher
 and the 0.10 version please? I am really stuck.
 
 TIA (and sorry for the lengthy mail).
 
 Vicent
 
 -- 
 Share what you know, learn what you don't.

Re: Customizing a website using forrest 0.10-dev and dispatcher

[David Crossley]

On Thu, Sep 11, 2014 at 06:52:28PM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 5:09 PM, David Crossley cross...@apache.org wrote:
  On Thu, Sep 11, 2014 at 01:48:58PM +0200, Vicent Mas wrote:
  Hi,
 
  I'm trying to build a website with forrest 0.10 and the dispatcher
  plugin. My current problem is that all my customizations are ignored. For
  instance, if I change the copyright in a footer it is not updated. I've 
  used
  the Dispatcher Quickstart (version 0.8 is the most modern version I found) 
  as
  a guide when possible.
 
  Not sure what you mean regarding version 0.8.
 
 I mean this document:
 
 http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.html

Ah. When using the dev version of Forrest, should use the local docs.

  The current, but perhaps out-of-date, document is in the plugin's docs.
  Do this:
   cd whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher
   forrest run
   http://localhost:/how/howto-dispatcher-quickstart.html
 
 I've done it but I get a Resource not found error.

That is very strange. It works locally for me.

Perhaps you need to clean your Forrest setup.
(Of course replace with Windows-specific commands.)
 cd $FORREST_HOME/main
 ./build.sh clean
 ./build.sh

Not sure what is needed to clean the Dispatcher plugin,
so do this:
 cd 
$FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher
 forrest clean
 $FORREST_HOME/tools/ant/bin/ant clean

Then do:
 forrest run
which should automatically build and deploy the Dispatcher plugin,
and the other plugins that it uses, from the local dev sources.
During that process the get-local Ant task should be indicating
that it is using the local sources.

 Anyway I've found
 the xml version of the document and the content seems to correspond to
 the document I mention above. The document talks about an
 org.apache.forrest.themes.core plugin that I'm unable to find and also
 about a pelt.fv file in that plugin, so I am lost.

Yes, because no-one has managed to update those docs yet.

As Sjur explained that old supporting plugin is not used anymore.

-David

  (Patches welcome :-)
 
 I wish I was able to patch it :-) Thanks once more for your help.
 
  I am hoping that someone who knows more can help you with
  the rest, e.g. Thorsten, Cyriaque, Brian, etc.
 
  -David
 
  The current structure of my website is as follows (best
  read with a monospace font):
 
  forrest
|-forrest.properties
|-forrest.properties.dispatcher.properties
|-forrest.properties.xml
|-build
|-src
  |-documentation
   |-Readme.txt
   |-sitemap.xmap
   |-skinconf.xml
   |-classes
   |-conf
   |-translations
   |-content
   |  |-xdocs
   ||-site.xml
   ||-tabs.xml
   ||-index.xml
   ||-files and folders with the website content
   |-resources
 |-images
  |-schema
  |-structurer
  |  |-url
  ||-screenshots
  |  |-index.structurer.xml (customize the html view of the
  screenshots/index.html page)
  |
  |-stylesheets
  |-themes
   |-common
   |  |-html
   ||- a bunch of customized contracts
   |-pelt
   |  |-css
   |  |-images
   |  |-panels
   ||-pelt-css.panel.xml
   ||-pelt-html.content.panel.xml
   ||-pelt-html.footer.panel.xml
   ||-pelt-html.head.panel.xml
   ||-pelt-html.header.panel.xml
   ||-pelt-html.leftbar.panel.xml
   ||-pelt-html.nav-main.panel.xml
   ||-pelt-html.panel.xml
   ||-pelt-html.screeshots_head.panel.xml (used in
   |   index.structurer.xml)
   |-common.structurer.xml
   |-pelt.structurer.xml
 
  The content of the $THEMES folder has been copied from
  $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/themer/themes
  in order to customise (adding/removing contracts or using my own contracts)
  how website pages are rendered.
  The $STRUCTURER folder allows to customize a given page differently to the
  bulk of pages.
 
  The above hierarchy worked in the past (when 0.9 was the development
  version) but currently it fails with both 0.9 stable and 0.10 development
  versions:
  - with 0.9 version I get the error explained in one of my previous mails
(Subject: Building my website with forrest 0.9. Thanks again to
  David Crossley for his help)
  - with 0.10 version my customizations are silently ignored but at least the
website is displayed
 
  It seems that my best chance is to use forrest 0.10.
 
  Could somebody tell me how should I customise my website with the 
  dispatcher
  and the 0.10 version please? I am really stuck.
 
  TIA (and sorry for the lengthy mail).
 
  Vicent
 
 Vicent
 
 -- 
 Share what you know, learn what you don't.

Re: Building my website with forrest 0.9

[David Crossley]

On Fri, Sep 12, 2014 at 12:53:49AM +1000, David Crossley wrote:
 On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org wrote:
  
   If that works, then try configuring that sample site
   to use Dispatcher. See its forrest.properties configuration file.
   Then do the 'forrest' command again.
  
  That fails.
  
  With the 0.10 version my website is built both with the skinner method
  and with the dispatcher plugin so I think my best option is to use the
  0.10 version and try to find out why the customizations are ignored.
  
  Thanks again for your help.
 
 Ah, good that it works with 0.10-dev
 
 So that confirms https://issues.apache.org/jira/browse/FOR-1188
 
 Would you please try with the projectInfo plugin.
 It has been difficult to get someone on Windows to confirm
 that it still has that problem.
 
 cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
 Enable it for Dispatcher in forrest.properties, i.e.
 project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
 Then do:
  forrest site

The remnants of this issue might be what is causing your
recent problems in the other discussion thread about
trying to view the local docs for the Dispatcher plugin.

-David

Re: Building my website with forrest 0.9

[David Crossley]

On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
 Hi,
 
 I've just installed forrest-0.9 with the help of David Crossley (thanks 
 again).
 
 Unfortunately it can't build my website (that I built when 0.9 was the
 developer version).
 With 'forrest run' I get the following error:
 
 Internal Server Error
 Message: null
 Description: No details available.
 Sender: org.apache.cocoon.servlet.CocoonServlet
 Source: Cocoon Servlet
 cause
 
 C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)
 
 request-uri
 /index.html
 
 Request URI
 index.html

 If I do a clean, run 'forrest' and read the broken-links.xml file it says:
 
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)linkmap.html/link
 /broken-links
 
 I don't know what to do now. Any ideas?

Those mangled Windows pathnames are certainly a problem.

First thing is to ensure that a default skinned site will work.
In a new directory, do:
 forrest seed-sample
 forrest

If that works, then try configuring that sample site
to use Dispatcher. See its forrest.properties configuration file.
Then do the 'forrest' command again.

 Should I try forrest 0.10?

Perhaps that might help.

I do recall some similar issues in the past.
I do not use Windows, so it is difficult for me to help.
Let us hope that one of the other committers that use
Dispatcher will assist.

-David

 TIA
 
 Vicent
 
 PS: I'm using Windows 8.1 (and missing my Ubuntu)
 
 -- 
 Share what you know, learn what you don't.
 

Re: Building my website with forrest 0.9

[David Crossley]

On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
 Hi,
 
 I've just installed forrest-0.9 with the help of David Crossley (thanks 
 again).
 
 Unfortunately it can't build my website (that I built when 0.9 was the
 developer version).

If you are referring just to the ViTables site
(that is listed here http://forrest.apache.org/live-sites.html#dispatcher)
then i do not see the need for using Dispatcher,
as that seems to be a straight-forward website.

-David

Re: How to install forrest 0.9

[David Crossley]

On Tue, Sep 09, 2014 at 01:43:52PM +0200, Vicent Mas wrote:
 Hi,
 after a long time without using Forrest I'm trying to redo  my website
 with it but I'm failing. I'd like to use the current version, 0.9.

Hello Vincent, good to hear from you again.

 The
 problem is that I don't know how to install it. I've downloaded the
 apache-forrest-0.9-sources.tar.gz  and
 apache-forrest-0.9-dependencies.tar.gz. as it is said in the link
 
 http://forrest.apache.org/mirrors.cgi
 
 But when I unpack those archives both of them have the same name
 (apache-forrest-0.9). So I can't leave both of them on the same
 folder. I've tried to put the dependencies package inside (and at the
 top level) of the sources package but then forrest refuses to run.
 I've tried the opposite with the same result. I'm sure I'm failing in
 an obvious way but i don't see my mistakes. Sorry if this is a stupid
 question but, could somebody tell me how install forrest 0-9 properly?

Not a silly question. We tried to clarify the notes on
that page already. It seems that it needs another tweak.

Do this:
cd to your-installation-directory.
Unpack the sources there.
Stay in that directory.
Unpack the dependencies there too.
This will append the extra bits into the
appropriate locations.

 TIA
 
 PS: I want to use the dispatcher plugin.

Please ask about that in a separate thread.
I wrote a Quickstart document a long time ago
which did work at that time. However things changed
and it probably needs tweaking. There was some
discussion in the mail archives. Some other Forrest
committers do use it, so they should be keen to
help you to update it.

-David

 -- 
 Share what you know, learn what you don't.
 

[jira] [Created] (FOR-1248) Fix subversion properties for svn:ignore

[David Crossley (JIRA)]

David Crossley created FOR-1248:
---

 Summary: Fix subversion properties for svn:ignore
 Key: FOR-1248
 URL: https://issues.apache.org/jira/browse/FOR-1248
 Project: Forrest
  Issue Type: Bug
  Components: Other
Affects Versions: 0.9, 0.10-dev
Reporter: David Crossley
Priority: Minor
 Fix For: 0.10-dev


I attempted a local vendor branch of our trunk, but our current settings for 
some svn:ignore properties prevent the local checkin. Fix them.



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

[jira] [Commented] (FOR-1248) Fix subversion properties for svn:ignore

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1248:
-

Then i added back the specific necessary properties.
Did not bother with the build ignore for the many lower-level directories, 
e.g. plugins.

Instead added svn:global-ignores build to the top-level.
People using svn clients v1.8 would need to add to their local 
~/.subversion/config file.

 Fix subversion properties for svn:ignore
 

 Key: FOR-1248
 URL: https://issues.apache.org/jira/browse/FOR-1248
 Project: Forrest
  Issue Type: Bug
  Components: Other
Affects Versions: 0.9, 0.10-dev
Reporter: David Crossley
Priority: Minor
 Fix For: 0.10-dev


 I attempted a local vendor branch of our trunk, but our current settings 
 for some svn:ignore properties prevent the local checkin. Fix them.



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

[jira] [Commented] (FOR-1248) Fix subversion properties for svn:ignore

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1248:
-

The commit carks it with:
svn: E125005: Cannot accept non-LF line endings in 'svn:ignore' property

It is difficult to find the problem ones. Doing this helped:
Got a list of all properties in my local svn copy:
]$ svn propget -R -v svn:ignore .  svn-properties-ignore.txt
Remove all:
]$ svn propdel -R svn:ignore .
Get the complete diff:
]$ svn diff  diff.txt
and then view with vi editor, so can see the problem Windows line-endings

 Fix subversion properties for svn:ignore
 

 Key: FOR-1248
 URL: https://issues.apache.org/jira/browse/FOR-1248
 Project: Forrest
  Issue Type: Bug
  Components: Other
Affects Versions: 0.9, 0.10-dev
Reporter: David Crossley
Priority: Minor
 Fix For: 0.10-dev


 I attempted a local vendor branch of our trunk, but our current settings 
 for some svn:ignore properties prevent the local checkin. Fix them.



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

Re: [GUMP@vmgump]: Project forrest-test (in module forrest) failed

[David Crossley]

Follow through from http://forrest.apache.org/gump.html
to forrest-test and then the Complete Output File at Gump.

---
...
 [java] * [13/60]   [0/0] 2.19s  0b  samples-b/sample.pdf
 [java] Exception in thread main java.lang.NoSuchMethodError: 
org.apache.xmlgraphics.xmp.Metadata.mergeInto(Lorg/apache/xmlgraphics/xmp/Metadata;)V
 [java] at 
org.apache.fop.render.pdf.PDFRenderingUtil.renderXMPMetadata(PDFRenderingUtil.java:342)
 [java] at 
org.apache.fop.render.pdf.PDFDocumentHandler.handleExtensionObject(PDFDocumentHandler.java:294)
...
---

So something changed recently at XML Graphics that affects our use of FOP.
The recent commit there is http://svn.apache.org/r1619414

Can anyone see why that would be so?

-David

On Fri, Aug 22, 2014 at 03:59:55AM +, Gump wrote:
 To whom it may engage...
 
 This is an automated request, but not an unsolicited one. For 
 more information please visit http://gump.apache.org/nagged.html, 
 and/or contact the folk at gene...@gump.apache.org.
 
 Project forrest-test has an issue affecting its community integration.
 This issue affects 1 projects.
 The current state of this project is 'Failed', with reason 'Build Timed Out'.
 For reference only, the following projects are affected by this:
 - forrest-test :  Apache Forrest software is a publishing framework that 
 trans...
 
 
 Full details are available at:
 http://vmgump.apache.org/gump/public/forrest/forrest-test/index.html
 
 That said, some information snippets are provided here.
 
 The following annotations (debug/informational/warning/error messages) were 
 provided:
  -INFO- Failed with reason build timed out
 
 
 
 The following work was performed:
 http://vmgump.apache.org/gump/public/forrest/forrest-test/gump_work/build_forrest_forrest-test.html
 Work Name: build_forrest_forrest-test (Type: Build)
 Work ended in a state of : Failed
 Elapsed: 1 hour 1 sec
 Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
 -Dbuild.sysclasspath=only 
 -Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar
  org.apache.tools.ant.Main -verbose 
 -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
 -Dproject.plugins.override=true gump-forrest-test 
 [Working Directory: /srv/gump/public/workspace/forrest/main]
 CLASSPATH: 
 /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-2.1.13-dev.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-asciiart-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-auth-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-batik-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-chaperon-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-fop-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-html-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-linkrewriter-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-lucene-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-profiler-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-template-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-validation-block.jar:/srv/gump/public/workspace/forrest/lib/core/cocoon-xsp-block.jar:/srv/gump/public/workspace/forrest/lib/core/chaperon-2004
  
 0205.jar:/srv/gump/public/workspace/forrest/lib/core/ehcache-core-2.2.0.jar:/srv/gump/public/workspace/forrest/lib/core/jing-2009.jar:/srv/gump/public/workspace/forrest/lib/core/jtidy-04aug2000r7-dev.jar:/srv/gump/public/workspace/forrest/lib/core/nekopull-0.2.4.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-log4j12-1.7.2.jar:/srv/gump/public/workspace/forrest/lib/core/slf4j-api-1.7.2.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-6.1.26.jar:/srv/gump/public/workspace/forrest/tools/jetty/jetty-util-6.1.26.jar:/srv/gump/public/workspace/forrest/build/plugins/lib/fop-1.0.jar:/srv/gump/public/workspace/forrest/build/xml-forrest.jar:/srv/gump/packages/apache-attic/avalon-framework-api-4.3.jar:/srv/gump/packages/apache-attic/avalon-framework-impl-4.3.jar:/srv/gump/packages/apache-attic/excalibur-component-2.2.1.jar:/srv/gump/packages/apache-attic/excalibur-datasource-2.2.2.jar:/srv/gump/packages/apache-attic/excalibur-instrument-api-2.2.1.jar:/srv/gump/packages/apach
  
 

Re: [GUMP@vmgump]: Project forrest-rat (in module forrest) failed

[David Crossley]

Hmmm, it came good all by itself.

Ah, the upgrade to commons-lang3 was reverted
http://svn.apache.org/r1615427
https://issues.apache.org/jira/browse/RAT-136

-David

On Fri, Aug 01, 2014 at 05:54:23PM +1000, David Crossley wrote:
 I have done a little investigation and provide some notes below.
 
 This is from Gump running the RAT tools for us.
 All has been going well until now.
 
 [1] http://forrest.apache.org/gump.html#forrest-rat
 
 [2] http://forrest.apache.org/gump.html#configuration
 
 Over at the Apache Creadur project, Phil has been
 giving RAT some attention. One of the tasks was to
 update to Commons Lang 3, so we now get the error
  java.lang.ClassNotFoundException: 
 org.apache.commons.lang3.time.DateFormatUtils
 
 Because Gump runs the trunk of each project, we get to know quickly.
 
 Our Gump Descriptor (linked from [2]) needs to change
 to commons-lang3.
 
 However Gump does not have a project descriptor for that.
 Remember that Gump went into minimalist mode recently,
 so has only what is necessary.
 
 It should be obvious by following the other Gump
 Descriptors how to set it up. If not, then the Gump
 dev mail list would help.
 
 Then follow the next run of Gump, via the link at the
 bottom of [1].
 
 -David
 
 
 On Thu, Jul 31, 2014 at 01:07:35AM +, Gump wrote:
  To whom it may engage...
  
  This is an automated request, but not an unsolicited one. For 
  more information please visit http://gump.apache.org/nagged.html, 
  and/or contact the folk at gene...@gump.apache.org.
  
  Project forrest-rat has an issue affecting its community integration.
  This issue affects 1 projects,
   and has been outstanding for 104 runs.
  The current state of this project is 'Failed', with reason 'Build Failed'.
  For reference only, the following projects are affected by this:
  - forrest-rat :  Apache Forrest software is a publishing framework that 
  trans...
  
  
  Full details are available at:
  http://vmgump.apache.org/gump/public/forrest/forrest-rat/index.html
  
  That said, some information snippets are provided here.
  
  The following annotations (debug/informational/warning/error messages) were 
  provided:
   -INFO- Failed with reason build failed
  
  
  
  The following work was performed:
  http://vmgump.apache.org/gump/public/forrest/forrest-rat/gump_work/build_forrest_forrest-rat.html
  Work Name: build_forrest_forrest-rat (Type: Build)
  Work ended in a state of : Failed
  Elapsed: 1 sec
  Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
  -Dbuild.sysclasspath=only org.apache.tools.ant.Main 
  -Dgump.merge=/srv/gump/public/gump/work/merge.xml gump-rat 
  [Working Directory: /srv/gump/public/workspace/forrest/main]
  CLASSPATH: 
  /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant-contrib/target/ant-contrib-20140731.jar:/srv/gump/public/workspace/rat/apache-rat-core/target/apache-rat-core-0.11-SNAPSHOT.jar:/srv/gump/public/workspace/rat/apache-rat-plugin/target/apache-rat-plugin-0.11-SNAPSHOT.jar:/srv/gump/public/workspace/rat/apache-rat-tasks/target/apache-rat-tasks-0.11-SNAPSHOT.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/cli/target/com
   
  mons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.5-SNAPSHOT.jar:/srv/gump/public/workspace/commons-lang-2.x/target/commons-lang-2.7-SNAPSHOT.jar
  -
   [echo]   Using Apache Ant(TM) version 1.9.5alpha compiled on July 
  31 2014
   [echo]   Build file 
  /srv/gump/public/workspace/forrest/main/build.xml
   [echo]   Use 'build.[sh|bat] -projecthelp' to see other options.
   [echo]   Build system home ${ant.home}
   [echo]   Build number 1
   [echo]   Project Name Forrest build file
   [echo]   Java Version 1.7  
   [echo]   Timestamp 201407310107
   [echo]   This is: apache-forrest 0.10-dev
   [echo] 
   [echo]   
  --
   [echo] 
  
  gump-rat:
  
  BUILD FAILED
  /srv/gump/public/workspace/forrest/main/build.xml:576: 
  java.lang.NoClassDefFoundError: 
  org/apache/commons/lang3/time/DateFormatUtils
  at 
  org.apache.rat.report.claim.impl.xml.SimpleXmlClaimReporter.startReport(SimpleXmlClaimReporter.java:132)
  at 
  org.apache.rat.report.claim.util.ClaimReporterMultiplexer.startReport

Re: [GUMP@vmgump]: Project forrest-rat (in module forrest) failed

[David Crossley]

I have done a little investigation and provide some notes below.

This is from Gump running the RAT tools for us.
All has been going well until now.

[1] http://forrest.apache.org/gump.html#forrest-rat

[2] http://forrest.apache.org/gump.html#configuration

Over at the Apache Creadur project, Phil has been
giving RAT some attention. One of the tasks was to
update to Commons Lang 3, so we now get the error
 java.lang.ClassNotFoundException: org.apache.commons.lang3.time.DateFormatUtils

Because Gump runs the trunk of each project, we get to know quickly.

Our Gump Descriptor (linked from [2]) needs to change
to commons-lang3.

However Gump does not have a project descriptor for that.
Remember that Gump went into minimalist mode recently,
so has only what is necessary.

It should be obvious by following the other Gump
Descriptors how to set it up. If not, then the Gump
dev mail list would help.

Then follow the next run of Gump, via the link at the
bottom of [1].

-David


On Thu, Jul 31, 2014 at 01:07:35AM +, Gump wrote:
 To whom it may engage...
 
 This is an automated request, but not an unsolicited one. For 
 more information please visit http://gump.apache.org/nagged.html, 
 and/or contact the folk at gene...@gump.apache.org.
 
 Project forrest-rat has an issue affecting its community integration.
 This issue affects 1 projects,
  and has been outstanding for 104 runs.
 The current state of this project is 'Failed', with reason 'Build Failed'.
 For reference only, the following projects are affected by this:
 - forrest-rat :  Apache Forrest software is a publishing framework that 
 trans...
 
 
 Full details are available at:
 http://vmgump.apache.org/gump/public/forrest/forrest-rat/index.html
 
 That said, some information snippets are provided here.
 
 The following annotations (debug/informational/warning/error messages) were 
 provided:
  -INFO- Failed with reason build failed
 
 
 
 The following work was performed:
 http://vmgump.apache.org/gump/public/forrest/forrest-rat/gump_work/build_forrest_forrest-rat.html
 Work Name: build_forrest_forrest-rat (Type: Build)
 Work ended in a state of : Failed
 Elapsed: 1 sec
 Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true 
 -Dbuild.sysclasspath=only org.apache.tools.ant.Main 
 -Dgump.merge=/srv/gump/public/gump/work/merge.xml gump-rat 
 [Working Directory: /srv/gump/public/workspace/forrest/main]
 CLASSPATH: 
 /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant-contrib/target/ant-contrib-20140731.jar:/srv/gump/public/workspace/rat/apache-rat-core/target/apache-rat-core-0.11-SNAPSHOT.jar:/srv/gump/public/workspace/rat/apache-rat-plugin/target/apache-rat-plugin-0.11-SNAPSHOT.jar:/srv/gump/public/workspace/rat/apache-rat-tasks/target/apache-rat-tasks-0.11-SNAPSHOT.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/cli/target/com
  
 mons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.5-SNAPSHOT.jar:/srv/gump/public/workspace/commons-lang-2.x/target/commons-lang-2.7-SNAPSHOT.jar
 -
  [echo]   Using Apache Ant(TM) version 1.9.5alpha compiled on July 31 
 2014
  [echo]   Build file /srv/gump/public/workspace/forrest/main/build.xml
  [echo]   Use 'build.[sh|bat] -projecthelp' to see other options.
  [echo]   Build system home ${ant.home}
  [echo]   Build number 1
  [echo]   Project Name Forrest build file
  [echo]   Java Version 1.7  
  [echo]   Timestamp 201407310107
  [echo]   This is: apache-forrest 0.10-dev
  [echo] 
  [echo]   
 --
  [echo] 
 
 gump-rat:
 
 BUILD FAILED
 /srv/gump/public/workspace/forrest/main/build.xml:576: 
 java.lang.NoClassDefFoundError: org/apache/commons/lang3/time/DateFormatUtils
   at 
 org.apache.rat.report.claim.impl.xml.SimpleXmlClaimReporter.startReport(SimpleXmlClaimReporter.java:132)
   at 
 org.apache.rat.report.claim.util.ClaimReporterMultiplexer.startReport(ClaimReporterMultiplexer.java:54)
   at org.apache.rat.Report.report(Report.java:417)
   at org.apache.rat.Report.report(Report.java:394)
   at org.apache.rat.anttasks.Report.createReport(Report.java:281)
   at org.apache.rat.anttasks.Report.execute(Report.java:198)
   at 

[jira] [Created] (FOR-1246) Upgrade packaged Ant to 1.9.x

[David Crossley (JIRA)]

David Crossley created FOR-1246:
---

 Summary: Upgrade packaged Ant to 1.9.x
 Key: FOR-1246
 URL: https://issues.apache.org/jira/browse/FOR-1246
 Project: Forrest
  Issue Type: Improvement
  Components: Core operations
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


Upgrade our packaged Apache Ant to a recent version.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (FOR-1246) Upgrade packaged Ant to 1.9.x

[David Crossley (JIRA)]

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

David Crossley commented on FOR-1246:
-

This was last done in r700693. See some notes about the process at that time, 
for our stuff in tools/ant/bin/*

 Upgrade packaged Ant to 1.9.x
 -

 Key: FOR-1246
 URL: https://issues.apache.org/jira/browse/FOR-1246
 Project: Forrest
  Issue Type: Improvement
  Components: Core operations
Affects Versions: 0.10-dev
Reporter: David Crossley
 Fix For: 0.10-dev


 Upgrade our packaged Apache Ant to a recent version.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)