Re: Forrest commands

[David Crossley <cr...@apache.org>]

Clay Leeds wrote:
> David Crossley wrote:
> > This error is also discovered using a simple xml well-formedness
> > test ... xmllint --noout clay-sitemap.xmap
> 
> [OT] I'd heard of using lint as a tool for validation, but never tried  
> it before. So in trying to resolve my forrest BUILD problems, I thought  
> I'd give xmllint a shot. Realizing that my Mac OS X box has its bases  
> in Unix, I did a 'locate xmllint' and lo-and-behold, it was listed!  
> Nifty!

And i presume that you saw how to configure it at
http://forrest.apache.org/docs/catalog.html

> > You can also use Forrest's own validation facilities ...
> > 'forrest validate-sitemap'
> 
> (the main reason for this post & its change in SUBJECT)
> I could not find 'validate-sitemap' listed anywhere (site, /forrest  
> -projecthelp)... Is there a place where these types of commands are  
> listed. I suspect it would be a boon to users--especially so-called  
> power-users! I did a Google search[1] and found a few links, of which  
> this[2] seems the most relevant (if a bit aged).

Actually it is a relic of our recent build re-organisation.
Some targets need a description added again so that they
are listed with 'forrest -projecthelp'. Added Issue FOR-216.

-- 
David Crossley

Re: Forrest commands

[David Crossley <cr...@apache.org>]

Clay Leeds wrote:
> David Crossley said:
> > And i presume that you saw how to configure it at
> > http://forrest.apache.org/docs/catalog.html
> 
> Yes.. I saw that, but it didn't 'click' in my head that I could actually
> use it. BTW, what's 'missing' from that otherwise extensive description,
> is how to configure Eclipse. I noticed that Thorsten indicated using a
> plugin (I don't recall which off-hand, but I know it's $$$). Is there a
> built-in way to do it, or would it work with XMLBuddy, which I already
> have installed?

Sorry, i cannot help, as i do not bother with fancy IDEs yet.
However, i suggest that you ask the question in a separate
topic. We will add the hints to that doc.

> > Actually it is a relic of our recent build re-organisation.
> > Some targets need a description added again so that they
> > are listed with 'forrest -projecthelp'. Added Issue FOR-216.
> 
> That was fast! Thanks!

It is the only way. Jump onto issues as soon as they become
apparent, and if they cannot be fixed now, document them
in the issue tracker.

-- 
David Crossley

Re: Forrest commands

[Clay Leeds <cl...@medata.com>]

David Crossley said:
> And i presume that you saw how to configure it at
> http://forrest.apache.org/docs/catalog.html

Yes.. I saw that, but it didn't 'click' in my head that I could actually
use it. BTW, what's 'missing' from that otherwise extensive description,
is how to configure Eclipse. I noticed that Thorsten indicated using a
plugin (I don't recall which off-hand, but I know it's $$$). Is there a
built-in way to do it, or would it work with XMLBuddy, which I already
have installed?

> Actually it is a relic of our recent build re-organisation.
> Some targets need a description added again so that they
> are listed with 'forrest -projecthelp'. Added Issue FOR-216.
>
> --
> David Crossley

That was fast! Thanks!

Web Maestro Clay
-- 
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc