Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Tue, 5 Feb 2008 14:04:02 +1100
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: Re: pdf-plugin with fop .94 - can sbdy please help?
Message-ID: <20080205030402.GB11926@igg.indexgeo.com.au>
References: <47A777B2.6060008@apache.org> <1202168074.6092.22.camel@cartman>
 <47A7C7C4.2020504@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47A7C7C4.2020504@apache.org>
User-Agent: Mutt/1.4.2.2i

Ferdinand Soethe wrote:
> Thorsten Scherler wrote:
> > Ferdinand Soethe wrote:
> >>- moved the libs from lib/core to the plugin-lib-dir
> >
> >IMO you moved too much (see the other mail).
> 
> That's fixed.

There are now copies of at least "commons-logging" jars.

> >>- moved the style-sheets from common skin to
> >>   plugin-resources-dir
> >>- adjusted output.xmap to the best of my understanding
> >
> >Try cocoon:// instead (see side note on the other mail) and I guess you
> >get back the fo.
> 
> Thanks Thorsten. That did the trick.
> 
> >>- removed the fo-pipeline from main sitemap
> >>- changed build.xml
> >
> >What did you change? Did not see a commit.
> 
> I actually had not committed build.xml yet.
> Done now.

See the notes at http://forrest.apache.org/docs/dev/howto/howto-buildPlugin.html#descriptor
"Managing the plugins descriptors" and keeping them
synchronised with the plugin's build.xml.
Although i suppose that that will happen after the merge and before
deploying the new plugin.

-David