Justin, I have uploaded the EMF jars to the osgeo repo. I do not have write access to the opengeo repo. I have created a Jira issue for the detail and patches. http://jira.codehaus.org/browse/GEOT-3466
I have everything building in GeoTools, with just one fix for WPS UOMsTypeImpl (same problems as GEOT-3431) as a class was made abstract. Don't know if it will still pass in GeoServer. Jody? Still working on GeoServer (builds in Eclipse, not javac, probably because ecj follows the *spec* and javac developers claim the spec is wrong! seen this before with generics). And the rest of youse, if anyone objects to upgrading EMF on trunk, please make yourself know. Kind regards, Ben. On 11/03/11 00:40, Justin Deoliveira wrote: > Great news Ben, this is something that have been lingering for a while now. I > doubt I will have time or a mandate to get to this before March 28 so it's al > yours. But I am of course glad to help out where I can. > > I say we pick the latest available EMF and go with that, which appears to be > 2.6.1 as you stated. So I say we grab those jars and stuff them into our > osgeo and opengeo repositories. I can do this if you don't have an account on > opengeo repo. > > +1 on pushing the dependency declaration up into the root pom as well. > > -Justin > > On Wed, Mar 9, 2011 at 8:00 PM, Ben > Caradoc-Davies<[email protected]> wrote: > Justin, > > I am quite keen to upgrade EMF to see if it helps resolve some of our > outstanding issues: > http://jira.codehaus.org/browse/GEOT-3431 > http://jira.codehaus.org/browse/GEOT-3327 > > I will not be able to devote serious time to this until 28 March at the > earliest, but you could give me a few hints as to how this should be done. > (If you are doing this yourself, please let me know.) > > - What version of EMF should we target? > > - The eclipse maven repos look far behind, and the last thing we need is > another repo in our builds (and I'm sure Andrea will agree with me). > > - EMF 2.6.1 is out: > http://www.eclipse.org/modeling/download.php?file=/modeling/emf/emf/downloads/drops/2.6.x/R201009141218/emf-xsd-SDK-2.6.1.zip > > - One of us could extract the emf/xsd/common binary and source jars from the > zip, rename them, and deploy them to the geotools repo. Is this how you > uploaded the existing artifacts? > > - This would also be a good time to put the dependencies under dependency > management in the root pom. One example, from the gt-xsd-core pom.xml: > > <dependency> > <groupId>org.eclipse.xsd</groupId> > <artifactId>xsd</artifactId> > <version>2.2.2</version> > </dependency> > <dependency> > <groupId>org.eclipse.emf</groupId> > <artifactId>common</artifactId> > <version>2.2.1</version> > </dependency> > <dependency> > <groupId>org.eclipse.emf</groupId> > <artifactId>ecore</artifactId> > <version>2.2.2</version> > </dependency> > > Just thinking aloud, so please interrupt me if I am going off track. :-) > > Kind regards, > > -- > Ben Caradoc-Davies<[email protected]> > Software Engineering Team Leader > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre > > > > -- > Justin Deoliveira > OpenGeo - http://opengeo.org > Enterprise support for open source geospatial. > > -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
