Hi Mathieu, thanks for the info, the eclipse mavenizer is cool. I think I will start with leaving the 7 jar out of the plugin. The viewer will be mostly used in rcp environments, so the needed plugins will be there anyway.
Andrea On Thu, Feb 17, 2011 at 10:14 AM, Mathieu Baudier <[email protected]> wrote: >> For the procedure for adding those swt jars: >> - http://docs.geotools.org/latest/developer/guide/procedures/add.html > > Just in case you are not already aware of it, there is a very handy > maven plugin to transform an Eclipse distribution into Maven > artifacts: > > mvn eclipse:make-artifacts > -DdeployTo=argeo-restricted::default::file:/my_maven_repository_root > -DeclipseDir=/path_to_my_eclipse_distribution > -DresolveVersionRanges=true > > By default it uses an artifact version like 3.6.1 instead of the full > OSGi version (3.6.1.v3655c, etc.) > > I guess that it would work with the webdav wagon used by OSGeo (see > instructions in the links sent by Jody). > But then it will upload the whole distribution (with RCP stuff etc.), > I'm not sure if this is what you want, although this could be nice to > have a consistent RCP platform in Maven, in case we add stuff at the > JFace level. > If you don't want to upload everything, I would recommend to remove > all the uneeded jars from a copy of the RCP SDK, and then use the > plugin. This could save you a lot of manual work. > > Here is how it looks like when done: > http://maven.argeo.org/argeo/org/eclipse/swt/ > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
