Hi List!

The EFeature module classpath is now managed by Maven2 only (see my last
post on this 
topic<http://osgeo-org.1803224.n2.nabble.com/EFeature-Moving-Eclipse-plug-in-implementation-to-eu-udig-catalog-efeature-td6310691.html>
).

The move from PDE to Maven2 did put up some struggles (of course). The end
result is that I now propose to add six new artifacts must be added to
GeoTools repos. I have imported these dependencies into my local repository,
but the effort required to do so each time the unsupported EFeature module
is checked out from scratch, argues for an addition to the SNAPSHOT and
release repos. I'v written up the procedure I've used on this RnD
page<http://docs.codehaus.org/display/GEOTOOLS/EFeatureDataStore+Build>,
but my hope is a +1 adding the following dependencies to the GeoTools
SNAPSHOT repo before I ask for a code review:

   - *org.eclipse.emf:query:1.2.100 *
   (redefined from 1.2.100.v200903190031, dependency com.ibm.icu does not
   exist in standard repos)
   - *org.eclipse.emf:edit:2.3.0*
   (redefined from 2.3.0-v200706262000)
   - *org.eclipse.emf:workspace:1.1.0*
   (redefined from 1.1.0-v200706131240, jar does not download from central
   repos)
   - *org.eclipse.emf:transaction:1.1.0*
   (redefined from 1.1.0-v200706131240, jar does not download from central
   repos)
   - *org.eclipse.emf:validation:1.1.0*
   (redefined from 1.1.0-v200706071520, dependency com.ibm.icu does not
   exist in standard repos)
   - *org.eclipse.core.runtime:3.6.0
   (redefined from *3.6.0-v20100505*, included org.eclipse.core.runtime
   qualifier versions in version range)*

The arguments for redefining these dependencies and adding them to GeoTools
(SNAPSHOT?) repo are

   - Original definitions in standard repos are broken and alternatives are
   not available
      - some jars does not download automatically (they exist in repos, but
      'mvn install' does not download them)
      - some artifacts have version ranges which does not include qualifier
      versions
      - deploying qualifier versions seems to be the when it comes to
      Eclipse artifacts
   - EMF artifacts deployed to central repo seems to be broken in general.
   - (I believe that the) EFeature module can not be added to the GeoTools
   build before these modules are added.

In addition, I expect that any code reviewers would also find
it demotivating to start out with a lot manual maven work before EFeature
can be built locally.

Best regards,
Kenneth
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to