Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@forrest.apache.org
Received-SPF: pass (hermes.apache.org: domain of sendtoandy@gmail.com
 designates 64.233.170.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=Vnq4DV1FSwPJ5WPjcqHQeI6WWw6UWAz9BowhDZAILz0gQ2L8HlP+gUnUCoMPkwHY6kKmTu6cIVsWY7ZZ1Uew90qslj6gdz7TkeiXY6WLIfW72FNlvC3P8e4IqyYyY3M0XsrvP41vmY7yqaNO97H0qJudCGGuxmBwlSI3PeYEnLQ=
Message-ID: <833b4fb60501040356729889d@mail.gmail.com>
Date: Tue, 4 Jan 2005 06:56:33 -0500
From: Andy J <sendtoandy@gmail.com>
Reply-To: Andy J <sendtoandy@gmail.com>
To: user@forrest.apache.org
Subject: Re: Is it right for me help request
In-Reply-To: <41D99D21.6020405@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <833b4fb6041231054149825802@mail.gmail.com>
	 <41D56A14.40902@apache.org>
	 <833b4fb605010303245dc2edb1@mail.gmail.com>
	 <41D99D21.6020405@apache.org>

Yes, I found it in a doc.  I'll see if I can find it and send you the link.


On Mon, 03 Jan 2005 19:29:37 +0000, Ross Gardler <rgardler@apache.org> wrote:
> Andy J wrote:
> > Cool...  One thing I tried in my brief eval was copying ALL the xmap
> > files into my document directory (which I though was the basic m.o.
> > for customization).  Doing this I kept getting java out of memory
> > errors until I /removed/ the xmap files from the document directory.
> 
> This is how we handled extensions in version 0.5 and earlier, version
> 0.6 introduced project sitemaps which simplify the extension process.
> Version 0.7 introduces the plugins, which even further simplify things.
> 
> If you found yourself trying this method of extension because a doc led
> you down that path we may need to update that doc so please let us know
> if clarification is needed.
> 
> Ross
> 
> > Originally I was thinking it would work more or less like
> > <xsl:includes> which maybe it does now.
> >
> >
> >
> > On Fri, 31 Dec 2004 15:02:44 +0000, Ross Gardler <rgardler@apache.org> wrote:
> >
> >>Andy J wrote:
> >>
> >>>I'm still trying to figure out if it will work in my case and was
> >>>hoping someone could pipe in about two questions.
> >>>
> >>>1.  I know the surest way to determine this is to try it - but I
> >>>didn't get that far and someone might know: will Forrest validate
> >>>against an XML Schema schema?  I have a lot invested in an existing
> >>>schema and don't want to spend more time morphing it to RNG or DTD.
> >>>So this is sort of a showstopper (or starter) issue.
> >>
> >>I should no the answer to this, but it seems I don't so I'll leave this
> >>one for someone else.
> >>
> >>
> >>>2.  My main use of Forrest would be this:  I have a homegrown and
> >>>growing CM infrastructure which produces and uses XML files for
> >>>various tasks (e.g., baseline, build, request, etc).  This system was
> >>>not so much designed (other than in concept) as it has been collected
> >>>but all the various parts produce and use XML.  So I have a plethora
> >>>of XML files in a structure which are always being updated, added,
> >>>etc.  What I need is something (like Forrest) to report on these.  My
> >>>intent is to make custom XSL stylesheets as appropriate so Forrest
> >>>would take the various XMLs and produce various output files.  Does
> >>>this sound like a good fit?
> >>
> >>Yes, especially if you use 0.7-dev, but still possible with 0.6.
> >>
> >>For 0.6 see http://forrest.apache.org/docs/project-sitemap.html which
> >>provides an example for what you want to do.
> >>
> >>This will still work in 0.7 when it is released, but we have a more
> >>manageable solution in 0.7-dev, see plugins at the following urls:
> >>
> >>http://forrest.apache.org/docs/dev/howto/howto-buildPlugin.html
> >>http://forrest.apache.org/docs/dev/plugins/usingPlugins.html
> >>
> >>Ross
> >>
> >
> >
> >
> >
> 
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.6.8 - Release Date: 03/01/2005
> 
>