Re: [gmf-dev] Issue with duplicate org.apache plug-ins

[Richard Gronback <richard.gronback@xxxxxxxxxxx>]

Hi Anthony,

It's not a problem, and it's not normally the case that the qualifier is
updated with each build.  Due to changes in the Batik feature and plug-in
made recently, the maps were updated as part of the release process.  As
long as no changes are made by the next I/RC build, it will remain as it is
below.  I'm not sure where the other one comes from, as it appears TPTP has
built it themselves.  We do not rebuild Xerces, for example, as we simply
pull the update jars provided by WTP to Callisto.  I'd recommend TPTP do
likewise and pull our update jars, if they're not already.

Best,
Rich


On 6/6/06 3:21 PM, "Anthony Hunter" <anthonyh@xxxxxxxxxx> wrote:

> 
> Hi Team,
> 
> When our customers extract all the zip files from the various Eclipse
> components, there are duplicate org.apache plug-ins. The picture below
> illustrates the issue.
> 
> 
> (Embedded image moved to file: pic19753.jpg)
> 
> 
> The issue for us is that both TPTP and GMF are pushing
> org.apache.batik_1.6.0.qualifier and that the .qualifier is different.
> 
> Even though nothing appears broken, our customer does not like the
> duplicate plug-ins.
> 
> Since we have batik in a separate map file and since the source never
> changes, we are wondering if we can stop relabeling the feature and plug-in
> and keep version 6.1.0.v20060531-1000. Both TPTP and GMF would push
> org.apache.batik_1.6.0_v20060531-1000 and the end result is that batik gets
> installed once when you extract everything.
> 
> Would there be any build problem in doing this?
> 
> Cheers...
> Anthony
> --
> Anthony Hunter mailto:anthonyh@xxxxxxxxxx
> Manager - Software Developer,
> IBM Rational Software: Aurora Core Common / Modeling Tools
> Phone: 613-591-7037
> _______________________________________________
> gmf-dev mailing list
> gmf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gmf-dev