Re: Is Gump still useful for you?

[Gav]

Hi Guys,

Yes Forrest is still interested - I will take a look over the next few
days to re-familiarize our setup.

Thanks!

Gav...


On Sat, Feb 24, 2018 at 4:52 AM, Stefan Bodewig  wrote:
> Hi all
>
> when writing Gump's quarterly report for the Apache board we usually
> include the phrase "Gump seems to remain useful for the projects using
> it". Back in September 2017 Gump builds stopped for several weeks and
> nobody seems to have noticed or at least complained about it. So maybe
> this isn't really true anymore?
>
> Currently the projects that have nags enabled in Gump are
>
> * Batik
> * XMLGraphics Commons
> * Santuario
> * Tomcat
>
> in addition to a few projects where I receive the nags myself.
>
> Are you even aware Gump is there and do you still consider it to provide
> value to your project? This is not any request for you to get involved
> but really a curious question.
>
> Cheers
>
> Stefan
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

RE: [Vote] Release Plan for Forrest 0.90

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Tuesday, 14 December 2010 9:15 AM
> To: dev@forrest.apache.org
> Subject: [Vote] Release Plan for Forrest 0.90
> 
> Please vote on this release plan.

+1 


Gav...

> 
> According to our guidelines,
> http://forrest.apache.org/guidelines.html#actions
> "A lazy majority vote requires
> 3 binding +1 votes and more binding +1 votes than -1 votes".
> 
> As usual anyone is encouraged to vote, just the votes
> of PMC members are binding.
> 
> According to the plan below:
> [1] end of vote on Release Plan
> Monday 2010-12-20 at 22:00 UTC
> http://www.timeanddate.com/worldclock/fixedtime.html?day=20&month=12&ye
> ar=2010&hour=22&min=0&sec=0&p1=0
> 
> Aiming for a release date of 7 February 2011 [4].
> 
> For background info on this step and on the release process
> in general, see
> http://forrest.apache.org/procedures/release/How_to_release.html#PrepRe
> lPlan
> 
> 
> The minimum Java version for this release is Java 1.5
> 
> 
> I will be the Release Manager.
> 
> People can help with various aspects of the release process. See [9].
> People can also help between now and then to prepare the codebase.
> 
> 
> For Plugins, see the proposal below.
> 
> 
> The phases are:
> 
> Voting to accept the Release Plan ends on:
> Monday 2010-12-20 at 22:00 UTC [1].
> 
> The first release candidate and start of testing:
> Monday 2011-01-31 at 22:00 UTC [2].
> 
> We create the release candidate on this day and start the testing.
> One week is available for this phase.
> Don't bother voting until towards the end of the week,
> because we might need a new release candidate.
> The vote needs to happen against the actual final packages.
> 
> During "code freeze" we do not add any new functionality or
> non-essential work, just bug fixes and documentation tweaks [5].
> 
> If necessary then we create another release candidate on
> Saturday 2011-02-05 at 22:00 UTC [3]
> to give people time to verify the signatures and checksums
> and to do final tests. Between this date and the release date
> there must no changes to SVN. If any are absolutely necessary,
> then we delay the release date and do another release candidate.
> 
> End of voting period:
> Monday 2011-02-07 at 22:00 UTC [4]
> This is the scheduled release date,
> then wait for the mirrors to receive it before
> sending the announcements.
> 
> 
> Plugins release plan:
> 
> In the past we have never done a proper "release" for any
> of the plugins. We have just done a "deploy" for some of them,
> which packages a plugin and copies it to our website to make
> it available to people who use a Forrest release.
> 
> That is not suitable. See [7]:
> "Releases are, by definition, anything that is published
> beyond the group that owns it." i.e. beyond our "dev" list.
> 
> To rectify that, i propose that we follow up after the
> core 0.9 release to actually vote and release each plugin
> that is suitable to be made widely available.
> 
> Please see the list showing the state of each Plugin [8].
> 
> Between now and mid-January, please work on your favourite
> plugin to get it ready, send patches etc. Deploy any that
> need to be either updated or made available. After the 0.9
> release is done, we will follow up to either "release" each
> one or to retract it.
> 
> Any that are suitable to be released would also be moved
> out of the "whiteboard/plugins".
> 
> If this general Plugin release plan is okay, then we can
> devise a more detailed procedure. After this batch of plugin
> releases, they can each be independently released as new
> plugin versions are needed.
> 
> 
> The proposed milestones are:
> 
> [1] end of vote on Release Plan
> Monday 2010-12-20 at 22:00 UTC
> http://www.timeanddate.com/worldclock/fixedtime.html?day=20&month=12&ye
> ar=2010&hour=22&min=0&sec=0&p1=0
> 
> [2] create initial release candidate, start testing
> Monday 2011-01-31 at 22:00 UTC
> http://www.timeanddate.com/worldclock/fixedtime.html?day=31&month=1&yea
> r=2011&hour=22&min=0&sec=0&p1=0
> 
> [3] create final release candidate if necessary
> Saturday 2011-02-05 at 22:00 UTC
> http://www.timeanddate.com/worldclock/fixedtime.html?day=5&month=2&year
> =2011&hour=22&min=0&sec=0&p1=0
> 
> [4] end of vote on final release candidate an

RE: BarCamp Apache Sydney 2010

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Tuesday, 7 December 2010 12:31 PM
> To: dev@forrest.apache.org
> Subject: BarCamp Apache Sydney 2010
> 
> The first BarCamp Apache Sydney is on this weekend
> Friday night and all day Saturday:
> http://barcamp.org/BarCampApacheSydney

I hope it went well, I am sorry I missed it.

Gav...

> 
> Some Forrest people will be there.
> 
> -David

RE: [Proposal] Release Plan for Forrest 0.90

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Thursday, 9 December 2010 11:00 AM
> To: dev@forrest.apache.org
> Subject: Re: [Proposal] Release Plan for Forrest 0.90
> 
> Tim Williams wrote:
> > Thanks David!  I'm in the midst of a double move - once to temporary
> > housing; then a couple weeks later, to the new house - and some other
> > rather large life-changes during this period but I'll certainly pitch
> > in as much as possible.  I could be more involved if all the dates
> > shifted by 2-3 weeks but if this works best for your schedule, I'll
> do
> > everything I can to support it.
> 
> Lets shift the main dates by three weeks.
> 
> However i would like to keep the Release Plan vote as-is,
> i.e. next week. I want to spread the word about a firm
> plan of action.

I am happy with whatever dates, I will try to help out as best I can where I
can
be of most use.

It is a shame you get to be RM again, I know you tried to encourage others
to do
it, maybe next time.

Gav...

> 
> All the best with your new opportunities.
> 
> -David

RE: doing svn up on the zone server (Was: svn commit: r1039238)

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Friday, 26 November 2010 12:06 PM
> To: dev@forrest.apache.org
> Subject: doing svn up on the zone server (Was: svn commit: r1039238)
> 
> However i cannot do 'svn up' on the zone server.
> 
> Do we each need to be in the "forrest" group?

Not needed, as per the Forrest Zone README.txt says:

"..To alter anything in /home/forrest/* log in and change to the 'forrest'
user:

sudo -s -u forrest -H

.."

(or sudo su -l forrest -p)


That would include doing an svn up.

HTH

Gav...

> 
> -David
> 
> > Author: crossley
> > Date: Fri Nov 26 01:56:38 2010
> > New Revision: 1039238
> >
> > URL: http://svn.apache.org/viewvc?rev=1039238&view=rev
> > Log:
> > notify forrest-dev list
> >
> > Modified:
> > forrest/zone/config/update-forrest-trunk.sh
> >
> > Modified: forrest/zone/config/update-forrest-trunk.sh
> > URL: http://svn.apache.org/viewvc/forrest/zone/config/update-forrest-
> trunk.sh?rev=1039238&r1=1039237&r2=1039238&view=diff
> >
> ===
> ===
> > --- forrest/zone/config/update-forrest-trunk.sh (original)
> > +++ forrest/zone/config/update-forrest-trunk.sh Fri Nov 26 01:56:38
> 2010
> > @@ -26,8 +26,7 @@ export FORREST_HOME=/home/forrest/source
> >  logfn=`date "+update-forrest-trunk-%Y%m%d%H.log"`
> >  logfile=${CONFIG}/$logfn
> >  sender=d...@forrest.apache.org
> > -recipient=gmcdona...@apache.org
> > -#recipient=$sender
> > +recipient=$sender

RE: A new release? Can I help?

[Gav...]

> -Original Message-
> From: Benson Margulies [mailto:bimargul...@gmail.com]
> Sent: Sunday, 17 October 2010 4:55 AM
> To: dev@forrest.apache.org
> Subject: Re: A new release? Can I help?
> 
> OK, I now understand about jing.
> 
> My motivations here are these: a bunch of foundation project use
> forrest; everyone has to update their branding; the Java 1.6 issue
> gums people up. Given the workaround, a release is not so urgent as I
> expected it to be.
> 
> Still, I'm willing to poke at some of the issues below, but it would
> be nice to know that there are a few residual PMC members here who
> could actually RM the release (and vote for it).

Residual PMC members? In what way?

Not having a release for 3 years doesn’t mean the PMC has gone away.

Gav...

> 
> On Fri, Oct 15, 2010 at 10:07 PM, David Crossley 
> wrote:
> > Benson Margulies wrote:
> >> Hello forrest dev:
> >>
> >> Java 1.5 is somewhat scarce on MacOSX and recent ubuntu. Is there
> any
> >> way I could help push out a release of the trunk, ...
> >
> > Thanks so much Benson. I don't have much time
> > but will try to help.
> >
> > Some quick response notes:
> >
> > * Yes please do help.
> >
> > * There has been some discussion about what needs
> > to be finalised. Some people have made individual
> > spurts of progress. As Forrest is moving slowly, please
> > see further back in archives. Some things were partially
> > dealt with and may need follow through.
> >
> > * Review issue tracker.
> > http://forrest.apache.org/issues.html#filters
> > The main filter is "FOR-roadmap-dev".
> >
> > * Review some outstanding patches. It would be
> > a shame not to include some more contributions
> > and we need to encourage our contributors.
> >
> > The review will encourage our committers to
> > apply it. Speaking for myself i don't have enough
> > time to investigate the following suggested ones.
> >
> > Glancing through the list i reckon that FOR-1203
> > and FOR-752 are the only likely candidates.
> > The others are either in plugins, which can be
> > handled at any time after the core release,
> > or need more work. IMO we should focus elsewhere
> > at this late stage.
> >
> > * I have made some progress at classifying the
> > licenses of our various supporting products.
> > We complicate things because we bundle these
> > products with our release.
> >
> > Next task is to ensure that we meet all of
> > their conditions, e.g. perhaps pass on NOTICES.
> >
> > * We have the release process at:
> > http://forrest.apache.org/procedures/release/How_to_release.html
> >
> > * Another useful resource is "Project tasks"
> > http://forrest.apache.org/tasks.html
> >
> > * I suggest that you install the "Forrestbar"
> > http://forrest.apache.org/tools/forrestbar.html
> > It is a great benefit for directed quick search/access
> > of our project resources.
> >
> > Thanks again for anything that you can manage
> > to assist with.
> >
> >  oOo
> >
> >> ... which (from the
> >> email archive) seems to be 1.6-friendly?
> >
> > Please note that Forrest does not require Java 6.
> > Let us know if the following issue does not address
> > what you are seeing.
> >
> > I was very concerned when i searched the net to see
> > that people do not realise the simple workaround.
> >
> > Today i added a new FAQ:
> > http://forrest.apache.org/faq.html#oldjing
> >
> > -David
> >

RE: Moving Forrest Zone to a FreeBSD Jail

[Gav...]

> > > > David Crossley wrote:
> > > > >
> > > > > Also we saw recently a failure with the old zone,
> > > > > but did not get an email message from the new zone.
> > > > > So perhaps something wrong with email orginating from
> > > > > the new zone.
> > > > >
> > > > > I will make a deliberate break, and see what happens.
> > > >
> > > > Yes, forrestbot on the new zone is not sending mail.
> > >
> > > Ok, I'll take a look and fix that tomorrow.
> >
> > looking, I believe I found the problem, testing...
> 
> Problem solved I'd say, I will test a break in the morning to be sure.
> 
> It was combination of :
> 
> a) - I had turned off notify on failure whilst setting up the new jail
> so we
> didn't get
> false alarms and double lots of emails for genuine failures. I needed
> to
> revert that
> now that we actually want these emails.
> 
> b) - The notify.email.from (default in notify.xml) value was not well
> liked
> by the new jail mail system, overriding it and appending the hostname
> made
> it work better.
> 
> c) - due to b) and in combination with rdns being incorrectly set, it
> wouldn't relay. Curing b) means the rdns doesn't matter that much, but
> that
> is also being fixed.
> 
> will report back my final tests and findings in the morning.
> 

Yep, all seems to be working well now.

Any changes I made will be committed afterwards once the PMC has approved 
the move.

Gav...

RE: Moving Forrest Zone to a FreeBSD Jail

[Gav...]

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Wednesday, 15 September 2010 7:46 PM
> To: dev@forrest.apache.org
> Subject: RE: Moving Forrest Zone to a FreeBSD Jail
> 
> 
> 
> > -Original Message-
> > From: Gav... [mailto:ga...@16degrees.com.au]
> > Sent: Tuesday, 14 September 2010 10:01 PM
> > To: dev@forrest.apache.org
> > Subject: RE: Moving Forrest Zone to a FreeBSD Jail
> >
> >
> >
> > > -Original Message-
> > > From: David Crossley [mailto:cross...@apache.org]
> > > Sent: Tuesday, 14 September 2010 9:56 PM
> > > To: dev@forrest.apache.org
> > > Subject: Re: Moving Forrest Zone to a FreeBSD Jail
> > >
> > > David Crossley wrote:
> > > >
> > > > Also we saw recently a failure with the old zone,
> > > > but did not get an email message from the new zone.
> > > > So perhaps something wrong with email orginating from
> > > > the new zone.
> > > >
> > > > I will make a deliberate break, and see what happens.
> > >
> > > Yes, forrestbot on the new zone is not sending mail.
> >
> > Ok, I'll take a look and fix that tomorrow.
> 
> looking, I believe I found the problem, testing...

Problem solved I'd say, I will test a break in the morning to be sure.

It was combination of :

a) - I had turned off notify on failure whilst setting up the new jail so we
didn't get
false alarms and double lots of emails for genuine failures. I needed to
revert that
now that we actually want these emails.

b) - The notify.email.from (default in notify.xml) value was not well liked
by the new jail mail system, overriding it and appending the hostname made
it work better.

c) - due to b) and in combination with rdns being incorrectly set, it
wouldn't relay. Curing b) means the rdns doesn't matter that much, but that
is also being fixed.

will report back my final tests and findings in the morning.

Gav...

> 
> Gav...
> 
> >
> > Thanks.
> >
> > Gav...
> >
> > >
> > > -David
> >
> 
> 

RE: Moving Forrest Zone to a FreeBSD Jail

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Tuesday, 14 September 2010 6:09 PM
> To: dev@forrest.apache.org
> Subject: Re: Moving Forrest Zone to a FreeBSD Jail
> 
> On Mon, Jul 19, 2010 Gav... wrote:
> > Hi All,
> >
> > Infra are working towards removing Helios our Zones machine. The
> Zones are
> > to be replaced with FreeBSD (8.1-RC2 currently) Jails.
> >
> > All projects zones are to be moved over the next few weeks. I have
> been
> > tasked mainly with this job, with help from others as
> > required.
> >
> > I have created new Jails but have yet to migrate an existing zone to
> a jail,
> > so I would like to start on familiar ground and
> > get the Forrest Zone moved - this week if possible. Anyone who has an
> acct
> > on our current zone setup will if they still require
> > it, get an acct on the new Jail.
> >
> > Does anyone foresee any issues in doing this? Is the timing ok?
> >
> > The only thing I can see is that FreeBSD (and now Debian/Ubuntu) uses
> the
> > Diablo Java rather than the sun jdk so if anyone knows
> > of any issues with that please let me know.
> >
> > I envisage a short crossover period where we will have both available
> > (forrest.zones.a.o and forrest2.zones.a.o) until we are happy all
> > is well at our new digs.
> >
> > If no objections I'll start soon (next couple of days)
> 
> Some messages have been going to the private@ forrest list
> for this. So trying to bring the technical discussion back here.
> 
> The old zone is being switched off on Friday 17 September
> i.e. in a few days.
> 
> Tim and i have done some quick checks.
> 
> I noticed that there have been changes to various files
> server-side on the new zone that are under SVN in forrest/zone
> So those changes need to be brought back and committed.

Sure, most, but not all, are local path changes to suit the new jail. I will
commit them just as soon as we have made the move away from the old zone
where
the current config files in svn are relevant.


> 
> Our zone documentation needs to be fixed:
> http://forrest.apache.org/zone.html

I can work on that after the switch.

Gav...

> 
> Also we saw recently a failure with the old zone,
> but did not get an email message from the new zone.
> So perhaps something wrong with email orginating from
> the new zone.
> 
> I will make a deliberate break, and see what happens.
> 
> However i do not have much time for this. So if someone
> else can help, that would be good.
> 
> -David

RE: Moving Forrest Zone to a FreeBSD Jail

[Gav...]

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Tuesday, 14 September 2010 10:01 PM
> To: dev@forrest.apache.org
> Subject: RE: Moving Forrest Zone to a FreeBSD Jail
> 
> 
> 
> > -Original Message-
> > From: David Crossley [mailto:cross...@apache.org]
> > Sent: Tuesday, 14 September 2010 9:56 PM
> > To: dev@forrest.apache.org
> > Subject: Re: Moving Forrest Zone to a FreeBSD Jail
> >
> > David Crossley wrote:
> > >
> > > Also we saw recently a failure with the old zone,
> > > but did not get an email message from the new zone.
> > > So perhaps something wrong with email orginating from
> > > the new zone.
> > >
> > > I will make a deliberate break, and see what happens.
> >
> > Yes, forrestbot on the new zone is not sending mail.
> 
> Ok, I'll take a look and fix that tomorrow.

looking, I believe I found the problem, testing...

Gav...

> 
> Thanks.
> 
> Gav...
> 
> >
> > -David
> 

RE: Moving Forrest Zone to a FreeBSD Jail

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Tuesday, 14 September 2010 9:56 PM
> To: dev@forrest.apache.org
> Subject: Re: Moving Forrest Zone to a FreeBSD Jail
> 
> David Crossley wrote:
> >
> > Also we saw recently a failure with the old zone,
> > but did not get an email message from the new zone.
> > So perhaps something wrong with email orginating from
> > the new zone.
> >
> > I will make a deliberate break, and see what happens.
> 
> Yes, forrestbot on the new zone is not sending mail.

Ok, I'll take a look and fix that tomorrow.

Thanks.

Gav...

> 
> -David

RE: [jira] Updated: (FOR-1122) Example site contentIntegration currently only works in forrest run mode

[Gav...]

> -Original Message-
> From: Tim Williams (JIRA) [mailto:j...@apache.org]
> Sent: Thursday, 19 August 2010 11:05 AM
> To: dev@forrest.apache.org
> Subject: [jira] Updated: (FOR-1122) Example site contentIntegration
> currently only works in forrest run mode
> 
> 
>  [ https://issues.apache.org/jira/browse/FOR-
> 1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> 
> Tim Williams updated FOR-1122:
> --
> 
> Fix Version/s: 0.10
>(was: 0.9-dev)
> 
> I think it just shouldn't be a part of the formal release, moving on
> for now.

Right.

So, I can move this to a branch - meaning I guess we copy the trunk and then 
remove
the contentIntegration site from trunk, or easier is to just move the content 
into
whiteboard.

Thoughts before I go ahead?

Gav...

> 
> > Example site contentIntegration currently only works in forrest run
> mode
> > -
> ---
> >
> > Key: FOR-1122
> > URL: https://issues.apache.org/jira/browse/FOR-1122
> > Project: Forrest
> >  Issue Type: Bug
> >  Components: Example Sites
> >Affects Versions: 0.9-dev
> >Reporter: Gavin
> > Fix For: 0.10
> >
> >
> > Due to some remote content being aggregated into the site, 'forrest
> site' will fail as it can not resolve the remote locations.
> 
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

Remaining Issues for release.

[Gav...]

Hi all,

http://s.apache.org/Xpc shows 17 remaining issues.

Going through them:

FOR-644, FOR-855, FOR-857, FOR-868, FOR-1149 - FOR-1152

above are issues leading to up doing a release. Of those I have checked
FOR-1149 through to FOR-1152 and believe they can be moved over to the next
release version.

FOR-889  Use by Ant of newer catalog entity resolver failing for Windows  =
push to 0.10 ?

FOR-922  update all docs that explain sitemap fragments  = not sure, ideally
should be done before release.

FOR-1069  add notices for US cryptographic export laws  = a continual issue
that shouldn't hold up a release.

FOR-1073  link elements with no href are created by html-to-document.xsl for
a/name  = needs checking again, ideally should be done before release, not
currently listed as a blocker.

FOR-1077  new CreationDate causes constant differences in output pdf
documents  = ideally should be done before release, not listed as a blocker.

FOR-1104  pdf output warnings "paragraph overflows the available area"  =
ideally should be done before release, not a blocker and could be moved to
0.10

FOR-1122  Example site contentIntegration currently only works in forrest
run mode  = I've mentioned this in another mail, suggesting we move this out
of core and into a branch so it can be worked on independant of this release
and only moved back into trunk after the release and after it is functional
again.

FOR-1184  using unreleased code for some supporting products  = I have no
problem with this being solved over time, sometimes we just can't help but
use unreleased code to make ours more stable. Push to 0.10 is my suggestion.

FOR-1187  upgraded PDF plugin was not deployed properly  = This plugin is
probably a bit special and hopefully the release can see this deployed at
the same time.

In summary then, I think we are nearly there! Like the docs say, let's be a
bit more brutal and get this release out there. I know we are not other
projects, but when I see other projects releasing every 3 months, or after a
dozen or so bugs fixed, or a new feature or two, I yearn for the days when
we can be a bit more like them.

Gav...

RE: svn commit: r979250 - /forrest/trunk/site-author/content/xdocs/live-sites.xml

[Gav...]

> -Original Message-
> From: gmcdon...@apache.org [mailto:gmcdon...@apache.org]
> Sent: Monday, 26 July 2010 9:52 PM
> To: s...@forrest.apache.org
> Subject: svn commit: r979250 - /forrest/trunk/site-
> author/content/xdocs/live-sites.xml
> 
> Author: gmcdonald
> Date: Mon Jul 26 11:51:49 2010
> New Revision: 979250
> 
> URL: http://svn.apache.org/viewvc?rev=979250&view=rev
> Log:
> Remove sites no longer using Apache Forrest, remove sites no longer in
> operation.
> 
> Modified:
> forrest/trunk/site-author/content/xdocs/live-sites.xml

Note I will publish this to the site in the morning.

Just thought it worth mentioning, of the 26 sites I've just removed that
no longer use Apache Forrest, more than half of them had switched to
either Wordpress or Drupal, with one of those being a Forrest Dev too!

I'm not sure how to interpret that, except that maybe we need to release
more and make things easier, if possible. Some perhaps worked out that
Forrest as a website tool wasn’t for them.

Gav...

FOR-1149 - regularly review our example sites - Push to 0.10

[Gav...]

Hi All,

I've tested our example sites at w3x html and css validators.

Our skins based sites pass both fine.

Or dispatcher site passes (x)html but fails css on parsing errors.

I've checked the skin based site at browsershots.org and looks fine in all
the popular browsers.
I did not test the dispatcher site at browsershots as I know there are many
problems with it.

So, as far as Issue FOR-1149 and its sub-tasks, I think we can push those
all out to 0.10 now
considering we are delaying anything dispatcher related to get this next
release out.

Just sending this email to confirm that is the right thing to do ?

Thanks

Gav...

RE: [jira] Commented: (FOR-1122) Example site contentIntegration currently only works in forrest run mode

[Gav...]

> -Original Message-
> From: Gavin (JIRA) [mailto:j...@apache.org]
> Sent: Monday, 26 July 2010 3:50 PM
> To: dev@forrest.apache.org
> Subject: [jira] Commented: (FOR-1122) Example site contentIntegration
> currently only works in forrest run mode
> 
> 
> [ https://issues.apache.org/jira/browse/FOR-
> 1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=12892185#action_12892185 ]
> 
> Gavin commented on FOR-1122:
> 
> 
> This refers to the site locared in trunk/examples/ContentIntegration.
> Just cd into that dir and do a 'forrest site' .
> 
> Note that Forrest Run also now has problems which I'll bring up on
> list.
> 

This examples/ContentIntegration site I think is too far broken to fix real 
soon; and depends
on the dispatcher for some of its usefulness.

I think it might be a good idea to move it out of our trunk and into a branch 
where
it can be worked on at leisure and re-inserted into trunk at a later date, thus 
not
holding up the next release.

Thoughts?

Gav...

RE: Propose moving main website to svnpubsub system.

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Wednesday, 21 July 2010 9:53 PM
> To: dev@forrest.apache.org
> Subject: Re: Propose moving main website to svnpubsub system.
> 
> On Mon, Jul 19, 2010 at 7:04 AM, Gav...  wrote:
> > Hi All,
> >
> > Over in infra land we have svnpubsub system for the immediate
> publishing of
> > website changes.
> >
> > The pubsub daemon watches our /www/forrest.apache.org area for
> commits and
> > as they come in,
> > does an immediate svn up on our web servers - making the changes live
> almost
> > immediate, rather
> > than having to wait an hour or two for the next sync to happen.
> >
> > This is currently being used by other projects such as httpd, apr,
> > trafficserver and a few others.
> >
> > After some early trial issues I'm confident that this system is now
> working
> > just fine and propose
> > that Apache Forrest move over to this system. We as a project need do
> > nothing (I will take care
> > of infra changes.)
> >
> > Our own publishing methods such as using Forrestbot would not need to
> change
> > (as all that does is
> > commit to our /site/ are of svn.)
> >
> > We currently commit to our svn /site/ area and a cronjob checks for
> updates
> > every 1/2 hour -- that
> > cronjob would no longer be necessary and the pubsub deamon would take
> over
> > listening for and performing
> > updates.
> >
> > Thoughts or concerns on doing this?
> 
> +1, Sounds like all good-ness to me:)
> 

Thanks, there is no rush to do this so I will wait for other opinions.

Gav...

> --tim

RE: Moving Forrest Zone to a FreeBSD Jail

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Wednesday, 21 July 2010 9:50 PM
> To: dev@forrest.apache.org
> Subject: Re: Moving Forrest Zone to a FreeBSD Jail
> 
> On Mon, Jul 19, 2010 at 6:46 AM, Gav...  wrote:
> > Hi All,
> >
> > Infra are working towards removing Helios our Zones machine. The
> Zones are
> > to be replaced with FreeBSD (8.1-RC2 currently) Jails.
> >
> > All projects zones are to be moved over the next few weeks. I have
> been
> > tasked mainly with this job, with help from others as
> > required.
> >
> > I have created new Jails but have yet to migrate an existing zone to
> a jail,
> > so I would like to start on familiar ground and
> > get the Forrest Zone moved - this week if possible. Anyone who has an
> acct
> > on our current zone setup will if they still require
> > it, get an acct on the new Jail.
> >
> > Does anyone foresee any issues in doing this? Is the timing ok?
> >
> > The only thing I can see is that FreeBSD (and now Debian/Ubuntu) uses
> the
> > Diablo Java rather than the sun jdk so if anyone knows
> > of any issues with that please let me know.
> >
> > I envisage a short crossover period where we will have both available
> > (forrest.zones.a.o and forrest2.zones.a.o) until we are happy all
> > is well at our new digs.
> >
> > If no objections I'll start soon (next couple of days)
> 
> +1, can you reset my password in the process too?

Thanks Tim, with no objections I'll start this tomorrow.
I'll add your ssh key and set you a temp sudo passwd.

Gav...

> 
> Thanks,
> --tim

Propose moving main website to svnpubsub system.

[Gav...]

Hi All,

Over in infra land we have svnpubsub system for the immediate publishing of
website changes.

The pubsub daemon watches our /www/forrest.apache.org area for commits and
as they come in, 
does an immediate svn up on our web servers - making the changes live almost
immediate, rather
than having to wait an hour or two for the next sync to happen.

This is currently being used by other projects such as httpd, apr,
trafficserver and a few others.

After some early trial issues I'm confident that this system is now working
just fine and propose
that Apache Forrest move over to this system. We as a project need do
nothing (I will take care
of infra changes.)

Our own publishing methods such as using Forrestbot would not need to change
(as all that does is
commit to our /site/ are of svn.)

We currently commit to our svn /site/ area and a cronjob checks for updates
every 1/2 hour -- that
cronjob would no longer be necessary and the pubsub deamon would take over
listening for and performing
updates.

Thoughts or concerns on doing this?

(For the time being our 'dist' area can remain as is, but that too can use
this system if we are happy 
with it)

Thanks

Gav...

Moving Forrest Zone to a FreeBSD Jail

[Gav...]

Hi All,

Infra are working towards removing Helios our Zones machine. The Zones are
to be replaced with FreeBSD (8.1-RC2 currently) Jails.

All projects zones are to be moved over the next few weeks. I have been
tasked mainly with this job, with help from others as
required.

I have created new Jails but have yet to migrate an existing zone to a jail,
so I would like to start on familiar ground and
get the Forrest Zone moved - this week if possible. Anyone who has an acct
on our current zone setup will if they still require
it, get an acct on the new Jail.

Does anyone foresee any issues in doing this? Is the timing ok?

The only thing I can see is that FreeBSD (and now Debian/Ubuntu) uses the
Diablo Java rather than the sun jdk so if anyone knows
of any issues with that please let me know.

I envisage a short crossover period where we will have both available
(forrest.zones.a.o and forrest2.zones.a.o) until we are happy all
is well at our new digs.

If no objections I'll start soon (next couple of days)

Thanks

Gav...

RE: release process for our plugins

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Saturday, 3 July 2010 7:18 PM
> To: dev@forrest.apache.org
> Subject: Re: release process for our plugins
> 
> David Crossley wrote:
> > David Crossley wrote:
> > > I have been doing some more review, and will attempt to
> > > present a proposal soon.
> >
> > Still :-)
> >
> > > --
> > > The following do not have an entry in the plugins
> > > descriptor file whiteboard-plugins.xml and have never
> > > been deployed to the website ...
> > > Database, OpenOffice.org-output, Blog, Lenya,
> > > DevTools, GoogleSitemap, rtf-output
> > >
> > > --
> > > The following do have an entry in the plugins
> > > descriptor file whiteboard-plugins.xml
> > > However they have never been deployed to the website
> > > which probably creates confusion ...
> > > Resume, XDoc, baetle, doac, ecs, foaf, skos, input.tei,
> > > NoteTaking, xhtml2, output.OOo, iCal, output.tei
> > >
> > > Some of those might not be relevant to deploy yet,
> > > but some are probably okay.
> >
> > I found a useful-looking attribute while browsing
> > the plugin build.xml files.
> >   
> >
> > If they are not ready enough to even have an
> > initial deployment then we can list them differently.
> > So people can still know about them and get interested.
> 
> I have finished the work with presenting plugins
> in the plugin lists.
> See http://forrest.apache.org/pluginDocs/
> 
> Also done a review and synchronisation of the configuration
> aspects of all plugins.
> See $FORREST_HOME/etc/review-plugin-deployment.txt

That looked like tricky work and the end result is excellent,
thanks for doing all that, great stuff!

Gav...

> 
> Still working on a proposal for getting many plugins
> out of the whiteboard and properly deployed.
> 
> Don't let that hold anyone up from working on the
> Forrest release. With our current release process,
> plugins have a separate release cycle to the core.
> 
> -David

RE: whiteboard fun

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Sunday, 6 June 2010 12:59 AM
> To: d...@forrest
> Subject: whiteboard fun
> 
> I'm playing with scala and using it to experiment with some new
> publishing ideas similar to what Ross did with forrest2.  It doesn't
> really do anything useful yet but it's enough code that I need to get
> it under version control.  Anyone mind my tossing it in the
> whiteboard?  The main concern being the 'distraction factor' - but I
> think it's immature enough where it won't be:)

It won't be distracting for me for a while at least, but will it be for you?

In my mind at least I was seeing you building up to be our next RM. :)

Gav...

> 
> Thanks,
> --tim

RE: release process for our plugins

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Monday, 7 June 2010 12:06 PM
> To: dev@forrest.apache.org
> Subject: Re: release process for our plugins
> 
> Gav... wrote:
> > David Crossley wrote:
> > > Gav... wrote:
> > > >
> > > > When code has been changed on a plugin since the last release,
> are we
> > > using
> > > > the
> > > > policy of 'lets upgrade the forrest version required as well as
> the
> > > plugin
> > > > version number' - that would make it easier all round. If that is
> ok,
> > > then I
> > > > can
> > > > just go round all plugins that have had any code changes since
> April
> > > 2007
> > > > and bump
> > > > their forrest version numbers to 0.9 ?
> > >
> > > No. We are not using that policy.
> > >
> > > The "forrestVersion" only gets incremented if there are
> > > changes that "require" the current version of Forrest.
> > >
> > > To do what you are suggesting would mean that users of the
> > > released versions of Forrest would not get any plugin updates.
> >
> > Ok, but the plugins when rebuilt will be done so with Java 1.5 , how
> > will that affect things?
> 
> Ah good point. We should have done a deploy of all
> plugins that had Java code (only some do) before
> doing that change.
> 
> To answer, i don't know what effect it will have.
> 
> > It's been so long since some were updated that I guess they would
> need
> > testing on 0.8 release before deciding if they are still compatible
> or
> > not.
> 
> This is part of our past problems. We don't deploy those
> plugins often enough and don't pay sufficent attention
> to their version numbers.
> 
> Hmmm, i don't know what to do.

Ok, what I was sort of suggesting before, was that we bump all
forrestversions of all
plugins to 0.9 (or 0.9-dev ?) and do ant deploy on them all. (not an ant
release which
can be done at our leisure later?). This will bring us up to date.

Doing the above, will that remove all plugins from being available to 0.8
users or not?
If not we're fine, if yes then perhaps we should do a final release of all
0.8 plugins
and do so from the versions of the plugins we have in the 0.8 tag we did at
release time.
Any changes after that will as above go into the 0.9 version.

I realise you said we should only bump the forrestversion only if 0.9
functionality is
introduced, but I'm suggesting this as a once off opportunity to catch up,
it would be
too time consuming to back and check every plugin at this stage, and being
so close
to a new 0.9 Forrest (core) release we really do need to catch up.
Afterwards, fine, 
we try and keep up and do it properly. This is pre 1.0 stable after all and
folks
should be encouraged to upgrade, we can not guarantee backwards
compatability and we
don't have any policy of back-porting.

Another thing to mention here, the 'dispatcher' plugin we so want out of the
whiteboard,
impossible if we don't bring it up to date -- in terms of documentation it
is shocking,
still mentions of  all over the place as well as *.fv
config files
which are superseded now after the dispatcher rewrite 6 months ago. I'd love
to start
updating the documentation for the dispatcher plugin but I'm stuck because
we need
to deploy it first -- your mention of deploy-docs, I could start using that,
but not
until it's at a 0.9 version I don't think.


> 
> > > > Obviously any 'plugin releases' between forrest versions can just
> > > have their
> > > > 'plugin
> > > > version' bumped - and for any of these we intend to start voting
> on?
> > > (After
> > > > this
> > > > next Forrest release if I'm interpreting correctly)
> > >
> > > Again only if it "requires" v0.9 functionality.
> >
> > huh, Im talking 'plugin version' such as 0.1, 0.2, 0.3 not the
> > 'forrest version'
> >
> > But I get it now I think, any total code changes that warrant a new
> > plugin version number, such as any release would. Minor code changes
> > whould stay at the same version number until there are sufficient to
> > warrant a bump in number (i.e release) - And, if any of those code
> > changes introduce 0.9 specific functionality, then we bump the
> 'forrest
> > version' also. Therefore it is assumed the 'forrest version' number
> is
> > the _minimum_ version we are saying it _will_ work on.
> >
> > &g

RE: release process for our plugins

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Monday, 7 June 2010 10:28 AM
> To: dev@forrest.apache.org
> Subject: Re: release process for our plugins
> 
> Gav... wrote:
> > David Crossley wrote:
> > >
> > > It should be easy to whip around each plugin and
> > > do a proper release of each.
> > >
> > > That also means that each plugin has a specific marked
> > > version, rather than just a continual work-in-progress.
> >
> > OK, when updating documentation for a plugin, all we need to is do
> > an 'ant deploy' on the plugin.
> 
> No. If only docs have changed then '... ant deploy-docs'.

ah ok great, I missed that option.

> 
> > When code has been changed on a plugin since the last release, are we
> using
> > the
> > policy of 'lets upgrade the forrest version required as well as the
> plugin
> > version number' - that would make it easier all round. If that is ok,
> then I
> > can
> > just go round all plugins that have had any code changes since April
> 2007
> > and bump
> > their forrest version numbers to 0.9 ?
> 
> No. We are not using that policy.
> 
> The "forrestVersion" only gets incremented if there are
> changes that "require" the current version of Forrest.
> 
> To do what you are suggesting would mean that users of the
> released versions of Forrest would not get any plugin updates.

Ok, but the plugins when rebuilt will be done so with Java 1.5 , how
will that affect things?

It's been so long since some were updated that I guess they would need
testing on 0.8 release before deciding if they are still compatible or
not.

> 
> > What happens to the older versions of the plugins ? The plugins
> system seems
> > a bit
> > broken currently, doesn't matter what forrest version you choose when
> > looking
> > at the plugins page, it shows the same plugin versions in all version
> tabs.
> 
> The system isn't broken. It is just that people maintaining
> the plugins have not handled them properly.
> 
> For example, the pdf plugin was updated and requires v0.9 but
> has not had its "forrestVersion" incremented. Nor was it
> deployed for 0.8 before making changes that require 0.9 version.
> See FOR-1187.
> 
> Similarly with the Dispatcher. It still says forrestVersion 0.8

Ok, but still, I'm confused as to why 0.8 version plugins, i.e. 
most of them, are appearing in the 0.7 and 0.9 versions of 
the plugins page. That's what I see as broken.
> 
> > Obviously any 'plugin releases' between forrest versions can just
> have their
> > 'plugin
> > version' bumped - and for any of these we intend to start voting on?
> (After
> > this
> > next Forrest release if I'm interpreting correctly)
> 
> Again only if it "requires" v0.9 functionality.

huh, Im talking 'plugin version' such as 0.1, 0.2, 0.3 not the 
'forrest version'

But I get it now I think, any total code changes that warrant a new
plugin version number, such as any release would. Minor code changes
whould stay at the same version number until there are sufficient to
warrant a bump in number (i.e release) - And, if any of those code
changes introduce 0.9 specific functionality, then we bump the 'forrest
version' also. Therefore it is assumed the 'forrest version' number is
the _minimum_ version we are saying it _will_ work on.

> 
> Please see the explanation at
> http://forrest.apache.org/docs/dev/howto/howto-buildPlugin.html

Oh, how I've read that a million times these last couple of days.

I have just updated the POD plugin - it had code changes from 2 years
ago, + doc changes and references dispatcher related documentation
examples that are or will be 0.9 specific, so I hope I was right in
bumping both the 'forrest version' and 'plugin version' in this case. (?)

Any more tweaks I make to those docs I'll just do a ant deploy-docs on them.

Gav...

> 
> -David

RE: release process for our plugins

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Friday, 4 June 2010 12:50 PM
> To: dev@forrest.apache.org
> Subject: Re: release process for our plugins
> 
> Gav... wrote:
> > David Crossley wrote:
> > >
> > > One very important reason for designing the plugin system
> > > the way that we did, was to ensure that each plugin has
> > > its own community supporting it.
> >
> > That doesn't seem to be the case to me at the moment, ...
> 
> That is one reason that i raised this issue again. We knew
> in the past that we had not properly followed a separate
> release cycle for each plugin.
> 
> > ... when core forrest devs
> > want to do a release, we need to ensure all plugins work, at least I
> see
> > that as the current situation.
> 
> That is different, and we would do that regardless of the
> plugins each being released separately.
> 
> It should be easy to whip around each plugin and
> do a proper release of each.
> 
> That also means that each plugin has a specific marked
> version, rather than just a continual work-in-progress.

OK, when updating documentation for a plugin, all we need to is do
an 'ant deploy' on the plugin.

When code has been changed on a plugin since the last release, are we using
the
policy of 'lets upgrade the forrest version required as well as the plugin
version number' - that would make it easier all round. If that is ok, then I
can
just go round all plugins that have had any code changes since April 2007
and bump
their forrest version numbers to 0.9 ?

What happens to the older versions of the plugins ? The plugins system seems
a bit
broken currently, doesn't matter what forrest version you choose when
looking 
at the plugins page, it shows the same plugin versions in all version tabs.

Obviously any 'plugin releases' between forrest versions can just have their
'plugin
version' bumped - and for any of these we intend to start voting on? (After
this
next Forrest release if I'm interpreting correctly)

Thanks

Gav...
> 
> -David

RE: stop re-generating PDF documents on Forrest website

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Sunday, 6 June 2010 4:42 PM
> To: dev@forrest.apache.org
> Subject: stop re-generating PDF documents on Forrest website
> 
> We have a PDF document copy of every page of our website.
> 
> I propose that we stop doing that. There are various reasons.
> 
> It makes it difficult to search, because one keeps hitting
> the PDF documents as well as the html pages.
> 
> Due to issue https://issues.apache.org/jira/browse/FOR-1077
> every PDF document is changed each time someone re-generates
> some other part of the website. This creates a lot of noise
> with the commit diffs making it difficult to oversee real changes.
> 
> We aleady demonstrate this ability with the PDF Plugin's own
> website and also with our example site on our zone server.
> Also the "sample" document on the main website has a
> demo http://forrest.apache.org/dtdx/document-v20.html#presentations
> 
> So i plan to go ahead and remove that soon, unless people
> speak up with concerns.

++1 to that, like you say, we don't actually need them for our docs, the
same way we don't need POD or Text or other plugins, as long as they are
documented and we have running examples elsewhere, it's all good.

Gav...

> 
> -David

RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml

[Gav...]

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Sunday, 6 June 2010 9:36 AM
> To: dev@forrest.apache.org
> Subject: RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> 
> 
> 
> > -Original Message-
> > From: Tim Williams [mailto:william...@gmail.com]
> > Sent: Sunday, 6 June 2010 9:00 AM
> > To: dev@forrest.apache.org
> > Subject: Re: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> >
> > On Sat, Jun 5, 2010 at 6:42 PM, Gav... 
> wrote:
> 
> 
> 
> 
> > >
> > > So, going back to the original form and altering it slightly:
> > >
> > >  > property="java_exists"/>
> > >
> > > seems to work fine, though I haven't seen wildcards in any
> examples,
> > I'm
> > > assuming this will work and set the property accordingly.
> >
> > Thanks Gav, you gonna commit this one or you want me to do it?
> >
> > --tim
> 
> Well, I've done it now.
> 
> However it won't have the desired effect David was after.
> 
> It will set the property "java_exists" to either true or false, that
> parts
> works, however just by setting the property at all is enough for later
> targets to use if="java_exists" to always be true (i.e. the property
> does
> exist, doesn't matter if it's true or not.
> 
> Ant 1.8 cures this by checking whether true or false.
> There is a workaround I've done before elsewhere, which means setting a
> variable
> in an extra target and having the other targets depend on the variable.
> 
> I won't apply that though, but try and find where I've done that before
> and
> post
> it here for review first. David may have been on the right path also as
> that
> at
> least will not set the property at all. Will look closer.
> 

Ok, I found where I've done it before.

See: https://issues.apache.org/jira/browse/FOR-1055

It is the same circumstances, see commit r774176 in
/forrest/trunk/main/forrest.build.xml
That will certainly do what we want, something like:


...

  

  


...

...

...

Will work, but I won't apply, other comments and other avenues to fix
welcome.

Gav...

RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Sunday, 6 June 2010 9:00 AM
> To: dev@forrest.apache.org
> Subject: Re: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> 
> On Sat, Jun 5, 2010 at 6:42 PM, Gav...  wrote:




> >
> > So, going back to the original form and altering it slightly:
> >
> >  property="java_exists"/>
> >
> > seems to work fine, though I haven't seen wildcards in any examples,
> I'm
> > assuming this will work and set the property accordingly.
> 
> Thanks Gav, you gonna commit this one or you want me to do it?
> 
> --tim

Well, I've done it now.

However it won't have the desired effect David was after.

It will set the property "java_exists" to either true or false, that parts
works, however just by setting the property at all is enough for later
targets to use if="java_exists" to always be true (i.e. the property does
exist, doesn't matter if it's true or not.

Ant 1.8 cures this by checking whether true or false.
There is a workaround I've done before elsewhere, which means setting a
variable
in an extra target and having the other targets depend on the variable.

I won't apply that though, but try and find where I've done that before and
post
it here for review first. David may have been on the right path also as that
at
least will not set the property at all. Will look closer.

Gav...

RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml

[Gav...]

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Sunday, 6 June 2010 8:29 AM
> To: dev@forrest.apache.org
> Subject: RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> 
> 
> 
> > -Original Message-
> > From: Gav... [mailto:ga...@16degrees.com.au]
> > Sent: Sunday, 6 June 2010 8:17 AM
> > To: dev@forrest.apache.org
> > Subject: RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> >
> >
> >
> > > -Original Message-
> > > From: Tim Williams [mailto:william...@gmail.com]
> > > Sent: Sunday, 6 June 2010 7:05 AM
> > > To: Forrest Developers List
> > > Subject: Re: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> > >
> > > On Sat, Jun 5, 2010 at 9:56 AM,   wrote:
> > > > Author: crossley
> > > > Date: Sat Jun  5 13:56:23 2010
> > > > New Revision: 951719
> > > >
> > > > URL: http://svn.apache.org/viewvc?rev=951719&view=rev
> > > > Log:
> > > > Better detection of "java_exists".
> > > > Issue: FOR-1137
> > > >
> > > > Modified:
> > > >    forrest/trunk/plugins/build.xml
> > > >
> > > > Modified: forrest/trunk/plugins/build.xml
> > > > URL:
> > >
> >
> http://svn.apache.org/viewvc/forrest/trunk/plugins/build.xml?rev=951719
> > > &r1=951718&r2=951719&view=diff
> > > >
> > >
> >
> ===
> > > ===
> > > > --- forrest/trunk/plugins/build.xml (original)
> > > > +++ forrest/trunk/plugins/build.xml Sat Jun  5 13:56:23 2010
> > > > @@ -87,7 +87,8 @@
> > > >       
> > > >       
> > > >     
> > > > -     > > type="dir"/>
> > > > +     > > includes="**/*.java"/>
> > > > +     > > setonempty="false"/>
> > > >   
> > > >    > > unless="no.echo.init">
> > > >     
> > >
> > > I'm pretty sure this is causing our ails at the moment.  I don't
> have
> > > time to figure out what it's all about and update it properly,
> should
> > > we revert for now?
> >
> > From what I can tell it should be something like:
> >
> > 
> >   
> > 
> >
> > (the includes= seems to include a dir rather than a set of files)
> >
> > I'll test it shortly.
> 
> I was wrong there, either should be acceptable and makes no difference
> to
> the output.

So, going back to the original form and altering it slightly:



seems to work fine, though I haven’t seen wildcards in any examples, I'm
assuming this will work and set the property accordingly.

Gav...

> 
> 
> >
> > Gav...
> >
> >
> >
> >
> > >
> > > --tim
> >
> 
> 

RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml

[Gav...]

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Sunday, 6 June 2010 8:17 AM
> To: dev@forrest.apache.org
> Subject: RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> 
> 
> 
> > -Original Message-
> > From: Tim Williams [mailto:william...@gmail.com]
> > Sent: Sunday, 6 June 2010 7:05 AM
> > To: Forrest Developers List
> > Subject: Re: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> >
> > On Sat, Jun 5, 2010 at 9:56 AM,   wrote:
> > > Author: crossley
> > > Date: Sat Jun  5 13:56:23 2010
> > > New Revision: 951719
> > >
> > > URL: http://svn.apache.org/viewvc?rev=951719&view=rev
> > > Log:
> > > Better detection of "java_exists".
> > > Issue: FOR-1137
> > >
> > > Modified:
> > >    forrest/trunk/plugins/build.xml
> > >
> > > Modified: forrest/trunk/plugins/build.xml
> > > URL:
> >
> http://svn.apache.org/viewvc/forrest/trunk/plugins/build.xml?rev=951719
> > &r1=951718&r2=951719&view=diff
> > >
> >
> ===
> > ===
> > > --- forrest/trunk/plugins/build.xml (original)
> > > +++ forrest/trunk/plugins/build.xml Sat Jun  5 13:56:23 2010
> > > @@ -87,7 +87,8 @@
> > >       
> > >       
> > >     
> > > -     > type="dir"/>
> > > +     > includes="**/*.java"/>
> > > +     > setonempty="false"/>
> > >   
> > >    > unless="no.echo.init">
> > >     
> >
> > I'm pretty sure this is causing our ails at the moment.  I don't have
> > time to figure out what it's all about and update it properly, should
> > we revert for now?
> 
> From what I can tell it should be something like:
> 
> 
>   
> 
> 
> (the includes= seems to include a dir rather than a set of files)
> 
> I'll test it shortly.

I was wrong there, either should be acceptable and makes no difference to
the output.


> 
> Gav...
> 
> 
> 
> 
> >
> > --tim
> 

RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Sunday, 6 June 2010 7:05 AM
> To: Forrest Developers List
> Subject: Re: svn commit: r951719 - /forrest/trunk/plugins/build.xml
> 
> On Sat, Jun 5, 2010 at 9:56 AM,   wrote:
> > Author: crossley
> > Date: Sat Jun  5 13:56:23 2010
> > New Revision: 951719
> >
> > URL: http://svn.apache.org/viewvc?rev=951719&view=rev
> > Log:
> > Better detection of "java_exists".
> > Issue: FOR-1137
> >
> > Modified:
> >    forrest/trunk/plugins/build.xml
> >
> > Modified: forrest/trunk/plugins/build.xml
> > URL:
> http://svn.apache.org/viewvc/forrest/trunk/plugins/build.xml?rev=951719
> &r1=951718&r2=951719&view=diff
> >
> ===
> ===
> > --- forrest/trunk/plugins/build.xml (original)
> > +++ forrest/trunk/plugins/build.xml Sat Jun  5 13:56:23 2010
> > @@ -87,7 +87,8 @@
> >       
> >       
> >     
> > -     type="dir"/>
> > +     includes="**/*.java"/>
> > +     setonempty="false"/>
> >   
> >    unless="no.echo.init">
> >     
> 
> I'm pretty sure this is causing our ails at the moment.  I don't have
> time to figure out what it's all about and update it properly, should
> we revert for now?

>From what I can tell it should be something like:


  


(the includes= seems to include a dir rather than a set of files)

I'll test it shortly.

Gav...




> 
> --tim

Fixing Locale on the zone (was: RE: Latin1 character problems in dispatcher)

[Gav...]

> Subject: Re: Latin1 character problems in dispatcher
> 
> 
> Den 20. mai. 2010 kl. 14.51 skrev Thorsten Scherler:
> 
> > further can you open a terminal and tell me what the output of
> "locale" are?
> 
> $ locale
> LANG="no_NO.UTF-8"
> LC_COLLATE="no_NO.UTF-8"
> LC_CTYPE="no_NO.UTF-8"
> LC_MESSAGES="no_NO.UTF-8"
> LC_MONETARY="no_NO.UTF-8"
> LC_NUMERIC="no_NO.UTF-8"
> LC_TIME="no_NO.UTF-8"
> LC_ALL="no_NO.UTF-8"
> 

Thanks to Sjur and Thorsten this got me to check the locale on the zone; the 
LANG= setting was empty so not set.

We can't set the locale for the Zone because that setting is shared with other 
zones (which will be cured when our
zone moves to jails.) , however, we can set it a user level.

I tested this by running manually:

$ export LANG=en_US.UTF-8
$ /export/home/config/run-forrestbot.sh forrest-sample-2.xml notify trunk

I then checked the zone at

http://forrest.zones.apache.org/ft/build/forrest-sample-2/index.html

and yay, sure enough the ?? had all vanished to be replaced with proper 
copyright and TM symbols etc.

This will disappear on the next forrestbot run however.

Because the forrestbot scripts are run under user crossley, David, could you 
please add

export LANG=en_US.UTF-8

to your .bash_profile, I believe that will then solve this permanently.


Thanks

Gav...

RE: release process for our plugins

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Friday, 4 June 2010 11:00 AM
> To: dev@forrest.apache.org
> Subject: Re: release process for our plugins
> 
> One very important reason for designing the plugin system
> the way that we did, was to ensure that each plugin has
> its own community supporting it.
> 
> -David

That doesn't seem to be the case to me at the moment, when core forrest devs
want to do a release, we need to ensure all plugins work, at least I see
that as the current situation.

Gav...

RE: release process for our plugins

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Friday, 28 May 2010 12:20 AM
> To: dev@forrest.apache.org
> Subject: Re: release process for our plugins
> 
> On Thu, May 27, 2010 at 5:16 AM, David Crossley 
> wrote:
> > We do have a process sorted out for releasing of Forrest core.
> > [1] How to release Forrest
> > http://forrest.apache.org/procedures/release/How_to_release.html
> >
> > I reckon that it meets the ASF requirements. Please see
> > this email where i have before tried to ensure that we do:
> > [2] http://markmail.org/message/kwecoaue7p4qcy2v
> > To: forrest-dev
> > Re: Clarification on the release requirements
> >
> > Unfortunately the links are broken in that display,
> > so i tracked them down again.
> >
> > Here are a couple of places where Roy set out some
> > principles/policy/reasons-for-doing-stuff ...
> > [3] http://markmail.org/message/3odlybipss4wnczl
> > [4] http://markmail.org/message/njray5dbazwcdcts
> >
> > I reckon that it would be worth our while to review
> > that discussion.
> >
> > There is other background material at
> > [5] http://www.apache.org/dev/#releases
> > [6] http://www.apache.org/dev/release.html
> >
> > With those principles in mind, we need to attend to our
> > release process for our plugins.
> >
> > We don't actually yet have a process.
> >
> > Do "find in page" for "plugin" at [1] to see the steps.
> > You will reach a point where our doc says fixme
> > and refers to a draft document at
> > [7] $FORREST_HOME/plugins/RELEASE_PROCESS.txt
> > There are some other notes at
> > [8] http://forrest.apache.org/docs/dev/howto/howto-buildPlugin.html
> >
> > We do have tools for doing "deploy" of plugins, i.e.
> > putting an updated version on the server.
> >
> > As described in [6] Releases FAQ,
> > "
> > What Is A Release?
> > Releases are, by definition, anything that is published beyond the
> group that owns it. In our case, that means any publication outside the
> group of people on the product dev list. If the general public is being
> instructed to download a package, then that package has been released.
> Each PMC must obey the ASF requirements on approving any release. How
> you label the package is a secondary issue, described below.
> > "
> >
> > It should be easy. For each plugin, the proposer puts a package
> > at their apache.org space. We each download, install, review,
> > and then vote. Then use the "release" Ant target rather than
> > the "deploy" target.
> >
> > However, we have another issue.
> >
> > We have been providing that software via our website.
> > If i understand correctly then we should be doing
> > that from w.a.o/dist/forrest/
> >
> > See some discussion at
> > https://issues.apache.org/jira/browse/FOR-1068
> >
> > Perhaps we should at least solve the "release process" issue now,
> > and leave the deployment issue until post 0.9 release.
> 
> The "release process" issue?  relative to plugins I assume?  The draft
> release doc in the plugins directory suggests that its possible to
> release plugins independent of the core but couldn't we, for now, just
> as well continue to do what we do and release the plugins with the
> core?  In other words, it seems to me we're meeting Roy's intent
> fairly well by releasing the whole bundle together - formal process,
> signed, etc.
> 
> I guess, what I'm wondering is... can we punt on plugin releases, move
> dispatcher to /plugins and just vote on the whole bundle as normal?
> Or, do you see something that needs addressing now, before a 0.9
> release?  Sorry, you were probably hoping for answers not questions:)

To me, a plugin means an add-on, in addition to, extra. However some of our
'plugins' are in fact required if Forrest is to be useful. Anyway,

The plugins (not whiteboard plugins) I think as you say, we could bundle
this
time around, it also shows that the plugin versions we bundle are guaranteed
to work with that Forrest release.

If this was somewhere else, where folks create plugins and work on them
alone
and maintain them alone independent of Forrest, then it would be easier, but
we
don't and it seems every plugin we have has to be maintained by forrest devs
in addition to the core in order to get a release out. That seems wrong to
me,
it gets harder each time as we accumulate more plugins. So that means I 
guess I'd rather plugins be done separately of a core Forrest release in the
future - if a plugin doesn't keep up, so be it I guess until someone wants
to take on maintaining it.

For this time, to get a release done quickly, I'm ok with doing what we have
always
done, as long as meets with guidelines.

Gav...

> 
> --tim

RE: Add RAT report to master summary

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Monday, 31 May 2010 3:11 PM
> To: dev@forrest.apache.org
> Subject: Re: Add RAT report to master summary
> 
> Gav... wrote:
> >
> > I'd like to add our RAT report
> > (http://ci.apache.org/projects/forrest/rat-output.txt)
> >  to the http://ci.apache.org/projects/rat-master-summary.html page.
> >
> > To do that, I need to produce an .xml output, not the .txt version
> currently
> > produced.
> >
> > Any problems with me doing that or can I go ahead?
> 
> "Go ahead" and just tell us what you have done is the most
> efficient way.

It is, and inline with other projects, the txt reports will disappear soon.

We are now listed at [1] and [2] with nice zero (0) against our name.

Gav...

[1] - http://ci.apache.org/projects/rat-master-summary.html

[2] - http://ci.apache.org/projects/forrest/rat-output.html


> 
> If anyone disputes, then they can raise a "-1".
> 
> -David
> 
> > It means our singular report will be available from
> >
> > http://ci.apache.org/projects/forrest/rat-output.html
> >
> > instead.
> >
> > Thanks
> >
> > Gav...
> >
> >

RE: trouble publishing project docs

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Friday, 28 May 2010 5:24 PM
> To: dev@forrest.apache.org
> Subject: Re: trouble publishing project docs
> 
> Tim Williams wrote:
> > David Crossley wrote:
> > > Tim Williams wrote:
> > >>
> > >> Just a guess, if you use keychain, is it out of sync with a
> recently
> > >> updated password change?
> > >
> > > Thanks for trying. No, it is not that. The "ASF Committers"
> > > password is there, and i can commit okay.
> > >
> > > However, it is just my local forrestbot that is not working.
> > >
> > > That is why i wonder if Ant or Jsvn might cache it.
> > >
> > > I also tried removing my deploy.svn.settings file,
> > > thinking that i would then get prompted for the password.
> > > But it didn't. And still gave the same credentials error.
> >
> > maybe:
> > rm -Rf ~/.ssh/auth
> 
> I suppose that you mean ~/.subversion/auth
> 
> Yeah already tried that in desperation. Tried again now
> but same issue.

So now you have removed the auth/svn.ssh directory, can you still
commit normally to trunk, using the same password you are using in
the deploy.svn.settings file -- if you have removed auth then you
will be prompted for a password from the command line.

Gav...

> 
> -David
> 
> > Though, it'd be strange that the command line would use keychain yet
> > the ant task would use these credentials.  I'm wildly guessing at
> this
> > stage in case you haven't noticed:)
> >
> > --tim
> >
> > http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.1

Add RAT report to master summary

[Gav...]

Hi,

I'd like to add our RAT report
(http://ci.apache.org/projects/forrest/rat-output.txt)
 to the http://ci.apache.org/projects/rat-master-summary.html page.

To do that, I need to produce an .xml output, not the .txt version currently
produced.

Any problems with me doing that or can I go ahead?

It means our singular report will be available from

http://ci.apache.org/projects/forrest/rat-output.html

instead.

Thanks

Gav...

RE: JIRA problems (Was: ForrestBot build for forrest-docs FAILED)

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Thursday, 15 April 2010 10:03 AM
> To: dev@forrest.apache.org
> Subject: Re: JIRA problems (Was: ForrestBot build for forrest-docs
> FAILED)
> 
> On Wed, Apr 14, 2010 at 1:36 PM, Andreas Lehmkuehler 
> wrote:
> > Hi,
> >
> > Gav... schrieb:
> >>
> >>> -Original Message-
> >>> From: David Crossley [mailto:cross...@apache.org]
> >>> Sent: Wednesday, 14 April 2010 7:43 PM
> >>> To: dev@forrest.apache.org
> >>> Subject: Re: JIRA problems (Was: ForrestBot build for forrest-docs
> >>> FAILED)
> >>>
> >>> On Mon, Apr 12, 2010 David Crossley wrote:
> >>>>
> >>>> ...
> >>>>>
> >>>>>     [java] X [0]                                     forrest-
> >>>
> >>> issues.html     BROKEN: /export/home/config/forrestbot-
> >>> trunk/conf/work/forrest-docs/. (Is a directory)
> >>>>
> >>>> ...
> >>>>
> >>>> Now that Jira is back online, we seem to be getting this problem
> >>>> on every run, rather than just sporadically.
> >>>>
> >>>> This is where forrest processes a report out of the JIRA
> >>>> issue tracker. I gather that the weird failure message is
> >>>> because Forrest suddenly has no content to process because
> >>>> the JIRA query failed to return results.
> >>>>
> >>>> Someone will need to investigate and follow up with ASF Infra.
> >>
> >> the forrest-issues.html is produced from the forrest.properties
> property:
> >>
> >>
> >> project.issues-rss-
> url=http://issues.apache.org/jira/secure/IssueNavigator.j
> >>
> >> spa?view=rss&pid=1231&fixfor=12310041&resolutionIds=-
> 1&sorter/field=prio
> >> rity&sorter/order=DESC&tempMax=25&reset=true&decorator=none
> >
> > Did you try to use https instead of http? We have a similar issue
> with some
> > attachements, which will be downloaded from JIRA from the PDFBox ant
> > build.xml.
> > After changing the protocol everything works fine.
> 
> Same here, I changed to https instead and all is well locally, I
> reckon we'll see if it helps the zone build too in a bit.  Thanks
> Andreas!
> 
> It'd be kinda cool to now know why though? :)

I think due to recent events most if not all of Jira redirects http to https
anyway.

Perhaps this link requires it, though my manual test of http: did redirect
to https: fine
on its own.

Gav...

> 
> --tim

RE: JIRA problems (Was: ForrestBot build for forrest-docs FAILED)

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Wednesday, 14 April 2010 7:43 PM
> To: dev@forrest.apache.org
> Subject: Re: JIRA problems (Was: ForrestBot build for forrest-docs
> FAILED)
> 
> On Mon, Apr 12, 2010 David Crossley wrote:
> > ...
> > >  [java] X [0] forrest-
> issues.html   BROKEN: /export/home/config/forrestbot-
> trunk/conf/work/forrest-docs/. (Is a directory)
> > ...
> >
> > Now that Jira is back online, we seem to be getting this problem
> > on every run, rather than just sporadically.
> >
> > This is where forrest processes a report out of the JIRA
> > issue tracker. I gather that the weird failure message is
> > because Forrest suddenly has no content to process because
> > the JIRA query failed to return results.
> >
> > Someone will need to investigate and follow up with ASF Infra.

the forrest-issues.html is produced from the forrest.properties property:

project.issues-rss-url=http://issues.apache.org/jira/secure/IssueNavigator.j
spa?view=rss&pid=1231&fixfor=12310041&resolutionIds=-1&sorter/field=prio
rity&sorter/order=DESC&tempMax=25&reset=true&decorator=none


I ran that url through manually and it picks up the feed content fine.
I also checked that the zone can reach that url and it can.

> 
> I did a quick server-side change to stop the barrage.
> Commented-out "forrest-docs" from my crontab.
> 
> People could debug this locally with the "site-author".
> 
> Need to find the request, perhaps in a locationmap.
> Try it manually, see what happens.

aha, see above, works fine manually.

> 
> Sorry, no time to help.

No problem, I'll look into it further tomorrow.

Gav...

> 
> -David

RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Monday, 5 April 2010 9:14 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
> 
> On Mon, Apr 5, 2010 at 7:04 AM, Tim Williams 
> wrote:
> > On Mon, Apr 5, 2010 at 6:43 AM, Gav... 
> wrote:
> >>
> >>
> >>> -Original Message-
> >>> From: Tim Williams [mailto:william...@gmail.com]
> >>> Sent: Monday, 5 April 2010 7:51 PM
> >>> To: dev@forrest.apache.org
> >>> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> not
> >>> resolve locationmap location
> >>>
> >>> On Mon, Apr 5, 2010 at 5:22 AM, Gav... 
> wrote:
> >>> >
> >>> >
> >>> >> -Original Message-
> >>> >> From: Tim Williams [mailto:william...@gmail.com]
> >>> >> Sent: Friday, 2 April 2010 11:13 PM
> >>> >> To: dev@forrest.apache.org
> >>> >> Subject: Re: forrest-sample-2 FAILED and build test failed:
> Could
> >>> not
> >>> >> resolve locationmap location
> >>> >>
> >>> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams
> 
> >>> >> wrote:
> >>> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
> >>> 
> >>> >> wrote:
> >>> >> >>> Automated build for forrest-sample-2 FAILED
> >>> >> >>>      [java]
> >>> >> >>>      [java]
> >>> >> >>>      [java] X [0]
> >>> linkmap.html
> >>> >>    BROKEN: Could not resolve locationmap location.
> >>> >> >>
> >>> >> >>
> >>> >> >> I get that same error doing 'build.sh test' locally.
> >>> >> >>
> >>> >> >> The build of this Dispatcher sample were okay on the
> >>> >> >> zone server before today.
> >>> >> >
> >>> >> > I'm getting the same thing.  It looks like a mounted
> locationmap
> >>> >> can't
> >>> >> > be resolved but it appears to be dispatcher-related code.  I
> don't
> >>> >> > know that code at all but a quick look seems like the resolver
> >>> field
> >>> >> > in the child class (RecursiveDirectoryTraversalAction) is
> hiding
> >>> the
> >>> >> > intended resolver in the parent class (AbstractTraversal).
> Can
> >>> you
> >>> >> > comment out the child class' resolver field and see if that
> helps?
> >>> >>  It
> >>> >> > seems to get me past that one but then introduces tons of
> other
> >>> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors.  The timing
> >>> seems
> >>> >> > right too,  it would have been introduced with r929463.
> >>> >>
> >>> >> I went ahead and applied that because I feel sure that's the
> right
> >>> >> thing to do.  I'm now getting errors like:
> >>> >>
> >>> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> >>> >> X [0]                                     linkmap.pdf BROKEN:
> >>> Invalid
> >>> >> byte 1 of 1-byte UTF-8 sequence.
> >>> >>
> >>> >> ... for every pdf file.  I don't have time to look into that one
> >>> right
> >>> >> now though, can someone see if they get the same?
> >>> >
> >>> > Yes, I am getting it too, but here we are again, a Windows only
> bug
> >>> it
> >>> > seems. I don’t get this on any linux box - which is why our zone
> >>> doesn’t
> >>> > complain.
> >>>
> >>> Actually, I'm on a Mac.
> >>
> >> fine, cant help then.
> >
> > Thanks Gav,
> > You may have, I think the default encoding on a Mac isn't utf-8
> > either.  I wonder if our source docs which claim utf-8 encoding,
> > aren't?  When I get home I'll try to open them in a text editor and
> > explicitly save one of the known failing docs with utf-8 encoding and
> > see if that helps.  Unless, of course, someone happens to have time
> to
> > do this test sooner:)
> 
> Firefox does think that my random sampling of content from our svn are
> ISO-8859-1 encoded and not UTF-8 (which the xml declaration claims) -
> this may be the problem?

That could also be the case,

W3 Schools , http://www.w3.org/International/O-charset and a couple of other
places also mention the high importance of and I'll quote "•Save your data
in the appropriate encoding from your editing environment." - so that may be
something to look into also, thought I'd mention that whilst I came across
it.

Gav...

> 
> --tim

RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Monday, 5 April 2010 9:05 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
> 
> On Mon, Apr 5, 2010 at 6:43 AM, Gav...  wrote:
> >
> >
> >> -Original Message-
> >> From: Tim Williams [mailto:william...@gmail.com]
> >> Sent: Monday, 5 April 2010 7:51 PM
> >> To: dev@forrest.apache.org
> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> not
> >> resolve locationmap location
> >>
> >> On Mon, Apr 5, 2010 at 5:22 AM, Gav... 
> wrote:
> >> >
> >> >
> >> >> -Original Message-
> >> >> From: Tim Williams [mailto:william...@gmail.com]
> >> >> Sent: Friday, 2 April 2010 11:13 PM
> >> >> To: dev@forrest.apache.org
> >> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> >> not
> >> >> resolve locationmap location
> >> >>
> >> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams
> 
> >> >> wrote:
> >> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
> >> 
> >> >> wrote:
> >> >> >>> Automated build for forrest-sample-2 FAILED
> >> >> >>>      [java]
> >> >> >>>      [java]
> >> >> >>>      [java] X [0]
> >> linkmap.html
> >> >>    BROKEN: Could not resolve locationmap location.
> >> >> >>
> >> >> >>
> >> >> >> I get that same error doing 'build.sh test' locally.
> >> >> >>
> >> >> >> The build of this Dispatcher sample were okay on the
> >> >> >> zone server before today.
> >> >> >
> >> >> > I'm getting the same thing.  It looks like a mounted
> locationmap
> >> >> can't
> >> >> > be resolved but it appears to be dispatcher-related code.  I
> don't
> >> >> > know that code at all but a quick look seems like the resolver
> >> field
> >> >> > in the child class (RecursiveDirectoryTraversalAction) is
> hiding
> >> the
> >> >> > intended resolver in the parent class (AbstractTraversal).
> Can
> >> you
> >> >> > comment out the child class' resolver field and see if that
> helps?
> >> >>  It
> >> >> > seems to get me past that one but then introduces tons of other
> >> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors.  The timing
> >> seems
> >> >> > right too,  it would have been introduced with r929463.
> >> >>
> >> >> I went ahead and applied that because I feel sure that's the
> right
> >> >> thing to do.  I'm now getting errors like:
> >> >>
> >> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> >> >> X [0]                                     linkmap.pdf BROKEN:
> >> Invalid
> >> >> byte 1 of 1-byte UTF-8 sequence.
> >> >>
> >> >> ... for every pdf file.  I don't have time to look into that one
> >> right
> >> >> now though, can someone see if they get the same?
> >> >
> >> > Yes, I am getting it too, but here we are again, a Windows only
> bug
> >> it
> >> > seems. I don’t get this on any linux box - which is why our zone
> >> doesn’t
> >> > complain.
> >>
> >> Actually, I'm on a Mac.
> >
> > fine, cant help then.
> 
> Thanks Gav,
> You may have, I think the default encoding on a Mac isn't utf-8
> either. 

Ah ok, that's interesting.

> I wonder if our source docs which claim utf-8 encoding,
> aren't?  When I get home I'll try to open them in a text editor and
> explicitly save one of the known failing docs with utf-8 encoding and
> see if that helps.  Unless, of course, someone happens to have time to
> do this test sooner:)

Well the impression I got from the thread I linked to, is that that source
input docs may actually be fine, but the way we are writing out to the
intermediates I guess to create the PDFs are claiming default encoding from
the operating system whether UTF-8 is specified or not. The difference in
the way Dispatcher handles our xml docs to PDF is obviously different to how
a non dispatcher enabled site does it, despite the same original source.

 It may be simpler than I've read, not being any kind of expert in java or
character encodings I'm not sure how much more of a goose chase (Australians
read: furfy) I should take this on.

I'll browse around some more in the meantime.

Gav...

> 
> --tim

RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Monday, 5 April 2010 7:51 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
> 
> On Mon, Apr 5, 2010 at 5:22 AM, Gav...  wrote:
> >
> >
> >> -Original Message-
> >> From: Tim Williams [mailto:william...@gmail.com]
> >> Sent: Friday, 2 April 2010 11:13 PM
> >> To: dev@forrest.apache.org
> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
> not
> >> resolve locationmap location
> >>
> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams 
> >> wrote:
> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
> 
> >> wrote:
> >> >>> Automated build for forrest-sample-2 FAILED
> >> >>>      [java]
> >> >>>      [java]
> >> >>>      [java] X [0]
> linkmap.html
> >>    BROKEN: Could not resolve locationmap location.
> >> >>
> >> >>
> >> >> I get that same error doing 'build.sh test' locally.
> >> >>
> >> >> The build of this Dispatcher sample were okay on the
> >> >> zone server before today.
> >> >
> >> > I'm getting the same thing.  It looks like a mounted locationmap
> >> can't
> >> > be resolved but it appears to be dispatcher-related code.  I don't
> >> > know that code at all but a quick look seems like the resolver
> field
> >> > in the child class (RecursiveDirectoryTraversalAction) is hiding
> the
> >> > intended resolver in the parent class (AbstractTraversal).   Can
> you
> >> > comment out the child class' resolver field and see if that helps?
> >>  It
> >> > seems to get me past that one but then introduces tons of other
> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors.  The timing
> seems
> >> > right too,  it would have been introduced with r929463.
> >>
> >> I went ahead and applied that because I feel sure that's the right
> >> thing to do.  I'm now getting errors like:
> >>
> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> >> X [0]                                     linkmap.pdf BROKEN:
> Invalid
> >> byte 1 of 1-byte UTF-8 sequence.
> >>
> >> ... for every pdf file.  I don't have time to look into that one
> right
> >> now though, can someone see if they get the same?
> >
> > Yes, I am getting it too, but here we are again, a Windows only bug
> it
> > seems. I don’t get this on any linux box - which is why our zone
> doesn’t
> > complain.
> 
> Actually, I'm on a Mac.

fine, cant help then.

Gav...

> 
> --tim

RE: forrest-sample-2 FAILED and build test failed: Could not resolve locationmap location

[Gav...]

> -Original Message-
> From: Tim Williams [mailto:william...@gmail.com]
> Sent: Friday, 2 April 2010 11:13 PM
> To: dev@forrest.apache.org
> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
> resolve locationmap location
> 
> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams 
> wrote:
> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley 
> wrote:
> >>> Automated build for forrest-sample-2 FAILED
> >>>      [java]
> >>>      [java]
> >>>      [java] X [0]                                     linkmap.html
>    BROKEN: Could not resolve locationmap location.
> >>
> >>
> >> I get that same error doing 'build.sh test' locally.
> >>
> >> The build of this Dispatcher sample were okay on the
> >> zone server before today.
> >
> > I'm getting the same thing.  It looks like a mounted locationmap
> can't
> > be resolved but it appears to be dispatcher-related code.  I don't
> > know that code at all but a quick look seems like the resolver field
> > in the child class (RecursiveDirectoryTraversalAction) is hiding the
> > intended resolver in the parent class (AbstractTraversal).   Can you
> > comment out the child class' resolver field and see if that helps?
>  It
> > seems to get me past that one but then introduces tons of other
> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors.  The timing seems
> > right too,  it would have been introduced with r929463.
> 
> I went ahead and applied that because I feel sure that's the right
> thing to do.  I'm now getting errors like:
> 
> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
> X [0] linkmap.pdf BROKEN: Invalid
> byte 1 of 1-byte UTF-8 sequence.
> 
> ... for every pdf file.  I don't have time to look into that one right
> now though, can someone see if they get the same?

Yes, I am getting it too, but here we are again, a Windows only bug it
seems. I don’t get this on any linux box - which is why our zone doesn’t
complain.

Only thing I could come up with via Go-ogle was this thread featuring some
known names:

http://www.mail-archive.com/j-...@xerces.apache.org/msg00030.html

Consensus there seems to be that Windows default to latin rather than utf8
and that OutputStreamWriter should be used in place of FileWriter.

Why this is a recent thing I don’t know, haven’t had time to look much
further, but I do know I didn’t get these errors when recently testing the
Java 1.5/1.6 scenarios before the vote. I also went back before Thorstens
recent commits and the errors remain - not that I thought for one minute
they were related, but tested it anyway.

Gav...

> Thanks,
> --tim

RE: trouble publishing project docs with forrestbot

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Wednesday, 17 March 2010 4:35 PM
> To: dev@forrest.apache.org
> Subject: trouble publishing project docs with forrestbot
> 
> Would another committer try to publish the Forrest project docs:
> 
> $] cat etc/publishing_our_site.txt

Done.

> 
> I haven't tried since before the recent SVN access changes.

hmm, LDAP has been introduced but this shouldn't have affected svn access in
any way.

Your old svn password is still your svn password. The main change is that
your people.a.o
changed to using LDAP.

There is the ability to sync the two (LDAP + svn) into one using

https://svn.apache.org/change-password - you will need to use your SVN
password to log in to this area , so is a good test to know you are using
the correct one in your settings file.

> 
> Note that i have edited my $FORREST_HOME/deploy.svn.settings file.

Edited in what way? As noted your svn password should not have changed,
unless you have synced it with LDAP already, in which case try your
people.a.o password.

> 
> I can commit changes to the sources.
> 
> Just having recent trouble with:
> $] forrest -f publish.xml deploy

So you can commit to repos/asf/forrest/trunk via the command line but not
repos/asf/forrest/site via forrestbot. As the acl is the same for both is
'sounds' like at least you are using the wrong p/w in the
deploy.svn.settings file.

Let me know if you continue to have trouble and we'll dig some more.

Gav...

> 
> -David

Remove cocoon-2.1 docs from Forrest Zone

[Gav...]

Hi All,

The Cocoon 2.1 docs are being built twice a day on our zone.

http://forrest.zones.apache.org/ft/build/cocoon-docs/2.1/index.html 

However, the official documentation for Cocoon 2.1 docs at

http://cocoon.apache.org/2.1/

has not been updated since 2008.

so, I suspect we are just wasting our zone usage here by continuing to build
their documentation. As of Cocoon 2.2 onwards, it looks like that they now
use Maven to build their docs.

So, are we ok to remove their docs and disable their builds for the 2.1 docs
?

Gav...

Zone updated to Java 1.5

[Gav...]

Hi all,

I've altered the zone setup to point to Java 1.5

I've also set the recipient to myself initially to see what if any failures
come in so I can sort them so as to avoid spamming the list during the
transition.



On another note, I see we still have our cronjobs set to 2 hourly.

One of them updates the trunk source every two odd hours.

The other three build our versions and run them every two even hours.

It was moved from 1 hour to two hours due to

https://issues.apache.org/jira/browse/FOR-1061 

I would say that issue is solved now, especially with the recent svn
upgrades.

However, I have another solution that makes better sense imho.

We should go back to 'checking svn'; every hour for new commits, but ONLY do
an 'svn update' IF 
any commits have happened during that time. The same for the builds, why
keep rebuilding every
hour or two hours if the source hasn't changed ?

Take this January and February for example where only 1 commit in each month
took place.
During that time the zone would have done an svn update and rebuild three
sites approximately 
700 times in that period, 698 of them needlessly.

So, I propose that we instead do a script like this:

-
svn st -u | grep *

if [ $? = 0 ]; then

 svn up

/export/home/config/update-forrest-trunk.sh

else

fi
-

We then change the cronjob to run the above script every hour instead, and
will do nothing if no commit has happened in that time. I've been running
this on Buildbot for a year now and works great.

Thoughts?

Gav...

Trunk updated to 1.5

[Gav...]

Hi All,

Forrest Trunk is now set to use Java 1.5

After doing an 'svn up' on trunk you should:

1. Point JAVA_HOME to a 1.5 java jdk

2. cd FORREST_HOME/main ; build clean; build

Any initial problems I would suggest replying to this thread initially.
We can then work out what are set up / teething problems and what are bugs
that should go to Jira.

Thanks

Gav...

[RESULT] - [VOTE] - Upgrade Java Version to 1.5

[Gav...]

Hi all,

The result of the vote is as follows.

+1 = Tim Williams, Cyriaque Dupoirieux, Brian M Dube, Thorten Scherler, Sina
K Heshkati, David Crossley, Sjur Moshagen, Gavin McDonald

+/- 0 = No Votes

-1 = No Votes

So, with 8 +1 Votes and no other votes, this vote passes.

Thank you all, I'll see about making necessary changes tomorrow.

Gav...


> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Thursday, 4 March 2010 10:02 AM
> To: dev@forrest.apache.org
> Subject: [VOTE] - Upgrade Java Version to 1.5
> 
> Hi All,
> 
> This vote is to move 'trunk' to using java version 1.5.
> This also means advising users/devs that this is the minimum required
> version and that testing on versions of Java earlier than 1.5 will not
> be
> supported.
> 
> Parts of the current trunk, including 'Dispatcher' do not work or do
> not
> work well with Java 1.4.x
> 
> I have tested current trunk and dispatcher with Java 1.5 and it works
> well
> FOR ME. Java 1.6 also works fine.
> 
> I propose that we move to Java 1.5 on trunk immediately following a
> successful vote. I also propose that before voting, that devs TEST Java
> 1.5
> on trunk and in their own current usage. Only vote for this change if
> you
> are happy that things will continue to work or will begin to work well
> for
> YOU.
> 
> This vote for moving to Java 1.5 is to last until at least after the
> next
> release, so that we have at least one official release using the
> minimum
> Java 1.5 spec.
> 
> Please take your time and vote when your ready, this vote will run for
> ONE
> WEEK beginning now and ending on 11th March 2010 12PM (noon) GMT time.
> 
> [ ] - +1 Yes let's make the move.
> 
> [ ] - +/-0 I don't mind either way.
> 
> [ ] - -1 I strongly object and here are my reasons ...
> 
> Thanks All
> 
> Gav..
> 

RE: [VOTE] - Upgrade Java Version to 1.5

[Gav...]

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Thursday, 4 March 2010 10:02 AM
> To: dev@forrest.apache.org
> Subject: [VOTE] - Upgrade Java Version to 1.5
> 
> Hi All,
> 
> This vote is to move 'trunk' to using java version 1.5.
> This also means advising users/devs that this is the minimum required
> version and that testing on versions of Java earlier than 1.5 will not
> be
> supported.
> 
> Parts of the current trunk, including 'Dispatcher' do not work or do
> not
> work well with Java 1.4.x
> 
> I have tested current trunk and dispatcher with Java 1.5 and it works
> well
> FOR ME. Java 1.6 also works fine.
> 
> I propose that we move to Java 1.5 on trunk immediately following a
> successful vote. I also propose that before voting, that devs TEST Java
> 1.5
> on trunk and in their own current usage. Only vote for this change if
> you
> are happy that things will continue to work or will begin to work well
> for
> YOU.
> 
> This vote for moving to Java 1.5 is to last until at least after the
> next
> release, so that we have at least one official release using the
> minimum
> Java 1.5 spec.
> 
> Please take your time and vote when your ready, this vote will run for
> ONE
> WEEK beginning now and ending on 11th March 2010 12PM (noon) GMT time.
> 

> [X] - +1 Yes let's make the move.

from me too.

Gav...

> 
> [ ] - +/-0 I don't mind either way.
> 
> [ ] - -1 I strongly object and here are my reasons ...
> 
> Thanks All
> 
> Gav..
> 

REMINDER : One day left to : [VOTE] - Upgrade Java Version to 1.5

[Gav...]

Hi All,

For those that haven't yet, to use your right to vote on this issue, 
there is one day and a few hours left to do so.

Cheers

Gav...

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Thursday, 4 March 2010 10:02 AM
> To: dev@forrest.apache.org
> Subject: [VOTE] - Upgrade Java Version to 1.5
> 
> Hi All,
> 
> This vote is to move 'trunk' to using java version 1.5.
> This also means advising users/devs that this is the minimum required
> version and that testing on versions of Java earlier than 1.5 will not
> be
> supported.
> 
> Parts of the current trunk, including 'Dispatcher' do not work or do
> not
> work well with Java 1.4.x
> 
> I have tested current trunk and dispatcher with Java 1.5 and it works
> well
> FOR ME. Java 1.6 also works fine.
> 
> I propose that we move to Java 1.5 on trunk immediately following a
> successful vote. I also propose that before voting, that devs TEST Java
> 1.5
> on trunk and in their own current usage. Only vote for this change if
> you
> are happy that things will continue to work or will begin to work well
> for
> YOU.
> 
> This vote for moving to Java 1.5 is to last until at least after the
> next
> release, so that we have at least one official release using the
> minimum
> Java 1.5 spec.
> 
> Please take your time and vote when your ready, this vote will run for
> ONE
> WEEK beginning now and ending on 11th March 2010 12PM (noon) GMT time.
> 
> [ ] - +1 Yes let's make the move.
> 
> [ ] - +/-0 I don't mind either way.
> 
> [ ] - -1 I strongly object and here are my reasons ...
> 
> Thanks All
> 
> Gav..
> 

[VOTE] - Upgrade Java Version to 1.5

[Gav...]

Hi All,

This vote is to move 'trunk' to using java version 1.5.
This also means advising users/devs that this is the minimum required
version and that testing on versions of Java earlier than 1.5 will not be
supported.

Parts of the current trunk, including 'Dispatcher' do not work or do not
work well with Java 1.4.x

I have tested current trunk and dispatcher with Java 1.5 and it works well
FOR ME. Java 1.6 also works fine.

I propose that we move to Java 1.5 on trunk immediately following a
successful vote. I also propose that before voting, that devs TEST Java 1.5
on trunk and in their own current usage. Only vote for this change if you
are happy that things will continue to work or will begin to work well for
YOU.

This vote for moving to Java 1.5 is to last until at least after the next
release, so that we have at least one official release using the minimum
Java 1.5 spec.

Please take your time and vote when your ready, this vote will run for ONE
WEEK beginning now and ending on 11th March 2010 12PM (noon) GMT time.

[ ] - +1 Yes let's make the move.

[ ] - +/-0 I don't mind either way.

[ ] - -1 I strongly object and here are my reasons ...

Thanks All

Gav..

RE: Java Version (was RE: Can't get Dispatcher working at all windows/linux from trunk)

[Gav...]

> -Original Message-
> From: Thorsten Scherler
> [mailto:thorsten.scherler@juntadeandalucia.es]
> Sent: Tuesday, 2 March 2010 8:44 PM
> To: dev@forrest.apache.org
> Subject: Re: Java Version (was RE: Can't get Dispatcher working at all
> windows/linux from trunk)
> 
> On Sat, 2010-02-27 at 07:37 -0500, Tim Williams wrote:
> > On Sat, Feb 27, 2010 at 7:08 AM, Gav... 
> wrote:
> > >
> > >
> > >> -Original Message-
> > >> From: David Crossley [mailto:cross...@apache.org]
> > >> Sent: Monday, 22 February 2010 8:11 PM
> > >> To: dev@forrest.apache.org
> > >> Subject: Re: Can't get Dispatcher working at all windows/linux
> from
> > >> trunk
> > >>
> > > 
> > >>
> > >> As said before, one of the issues is the agreed Java base version.
> > >> See the "build.compiler.vm" parameter in our build.xml
> > >> and instructions in the Release documentation and recent
> discussion
> > >> in these dev archives.
> > >>
> > >> -David
> > >
> > > Seems to me, from my tests at least on linux/windows, it is the
> only issue
> > > in
> > > getting dispatcher working. All of the plugins would need checking
> too I
> > > guess.
> > >
> > > so how about we get on and vote for moving to 1.5 immediately and
> for the
> > > next
> > > release, deciding after then to perhaps move to 1.6 ?
> >
> > +1
> 
> +1
> 
> ...but as David always says: this is not a vote thread, but the issue
> needs one.

True, I was gauging interest at the proposal of moving to 1.5 now with 1.6
being the goal after the next release (so we then have at least a released
version running on 1.5)

I'll start a vote thread soon.

Gav...

> 
> salu2
> --
> Thorsten Scherler 
> Open Source Java 
> 
> Sociedad Andaluza para el Desarrollo de la Sociedad
> de la Información, S.A.U. (SADESI)
> 
> 
> 

Java Version (was RE: Can't get Dispatcher working at all windows/linux from trunk)

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Monday, 22 February 2010 8:11 PM
> To: dev@forrest.apache.org
> Subject: Re: Can't get Dispatcher working at all windows/linux from
> trunk
> 

> 
> As said before, one of the issues is the agreed Java base version.
> See the "build.compiler.vm" parameter in our build.xml
> and instructions in the Release documentation and recent discussion
> in these dev archives.
> 
> -David

Seems to me, from my tests at least on linux/windows, it is the only issue
in
getting dispatcher working. All of the plugins would need checking too I
guess.

so how about we get on and vote for moving to 1.5 immediately and for the
next
release, deciding after then to perhaps move to 1.6 ? We are after all still
in
the 0.x development stages and we are more obliged to make developers lives
easier
at this stage ahead of the concerns of users even though I feel most users
would
likely have been on 1.5+ themselves for a while now. The other option is
moving 
directly to 1.6 (more correctly java 6). 

I'm happy with either, what I would not be happy about is people dallying
around 
for another few months before making a decision. This need to be sorted now
so
devs can get on with a working trunk.

Gav...

RE: Can't get Dispatcher working at all windows/linux from trunk

[Gav...]

> -Original Message-
> From: Cyriaque Dupoirieux [mailto:cyriaque.dupoiri...@pco-
> innovation.com]
> Sent: Tuesday, 23 February 2010 6:49 PM
> To: dev@forrest.apache.org
> Subject: Re: Can't get Dispatcher working at all windows/linux from
> trunk
> 
> le 22/02/2010 15:53 Gav... a écrit :
> >
> >
> >> -Original Message-
> >> From: Thorsten Scherler
> >>
> >>> ... SNIP ...
> >>>
> >>
> >>
> D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apac
> >>
> he.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\pl
> >> ugins\org.apache.forrest.plugin.input.projectInfo
> >>
> >>> (Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
> >>>
> >>
> >> Hmm that reminds me on a bug that gavin had and fixed. It was
> something
> >> about the locationmap and add a certain location, but I am not
> >> remembering the issue anymore. ...but AFAIR there was a comment in
> the
> >> code somewhere about it.
> >>
> >> Gavin do you remember?
> >>
> > I looked, seems like the problem encountered in FOR-1108 - in fact
> Cyriaque commented
> > the exact same problem in October 2008. Look at the SVN tab on that
> issue to see
> > what was done to cure that.
> >
> > Cyriaque, are you using a year old trunk? Any reason not to update?
> >
> > Gav...
> >
> Ho ? I am going to check if I have a local copy modified - and then not
> up-to-date with the trunk
> I try this morning and tell you,

Ok great, hopefully we'll have you back and running again soon :)

Gav...

> 
> Salutations,
> Cyriaque,

RE: Dispatcher problem with forrest seed

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Thursday, 7 January 2010 12:11 PM
> To: dev@forrest.apache.org
> Subject: Re: Dispatcher problem with forrest seed
> 
> Brian M Dube wrote:
> >
> > I'm still looking into all this, but how are you and the zone testing
> > the dispatcher with 1.4.x? There features there that require 1.5 to
> > build.
> 
> The zone does a 'clean; build' every 2 hours. Java 1.4.2 is the
> base until the Forrest project decides to move forward.
> 
> Regarding the Dispatcher build issues, the only thing that
> i can think of is that the "seed site" does not actually
> do very much with the Dispatcher. It has only one or two
> simple demos of Dispatcher ability. So i suppose that it is
> not using those parts that reported issues. Not a decent test.

Note that the zone is NOT using dispatcher, it tries to and fails to 
load the dispatcher plugin, but continues on to an otherwise successful
build and deploys an ordinary non-dispatcher version of the site.

Either fixing the issues for java 1.4 or upgrading the zone to use 1.5 or
1.6 is the solution.

Gav...

> 
> -David

RE: Can't get Dispatcher working at all windows/linux from trunk

[Gav...]

> -Original Message-
> From: Thorsten Scherler
> [mailto:thorsten.scherler@juntadeandalucia.es]
> Sent: Monday, 22 February 2010 10:26 PM
> To: ga...@16degrees.com.au
> Subject: RE: Can't get Dispatcher working at all windows/linux from
> trunk
> 



> > > > > As said before, one of the issues is the agreed Java base
> version.
> > > > > See the "build.compiler.vm" parameter in our build.xml
> > > > > and instructions in the Release documentation and recent
> discussion
> > > > > in these dev archives.
> > > >
> > > > Yep, I read briefly but need to go back in case I missed
> something.
> >
> > And there lies the clue!
> >
> > Despite having set default java to either 1.5 or 1.6, despite setting
> > JAVA_HOME to point to 1.5 or 1.6, it still compiled using 1.4 due to
> the
> > fact that the build.compiler.vm was still set at 1.4 !!
> >
> > I have now brought my local copy back up to trunk:HEAD, changed the
> > setting to 1.5, changed the JAVA_HOME to 1.5 and Dispatcher now works
> > fine on Windows and Linux !!
> >
> > (Have others tried that and had success/failure)
> >
> > Looking at the Forrest Zone at
> >
> > http://forrest.zones.apache.org/ft/build/forrest-sample-2/
> >
> > it is clearly not using Dispatcher.
> >
> > I also tested in 1.6 and get the following compile errors:
> >
> > compile:
> > Created dir: /home/gmcdonald/asf/forrest/build/classes
> > Compiling 33 source files to
> /home/gmcdonald/asf/forrest/build/classes
> >
> /home/gmcdonald/asf/forrest/main/java/org/apache/forrest/util/IdGenerat
> orTransformer.java:177: unmappable character for encoding UTF8
> > //  - Quelques
> > r�gles... > ^
> >
> /home/gmcdonald/asf/forrest/main/java/org/apache/forrest/util/IdGenerat
> orTransformer.java:180: unmappable character for encoding UTF8
> > //  - Quelques
> > r�gles...
> >
> ^
> > 2 errors
> >
> > So, getting closer to having 1.6 work too.
> 
> Hmm, that is under Windows right?
> 
> I have seen it before in other projects.

actually no, that was under Linux (using java 1.6.0_15-b03)

I tested Forrest & dispatcher under Windows using Java 1.6 (using java
1.6.0_18-b07) and that too, now works fine without any errors.

So to re-cap my situation now:

Using Java 1.4.x under Windows or Linux - dispatcher does not work.

(but if you roll back whiteboard/plugins/dispatcher to r886146 then
that older version works fine with rest of current trunk)

Using Java 1.5.x under Windows or Linux - current dispatcher works fine.

Using Java 1.6.x under Windows - current dispatcher works fine.

Using Java 1.6.x under Linux - current dispatcher does not work.
(with those two utf8 errors mentioned)

With all the above - set the build.compiler.vm to match java version.

also note I don't have a MAC to test the above scenarios.

HTH

Gav...



> 
> >
> > > >
> > > > One thing is for sure, the forward momentum of this project
> depends on this
> > > > being resolved, and soon. We should vote on a minimum version of
> java soon,
> > > > then work on fixing it for that version - as tried and tested as
> much as I
> > > > have, dispatcher for me doesn't work in any of them.
> > >
> > > I personally prefer to use 1.6 as minimum since 1.4 and 1.5 are not
> > > officially supported anymore. However to make the dispatcher work
> with
> > > 1.4 is not that hard since it is mostly generic compilation
> exception.
> >
> > If others can test, and it is as simple as upping the
> build.compiler.vm
> > setting, then I say we should do it right now, but others may have
> other
> > views.
> 
> Well, nothing is fater to raise build.compiler.vm settings other then
> having a vote. ...but I reckon it should not hard to get it 1.4 conform
> my problem is ATM I am having too much commercial work to actually do
> some coding on the dispatcher.
> 
> >
> > As we are still in the 0.X range of release versions, then if we can
> fix
> > the above UTF8 problem I'd be happy to go straight to 1.6
> 
> If you under windows I could ask a co worker that had the similar
> problem.
> 
> aslu2
> 
> >
> >
> > Thanks for looking into it.
> >
> > Gav...
> >
> > >
> > > salu2
> >
> >
> --
> Thorsten Scherler 
> Open Source Java 
> 
> Sociedad Andaluza para el Desarrollo de la Sociedad
> de la Información, S.A.U. (SADESI)
> 
> 
> 

RE: Can't get Dispatcher working at all windows/linux from trunk

[Gav...]

> -Original Message-
> From: Thorsten Scherler
> [mailto:thorsten.scherler@juntadeandalucia.es]
> Sent: Monday, 22 February 2010 11:55 PM
> To: dev@forrest.apache.org
> Subject: Re: Can't get Dispatcher working at all windows/linux from
> trunk
> 
> On Mon, 2010-02-22 at 14:46 +0100, Cyriaque Dupoirieux wrote:
> > le 22/02/2010 11:48 Thorsten Scherler a écrit :
> > > On Mon, 2010-02-22 at 20:22 +1000, Gav... wrote:
> > >
> >
> > ... SNIP ...
> > >>> I did *not* get it working. I needed to go back to before
> > >>> the Dispatcher merge. I did 'svn up' to r882421 2009-11-20.
> > >>>
> > >> Ah right, ok, same as what I did then, 'somebody' must have it
> working
> > >> and it needs to be sorted soon otherwise it doesn't belong in
> trunk.
> > >>
> > > Hmm, I will try now as well. Can you post the exception that you
> got
> > > again, please
> > >> As said before, one of the issues is the agreed Java base version.
> > >> See the "build.compiler.vm" parameter in our build.xml
> > >> and instructions in the Release documentation and recent
> discussion
> > >> in these dev archives.
> > >>
> > >> Yep, I read briefly but need to go back in case I missed
> something.
> > >>
> > >> One thing is for sure, the forward momentum of this project
> depends on this
> > >> being resolved, and soon. We should vote on a minimum version of
> java soon,
> > >> then work on fixing it for that version - as tried and tested as
> much as I
> > >> have, dispatcher for me doesn't work in any of them.
> > >>
> > > I personally prefer to use 1.6 as minimum since 1.4 and 1.5 are not
> > > officially supported anymore. However to make the dispatcher work
> with
> > > 1.4 is not that hard since it is mostly generic compilation
> exception.
> > >
> > > salu2
> > >
> > I agree, I don't see the use to be compliant with old java
> versions...
> > I have lots of problems to make the dispatcher work again and it may
> be
> > why I am very silent at the moment.
> > I hope I can help if someone can give me some clues...
> > Here are the problems I met with the dispatcher plugin generation
> with
> > build.compiler.vm=1.5 :
> >
> > ...
> >
> > Cocoon will report the status of each document:
> >   - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
> >
> > -
> ---
> > cocoon 2.1.12-dev
> > Copyright (c) 1999-2007 Apache Software Foundation. All rights
> reserved.
> > -
> ---
> > ^int/
> > ^examples/
> > * [1/26][26/29]   12.671s 10.1Kb  linkmap.html
> > * [3/24][0/0] 0.125s 2.0Kb   linkmap.dispatcher.css
> > X [0] changes.html  BROKEN:
> >
> D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apac
> he.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\pl
> ugins\org.apache.forrest.plugin.input.projectInfo
> > (Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
> > X [0] todo.html BROKEN:
> >
> D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apac
> he.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\pl
> ugins\org.apache.forrest.plugin.input.projectInfo
> > (Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
> 
> 
> Hmm that reminds me on a bug that gavin had and fixed. It was something
> about the locationmap and add a certain location, but I am not
> remembering the issue anymore. ...but AFAIR there was a comment in the
> code somewhere about it.
> 
> Gavin do you remember?

I looked, seems like the problem encountered in FOR-1108 - in fact Cyriaque 
commented
the exact same problem in October 2008. Look at the SVN tab on that issue to see
what was done to cure that.

Cyriaque, are you using a year old trunk? Any reason not to update?

Gav...

> 
> salu2
> 
> > * [6/21][0/0] 0.093s 1.2Kb   themes/leather-dev.css
> > X [0]
> > how/howto-dispatcher-contracts.html   BROKEN:
> >
> D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apac
> he.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\pl
> ugins\svnHelpe

RE: Can't get Dispatcher working at all windows/linux from trunk

[Gav...]

> -Original Message-
> From: David Crossley [mailto:cross...@apache.org]
> Sent: Monday, 22 February 2010 8:11 PM
> To: dev@forrest.apache.org
> Subject: Re: Can't get Dispatcher working at all windows/linux from
> trunk
> 
> Gav... wrote:
> >
> > I see Davids thread 'strange dispatcher behaviour after merge' is
> exactly the same problems
> > as I am getting now. David, I see no follow up solution, what did you
> do to get it going again?
> >
> > I also note Brian says he is not having any issues either, Brian,
> what did you need to change
> > to get dispatcher in current trunk working for you?
> 
> I did *not* get it working. I needed to go back to before
> the Dispatcher merge. I did 'svn up' to r882421 2009-11-20.

Ah right, ok, same as what I did then, 'somebody' must have it working 
and it needs to be sorted soon otherwise it doesn't belong in trunk.

> 
> As said before, one of the issues is the agreed Java base version.
> See the "build.compiler.vm" parameter in our build.xml
> and instructions in the Release documentation and recent discussion
> in these dev archives.

Yep, I read briefly but need to go back in case I missed something.

One thing is for sure, the forward momentum of this project depends on this
being resolved, and soon. We should vote on a minimum version of java soon, 
then work on fixing it for that version - as tried and tested as much as I 
have, dispatcher for me doesn't work in any of them.

Gav...

> 
> -David

RE: Can't get Dispatcher working at all windows/linux from trunk

[Gav...]

> -Original Message-
> From: Gav... [mailto:ga...@16degrees.com.au]
> Sent: Monday, 22 February 2010 3:54 PM
> To: dev@forrest.apache.org
> Subject: RE: Can't get Dispatcher working at all windows/linux from
> trunk
> 
> 
> 
> > -Original Message-
> > From: Gavin [mailto:ga...@16degrees.com.au]
> > Sent: Monday, 22 February 2010 1:43 PM
> > To: dev@forrest.apache.org
> > Subject: Can't get Dispatcher working at all windows/linux from trunk
> >
> > Using a fresh trunk - in fact on a Windows machine and a Linux
> machine
> > that have never had Forrest installed on it before, I can get a
> > 'forrest
> > seed' site working normally.
> >
> > As soon as I dispatcher enable it in forrest.properties, I get a
> whole
> > heap of errors in both 'forrest run' and 'forrest site' - the build
> > continues to completion and I end up with a skinned site still, the
> > dispatcher was not enabled.
> >
> > This is on Windows XP, Ubuntu 8.10, using all combinations of java
> > 1.4.2, java 5 and java 6 jdks on both machines. With java 5 and 6 I
> get
> > the same 21 errors (pasted below) and with 1.4.2 I get more - 54
> > errors.
> >
> > Others seem to get further than me, to the point of a basic seed site
> > working fine, so have I missed some developer step not mentioned in
> the
> > docs that I might have forgotten?
> 
> I see Davids thread 'strange dispatcher behaviour after merge' is
> exactly the same problems
> as I am getting now. David, I see no follow up solution, what did you
> do to get it going again?
> 
> I also note Brian says he is not having any issues either, Brian, what
> did you need to change
> to get dispatcher in current trunk working for you?
> 
> The problem for me lies completely in the dispatcher plugin as I get
> those errors trying to
> run an 'ant test' or 'ant local-deploy' from within the dispatcher
> plugin dir.

I tested by going back to just before the new dispatcher merger:

$ cd $forrest_home/whiteboard/plugins

$ svn up org.apache.forrest.plugin.internal.dispatcher -r886146

$ svn up org.apache.forrest.themes.core -r886146

$ svn up whiteboard-plugins.xml -r886146

Now the dispatcher works fine with the current trunk and java 1.4.2, java 5 and 
java 6

Obviously not a solution to our current trunk, but a workaround should anyone 
need to get
dispatcher working for their own needs.

> 
> 
> Thanks
> 
> Gav...
> 
> >
> > 
> > Apache Forrest.  Run 'forrest -projecthelp' to list options
> >
> > Buildfile: /home/gmcdonald/asf/forrest/main/forrest.build.xml
> >
> > check-java-version:
> > This is apache-forrest-0.9-dev
> > Using Java 1.6 from /usr/lib/jvm/java-6-sun-1.6.0.15/jre
> > Using Apache Ant version 1.7.1 compiled on September 26 2008
> > from /home/gmcdonald/asf/forrest/tools/ant
> >
> > 
> >
> > fetch-plugins-descriptors:
> > Fetching plugins descriptor:
> > http://forrest.apache.org/plugins/plugins.xml
> > Getting: http://forrest.apache.org/plugins/plugins.xml
> > To: /home/gmcdonald/forrest-sites/forrest-seed/build/tmp/plugins-
> 1.xml
> > local file date : Mon Feb 22 09:45:04 EST 2010
> > Not modified - so not downloaded
> > Fetching plugins descriptor:
> > http://forrest.apache.org/plugins/whiteboard-plugins.xml
> > Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
> > To: /home/gmcdonald/forrest-sites/forrest-seed/build/tmp/plugins-
> 2.xml
> > local file date : Mon Feb 22 09:49:46 EST 2010
> > Not modified - so not downloaded
> > Plugin list loaded from
> http://forrest.apache.org/plugins/plugins.xml.
> > Plugin list loaded from
> > http://forrest.apache.org/plugins/whiteboard-plugins.xml.
> >
> >
> >   --
> >   Installing plugin: org.apache.forrest.plugin.output.pdf
> >   --
> >
> > 
> >
> > fetch-local-unversioned-plugin:
> >
> > get-local:
> > Trying to locally get org.apache.forrest.plugin.output.pdf
> > Looking in local /home/gmcdonald/asf/forrest/plugins
> > Found !
> >
> > 
> >
> > configure-plugin:
> >
> > configure-output-plugin:
> > Mounting output plugin: org.apache.forrest.plugin.output.pdf
> > Processing /home/gmcdonald/forrest-sites/forrest-
> > seed/build/tmp/output.xmap to /home/gmcdonald/forrest-sites/forr

RE: Can't get Dispatcher working at all windows/linux from trunk

[Gav...]

> -Original Message-
> From: Gavin [mailto:ga...@16degrees.com.au]
> Sent: Monday, 22 February 2010 1:43 PM
> To: dev@forrest.apache.org
> Subject: Can't get Dispatcher working at all windows/linux from trunk
> 
> Using a fresh trunk - in fact on a Windows machine and a Linux machine
> that have never had Forrest installed on it before, I can get a
> 'forrest
> seed' site working normally.
> 
> As soon as I dispatcher enable it in forrest.properties, I get a whole
> heap of errors in both 'forrest run' and 'forrest site' - the build
> continues to completion and I end up with a skinned site still, the
> dispatcher was not enabled.
> 
> This is on Windows XP, Ubuntu 8.10, using all combinations of java
> 1.4.2, java 5 and java 6 jdks on both machines. With java 5 and 6 I get
> the same 21 errors (pasted below) and with 1.4.2 I get more - 54
> errors.
> 
> Others seem to get further than me, to the point of a basic seed site
> working fine, so have I missed some developer step not mentioned in the
> docs that I might have forgotten?

I see Davids thread 'strange dispatcher behaviour after merge' is exactly the 
same problems
as I am getting now. David, I see no follow up solution, what did you do to get 
it going again?

I also note Brian says he is not having any issues either, Brian, what did you 
need to change
to get dispatcher in current trunk working for you?

The problem for me lies completely in the dispatcher plugin as I get those 
errors trying to
run an 'ant test' or 'ant local-deploy' from within the dispatcher plugin dir.


Thanks

Gav...

> 
> 
> Apache Forrest.  Run 'forrest -projecthelp' to list options
> 
> Buildfile: /home/gmcdonald/asf/forrest/main/forrest.build.xml
> 
> check-java-version:
> This is apache-forrest-0.9-dev
> Using Java 1.6 from /usr/lib/jvm/java-6-sun-1.6.0.15/jre
> Using Apache Ant version 1.7.1 compiled on September 26 2008
> from /home/gmcdonald/asf/forrest/tools/ant
> 
> 
> 
> fetch-plugins-descriptors:
> Fetching plugins descriptor:
> http://forrest.apache.org/plugins/plugins.xml
> Getting: http://forrest.apache.org/plugins/plugins.xml
> To: /home/gmcdonald/forrest-sites/forrest-seed/build/tmp/plugins-1.xml
> local file date : Mon Feb 22 09:45:04 EST 2010
> Not modified - so not downloaded
> Fetching plugins descriptor:
> http://forrest.apache.org/plugins/whiteboard-plugins.xml
> Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
> To: /home/gmcdonald/forrest-sites/forrest-seed/build/tmp/plugins-2.xml
> local file date : Mon Feb 22 09:49:46 EST 2010
> Not modified - so not downloaded
> Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml.
> Plugin list loaded from
> http://forrest.apache.org/plugins/whiteboard-plugins.xml.
> 
> 
>   --
>   Installing plugin: org.apache.forrest.plugin.output.pdf
>   --
> 
> 
> 
> fetch-local-unversioned-plugin:
> 
> get-local:
> Trying to locally get org.apache.forrest.plugin.output.pdf
> Looking in local /home/gmcdonald/asf/forrest/plugins
> Found !
> 
> 
> 
> configure-plugin:
> 
> configure-output-plugin:
> Mounting output plugin: org.apache.forrest.plugin.output.pdf
> Processing /home/gmcdonald/forrest-sites/forrest-
> seed/build/tmp/output.xmap to /home/gmcdonald/forrest-sites/forrest-
> seed/build/tmp/output.xmap.new
> Loading
> stylesheet /home/gmcdonald/asf/forrest/main/var/pluginMountSnippet.xsl
> Moving 1 file to /home/gmcdonald/forrest-sites/forrest-seed/build/tmp
> 
> configure-plugin-locationmap:
> Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
> Processing /home/gmcdonald/forrest-sites/forrest-
> seed/build/tmp/locationmap.xml to /home/gmcdonald/forrest-
> sites/forrest-seed/build/tmp/locationmap.xml.new
> Loading
> stylesheet
> /home/gmcdonald/asf/forrest/main/var/pluginLmMountSnippet.xsl
> Moving 1 file to /home/gmcdonald/forrest-sites/forrest-seed/build/tmp
> 
>   --
>   Installing plugin: org.apache.forrest.plugin.internal.dispatcher
>   --
> 
> 
> check-plugin:
> org.apache.forrest.plugin.internal.dispatcher is not available in the
> build dir. Trying to fetch it...
> 
> init-props:
> 
> echo-settings-condition:
> 
> echo-settings:
> 
> init-proxy:
> 
> fetch-plugins-descriptors:
> 
> fetch-plugin:
> Trying to find the description of
> org.apache.forrest.plugin.intern

[OT] Send xml email from html form data

[Gav...]

Hi All,

 

Off topic sorry, but thought someone here might know the best approach.

 

I'm trying to create an xml output file from form data of an  html web page.

 

Is there a program out there to do this or what would be a sensible approach

In handing this? Perhaps an xslt stylesheet to convert a txt output document
but 

I was hoping there was a more direct route.

 

Thanks

 

Gav...

RE: Usage of content-author etc

[Gav....]

> -Original Message-
> From: Cyriaque Dupoirieux [mailto:[EMAIL PROTECTED]
> Sent: Friday, 4 April 2008 5:27 PM
> To: dev@forrest.apache.org
> Subject: Re: Usage of content-author etc
> 
> le 02/04/2008 16:23 Gav a écrit :
> > Hi All,
> >
> > I was looking at trying to finish off FOR-797
> >
> > (A moving target being in the Whiteboard, some of them will need
> > doing again ...)
> >
> > Looking at content-author.ft it simply states to put the contract
> > in the view somewhere.
> >
> > So I added :-
> >
> > 
> >
> > ..into 'pelt-html.content.panel.xml'
> >
> > Nothing shows up, looking at the source of the page
> > the comments are there but no content inbetween.
> >
> > looking at the code of the contract, it is looking for
> > a div class="author" somewhere, so I added one, but still
> > can not see where an actual authors name is supposed to
> > come from or in fact where it is supposed to appear.
> >
> Add authors in your header :
> http://forrest.apache.org/dtdx/document-v20.dtdx.html#authors

Thanks, I have added an authors section and this shows up if I
include the contract 'content-authors.ft' , so that is another
one I can commit later, however I was working on the singular
'content-author.ft' (note no s at the end) , so, still stumped
on getting this to work, its purpose etc..


Thanks.

Gav...

> > I have converted some other contracts and work fine, as I want
> > to make sure all contracts work before committing, any hints
> > on this probably brain-dead simple one would be great :)
> >
> >
> > I also think we should create a test view, either a page or few pages
> > containing all these contracts so they can be tested on forrest-sample-2
> > - any changes elsewhere that break any of these will then be
> hightlighted.
> >
> >
> >
> >
> > Gav...
> >
> >
> >
> 
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.519 / Virus Database: 269.21.7/1332 - Release Date: 3/17/2008
> 10:48 AM

Usage of content-author etc

[Gav....]

Hi All,

I was looking at trying to finish off FOR-797

(A moving target being in the Whiteboard, some of them will need
doing again ...)

Looking at content-author.ft it simply states to put the contract
in the view somewhere.

So I added :-



..into 'pelt-html.content.panel.xml' 

Nothing shows up, looking at the source of the page
the comments are there but no content inbetween.

looking at the code of the contract, it is looking for
a div class="author" somewhere, so I added one, but still
can not see where an actual authors name is supposed to
come from or in fact where it is supposed to appear.

I have converted some other contracts and work fine, as I want
to make sure all contracts work before committing, any hints
on this probably brain-dead simple one would be great :)


I also think we should create a test view, either a page or few pages
containing all these contracts so they can be tested on forrest-sample-2
- any changes elsewhere that break any of these will then be hightlighted.




Gav...

PDF output and Dispatcher

[Gav....]

Hi All,

This was going to be an email about how PDF was not working with Dispatcher,
more accurately that it did not work using Pelt Theme or any theme that does
not over-ride FO from /common/ .

Usually, when I copy over Pelt Theme for over-riding to my project, I also
copy over /common/ just in case I need to change any of that too. This was
my downfall here, because changes made to /common/fo recently did not get
updated in my local project, so broke PDF output.

I then spent 1/2 hr fault-finding and correcting errors in
layout-master-set.ft only to find that this had already been done in
whiteboard. 

So, a doh! moment for me, and a heads-up to anyone else that has local
copies of themes/common/* , remember to update them, better still, try not
to change anything in common, copy it to /pelt/ and change it there instead.

Gav...

RE: dependency on project symbols file (Was: svn commit: r632740)

[Gav....]

> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 4 March 2008 4:01 PM
> To: dev@forrest.apache.org
> Subject: Re: dependency on project symbols file (Was: svn commit: r632740)
> 
> David Crossley wrote:
> > David Crossley wrote:
> > >
> > > No. What the above means is that i configured the core
> > > to have a project symbols file. If they over-ride that in
> > > their project's xml catalog they can supply their own file.
> >
> > Aha, i found it. When this ability for "project and core symbols"
> > was added in forrest-0.8 version, i declared the project symbols
> > in the xml catalog.xcat file of our seed projects. However i only
> > supplied the actual file of symbols in the "fresh-site" not in
> > the main/template-sites/basic/
> >
> > So if people based their sites on 'forrest seed' then all would
> > be okay. However, if based on 'forrest seed-basic' then not.
> 
> All is okay now. I found a workaround and described its implementation
> in FOR-1071.
> 

Thanks, yes, just copying in the file works fine.

I tend to use 'forrest seed-basic' these days when starting new sites rather
than strip down a nicely populated 'forrest seed'.

Gav...


> -David
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.20.9 - Release Date: 2/20/2008
> 12:00 AM

RE: [jira] Closed: (FOR-1072) [PATCH] Bugfixes and improvements for PDF output plugin

[Gav....]

Hi All,

Using Trunk and a fresh 'forrest seed-basic' , when I do 'forrest run' I get

Request URI

index.pdf

cause

Error(Unknown location): For fo:simple-page-master, fo:region-body must be
declared before fo:region-before.

when viewing its PDF.

Console output says :-

WARN - Mismatch: simple-page-master (http://www.w3.org/1999/XSL/Format) vs.
layo
ut-master-set (http://www.w3.org/1999/XSL/Format)
WARN - Mismatch: simple-page-master (http://www.w3.org/1999/XSL/Format) vs.
root
 (http://www.w3.org/1999/XSL/Format)


I will try again with another new seed and see what happens.

Gav...


> -Original Message-
> From: Jeremias Maerki (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 4 March 2008 6:40 PM
> To: dev@forrest.apache.org
> Subject: [jira] Closed: (FOR-1072) [PATCH] Bugfixes and improvements for
> PDF output plugin
> 
> 
>  [ https://issues.apache.org/jira/browse/FOR-
> 1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Jeremias Maerki closed FOR-1072.
> 
> 
> Resolution: Fixed
> 
> I think that's it for the moment.
> 
> > [PATCH] Bugfixes and improvements for PDF output plugin
> > ---
> >
> > Key: FOR-1072
> > URL: https://issues.apache.org/jira/browse/FOR-1072
> > Project: Forrest
> >  Issue Type: Improvement
> >  Components: Plugin: output.pdf
> >Affects Versions: 0.9-dev
> >Reporter: Jeremias Maerki
> > Fix For: 0.9-dev
> >
> > Attachments: forrest-pdf-touchup.patch, forrest-pdf-
> touchup2.patch, forrest-pdf-touchup3.patch
> >
> >
> > I've been playing with Forrest Trunk to get the FOP website to work. I
> found a number of problems which I've fixed with the attached patch. The
> changes in detail:
> > - PDFs generated from an FAQ page inserted the section number (1.1, 1.2
> etc.) twice in front of the section title. I've just filtered it now. It
> may not be the best way to fix this.
> > - Added a bookmark entry for the table of contents if it is enabled.
> > - Added keep-with-next.within-column="always" for all section titles,
> header elements of note/warning/fixme boxes and table captions. The new
> FOP supports keeps so you should use them. Otherwise, page break decision
> can be really ugly.
> > - Added keep-with-previous.within-column="always" for note/warning/fixme
> boxes so the don't land on a new page as first elements. This preserves
> the context.
> > - table rows with th elements are now placed in the fo:table-header, so
> the headers are repeated on each page the table spans.
> > - Used proportional-column-width(1) instead of a fixed width calculation
> for the column widths which automatically makes use of the whole page
> width regardless of the page margin settings.
> > - Fixed placement of page number and document title depending on
> "double-sided" setting. --> Page number to the "outside" and document
> title to the "inside".
> > - Filtered out link elements with no href (which are created by html-to-
> document.xsl for " at all but trunk does. Maybe that's wrong in the first place.
> > I'd appreciate a quick turn-around with this patch (if possible) as this
> would allow us to switch to Forrest Trunk for the FOP 0.95 release (we
> want to eat our own dogfood). Without this patch, our compliance PDF page
> fails due to the "

RE: svn commit: r632740 - in /forrest/trunk: main/fresh-site/src/documentation/content/xdocs/samples-b/ main/webapp/ main/webapp/resources/schema/ main/webapp/resources/schema/entity/ site-author/ sit

[Gav....]

Hi All,

This may be related to this commit.

After doing : svn up; cd main; build clean; build
Then doing a 'forrest seed-basic' 'forrest run' gives me :-

17:59:29.984 EVENT  Started [EMAIL PROTECTED]
Failed to create InputSource (java.io.FileNotFoundException:
D:\web\16degrees\sr
c\documentation\resources\schema\symbols-project-v10.ent (The system cannot
find
 the file specified)):
file:/D:/web/16degrees/src/documentation/resources/schema
/symbols-project-v10.ent

.. and outputs nothing in the web browser.

Gav...

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Sunday, 2 March 2008 8:22 PM
> To: [EMAIL PROTECTED]
> Subject: svn commit: r632740 - in /forrest/trunk: main/fresh-
> site/src/documentation/content/xdocs/samples-b/ main/webapp/
> main/webapp/resources/schema/ main/webapp/resources/schema/entity/ site-
> author/ site-author/content/xdocs/docs_0_90/ whiteboard/plugins/org...
> 
> Author: crossley
> Date: Sun Mar  2 03:22:23 2008
> New Revision: 632740
> 
> URL: http://svn.apache.org/viewvc?rev=632740&view=rev
> Log:
> Enable configuration of some Cocoon sitemap components, e.g. output html
> encoding and document type declaration for html and xhtml serializers,
> JTidy properties file location for html generator.
> Issue: FOR-1071
> 
> Added:
> forrest/trunk/main/webapp/resources/schema/entity/symbols-project-
> v10.ent
>   - copied unchanged from r632666, forrest/trunk/main/fresh-
> site/src/documentation/resources/schema/symbols-project-v10.ent
> Modified:
> forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-
> b/xml-entities.xml
> forrest/trunk/main/webapp/resources/schema/catalog.forrest.xcat
> forrest/trunk/main/webapp/resources/schema/entity/symbols-core-v10.ent
> forrest/trunk/main/webapp/sitemap.xmap
> forrest/trunk/site-author/content/xdocs/docs_0_90/faq.xml
> forrest/trunk/site-author/status.xml
> 
> forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispat
> cher/internal.xmap
> 
> Modified: forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples-b/xml-entities.xml
> URL: http://svn.apache.org/viewvc/forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples-b/xml-
> entities.xml?rev=632740&r1=632739&r2=632740&view=diff
> ==
> 
> --- forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-
> b/xml-entities.xml (original)
> +++ forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-
> b/xml-entities.xml Sun Mar  2 03:22:23 2008
> @@ -50,8 +50,11 @@
>  
>  
>You can supply lists of symbols for your own project too. Create a
> fresh
> -  site with 'forrest seed' and see the set
> -  src/documentation/resources/schema/symbols-project-
> v10.ent
> +  site with 'forrest seed' and see the set at the
> +  src/documentation/resources/schema/symbols-project-
> v10.ent file.
> +  Copy that file to your own projects at the same location. Also add
> the
> +  entry to your project xml catalog as shown in the seed site at
> +  src/documentation/resources/schema/catalog.xcat file.
>  
>  
>For example, use "&myp-t;" to represent the
> project name
> 
> Modified: forrest/trunk/main/webapp/resources/schema/catalog.forrest.xcat
> URL:
> http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/ca
> talog.forrest.xcat?rev=632740&r1=632739&r2=632740&view=diff
> ==
> 
> --- forrest/trunk/main/webapp/resources/schema/catalog.forrest.xcat
> (original)
> +++ forrest/trunk/main/webapp/resources/schema/catalog.forrest.xcat Sun
> Mar  2 03:22:23 2008
> @@ -52,6 +52,8 @@
>  
>  uri="entity/symbols-core-v10.ent"/>
> +   +uri="entity/symbols-project-v10.ent"/>
>  
>uri="entity/skinconf-common-plugins-07-1.xml"/>
> 
> Modified: forrest/trunk/main/webapp/resources/schema/entity/symbols-core-
> v10.ent
> URL:
> http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/en
> tity/symbols-core-v10.ent?rev=632740&r1=632739&r2=632740&view=diff
> ==
> 
> --- forrest/trunk/main/webapp/resources/schema/entity/symbols-core-v10.ent
> (original)
> +++ forrest/trunk/main/webapp/resources/schema/entity/symbols-core-v10.ent
> Sun Mar  2 03:22:23 2008
> @@ -20,5 +20,16 @@
> 

Call for Papers Opens for ApacheCon US 2008

[Gav....]

 
 Call for Papers Opens for ApacheCon US 2008
 
 !REMINDER: this will be a short CFP, ending on 3 April, so please be
 sure to get your CFP submissions in soon!
 
 The Apache Software Foundation (ASF) invites submissions to its official
 users' conference, ApacheCon US 2008, held 3 November through 7
 November, 2008 at the Sheraton New Orleans.  ApacheCon serves as a forum
 for showcasing the ASF's latest developments, including its projects,
 membership, and communities.  ApacheCon offers unparalleled educational
 opportunities, with dedicated presentations, hands-on trainings, and
 sessions that address core technology, development, business/marketing,
 and licensing issues in Open Source.
 
 The conference program includes competitively selected presentations,
 trainings/workshops, and a small number of invited speakers. All
 sessions undergo a peer review process by the ApacheCon Conference
 Planning team.
 
 With the great success of ApacheCon US 2007, we are excited to move to
 New Orleans in 2008.  We're proud to announce that we are going to
 intensify and deepen the pre-conference trainings by offering 2-day
 trainings alongside full- and half-day trainings, and each training
 session will have certifications of completion for those who fulfill all
 the requirements of the training.
 
 The ASF comprises some of the most active and recognized developers in
 the Open Source community.  By bringing together the pioneers,
 developers, and users of flagship Open Source technologies, ApacheCon
 provides an influential platform for dialogue, between the speaker and
 the audience, between project contributors and the community at large,
 traversing a wide range of ideas, expertise, and personalities.
 
 ApacheCon welcomes submissions from like-minded delegates across many
 fields, geographic locations, and areas of development.  Please note you
 do not need to be committer or project contributor at the ASF to submit
 a proposal!  The unique nature of the Apache community lends itself to
 creating a conference content that is not only the best of Open Source
 but cutting edge as well.
 
 Conference Themes and Topics
 
 * Apache HTTP server topics: installation, configuration, migration
 * ASF-wide projects such as, Jakarta, Tomcat, Maven, Geronimo,
   Harmony, Lucene, SpamAssassin, Portals, and Web Services
 * Scripting languages and dynamic content such as Java, Perl, Python,
   Ruby, XSL, and PHP
 * Security and e-commerce
 * Performance tuning, load balancing and high availability
 * New technologies and initiatives such as Web Services and Web 2.0
 * ASF-Incubated projects such as Abdera, CXF, and Qpid
 * Case studies and industry profiles demonstrating the use of Apache
   software
 * Open source community and business models, legal and marketing
   issues
 
 NOTE: Marketing-oriented submissions aimed at promoting specific
 organizations or products will not be accepted.
 
 
 Submission Guidelines
 
 Submissions must include title; speaker's name with affiliation and
 email address; format (Training vs. General Session) and duration
 (1-hour general session, or half-, full-day, or two-day training);
 expertise level (beginner to advanced); a full description including
 abstract and objectives (200 words or less);  intended audience and
 maximum number of participants, with background knowledge expected of
 the participants (Trainings only); and speaker bio (100 words or less).
   Full presentation and training materials will be due at a later
 date, as noted below.
 
 Types of Submissions: Trainings, General Sessions, Case Studies and
 Industry Profiles.
 
 Speakers whose proposals are accepted have registration fees waived,
 reasonable travel and part of their lodging expenses paid.  Only one
 speaker will be covered per accepted proposal.
 
 
 Important Dates
 
 Proposal submission deadline:  3  April, 2008 *Before* ApacheCon Europe!
 Notification of acceptance:25 April, 2008
 Materials for Web site:3  October, 2008
 Materials for Trainings:   17 October, 2008
 Conference Date:   Monday to Friday, 3-7 November 2008
 Trainings: Monday and Tuesday, 3-4 November 2008
 General Sessions:  Wednesday to Friday, 5-7 November 2008
 
 
 To submit your completed proposal, please follow the directions to logon
 here to the existing ApacheCon CFP system:
http://www.us.apachecon.com/us2008/
 
 Use your existing ApacheCon CFP login, or create a new one as needed.
 Then under ApacheCon US 2008 Status and Options, click the "Fill out a
 CFP form" link.
 
 If you are not yet subscribed to the ApacheCon announcement mailing
 list, send an email message to [EMAIL PROTECTED]
 
 
 About ApacheCon US 2008
 
 ApacheCon is co-produced by the Apache Software Foundation and Stone
 Circle Productions. The ApacheCon Planning team comprises ASF Members
 from all over the world working on a wholly-volunteer bas

RE: lost svn history for samples (Was: commit: r556367 [1/2])

[Gav....]

David,

> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 30 January 2008 2:49 PM
> To: dev@forrest.apache.org
> Subject: Re: lost svn history for samples (Was: commit: r556367 [1/2])
> 
> On Sat, Jul 21, 2007 David Crossley wrote:
> > Gav wrote:
> > > From: David Crossley
> > > >
> > > > Ooops. You should have used 'svn move'. This has now lost all
> > > > the svn history for those files.
> > >
> > > Welcome back :)
> > >
> > > Do you know, I did try and use 'svn move' but it would have
> > > none of it, several complaints of which I can't remember.
> >
> > If you have problems when commiting, then please discuss
> > it with your friends.
> >
> > > I suppose we could revert back before this commit and then try
> > > the svn move again ?
> >
> > Yes please. We connot afford to lose svn history.
> >
> > If you continue to have trouble, then one of the other
> > committers will need to help.
> >
> > > One file doesn't get moved but gets changed
> > > instead (index.xml) meaning we can't move that directory whole, each
> file
> > > would need to be done individually I think.
> >
> > There is always a way. Perhaps index.xml needs to be copied
> > and the others moved. Individually perhaps. It is trivial
> > to create a temporary shell script to do the individual
> > moves and copies. For example, use 'ls samples > temp.sh'
> > and vi to edit it into a shell script which performs a
> > list of 'svn mv' or 'svn cp' commands.
> 
> Done now. See https://issues.apache.org/jira/browse/FOR-1063

Wow, much work had to be done here, goes to show how a simple mistake
can blow out.
> 
> In future please do reverts promptly. It makes it more difficult
> to do it later.

Absolutely, I did try at the time, my svn foo not being up to scratch I
stuffed that up too.

Thanks for your hard work on this and correcting it all.

Gav...

> 
> -David
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.19.2 - Release Date: 1/12/2008
> 12:00 AM

Convert html site docs to xdoc etc

[Gav....]

Hi All,

Im helping a bit with getting stdcxx site converted to using Forrest.
The simple docs on the main part of the site are done.

Martin has asked if it is possible to convert other docs [1][2] so that
they can be integrated into the Forrest source xdoc format.

There is an awful lot of pages in those docs so an automated way to do this
would be great. Once converted to xdoc I guess after that it is a manual
process to put the pages into tabs.xml and site.xml etc.

The current 'new' site has been started and Martin has put it up in his own
area [3] as a sandbox until forrest deploy etc has been worked out.

Any ideas ?

Thanks

Gav...

[1] - http://stdcxx.apache.org/doc/stdlibref/index.html

[2] - http://stdcxx.apache.org/doc/stdlibug/index.html

[3] - http://people.apache.org/~sebor/stdcxx/forrest-site/

Using different Forrest Versions and Dispatcher

[Gav....]

Hi All,

Just wanted to double-check, I am using 0.9-dev, another Apache project
is playing with Forrest and is using 0.8.

Am I ok to implement the latest Dispatcher trunk ?

I want to use dispatcher and pelt theme initially, but want to be sure those
with 0.8 release will be able to use the newer changes ok.

Thanks

Gav...

RE: content-txt-link.ft query

[Gav....]

> -Original Message-
> From: Thorsten Scherler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 9 January 2008 10:18 PM
> To: dev@forrest.apache.org
> Subject: Re: content-txt-link.ft query
> 
> On Wed, 2008-01-09 at 21:32 +0900, Gav wrote:
> > Hi All,
> >
> > Taking a look at finishing off FOR-797 over the next few days.
> > I have done some, will commit all together. I can not get content-txt-
> link
> > to work however.
> >
> > content-pdf-link.ft works fine when called from pelt-
> html.content.panel.xml
> > but as soon as I include content-txt-link.ft in there I get :-
> >
> > " .. dispatcherError: 500 - Internal server error
> > The contract "content-txt-link" has thrown an exception by resolving the
> > implementation from "cocoon://resolve.contract.html.content-txt-link".
> >
> > dispatcherErrorStack:
> > org.apache.excalibur.source.SourceException: Exception during processing
> of
> > cocoon://resolve.contract.html.content-txt-link .. "
> >
> > When I look at resolve-contract.html I get
> >
> >
> >   Error 440
> >
> > 
> >
> >   Template not found. This functions is a fallback when no ft is
> found.
> > This
> >   is just a dummy, it will output *nothing*.
> >
> > etc..
> >
> > My updated content-txt-link.ft looks like :-
> 
> The above error tells me that it is a problem with resolving.
> 
> Where did you store the content-txt-link?

That's what I thought, I left it in its original place - in /common/html/
(I also copied themes/common/ into my local test project, so it is changed
in both the original plugin location and in the copied location. Maybe I'll
try moving it to pelt dir as that is the theme active, but it should really
be finding it where it is.

Thanks

Gav...

> 
> salu2
> 
> >
> >  >   xmlns:forrest="http://apache.org/forrest/templates/1.0";>
> >   
> > content-txt-link will output the TXT link with image to the content.
> >   
> >   
> > 
> >   
> >>   xmlns:forrest="http://apache.org/forrest/templates/1.0";
> >   name="content-txt-link" inputFormat="xsl" >
> >  > xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
> >   
> >> select="$defaultVariables/*/[EMAIL PROTECTED]'skin-img-dir']/@value"/>
> >> select="$defaultVariables/*/[EMAIL PROTECTED]'filename-noext']/@value"/
> >   
> > 
> >   
> >  > alt="TXT - icon" />
> > TXT
> >   
> > 
> >   
> > 
> >   
> > 
> >
> > I must have missed something ??
> >
> > Gav...
> --
> Thorsten Scherler thorsten.at.apache.org
> Open Source Java  consulting, training and solutions
> 
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.17.9 - Release Date: 12/25/2007
> 12:00 AM

content-txt-link.ft query

[Gav....]

Hi All,

Taking a look at finishing off FOR-797 over the next few days.
I have done some, will commit all together. I can not get content-txt-link
to work however.

content-pdf-link.ft works fine when called from pelt-html.content.panel.xml
but as soon as I include content-txt-link.ft in there I get :-

" .. dispatcherError: 500 - Internal server error
The contract "content-txt-link" has thrown an exception by resolving the
implementation from "cocoon://resolve.contract.html.content-txt-link".

dispatcherErrorStack:
org.apache.excalibur.source.SourceException: Exception during processing of
cocoon://resolve.contract.html.content-txt-link .. "

When I look at resolve-contract.html I get 


  Error 440
  


  Template not found. This functions is a fallback when no ft is found.
This
  is just a dummy, it will output *nothing*.

etc..

My updated content-txt-link.ft looks like :-

http://apache.org/forrest/templates/1.0";>
  
content-txt-link will output the TXT link with image to the content.
  
  

  
  http://apache.org/forrest/templates/1.0";
  name="content-txt-link" inputFormat="xsl" >
http://www.w3.org/1999/XSL/Transform";>
  
  
  

  

TXT
  

  

  


I must have missed something ??

Gav...

RE: svn commit: r609838 - /forrest/trunk/site-author/content/xdocs/zone.xml

[Gav....]

Thanks for doing this. I tried actually reverting the patch by going back to
the previous revision for this file, then SVN wouldn't let me commit it :(

I need to get a handle on reverting properly, only thing works for me at
present is overwriting and committing again, bit of a waste.

Gav...(on my way to redbean)

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 8 January 2008 11:27 AM
> To: [EMAIL PROTECTED]
> Subject: svn commit: r609838 - /forrest/trunk/site-
> author/content/xdocs/zone.xml
> 
> Author: crossley
> Date: Mon Jan  7 18:26:50 2008
> New Revision: 609838
> 
> URL: http://svn.apache.org/viewvc?rev=609838&view=rev
> Log:
> Revert changes to "source" sections from r602662.
> Re-add a note about our Apache httpd being managed by Solaris SMF (FOR-
> 940).
> 
> Modified:
> forrest/trunk/site-author/content/xdocs/zone.xml
> 
> Modified: forrest/trunk/site-author/content/xdocs/zone.xml
> URL: http://svn.apache.org/viewvc/forrest/trunk/site-
> author/content/xdocs/zone.xml?rev=609838&r1=609837&r2=609838&view=diff
> ==
> 
> --- forrest/trunk/site-author/content/xdocs/zone.xml (original)
> +++ forrest/trunk/site-author/content/xdocs/zone.xml Mon Jan  7 18:26:50
> 2008
> @@ -36,21 +36,31 @@
>  https://svn.apache.org/repos/asf/forrest/zone and
>  additional private stuff is in our pmc/forrest/zone SVN.
>
> -  
> +  
> +config
> +  
> +
> +  
>  creates /export/home/config ... $CONFIG
>  directories /forrestbot-*/ are the forrestbot homes, see below.
>  setenv*.sh ... these are sourced by the forrestbots and other
>cronjobs and user configs, to set the environment.
> -  
> -  
> +
> +  
> +htdocs
> +  
> +  
>  creates /var/apache2/htdocs ... $DOC_ROOT
>  directories /ft/ and /fts/ are the forrestbot config and results, see
> below.
> -  
> -  
> +
> +  
> +test-sources
> +  
> +  
>  A place to hold sources for various test sites.
>  Normally these would be in the relevant project's SVN.
>  Hold them here until building properly.
> -  
> +
>
>  All files are owned in the group "other" so any one of us can
>  edit/update. Make sure that your 'umask' is set properly so that
> new
> @@ -75,18 +85,33 @@
>  Various local software is installed in /export/opt/
> (not
>  managed with SVN) ...
>
> +  
> +Our Apache httpd server is managed using
> +http://www.apache.org/dev/solaris-
> zones.html#apache2_smf">Solaris SMF
> +
> +   so should always come back up automatically after a failure or
> machine reboot.
> +  
>
>  Forrest
> -
> +
> +  forrest-trunk
> +
> +
>  svn checkout of trunk.
>  automatically 'svn update' and 'build' via cron: $CONFIG/update-forrest-
> trunk.sh
> -
> -
> +
> +
> +  forrest-trunk-stable
> +
> +
>  svn checkout of trunk, manually updated as needed.
> -
> -
> +
> +
> +  forrest-release
> +
> +
>  svn checkout of current release branch, manually updated as needed.
> -
> +
>  
>To manually update -stable or -release do this:
>  
> @@ -107,17 +132,23 @@
>  There are various forrestbots operating with different versions
> of
>  forrest. Their home is at $CONFIG
>
> -  
> +  
> +$CONFIG/forrestbot-trunk
> +  
> +  
>  forrestbot operating with trunk.
>  builds various sites automatically, triggered via cron.
>  Configuration files and the generated results are at $DOC_ROOT/ft/
>  FIXME: The web interface is coming soon.
> -  
> -  
> +
> +  
> +$CONFIG/forrestbot-trunk-stable
> +  
> +  
>  forrestbot operating with trunk-stable.
>  builds various sites, only runs when needed, triggered via cron.
>  Configuration files and the generated results are at $DOC_ROOT/fts/
> -  
> +
>
>  Forrestbot logs are at $CONFIG/forrestbot-trunk*/logs/ and old
> ones are
>  cleaned up by the crontab. There is also a log file for each site
> that
> @@ -160,12 +191,7 @@
>  Keep an occasional eye on $CONFIG/update-forrest-trunk.log This
> is
>  the output of the cronjob to do svn update to

RE: svn commit: r602662 - /forrest/trunk/site-author/content/xdocs/zone.xml

[Gav....]

> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 13 December 2007 9:11 AM
> To: Forrest Developers List
> Subject: Re: svn commit: r602662 - /forrest/trunk/site-
> author/content/xdocs/zone.xml
> 
> Those "source" elements were deliberate to give some structure to the
> text,
> e.g. the first one has three separate lines. Changing them to "notes"
> loses that structure.

I realized that, and that it was supposed to be a temporary fix. However I
misunderstood the FIXME contained within, and assumed it was waiting for
'notes' to come along, which it has. What it actually means is that it is
waiting for notes to be improved.

So what to do now, shall I convert those back to , just leaving my
actual text changes further down, or talk about what you want doing to
notes, so we can perhaps add bullet points or whatever to the notes element
in the DTD.

Gav...(happy to do either)

> 
> -David
> 
> > Author: gmcdonald
> > Date: Sun Dec  9 03:42:55 2007
> > New Revision: 602662
> >
> > URL: http://svn.apache.org/viewvc?rev=602662&view=rev
> > Log:
> > As per the FIXME, changed to using the note class, also updated the zone
> SMF config information, fixes FOR-940
> >
> > Modified:
> > forrest/trunk/site-author/content/xdocs/zone.xml
> >
> > Modified: forrest/trunk/site-author/content/xdocs/zone.xml
> > URL: http://svn.apache.org/viewvc/forrest/trunk/site-
> author/content/xdocs/zone.xml?rev=602662&r1=602661&r2=602662&view=diff
> >
> ==
> 
> > --- forrest/trunk/site-author/content/xdocs/zone.xml (original)
> > +++ forrest/trunk/site-author/content/xdocs/zone.xml Sun Dec  9 03:42:55
> 2007
> > @@ -36,31 +36,21 @@
> >  https://svn.apache.org/repos/asf/forrest/zone and
> >  additional private stuff is in our pmc/forrest/zone SVN.
> >
> > -  
> > -config
> > -  
> > -
> > -  
> > +  
> >  creates /export/home/config ... $CONFIG
> >  directories /forrestbot-*/ are the forrestbot homes, see below.
> >  setenv*.sh ... these are sourced by the forrestbots and other
> >cronjobs and user configs, to set the environment.
> > -
> > -  
> > -htdocs
> > -  
> > -  
> > +  
> > +  
> >  creates /var/apache2/htdocs ... $DOC_ROOT
> >  directories /ft/ and /fts/ are the forrestbot config and results, see
> below.
> > -
> > -  
> > -test-sources
> > -  
> > -  
> > +  
> > +  
> >  A place to hold sources for various test sites.
> >  Normally these would be in the relevant project's SVN.
> >  Hold them here until building properly.
> > -
> > +  
> >
> >  All files are owned in the group "other" so any one of us can
> >  edit/update. Make sure that your 'umask' is set properly so
> that new
> > @@ -87,25 +77,16 @@
> >
> >
> >  Forrest
> > -
> > -  forrest-trunk
> > -
> > -
> > +
> >  svn checkout of trunk.
> >  automatically 'svn update' and 'build' via cron: $CONFIG/update-
> forrest-trunk.sh
> > -
> > -
> > -  forrest-trunk-stable
> > -
> > -
> > +
> > +
> >  svn checkout of trunk, manually updated as needed.
> > -
> > -
> > -  forrest-release
> > -
> > -
> > +
> > +
> >  svn checkout of current release branch, manually updated as needed.
> > -
> > +
> >  
> >To manually update -stable or -release do this:
> >  
> > @@ -126,23 +107,17 @@
> >  There are various forrestbots operating with different versions
> of
> >  forrest. Their home is at $CONFIG
> >
> > -  
> > -$CONFIG/forrestbot-trunk
> > -  
> > -  
> > +  
> >  forrestbot operating with trunk.
> >  builds various sites automatically, triggered via cron.
> >  Configuration files and the generated results are at $DOC_ROOT/ft/
> >  FIXME: The web interface is coming soon.
> > -
> > -  
> > -$CONFIG/forrestbot-trunk-stable
> > -  
> > -  
> > +  
> > +  
> >  forrestbot oper

RE: [jira] Updated: (FOR-1034) SKOS Plugin - Update 20070802

[Gav....]

Thanks Sina, I should be able to test and commit over the next couple of
days.

Cheers

Gav...

> -Original Message-
> From: Sina K. Heshmati (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Monday, 10 December 2007 9:35 PM
> To: dev@forrest.apache.org
> Subject: [jira] Updated: (FOR-1034) SKOS Plugin - Update 20070802
> 
> 
>  [ https://issues.apache.org/jira/browse/FOR-
> 1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Sina K. Heshmati updated FOR-1034:
> --
> 
> Attachment: skos-20071210-03.tar.gz
> skos-20071210-03.patch
> 
> Thank you Gavin for the follow-up and sorry for the delay!
> 
> In addition to the diff file, I made an archive of the newly created files
> that you could extract in $FORREST_HOME. Here [1] is an instance of the
> plugin that I just built.
> 
> Sina
> 
> [1] http://sina.khakbaz.com/2007/forrest-skos/
> 
> > SKOS Plugin - Update 20070802
> > -
> >
> > Key: FOR-1034
> > URL: https://issues.apache.org/jira/browse/FOR-1034
> > Project: Forrest
> >  Issue Type: Improvement
> >  Components: Plugin: input.skos
> >Affects Versions: 0.9-dev
> >Reporter: Sina K. Heshmati
> >Assignee: Ross Gardler
> >Priority: Minor
> > Fix For: 0.9-dev
> >
> > Attachments: apache-forrest-skos-20070820.patch, apache-forrest-
> skos-20070820.tar.gz, apache-forrest-skos-20070820.tar.gz, skos-20070802-
> 01.patch, skos-20070802-02.tar.gz, skos-20071210-03.patch, skos-20071210-
> 03.tar.gz
> >
> >
> > * Switched to use Dispatcher as the rendering engine.
> > * Added glossary samples published by W3C.
> > * Tabs in source files are removed (thanks to David for pointing out).
> 
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

RE: Unreleased Coccon Code in Forrest 0.8

[Gav....]

Sorry Ferdinand for my late input here,

> -Original Message-
> From: Ferdinand Soethe [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 1 December 2007 6:50 PM
> To: dev@forrest.apache.org
> Subject: Unreleased Coccon Code in Forrest 0.8
> 
> An Apache colleague looking at Forrest 0.8 just noticed that
> we have used unreleased Cocoon Code in our release and told
> me that this is not longer permitted.

Is this 'unreleased code' in a public SVN, in trunk or a branch etc ?
Is the code covered by i/CLAs, in other words was the code written and
committed and covered by an iCLA. If yes then surely any Apache project is
covered here. It matters not that it was released or not by Cocoon, that
only proves that Cocoon PMC endorse it as part of their release. What
matters is that it is open source code under the Apache 2.0 license and
that when we released it as part of our official release then the Forrest
PMC endorsed it.

Another example, if someone wanted to take some of Forrests code, either
released or from trunk, as long as they adhere to the Apache 2.0 license,
surely they can do so?

I'd like to see where it says 'this is no longer permitted' before I change
my mind :)

> 
> Do we need top change our release procedures to avoid that
> in the future?
> 

No, I don't think we do, sure we can tighten up and make sure we are using
code under the license correctly, but I see no reason why we can not take
unreleased code and incorporate it.

One last thought came to mind though (which may contradict some of what I
say above, we'll see) , if Cocoon are not endorsing code that we are using,
then mentioning the name 'Cocoon' in that code or in the package name may
imply that Cocoon too endorse that code, we may therefore need to remove any
Cocoon references and repackage it as a Forrest lib etc or whatever. That
may end up being harder than it sounds.

Gav...


> 
> 
> Take care,
> Ferdinand

RE: svn commit: r602293 - /forrest/trunk/site-author/content/xdocs/live-sites.xml

[Gav....]

To explain this, rather than alter our previous DTDs, I'll upgrade any
xdocs to the latest 2.0 that need any rel="nofollow" adding to any
links. I think this is probably the best approach. If no objections I'll
continue this method and do the rest that I find in one commit.

Gav...

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 8 December 2007 10:52 AM
> To: [EMAIL PROTECTED]
> Subject: svn commit: r602293 - /forrest/trunk/site-
> author/content/xdocs/live-sites.xml
> 
> Author: gmcdonald
> Date: Fri Dec  7 17:51:59 2007
> New Revision: 602293
> 
> URL: http://svn.apache.org/viewvc?rev=602293&view=rev
> Log:
> Upgrade xdoc to document v2.0, alter to suit and add rel=nofollow as
> appropriate
> 
> Modified:
> forrest/trunk/site-author/content/xdocs/live-sites.xml
> 
> Modified: forrest/trunk/site-author/content/xdocs/live-sites.xml
> URL: http://svn.apache.org/viewvc/forrest/trunk/site-
> author/content/xdocs/live-
> sites.xml?rev=602293&r1=602292&r2=602293&view=diff
> ==
> 
> --- forrest/trunk/site-author/content/xdocs/live-sites.xml (original)
> +++ forrest/trunk/site-author/content/xdocs/live-sites.xml Fri Dec  7
> 17:51:59 2007
> @@ -15,7 +15,8 @@
>See the License for the specific language governing permissions and
>limitations under the License.
>  -->
> - "http://forrest.apache.org/dtd/document-v12.dtd";>
> + +"http://forrest.apache.org/dtd/document-v20.dtd";>
>  
>
>  Examples Built-With-Forrest
> @@ -27,8 +28,8 @@
>  
>  
>If you want your site added to the list, then please send a request
> to the
> -  mailing lists or to the
> -  Issue tracker. Tell us the URL, Name,
> and
> +  mailing lists or to the
> +  Issue tracker. Tell us the URL, Name, and
>catch-phrase.
>  
>  
> @@ -40,130 +41,130 @@
>  section for some examples of such sites.
>
>
> -Apache XML Project
> (xml.apache.org)
> -Apache Forrest
> -Apache Cocoon
> -Apache Lenya
> -http://aft.sourceforge.net/";>Anteater -
> Ant-based functional testing
> -http://chaperon.sourceforge.net";>Chaperon
> - text parser
> - href="http://www.iasandcb.pe.kr/3g/";>IAS&CB
> -Some  href="http://www.apache.org/~coar/people.html";>Apache
> -Committer personal pages
> -Apache FOP
> +Apache XML Project
> (xml.apache.org)
> +Apache Forrest
> +Apache Cocoon
> +Apache Lenya
> +http://aft.sourceforge.net/";
> rel="nofollow">Anteater - Ant-based functional testing
> +http://chaperon.sourceforge.net";
> rel="nofollow">Chaperon - text parser
> +http://www.iasandcb.pe.kr/3g/";
> rel="nofollow">IAS&CB
> +Some http://www.apache.org/~coar/people.html";>Apache
> +Committer personal pages
> +Apache FOP
>  (Formatting Objects Processor)
> -http://www.dream-models.com/";>Dream Models
> +http://www.dream-models.com/"; rel="nofollow">Dream
> Models
>  - gather information about electric radio controlled
> helicopters
> - href="http://people.apache.org/~vgritsenko/stats/";>Apache Stats (Vadim's
> Home Page) - some web statistics
> -http://www.indexgeo.net/zalarm/";>Z-alarm - Ensure
> -information server integrity
> -http://jakarta.apache.org/poi/";>Apache Jakarta
> POI
> -http://terra-intl.com/";>Terra-International, Inc.
> (Japanese)
> -http://jakarta.terra-intl.com/poi/";>Apache
> Jakarta POI (Japanese Translation)
> -http://xfp.sourceforge.net/";>XFP -
> eXtensible Filtering Pipelines
> - href="http://www.atlassian.com/software/jira/docs/latest";>JIRA bugtracker
> documentation
> - href="http://www.phpopentracker.de/";>phpOpenTracker - A framework
> solution for the analysis of website traffic and visitor analysis
> -http://ws.apache.org/";>Apache Web Services
> Project
> -http://ws.apache.org/wsif/";>Apache WSIF
> Project - Web Services Invocation Framework
> -http://xml.apache.org/xmlbeans/";>Apache
> XMLBeans - An XML-Java binding tool
> -http://druid.sourceforge.net/";>Druid: The
> Database Manager - GUI tool to create datab

RE: rel not in DTD

[Gav....]

Thanks guys for your replies.

See svn I have added in just the rel attribute, there were more that looked
useful but if we need them we can add them as and when - like this one.

There were 2 possible places I saw in the v2.0 DTD, it seemed appropriate
where it has ended up, rather than just restrict rel to the 'a' element.

I also made a start on adding rel="nofollow" , to just the thanks page so
far, but there are many more with external links to programs that we use so
will go through those over the next few days. 

Gav...

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Ross Gardler
> Sent: Tuesday, 6 November 2007 10:22 PM
> To: dev@forrest.apache.org
> Subject: Re: rel not in DTD
> 
> Our standing position on the DTD's is that if it is in the XHTML2
> subset we intend to [err... well... err...]  use(?)  then it can go
> in.
> 
> So I say go for it.
> 
> Ross

RE: rel not in DTD

[Gav....]

> -Original Message-
> From: Thorsten Scherler [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 6 November 2007 8:28 PM
> To: dev@forrest.apache.org
> Subject: Re: rel not in DTD
> 
> On Tue, 2007-11-06 at 19:54 +0900, Gav wrote:
> > Apologies if I'm missing something obvious here, but the attribute 'rel'
> > that belongs to element 'a' is not in our v1.3 or 2.0 DTDs.
> 
> http://forrest.apache.org/dtdx/document-v13.html
> http://forrest.apache.org/dtdx/document-v20.html
> 
> Search for fork.

Thanks Thorsten, but I don't see how that is relevant to what I am trying to
do.

Consider :-

http://www.example.com> Example.com 

In some cases to stop search engines following the link, giving it ranking
points etc we need to be outputting instead :

http://www.example.com rel="nofollow"> Example.com 

W3C specify this in html 4.01 through to current proposed xhtml2

http://www.w3.org/TR/html401/struct/links.html#edef-A
http://www.w3.org/TR/xhtml2/xhtml2-doctype.html

The value of rel="" can be many things, search engines decided that if it
contained "nofollow" then no weightings would be applied to the link and
it would not be spidered out from that point.

See also http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

There are also other attributes missing from our DTD, which makes me wonder
if I missed a point somewhere, or maybe just because a documentation
framework such as Forrest minimized and left out those that more than likely
would not be used.

Gav...

> 
> salu2
> 
> >
> > Therefore Forrest and any other site can not use rel="follow" without
> > breaking the DTD and therefore a site build.
> >
> > Should we add this to the DTD - this would affect 0.8 and 0.9 users
> which
> > I think is fine and probably necessary.
> >
> > Or is there another approach to this?
> >
> > Gav...
> --
> Thorsten Scherler thorsten.at.apache.org
> Open Source Java  consulting, training and solutions

rel not in DTD

[Gav....]

Apologies if I'm missing something obvious here, but the attribute 'rel'
that belongs to element 'a' is not in our v1.3 or 2.0 DTDs.

Therefore Forrest and any other site can not use rel="follow" without
breaking the DTD and therefore a site build.

Should we add this to the DTD - this would affect 0.8 and 0.9 users which
I think is fine and probably necessary.

Or is there another approach to this?

Gav...

RE: projectInfo plugin property changes

[Gav....]

Not sure how successful or not it was at this stage, but I tried to deploy
it :-

checkout-deployed-docs:

deploy-docs:
 [echo] Deploying plugin documentation to the web server
 [copy] Copying 95 files to
D:\Apache2\forrest\build\svn-plugin-docs-deploy\
plugins_0_80\org.apache.forrest.plugin.input.projectInfo
 [exec] svn: warning:
'plugins_0_80\org.apache.forrest.plugin.input.projectI
nfo\skin\print.css' is already under version control
 [exec] svn: warning:
'plugins_0_80\org.apache.forrest.plugin.input.projectI
nfo\skin\screen.css' is already under version control
 [exec] A  (bin)
plugins_0_80\org.apache.forrest.plugin.input.projectInfo\s
kin\images\Thumbs.db

deploy:
 [echo] Deploying unversioned plugin
org.apache.forrest.plugin.input.project
Info to the download server
 [copy] Copying 1 file to
D:\Apache2\forrest\build\svn-plugins-deploy\0.8
 [copy] Copying 1 file to D:\Apache2\forrest\build\svn-plugins-deploy

updateSVN:
 [exec] svn: warning:
'0.8\org.apache.forrest.plugin.input.projectInfo.zip'
is already under version control
 [exec] svn: warning: 'org.apache.forrest.plugin.input.projectInfo.zip'
is a
lready under version control

Off to work, so will take a look later.

Gav...

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Ross Gardler
> Sent: Thursday, 25 October 2007 6:14 AM
> To: dev@forrest.apache.org
> Cc: Ross Gardler
> Subject: Re: projectInfo plugin property changes
> 
> On 24/10/2007, Ross Gardler <[EMAIL PROTECTED]> wrote:
> > On 24/10/2007, David Crossley <[EMAIL PROTECTED]> wrote:
> 
> ...
> 
> > Thanks for the nudge. I fixed this now. next Cocoon Docs build should
> work.
> 
> Correction, I have fixed this in SVN, however, due to the fact that I
> am currently working on an old Windows 2000 machine I can't do "and
> deploy" of the projectInfo plugin (weird dos errors)
> 
> I'm going to bed now. If anyone is so inclined please do:
> 
> cd $FORREST_HOME
> svn up
> cd plugins/org.apache.forrest.plugins.input.prinectInfo
> ant deploy
> 
> I'm on a machine tomorrow that will handle the deployment, so if noone
> has done it I will do so.
> 
> Ross

RE: [jira] Commented: (FOR-813) 'Forrest run' as Windows Service

[Gav....]

> -Original Message-
> From: Gavin (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 16 October 2007 7:51 PM
> To: dev@forrest.apache.org
> Subject: [jira] Commented: (FOR-813) 'Forrest run' as Windows Service
> 
> 
> [ https://issues.apache.org/jira/browse/FOR-
> 813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel#action_12535229 ]
> 
> Gavin commented on FOR-813:
> ---
> 
> Ok, the license is fine for this.

Now that is sorted, we need to revisit the issue.

What is the consensus from current devs, do we want to persue this
and add it in to our distribution (in /tools/ maybe).

I'd like to know so that the next step of testing it out on Forrest
can be done.

Thanks

Gav...

> 
> > 'Forrest run' as Windows Service
> > 
> >
> > Key: FOR-813
> > URL: https://issues.apache.org/jira/browse/FOR-813
> > Project: Forrest
> >  Issue Type: New Feature
> >  Components: Launch 'forrest run'
> >Affects Versions: 0.7, 0.8
> >Reporter: Johannes Schaefer
> >Assignee: Johannes Schaefer
> >Priority: Minor
> > Attachments: wrapper_license.txt
> >
> >
> > Up to now Forrest has to run in a command window on Windows
> > using 'forrest run'. For Server Operation this is not acceptable, so,
> > Forrest hasa to run as a Windows (Win32, WinNT) Service.
> > Jetty may run as such a Service using a wrapper, e.g.
> > "... the java wrapper provided by http://wrapper.tanukisoftware.org
> >   to provide jetty as an Win32 service."
> > (from jetty-4.2.25\extra\win32\readme.txt)
> 
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

RE: [jira] Commented: (FOR-1047) Add Documentation For Using Debian Update Alternatives System To Set Up The Forrest Environment

[Gav....]

> -Original Message-
> From: Ross Gardler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 3 October 2007 6:05 PM
> To: dev@forrest.apache.org
> Subject: Re: [jira] Commented: (FOR-1047) Add Documentation For Using
> Debian Update Alternatives System To Set Up The Forrest Environment
> 
> Brian M Dube wrote:
> > Gavin (JIRA) wrote:
> >> [
> >> https://issues.apache.org/jira/browse/FOR-
> 1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel#action_12530310
> >> ]
> >> Gavin commented on FOR-1047:
> >> 
> >>
> >> This looks good thanks, I suspect maybe we do not have any devs using
> >> Debian to confirm all this works so we might have to trust your
> >> judgment on this. If no one objects in the meantime, I will add this
> >> in a few days.
> >
> > I use Debian and I can confirm the Debian alternatives system exists.
> >
> > Do we need (to maintain) this? This is a Debian feature which is
> > documented by Debian. It is beyond our control and it may change.
> 
> Perhaps a pointer to their docs would be better?

We have Forrest specific commands on that page for various OS's, just
as likely to change and/or deprecation as the Debian one provided.

I think a link to the docs at
http://www.debian.org/doc/FAQ/ch-customizing.en.html (Debian does not have
good docs it seems) and a
mention of the specific Forrest command is a good compromise, will leave
out the rest that can be gleaned from Debian docs.

Something like :

* For systems that use the Debian update-alternatives system:

To install a Forrest entry, first, gather the path to Forrest's executable,
and also note its version. In this example, Forrest has been unpacked and
placed into '/opt/Apache/apache-forrest-0.8' (the executable is at
bin/forrest). Then execute this command (here we use sudo to execute
update-alternatives with root privileges):

sudo update-alternatives --install /usr/bin/forrest forrest
'/opt/Apache/apache-forrest-0.8/bin/forrest' 800

For more specific documentation on Debian's update-alternatives see
http://www.debian.org/doc/FAQ/ch-customizing.en.html



Gav...

> 
> Ross
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.487 / Virus Database: 269.13.22 - Release Date: 9/17/2007
> 12:00 AM

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

[Gav....]

Here is my summary of why these issues remain outstanding/unpatched
and my position on them.

> Key Summary
> FOR-1034SKOS Plugin - Update 20070802
> https://issues.apache.org/jira/browse/FOR-1034

I have tried working with it but the latest patches don't work for me.
I am happy to apply it once I get an updated patch file - others may
want to give the new patches a try as is, it may work for others on
linux maybe I don't know.

> FOR-998 [PATCH] Resolve empty cells.
> https://issues.apache.org/jira/browse/FOR-998

I am unsure as to the purpose of the patch and so possibly I misunderstand
its intention. My understanding of missing spaces table is to emphasise what
happens if you don't include empty cell entries. The patch seems to work
around the empty cell entries on the table that does not require them due to
the nature of being an example of what happens when they are missing.

I would like others opinions as to the validity of the patch and whether or
not it should be applied. I'll be happy to apply it if others agree.

> FOR-934 i18n language override menu
> https://issues.apache.org/jira/browse/FOR-934

I have not fully investigated the implications of this, perhaps Sjur or
someone else could revisit it.

> FOR-905 Recent change in cygwin appears to prevent the classpath for
> loop in the forrest command from working
> https://issues.apache.org/jira/browse/FOR-905

I do not use Cygwin for anything other than applying patches, I have
commented on the issue though. Someone else who uses cygwin with forrest
needs to investigate.

> FOR-795 Navigation bars for easy access in long documents
> https://issues.apache.org/jira/browse/FOR-795

I agree with Ross' comments that it would be very useful. The patch is built
against 0.6/0.7 so would need updating and reworking for 0.9 I guess.

> FOR-752 Forrestbot "build" workstage creates spurious
> "build/webapp/WEB-INF/logs" directory

No more comment to make than is already in the Issue, if no-one wants to
enhance the patch then it could be applied as is. I am in the same boat as
Matthieu here, I don't fully understand if there will be further
consequences as a result of applying the patch. If others comment that it is
fine as is then I can apply it if others have no time, just let me know.

> https://issues.apache.org/jira/browse/FOR-752
> FOR-652 CSS Style Sheets need cleanup, optimization and better naming
> of elements

I have assigned this to myself and will work on it soon.

> https://issues.apache.org/jira/browse/FOR-652
> FOR-635 images not reliably reproduced in PDFs
> https://issues.apache.org/jira/browse/FOR-635

I have tried and failed on this one, Ross has had more success I think. I
will be leaving this one to someone else. I have removed the patch available
as it does not solve the problem.

> FOR-412 use CSS for displaying list of Changes
> https://issues.apache.org/jira/browse/FOR-412

This has been revisited, the patch and issue now rely on Issue FOR-970 if
that is a viable option.

> FOR-355 Improved PDF configurability (e.g., TOC, Page Numbers, logo)
> https://issues.apache.org/jira/browse/FOR-355

This has been worked on recently and is getting close to being finished.

> FOR-311 OOo Headings bug causes Forrest to fail
> https://issues.apache.org/jira/browse/FOR-311

I don't use OpenOffice. Clay Leeds has done an awful lot to this as have
others, not sure how much more is left to do.

> FOR-280 gather index terms from documents to create index page with
> links
> https://issues.apache.org/jira/browse/FOR-280

This still looks interesting to me and will look at it again when I can.

Gav...

RE: faq-to-document.xsl

[Gav....]

In addition, your 1.2 docs faq shows a ToC, just your 2.0 does not.

http://lenya.apache.org/docs/1_2_x/how-to/faq.html


Gav...

> -Original Message-
> From: Gav [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 23 August 2007 7:50 AM
> To: dev@forrest.apache.org
> Subject: RE: faq-to-document.xsl
> 
> Hi Thorsten,
> 
> Needs more investigation I think.
> 
> Our FAQ [1] has a ToC and works just fine.
> 
> Gav...
> 
> [1] - http://forrest.apache.org/docs_0_90/faq.html
> 
> 
> 
> > -Original Message-
> > From: Thorsten Scherler
> [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, 22 August 2007 9:15 PM
> > To: dev@forrest.apache.org
> > Subject: faq-to-document.xsl
> >
> > Hi all,
> >
> > the http://issues.apache.org/bugzilla/show_bug.cgi?id=42350 is caused by
> > the faq-to-document.xsl:
> > ...
> > 
> > 
> >   Questions
> >   
> > 
> >   
> > ...
> >
> > This causes only one level 1 section:
> > 
> > 
> > 
> > ...
> >
> > But if one configures the skinconf toc @min-sections to 2 then it
> results
> > in the above bug.
> >
> > I would like to patch it the following way:
> > -
> > -  Questions
> > -  
> > -
> > +
> >
> > Did I miss something or can I go ahead and change the code?
> >
> > salu2
> > --
> > Thorsten Scherler thorsten.at.apache.org
> > Open Source Java  consulting, training and solutions
> >
> >
> > --
> > Internal Virus Database is out-of-date.
> > Checked by AVG Free Edition.
> > Version: 7.5.476 / Virus Database: 269.11.2/933 - Release Date: 8/2/2007
> > 2:22 PM
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.11.2/933 - Release Date: 8/2/2007
> 2:22 PM

RE: faq-to-document.xsl

[Gav....]

Hi Thorsten,

Needs more investigation I think.

Our FAQ [1] has a ToC and works just fine.

Gav...

[1] - http://forrest.apache.org/docs_0_90/faq.html



> -Original Message-
> From: Thorsten Scherler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 22 August 2007 9:15 PM
> To: dev@forrest.apache.org
> Subject: faq-to-document.xsl
> 
> Hi all,
> 
> the http://issues.apache.org/bugzilla/show_bug.cgi?id=42350 is caused by
> the faq-to-document.xsl:
> ...
> 
> 
>   Questions
>   
> 
>   
> ...
> 
> This causes only one level 1 section:
> 
> 
> 
> ...
> 
> But if one configures the skinconf toc @min-sections to 2 then it results
> in the above bug.
> 
> I would like to patch it the following way:
> -
> -  Questions
> -  
> -
> +
> 
> Did I miss something or can I go ahead and change the code?
> 
> salu2
> --
> Thorsten Scherler thorsten.at.apache.org
> Open Source Java  consulting, training and solutions
> 
> 
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.11.2/933 - Release Date: 8/2/2007
> 2:22 PM

RE: lost svn history for samples (Was: commit: r556367 [1/2])

[Gav....]

> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]
> Sent: Monday, 23 July 2007 6:55 AM
> To: dev@forrest.apache.org
> Subject: Re: lost svn history for samples (Was: commit: r556367 [1/2])
> 
> Gav wrote:
> >
> > Ok, someone then had better let me know the best way to revert trunk
> back
> > so I don't bu&&er up the history again.
> >
> > I know I can revert my local changes back to before, but then should I
> > commit that, then make make new changes with svn:move then commit again
> ?
> > Is that the best way to approach it ?
> 
> That should work.
> 
> -David

Apologies for the delay in reverting MOTD stuff.

I now want to be sure that what I need to do is correct so I don't bugger it
up again.

I need to revert my copy of the entire /fresh-site/ to r556365

Then commit
Then publish site docs again
Then start again with my changes using svn move etc..

Does that sound about right

I will make time to do this over the weekend.

Gav...

GSoC Code Deadline

[Gav....]

To our two students Oshani and Sina,

I am sure you are well aware, but as a timely reminder
and to inform the rest of the list, the deadline for 
uploading code to google is August 20th - that's 5 DAYS
to go from now !!

As Mentors, myself and Ross have until August 31st to evaluate code
that you provide here by 20th August (we may have an allowance of
1 or 2 days at most) so anything posted after that date will not
be able to be part of the evaluation.

Thank you both for your contributions so far.


Gav...

POssible DOAP additions ?

[Gav....]

I believe it was Thorsten that introduced us to the delights of
www.ohloh.net - I find the information there very interesting
and always take at least a weekly look at what shows up about Forrest
stats, and also other projects there.

I do not think it is a flash in the pan site and will become more
than it is now in collecting and delivering cvs/svn/committer stats.

I saw a message that they are creating an API for it [1] and in
particular this caught my eye ...

"...So far, we are planning on creating a REST API on top of ohloh, enabling
the ability get information on projects, accounts, stacks, etc... We would
support XML and JSON out/in and also require a free API key that would limit
the number of requests a day (to keep our servers reponsive).

What could one do with this?

I'm hoping you tell us. Off the top of my head, I imagine people might want
to

* track who has kudo'd them
* write a doap converter
* resurface project analytics into their own websites
* enrich a user identity with Ohloh stats
* derive your own data, like what is the most popular language in the
UK?

While we're still designing this feature, now is the time to pipe up and
provide feedback and concerns. Thanks in advance!..."

So , question is, is there an interest in leveraging ohloh information into
a plugin, either extend existing DOAP, or something else ?

If we get an interest, I'd like to supply an approved reply to that thread.

Gav...

[1] - http://www.ohloh.net/blog/ohloh_api#posts-2044

RE: svn commit: r565204 - in /forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.foaf: ./ resources/stylesheets/ src/documentation/content/xdocs/

[Gav....]

> -Original Message-
> From: Brian M Dube [mailto:[EMAIL PROTECTED]
> Sent: Monday, 13 August 2007 2:35 PM
> To: dev@forrest.apache.org
> Subject: Re: svn commit: r565204 - in
> /forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.foaf: ./
> resources/stylesheets/ src/documentation/content/xdocs/
> 
> Oshani Seneviratne wrote:
> > Hi,
> >
> > There are 2 other files: "resources/stylesheets/foaf-to-index.xsl" and
> > "src/documentation/content/xdocs/samples/foafIndex.xml" in the patch I
> > submitted for FOR-1020 [1].
> >
> > [1] https://issues.apache.org/jira/secure/attachment/12363666/FOR-
> 1020_12082007.patch
> >
> > Those files need to be added to the svn in addition to the following
> > updates, as they are required to get the plugin working as expected.
> >
> > Please advice if I need to do any changes here or if you need a new
> patch.
> 
> These have now been added. Thanks.
> 
> Brian

Thanks for applying Brian, don't know how I missed that.
I applied that patch, tested, did svn diff, svn ci but missed
that I had to do svn add on two of the files. Cheers

Gav...

RE: GSoC work on plugins

[Gav....]

> -Original Message-
> From: Oshani Seneviratne [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 9 August 2007 5:24 PM
> To: dev@forrest.apache.org
> Subject: Re: GSoC work on plugins
> 
> Hi,
> 
> On 8/9/07, Gav <[EMAIL PROTECTED]> wrote:
> > This is for Oshani bur the rest of the list need to know what is
> happening ,
> >
> > Oshani, you have been absent from this list for nearly a month, a
> private
> > mail I sent you two weeks ago (giving you the opportunity to reply in
> > private) has gone unanswered.
> >
> > Here is the situation.
> >
> > FOAF plugin needs completing - this was due on your own timeline of July
> > 9th. You explained to me reasons for this and I accepted them. You
> assured
> > me you would get back on track.
> 
> 
> Apologies for being absent from the list. And thanks for the extra push.
> 
> >
> > Here is what I propose you do :-
> >
> > 1. Take a look at and solve issues FOR-1008 and FOR-1020. Send in
> separate
> > patches for the issues so I can test and apply them easily and timely.
> 
>  Will do.
> 
> 
> > What else needs to be done to complete FOAF plugin ?
> 
> Well, sometime back Ross put the suggestion of making the DOAP plugin
> use the FOAF plugin to render the FOAF info in DOAP files [1].
> 
> [1] http://marc.info/?l=forrest-dev&m=118113739206310&w=2
> 
> I would like to give a try at this, but at the moment I am exactly not
> sure how this could be done! This was not in the original proposal,
> but I think it would be really useful for Forrest.

Yes, I agree it would be useful. However there are hurdles in the way
of getting it working properly - at least in terms of GSoC deadlines.

If you are still interested in doing this after GSoC has finished, I
think that would be great and you will of course get whatever help is
needed. The dependency between plugins is probably the only major
hurdle that has not been done before.

> 
> 
> > 2. Create the DOAC plugin and submit the code as a patch.
> > 3. Complete the DOAC plugin.
> >
> > Thoroughly test with lots of examples the FOAF and DOAC plugins.
> >
> > IF you have time after that, being the hCalendar plugin.
> >
> > You need to start doing this now - I do not want to see a last minute
> rush
> > of code submitted just before the deadline.
> >
> 
> Thank you very much for the revised proposal on my behalf. I will try
> my best to complete it on time.
> 
> Oshani

No problem, it is a suggested revised proposal, if you are happy with it
then great, you are of course welcome to submit your own. With the time
we have left though, I hope we can achieve all of what is in this one.

Gav...

RE: DOAP in use

[Gav....]

> -Original Message-
> From: Ross Gardler [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 7 August 2007 4:40 AM
> To: Forrest Developers List
> Subject: DOAP in use
> 
> As many of you will have noticed I've been doing quite a bit of work on
> the DOAP plugin recently. This is for a project here, called Simal, we
> need to create an internal catalogue of projects similar to
> projects.apache.org and since I'd already done much of the work on the
> DOAP plugin here I thought I'd get things kick started by using Forrest.
> 
> [ASIDE] I say "kick started" because I still have my concerns about the
> current architecture of Forrest. I hope to find the resources to do this
> with my Forrest 2 experimental code, but right now I don't have the
> necessary resources so am focusing on the existing Forrest.
> 
> Anyway, the resulting project site makes a reasonable demo of the DOAP
> plugin and, in particular, its emerging AJAX features. It's somewhat
> lacking in content in the catalogue right now, CSS styling is limited
> and useful features like hyperlinks are missing, but you can see the
> basic idea of where the DOAP plugin is heading.
> 
> AJAX Browser: http://simal.oss-watch.ac.uk/catalogueBrowser.html
> 
> Embedded RSS:
> http://simal.oss-watch.ac.uk//projectDetails/jisc/elfdemo_uhi.html
> 
> (OK so the RSS demo is a bit poor since it's not been updated for many
> years, but well, sooner or later we'll get more realistic sample data in
> there)
> 
> Ross

This looks great Ross, good work. I hope to find more time soon to take a
closer look.

Gav...

RE: [Proposal] decide the future of forrestdoc

[Gav....]

Ok, so we have given plenty more time.

Looking again at the link Vincent gave ,

http://www.nabble.com/Forrestdoc-and-Maven-JXR-tf3864888s177.html

shows that Maven are in agreement and happy to take the code.

What happens now ?

Gav...

> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 19 July 2007 7:45 AM
> To: dev@forrest.apache.org
> Subject: Re: [Proposal] decide the future of forrestdoc
> 
> Ross Gardler wrote:
> >
> > OK, so lets leave it a little while longer to ensure others can object
> > if they want to. Then under lazy consensus we can offer it to the
> > Maven community.
> >
> > [NOTE: my interpretation is that we don't need a vote for this but
> > there is time to correct me if I am wrong]
> 
> I agree with you. In an earlier message i tried to
> carefully choose words to express that.
> 
> -David

GSoC work on plugins

[Gav....]

This is for Oshani bur the rest of the list need to know what is happening ,

Oshani, you have been absent from this list for nearly a month, a private
mail I sent you two weeks ago (giving you the opportunity to reply in
private) has gone unanswered.

Here is the situation.

FOAF plugin needs completing - this was due on your own timeline of July
9th. You explained to me reasons for this and I accepted them. You assured
me you would get back on track.

DOAC Plugin needs starting and completing. This was due July 14th.

hCalendar Plugin needs starting and completing. This was due July 18th.

hResume plugin needs starting and completing. This was due July 31st.

Now is supposed to be well into Stage 4 - Final Touch ups.

You are due to upload code to Google on August 20th.
I am due to start evaluating your final evaluation on August 20th also.

Here is what I propose you do :-

1. Take a look at and solve issues FOR-1008 and FOR-1020. Send in separate
patches for the issues so I can test and apply them easily and timely.

What else needs to be done to complete FOAF plugin ?

2. Create the DOAC plugin and submit the code as a patch.
3. Complete the DOAC plugin.

Thoroughly test with lots of examples the FOAF and DOAC plugins.

IF you have time after that, being the hCalendar plugin.

You need to start doing this now - I do not want to see a last minute rush
of code submitted just before the deadline.

As always, myself , Ross and the rest of forrest list are here and have
always been here to answer any questions if you are stuck.

Today is August 9th, so there is only 11 days to go before final evaluations
begin.

Gav...

RE: Add a list to MARC

[Gav....]

Thanks Hank, 

That's good news, much appreciated :)

Gav...


> -Original Message-
> From: Hank Leininger [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 25 July 2007 4:20 AM
> To: Gav
> Subject: Re: Add a list to MARC
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Fri, 15 Jun 2007, Gav wrote:
> 
> > I could have sworn back in the marc.theaimsgroup days we had a Apache
> > Forrest User list. I don't see it any more on marc.info .
> 
> Hm, I don't think so, it looks to me like we only ever had -dev.
> 
> > Could we add forrest-user list in please. [EMAIL PROTECTED]
> 
> Sure, I've added -user, and also -svn and -site-svn.  I think the
> full-text indexer is still a little behind, but all the messages should
> be up.
> 
> Thanks,
> 
> Hank Leininger <[EMAIL PROTECTED]>
> D639 2E70 96A4 96D4 9AB6  95D6 A8FD BA7C 7093 F8F3
> -BEGIN PGP SIGNATURE-
> 
> iD8DBQFGpl8EqP26fHCT+PMRAsi8AJ9gyxfow0UkXqVD1NBShtm915gZDwCfS2Ji
> 4czs1E1dPzZSl7Z2RLtAA4U=
> =yZal
> -END PGP SIGNATURE-

RE: lost svn history for samples (Was: commit: r556367 [1/2])

[Gav....]

> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 21 July 2007 1:09 PM
> To: dev@forrest.apache.org
> Subject: Re: lost svn history for samples (Was: commit: r556367 [1/2])
> 
> Gav wrote:
> > From: David Crossley
> > >
> > > Ooops. You should have used 'svn move'. This has now lost all
> > > the svn history for those files.
> >
> > Welcome back :)
> >
> > Do you know, I did try and use 'svn move' but it would have
> > none of it, several complaints of which I can't remember.
> 
> If you have problems when commiting, then please discuss
> it with your friends.
> 
> > I suppose we could revert back before this commit and then try
> > the svn move again ?
> 
> Yes please. We connot afford to lose svn history.
> 
> If you continue to have trouble, then one of the other
> committers will need to help.

Ok, someone then had better let me know the best way to revert trunk back
so I don't bu&&er up the history again.

I know I can revert my local changes back to before, but then should I
commit that, then make make new changes with svn:move then commit again ?
Is that the best way to approach it ?

Gav...

> 
> > One file doesn't get moved but gets changed
> > instead (index.xml) meaning we can't move that directory whole, each
> file
> > would need to be done individually I think.
> 
> There is always a way. Perhaps index.xml needs to be copied
> and the others moved. Individually perhaps. It is trivial
> to create a temporary shell script to do the individual
> moves and copies. For example, use 'ls samples > temp.sh'
> and vi to edit it into a shell script which performs a
> list of 'svn mv' or 'svn cp' commands.
> 
> -David

RE: [Proposal] decide the future of forrestdoc

[Gav....]

As the 'other' interested party initially in this code here is
my stance.

If 'ForrestDoc' stays at Forrest I am happy to work on it where
I can as I said in my original reply, apply patches, work on
code I understand, try and understand what I don't etc etc ...

If Maven decide they want it over there, that's fine with me
too, but I wont be able to go over there and help at this
time, I am already spread as much across the ASF as I can and
want to manage. (No loss to the Maven folk there though :) )

I agree we are thin on the ground for active devs at this time
and in other threads we are talking about some major overhauls
of Forrests workings. We could probably do without maintaining
code that we haven't had a need for up to now.

I am therefore +1 on releasing it to Maven if they want it.

Gav...

> -Original Message-
> From: Thorsten Scherler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 18 July 2007 8:17 AM
> To: dev@forrest.apache.org
> Subject: Re: [Proposal] decide the future of forrestdoc
> 
> On Tue, 2007-07-17 at 12:24 +0100, Ross Gardler wrote:
> ...
> > > Adding the part "Vincent being an ASF committer expressing he is
> acting
> > > for an ASF community (maven)" is changing a WEE bit the situation.
> > >
> > > Can't we leverage? For now the scale for people that are sharing
> > > interest it is about 2 forrest : 1 maven (and code still in forrest).
> It
> > > is IMO ATM our duty to maintain the code.
> >
> > It is our duty to maintain the code, I agree. But the "our" in that
> > sentence refers to the ASF, not to Forrest. We (Forrest) are not
> > maintaining the code, Maven say they want to use and maintain it and,
> > more importantly, Vincent is doing it.
> 
> As I understand the thread
> http://www.nabble.com/Forrestdoc-and-Maven-JXR-tf3864888s177.html they
> are still deciding. Reading your words it sounds they already have
> consensus they want be the new host.
> 
> As I said I am very welcome if maven want the code, they can have it.
> 
> >
> > > As soon as we see a wave of patches coming from the maven community we
> > > may re think the situation, but for now I do not see the need.
> >
> > OK, so will you please apply the patches so that Vincent can proceed
> > unhindered. (that doesn't mean I won't do so, only that right now I do
> > not have the time)
> 
> I know that you are on travel, all patches are applied besides
> https://issues.apache.org/jira/browse/FOR-1024 (see my comment on it!)
> from Gavin and me.
> 
> We are a community that does not only exist of Ross and David to do the
> work (I just finished a similar mail to the user ml). At least I hope
> so!
> 
> ...but please let us apply a realistic time frame for issues, why is
> everybody in a hurry this days?
> 
> >
> > > > Vincent, are you reading this thread? If so can you liaise with the
> > > > Maven community to see if they would like to accept the code into
> > > > their SVN. Be aware that Forrest have not yet decided they will
> donate
> > > > the code (see above), but if Maven don't want it you could save us
> > > > some time.
> > >
> > > My question is how many people are interested in maintain/develop the
> > > code in the maven community?
> >
> > I don't know the answer, but I do know it is one more *active*
> > committer than in the Forrest community.
> 
> If there is a commitment for the code I am all for giving to maven.
> 
> Anyway if there is a vote right no I am -0.
> 
> Since we are in forrest in a hurry this days.
> 
> salu2
> --
> Thorsten Scherler thorsten.at.apache.org
> Open Source Java  consulting, training and solutions

RE: lost svn history for samples (Was: commit: r556367 [1/2])

[Gav....]

> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 18 July 2007 3:27 PM
> To: Forrest Developers List
> Subject: lost svn history for samples (Was: commit: r556367 [1/2])
> 
> Ooops. You should have used 'svn move'. This has now lost all
> the svn history for those files.
> 
> -David

Welcome back :)

Do you know, I did try and use 'svn move' but it would have
none of it, several complaints of which I can't remember.

I suppose we could revert back before this commit and then try
the svn move again ? One file doesn't get moved but gets changed
instead (index.xml) meaning we can't move that directory whole, each file
would need to be done individually I think.

Anyway, I haven't closed the Issue as I thought I'd wait for your thoughts
on the outcome, no-one else seems interested in this stuff but didn't
want to close it until you were satisfied. I never tested on a MAC.

Gav...

> 
> > Author: gmcdonald
> > Date: Sat Jul 14 23:39:28 2007
> > New Revision: 556367
> >
> > URL: http://svn.apache.org/viewvc?view=rev&rev=556367
> > Log:
> > Part Two - Re-organised samples into two sections, highlights the use of
> sub-tabs etc. General improvement and also Fix for FOR-1001
> >
> > Added:
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples/
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples/index.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/ascii-art.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/cocoon-pyramid.aart   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/custom.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/customSchema.xml   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/ellipse.svg   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/embedded_html.html   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/faq.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/hello-v10.dtd   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/helloAgain.pdf   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/howto-howto.xml   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/icon-d.png   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/index.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/linking.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/locationmap/
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/locationmap/index.xml
> (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/sample.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/static.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/svg.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/usemap.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples1/xml-entities.xml   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples2/
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples2/demo-i18n.de.xml   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples2/demo-i18n.fr.xml   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples2/demo-i18n.nl.xml   (with
> props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples2/demo-i18n.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples2/i18n.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/content/xdocs/samples2/index.xml   (with props)
> > forrest/trunk/main/fresh-
> site/src/documentation/co

RE: svn commit: r556408 - in /forrest/site: docs_0_70/body-index.html docs_0_80/body-index.html docs_0_90/body-index.html pluginDocs/index.html versions/index.html

[Gav....]

Pants, will try to fix my site-author publish yet again.

Gav...

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Sunday, 15 July 2007 9:53 PM
> To: [EMAIL PROTECTED]
> Subject: svn commit: r556408 - in /forrest/site: docs_0_70/body-index.html
> docs_0_80/body-index.html docs_0_90/body-index.html pluginDocs/index.html
> versions/index.html
> 
> Author: gmcdonald
> Date: Sun Jul 15 06:52:31 2007
> New Revision: 556408
> 
> URL: http://svn.apache.org/viewvc?view=rev&rev=556408
> Log:
> Publish from forrestbot
> 
> Modified:
> forrest/site/docs_0_70/body-index.html
> forrest/site/docs_0_80/body-index.html
> forrest/site/docs_0_90/body-index.html
> forrest/site/pluginDocs/index.html
> forrest/site/versions/index.html
> 
> Modified: forrest/site/docs_0_70/body-index.html
> URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/body-
> index.html?view=diff&rev=556408&r1=556407&r2=556408
> ==
> 
> --- forrest/site/docs_0_70/body-index.html (original)
> +++ forrest/site/docs_0_70/body-index.html Sun Jul 15 06:52:31 2007
> @@ -26,7 +26,10 @@
>  
>  
>  Apache Forrest documentation
> +
> +
>  
> +
> 
>  
>  
> 
> Modified: forrest/site/docs_0_80/body-index.html
> URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/body-
> index.html?view=diff&rev=556408&r1=556407&r2=556408
> ==
> 
> --- forrest/site/docs_0_80/body-index.html (original)
> +++ forrest/site/docs_0_80/body-index.html Sun Jul 15 06:52:31 2007
> @@ -23,7 +23,10 @@
>  
>  
>  Apache Forrest documentation
> +
> +
>  
> +
> 
>  
>A good place to get started in our docs is the
> 
> Modified: forrest/site/docs_0_90/body-index.html
> URL: http://svn.apache.org/viewvc/forrest/site/docs_0_90/body-
> index.html?view=diff&rev=556408&r1=556407&r2=556408
> ==
> 
> --- forrest/site/docs_0_90/body-index.html (original)
> +++ forrest/site/docs_0_90/body-index.html Sun Jul 15 06:52:31 2007
> @@ -23,7 +23,10 @@
>  
>  
>  Apache Forrest 0.90-dev documentation
> +
> +
>  
> +
> 
>  
>  Note
> 
> Modified: forrest/site/pluginDocs/index.html
> URL:
> http://svn.apache.org/viewvc/forrest/site/pluginDocs/index.html?view=diff&;
> rev=556408&r1=556407&r2=556408
> ==
> 
> --- forrest/site/pluginDocs/index.html (original)
> +++ forrest/site/pluginDocs/index.html Sun Jul 15 06:52:31 2007
> @@ -120,6 +120,7 @@
>  
>  
>  Plugins documentation for each version
> +
> 
>  
>Plugins documentation is available for various releases ...
> 
> Modified: forrest/site/versions/index.html
> URL:
> http://svn.apache.org/viewvc/forrest/site/versions/index.html?view=diff&re
> v=556408&r1=556407&r2=556408
> ==
> 
> --- forrest/site/versions/index.html (original)
> +++ forrest/site/versions/index.html Sun Jul 15 06:52:31 2007
> @@ -120,6 +120,7 @@
>  
>  
>  Version Specific Documentation
> +
> 
>  
>Documentation is available for various releases ...
> 
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.10.6 - Release Date: 7/14/2007
> 12:00 AM