Okay; the script worked for me - however I am running into a bit of bind using 
it to create a dropins-3.7.1.zip  

I was also above to grab just the internationalisation plugins using:

cp *\.nl_* ~\java\371\dropins\plugins

In the current structure of dropins has:

dropins/features
dropins//plugins

With the feature directory having …

org.eclipse.babel.nls_eclipse_de_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.emft.eef_de_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.gmp.gmf-tooling_de_3.6.0.v20100709043401
org.eclipse.babel.nls_eclipse_es_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.emft.eef_es_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.gmp.gmf-tooling_es_3.6.0.v20100709043401
org.eclipse.babel.nls_eclipse_fr_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.emft.eef_fr_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.gmp.gmf-tooling_fr_3.6.0.v20100709043401
org.eclipse.babel.nls_eclipse_it_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.emft.eef_it_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.gmp.gmf-tooling_it_3.6.0.v20100709043401
org.eclipse.babel.nls_eclipse_ko_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.emft.eef_ko_3.6.0.v20100709043401 
org.eclipse.babel.nls_modeling.gmp.gmf-tooling_ko_3.6.0.v20100709043401


I think I understand that your pom-language.xml just downloads the plugins. Now 
this may be correct? Since the udig_langauge feature is actually the one 
responsible for rounding up the language translations we use (rather then the 
official features mentioned above).  

With that assumption I should get:
dropins/features/udig_language
dopins/plugins/ (the nl plugins)

I don't really think that is correct … suggestions? Maybe I should leave the 
features out of it...
--  
Jody Garnett


On Sunday, 22 January 2012 at 10:45 AM, Severin (aka Cliff) wrote:

> 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 <[email protected] 
> (mailto:[email protected])> 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..."
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
>  
>  


_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel

Reply via email to