Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-dev] geoscript-groovy-1.1-SNAPSHOT
Actually it does not, it means that we explicitly cannot use groovy-all. Each time we submit a bundle that contains bundles, we have to unpack it and submit each part one at a time :D

In this case because groovy-all includes an earlier version of antlr it cannot be used.

We are looking for a solution for groovy which uses a version of antlr 3.5 or above, the trouble is the Antlr community has not updated their grammer.

- http://jira.codehaus.org/browse/GROOVY-5299 Antlr 4 grammar creation task


On Wed, Aug 14, 2013 at 5:17 AM, Jared Erickson <jared.erickson@xxxxxxxxx> wrote:
Jody,

The groovyall jar comes with antrl embedded.  Would this help?

http://mvnrepository.com/artifact/org.codehaus.groovy/groovy-all/1.8.9

Jared


On Mon, Aug 12, 2013 at 9:13 PM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
So worst case we use another flavour of GeoScript, however that has a large impact on Andrea Antonello's business.

An alternative is to make a wizard page where user's install ANTLR 2.7.x (and pretend it is a driver or something), or we make a community update site for GeoScript and distribute some of this stuff outside of the banner of LocationTech.

I have a skype meeting later today where I will try and resolve some of this - but there does not seem to be a lot of leeway. Antlr messed something up, and projects such as Groovy are impacted (until they drum up enough funding to upgrade).

Jody


On Tue, Aug 13, 2013 at 1:05 PM, Jared Erickson <jared.erickson@xxxxxxxxx> wrote:
Ugh, I haven't heard about Groovy moving off of ANTLR 2.7.x.  Even the most recent version, 2.1.6, depends on ANTRL 2.7:


I am definitely not the main point of contact for LocationTech stuff, but I can help.  I think Tim submitted GeoScript proposal.  Justin would know for sure.

Thanks,
Jared

On Aug 12, 2013, at 7:48 PM, Jody Garnett wrote:

Do not apologise - thanks so much for the getting this ready!  It is more we are being difficult hanging back on an old version while this legal review takes place.

Note that the groovy dependency is in a lot of trouble as it makes use of antrl-2.7.7. Apparently the entire Antlr 2.7.x series has IP issues. So if you hear of any action on groovy updating it would be very helpful.

At this point I am concerned we are are going to have to ask users to download antlr-2.7.7 themselves just so geoscript groovy will work :(

Jared are you the best point of contact for this LocationTech stuff? Like will you be leading the proposal for GeoScript to join LocationTech?

Jody 


On Tue, Aug 13, 2013 at 12:11 PM, Jared Erickson <jared.erickson@xxxxxxxxx> wrote:
Hi Jody,

I just pushed a branch (https://github.com/jericks/geoscript-groovy/tree/1.1-M0) that targets GeoTools 9.0-M0.  All unit tests pass but there is a slight reduction in functionality and a few known bugs.  

Justin, could you work your maven repo magic and publish geoscript-groovy 1.1-M0?  

Thanks Jody and Justin, I apologize for any problems this caused.

Jared 

On Aug 12, 2013, at 1:20 PM, Jody Garnett wrote:

Yeah we cannot upgrade to 9.4, due to feature collections API change - it no longer has events and rather then hold everyone up uDig is staying on this version until we are done incubation / legal review.

We are likely to only go through the legal review of GeoTools once each cycle, next time it will be faster only the changes will be checked. The first time the review covers all the code, and the contributor policies for each project. With that in mind let me introduce Sharon (from Eclipse) who will be in touch when I submit GeoScript for review - she may end up with a few questions.

Are you able to identify a revision that matches 9.0-M0 ?


On Tue, Aug 13, 2013 at 3:47 AM, Jared Erickson <jared.erickson@xxxxxxxxx> wrote:
Hi all!

GeoScript Groovy 1.1-SNAPSHOT compiles with GeoTools 9-M0 but three unit tests fail and getting them to pass really requires upgrading GeoTools to 9.0 at least.  Would you like a release anyways?  I can tag a version tonight that depends on 9-M0 if you would like.

I am about to release 1.1 which will depend on GeoTools 9.4.  Will that work for uDig in the future?

Thanks,
Jared


On Mon, Aug 12, 2013 at 9:21 AM, Justin Deoliveira <jdeolive@xxxxxxxxxxx> wrote:
Hey Jody,

Bringing Jared (the groovy geoscript maintainer) into the conversation. 

@jared: Let me know if there is a specific tag or revision we can push. Also i can set you up with deploy access to repo.opengeo.org, which will probably be a useful thing anyways.

-Justin




On Mon, Aug 12, 2013 at 9:36 AM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
Morning Justin:

I am trying to grind through this uDig dependency audit - and have found it is a moving target! Turns out the reason is a SNAPSHOT dependency on geoscript, which has changed its dependency since I last did a check.

Can I ask you to deploy a version we can use - way back at GeoTools 9.0-M0, and we will throw it to Eclipse legal for review.

(Not to worry if you push GeoScript through review later, they will do a "diff" on any new content and perform a faster review).

Jody



--
Justin Deoliveira
Enterprise support for open source geospatial.








Back to the top