|Re: [Embedded Birt] : Migration to 3.7 [message #690452 is a reply to message #690269]
||Wed, 29 June 2011 14:29
| Jason Weathersby
Registered: July 2009
There are more libs because the runtime jars are no longer in the
platform/plugins directory. All the birt functionality is one jar. The
only jars that I see that could be trimmed are the datatools jars, which
have jars for different data source types. You could also remove
derby.jar if you do not want to use the sample db.
On 6/29/2011 5:53 AM, miaou wrote:
> Hi everybody,
> I plan to migrate to Birt 3.7 version.
> We have embedded Birt engine into our application as many of you have done.
> According to the wiki migration page
> (htp://wiki.eclipse.org/Birt_3.7_Migration_Guide), external runtime is
> no more necessary, nor the following code :
> Only add all ReportEngine/lib jars to application classpath (WEB-INF/lib
> for example) is required.
> Comparing Birt 2.6.2 to 3.7 version, I note that there are many more
> libraries (24 vs 78).
> I can guess that some of them are optional, but is there any
> documentation about library requirement and feature ?
> The aim is :
> I want to avoid as much as possible library conflict.
> As Birt libraries are still not publish on any maven repository, I would
> like to create my own maven descriptor file and publish Birt libraries
> on my local maven proxy.
> Thanks you for any help.
> Best Regards,
Powered by FUDForum
. Page generated in 0.02395 seconds