Re: [udig-devel] Automate language fragment gathering

["Severin (aka Cliff)" <djseverin@xxxxxxxxx>]

Hi Jody,

This was an experiment intended to make life easier when creating the language drop-ins zip.

This method ties Tycho into the method used to download libs. Instead of explicitly stating each and every fragment in the pom, I use Tycho to read these from the feature.xml.

When run, the pom cherry picks only the fragments required by the udig language feature. The difficulty I am having is that it also downloads the parent plugins and a handful of transitives.

In my testing so far, the entire contents of the libs directory created by the languages pom can be placed into the drop-ins directory; or added to the target platform along with the delta pack. Both options appear to work quite nicely.

In summary, the intent was to create a convenience tool capable of automagically creating the languages drop-in.

Cheers,
  Sev


On Sunday, 22 January 2012, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
> For those who develop internationalized versions of uDig and rely on the language fragments provided by net.refractions.udig_language_feature, you will now find a maven pom within this feature's project directory named pom-languages.xml.
> This maven script makes use of Tycho to read the OSGi feature.xml, download the required plugins and fragments, and finally create and copy them into net.refractions.udig_language_feature/lib.
> It is then simply a case of adding net.refractions.udig_language_feature/lib to your Target Platform. (Preferences -> Plugin development -> Target Platform).
>
> Okay so let me get this straight … this changes the development environment we need to work on uDig?
> Does this replace the dropins dowload or do I need to use this technique to create a new dropins download. 
>
> If someone could review this that would be great.
> Sadly, this script downloads transitive dependencies as well and I have not been able to stop it doing so. This appears to be a limitation of Tycho.
>
> So it is not ignoring the "provided" setting? Sigh.
>
> If you prefer to use the Dropins method to introduce the fragments to your development environment, you could theoretically just copy the lib directory to your eclipse/dropins directory and remove any unwanted jars.
>
> Is there something we have done wrong with setting up drop ins that is making this necessary?
> The udig_language feature was only required as we did not want to depend on the entire bable project (and only wished to grab translations for those parts of the RCP we are using).
> On this page (http://www.eclipse.org/babel/downloads.php) it appears as if they just finished a release on Nov 28th; so I could make a new dropins zip if that would help?
> Jody

-- 
"We are dreamers, shapers, singers and makers..."