Skip to main content



      Home
Home » Archived » BIRT » JAR Hell with BIRT
JAR Hell with BIRT [message #38077] Wed, 18 May 2005 10:05 Go to next message
Eclipse UserFriend
Originally posted by: mohsen_s.myrealbox.com

Dear BIRT Team,
I've noticed that there 5 "derby.jar"s, 2 "fop.jar"s, and 2 "batik.jar"s in
the birt designer 1.0 M3 release. It makes the size of this release very
large. Is it possible to have all the jar fils somewhere in a repository and
each birt plugin loads it from there.

Thanks.
Re: JAR Hell with BIRT [message #38438 is a reply to message #38077] Wed, 18 May 2005 16:16 Go to previous messageGo to next message
Eclipse UserFriend
Mohsen,

Please file a Bugzilla entry for this issue. I believe the duplicate JARs
exist today so that each plugin can be independent; it allowed the various
development teams to work independently on their plugins. You are right
that, over time, BIRT should find and remove duplicates. Your Bugzilla entry
will help remind the team to get this done.

Thanks,

- Paul

Paul Rogers
BIRT PMC

"Mohsen Saboorian" <mohsen_s@myrealbox.com> wrote in message
news:d6fdvk$mdj$1@news.eclipse.org...
> Dear BIRT Team,
> I've noticed that there 5 "derby.jar"s, 2 "fop.jar"s, and 2 "batik.jar"s
> in
> the birt designer 1.0 M3 release. It makes the size of this release very
> large. Is it possible to have all the jar fils somewhere in a repository
> and
> each birt plugin loads it from there.
>
> Thanks.
>
>
Re: JAR Hell with BIRT [message #45467 is a reply to message #38438] Mon, 13 June 2005 18:50 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: myname(with.between names).lombardisoftware.com

Normally I would guess Eclipse will put these jars into separate plug-ins
(org.batik, org.derby etc) that BIRT depends on.

This way, you still get the ability to just use a few of the BIRT plug-ins,
while you don't have this duplication.

Putting jars in plug-ins like this can also cause potential classloading
issues that I've seen recently with 3.1RC1
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=97155). This might be a
gotcha when you upgrade BIRT to 3.1... When multiple plug-ins that depends
on eachother all have the same jars it seems to cause problems in later 3.1
releases.

I should perhaps comment on this in bugzilla, but that would require me to
go look for it :)

- Morten Moeller
Lombardi Software
http://www.lombardisoftware.com/


Paul Rogers wrote:

> Mohsen,
>
> Please file a Bugzilla entry for this issue. I believe the duplicate JARs
> exist today so that each plugin can be independent; it allowed the various
> development teams to work independently on their plugins. You are right
> that, over time, BIRT should find and remove duplicates. Your Bugzilla
> entry will help remind the team to get this done.
>
> Thanks,
>
> - Paul
>
> Paul Rogers
> BIRT PMC
>
> "Mohsen Saboorian" <mohsen_s@myrealbox.com> wrote in message
> news:d6fdvk$mdj$1@news.eclipse.org...
>> Dear BIRT Team,
>> I've noticed that there 5 "derby.jar"s, 2 "fop.jar"s, and 2 "batik.jar"s
>> in
>> the birt designer 1.0 M3 release. It makes the size of this release very
>> large. Is it possible to have all the jar fils somewhere in a repository
>> and
>> each birt plugin loads it from there.
>>
>> Thanks.
>>
>>
Re: JAR Hell with BIRT [message #45526 is a reply to message #45467] Mon, 13 June 2005 21:12 Go to previous message
Eclipse UserFriend
Some time ago, I proposed to the Spring team to release as part of each
official release their Spring library in an Eclipse plugin format, this
will make easier for Eclipse/RCP developers to adopt their libraries,
instead of everybody making their own plugin of popular OSS projects.

Now that Eclipse is becoming widely used as an application platform this
should be extended to other popular OSS projects: Hibernate, Derby, etc.

Morten Moeller wrote:
> Normally I would guess Eclipse will put these jars into separate plug-ins
> (org.batik, org.derby etc) that BIRT depends on.
>
> This way, you still get the ability to just use a few of the BIRT plug-ins,
> while you don't have this duplication.
>
> Putting jars in plug-ins like this can also cause potential classloading
> issues that I've seen recently with 3.1RC1
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=97155). This might be a
> gotcha when you upgrade BIRT to 3.1... When multiple plug-ins that depends
> on eachother all have the same jars it seems to cause problems in later 3.1
> releases.
>
> I should perhaps comment on this in bugzilla, but that would require me to
> go look for it :)
>
> - Morten Moeller
> Lombardi Software
> http://www.lombardisoftware.com/
>
>
> Paul Rogers wrote:
>
>
>>Mohsen,
>>
>>Please file a Bugzilla entry for this issue. I believe the duplicate JARs
>>exist today so that each plugin can be independent; it allowed the various
>>development teams to work independently on their plugins. You are right
>>that, over time, BIRT should find and remove duplicates. Your Bugzilla
>>entry will help remind the team to get this done.
>>
>>Thanks,
>>
>> - Paul
>>
>>Paul Rogers
>>BIRT PMC
>>
>>"Mohsen Saboorian" <mohsen_s@myrealbox.com> wrote in message
>>news:d6fdvk$mdj$1@news.eclipse.org...
>>
>>>Dear BIRT Team,
>>>I've noticed that there 5 "derby.jar"s, 2 "fop.jar"s, and 2 "batik.jar"s
>>>in
>>>the birt designer 1.0 M3 release. It makes the size of this release very
>>>large. Is it possible to have all the jar fils somewhere in a repository
>>>and
>>>each birt plugin loads it from there.
>>>
>>>Thanks.
>>>
>>>
>
>
Previous Topic:Running Stand alone
Next Topic:Problem with design file
Goto Forum:
  


Current Time: Thu May 08 07:51:06 EDT 2025

Powered by FUDForum. Page generated in 0.03745 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top