EFeature: Adding missing and repaired maven artifacts to GeoTools repos
-----------------------------------------------------------------------

                 Key: GEOT-3567
                 URL: http://jira.codehaus.org/browse/GEOT-3567
             Project: GeoTools
          Issue Type: Improvement
          Components: core xml, data, data vpf, data wfs, ext wms, ext xml-xsd
    Affects Versions: 8.0-M0
            Reporter: Kenneth Gulbrandsøy
            Assignee: Kenneth Gulbrandsøy
            Priority: Blocker
         Attachments: org.eclipse.emf-validation-1.1.0-v200706071520!.tar.gz, 
org.eclipse.emf.query-1.2.100-v200903190031!.tar.gz

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 GeoTools. 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 repos:

* *org.eclipse.emf:query:1.2.100-v200903190031!*
  (redefined from 1.2.100.v200903190031, dependency com.ibm.icu does not exist 
in standard repos)
* *org.eclipse.emf:validation:1.1.0-v200706071520!*
  (redefined from 1.1.0-v200706071520, dependency com.ibm.icu does not exist in 
standard repos)

In addition, the following dependencies 
{code:lang=xml}

<dependencyManagement>
    <dependencies>
    ...    
       <dependency>
         <groupId>org.eclipse.equinox</groupId>
         <artifactId>app</artifactId>
         <version>1.0.0-v20070606</version>
       </dependency>
       <dependency>
         <groupId>org.eclipse.emf</groupId>
         <artifactId>edit</artifactId>
         <version>2.3.0-v200706262000</version>
       </dependency>
       <dependency>
         <groupId>org.eclipse.emf</groupId>
         <artifactId>query</artifactId>
         <version>1.2.100-v200903190031</version>
       </dependency>
       <dependency>
         <groupId>org.eclipse.emf</groupId>
         <artifactId>workspace</artifactId>
         <version>1.1.0-v200706131240</version>
       </dependency>
       <dependency>
         <groupId>org.eclipse.emf</groupId>
         <artifactId>transaction-v200706131240</artifactId>
         <version>1.1.0</version>
       </dependency>
       <dependency>
         <groupId>org.eclipse.emf</groupId>
         <artifactId>validation</artifactId>
         <version>1.1.0</version>
       </dependency>
    ...
   </dependencies>
<dependencyManagement>

{code}

should be added to the <dependencyManagement> element in the global POM file at 
../trunk/pom.xml to ensure that these versions are favored when resolving 
dependencies (this solves a few missing dependency problems resulting from 
version range mismatches resulting from qualifier versions not included). 

The arguments for redefining these dependencies and adding them to GeoTools 
repos 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 standard 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.

I have attached the jars and the companion POM-files to this issue. According 
to the developer guide, these are the steps required to add the each artifact.

# Extract one of the attached zip files
# > mvn deploy:deploy-file -Dfile=your-artifact-1.0.jar -DpomFile=your-pom.xml


Cheers,
Kenneth

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
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
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to