Mule

Upgrade Groovy version to 1.6.x

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.2
  • Fix Version/s: 3.0.0-M2
  • Component/s: Build: Distributions
  • Labels:
    None
  • User impact:
    Low
  • Similar Issues:
    MULE-4701 Update Groovy to 1.7.x
    MULE-3286 Upgrade Groovy dependency to 1.5.x
    MULE-3739 Upgrade to version 3.0.4 of smack API
    MULE-2855 Upgrade Groovy dependency to 1.5.4
    MULE-5622 Upgrade Groovy to 1.8.x
    MULE-1821 Upgrade Jetty version
    MULE-3350 Upgrade to latest CXF version
    MULE-6006 Upgrade CXF version to 2.5.1
    MULE-941 We should upgrade to the new Version of Jotm
    MULE-5922 Upgrade CXF version to latest (2.5.0)

Description

1.6 is finally out, after a number of RCs: http://groovy.codehaus.org/Download

Issue Links

Related
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment - 03/Mar/09 05:50 PM

Groovy 1.6.0 also bundles the JSR-223 scripting engine OOTB, so we can drop it from the distribution too

Show
Andrew Perepelytsya added a comment - 03/Mar/09 05:50 PM Groovy 1.6.0 also bundles the JSR-223 scripting engine OOTB, so we can drop it from the distribution too
Hide
Permalink
Ittai Balaban added a comment - 02/Jan/10 03:07 PM

By now, Groovy 1.7 has been released.

At present working with Mule/Groovy in Eclipse is very unpleasant, because while Mule uses v1.5.6, the Eclipse Groovy plugin is compatible with either 1.6.7 or 1.7. This causes frequently bad interaction, due to incompatibility between the 1.5.6 and 1.6.7/1.7 Groovy compilers.

Are there any plans to upgrade the Groovy dependency?

Show
Ittai Balaban added a comment - 02/Jan/10 03:07 PM By now, Groovy 1.7 has been released. At present working with Mule/Groovy in Eclipse is very unpleasant, because while Mule uses v1.5.6, the Eclipse Groovy plugin is compatible with either 1.6.7 or 1.7. This causes frequently bad interaction, due to incompatibility between the 1.5.6 and 1.6.7/1.7 Groovy compilers. Are there any plans to upgrade the Groovy dependency?
Hide
Permalink
Dirk Olmes added a comment - 02/Jan/10 11:20 PM

Yes, we plan to update, hence this JIRA.

However, this is not top priority. If someone steps up and attaches a patch will move this issue up in the priority chain (hint, hint).

Show
Dirk Olmes added a comment - 02/Jan/10 11:20 PM Yes, we plan to update, hence this JIRA. However, this is not top priority. If someone steps up and attaches a patch will move this issue up in the priority chain (hint, hint).
Hide
Permalink
Ittai Balaban added a comment - 03/Jan/10 11:24 AM

Point taken.

Is there any documentation you can point me at, towards generating updated POM file/s? I've looked at these previously, and don't quite understand how you manage your dependency versioning.

Show
Ittai Balaban added a comment - 03/Jan/10 11:24 AM Point taken. Is there any documentation you can point me at, towards generating updated POM file/s? I've looked at these previously, and don't quite understand how you manage your dependency versioning.
Hide
Permalink
Dirk Olmes added a comment - 04/Jan/10 06:27 AM

I see your confusion ... for starters, I have removed the confusing version properties from the toplevel POM, they're not used anywhere.

http://fisheye.codehaus.org/changelog/mule/?cs=16359

Show
Dirk Olmes added a comment - 04/Jan/10 06:27 AM I see your confusion ... for starters, I have removed the confusing version properties from the toplevel POM, they're not used anywhere. http://fisheye.codehaus.org/changelog/mule/?cs=16359
Hide
Permalink
Dirk Olmes added a comment - 04/Jan/10 07:18 AM

Now that you got me started, I went all the way:

http://fisheye.codehaus.org/changelog/mule/?cs=16360

Groovy 1.7 is not yet available in public repositories ...

Show
Dirk Olmes added a comment - 04/Jan/10 07:18 AM Now that you got me started, I went all the way: http://fisheye.codehaus.org/changelog/mule/?cs=16360 Groovy 1.7 is not yet available in public repositories ...
Hide
Permalink
Dirk Olmes added a comment - 04/Jan/10 07:34 AM

Of course I forgot to update the launch scripts. See why we shy away from groovy updates?

http://fisheye.codehaus.org/changelog/mule/?cs=16363

Show
Dirk Olmes added a comment - 04/Jan/10 07:34 AM Of course I forgot to update the launch scripts. See why we shy away from groovy updates? http://fisheye.codehaus.org/changelog/mule/?cs=16363
Hide
Permalink
Ittai Balaban added a comment - 04/Jan/10 08:58 AM

I'm happy to be the catalyst.

Groovy 1.7 is out on the codehaus repository - http://repository.codehaus.org
Note the eclipse groovy plugin supports 1.7 and 1.6.7. I imagine 1.6.7 is compiler-compatible with 1.6.5, but have not tried it out.

Show
Ittai Balaban added a comment - 04/Jan/10 08:58 AM I'm happy to be the catalyst. Groovy 1.7 is out on the codehaus repository - http://repository.codehaus.org Note the eclipse groovy plugin supports 1.7 and 1.6.7. I imagine 1.6.7 is compiler-compatible with 1.6.5, but have not tried it out.
Hide
Permalink
Dirk Olmes added a comment - 05/Jan/10 07:09 AM

Oh fun! Groovy 1.7.0 causes test failures. So let's go back to Groovy 1.6.7 for now. As a good side effect, the launcher scripts do not require constant updates any more as they detect the used JARs now.

http://fisheye.codehaus.org/changelog/mule/?cs=16373

Show
Dirk Olmes added a comment - 05/Jan/10 07:09 AM Oh fun! Groovy 1.7.0 causes test failures. So let's go back to Groovy 1.6.7 for now. As a good side effect, the launcher scripts do not require constant updates any more as they detect the used JARs now. http://fisheye.codehaus.org/changelog/mule/?cs=16373
Hide
Permalink
Dirk Olmes added a comment - 05/Jan/10 09:04 AM

merge to 3.0-M2 release branch: http://fisheye.codehaus.org/changelog/mule/?cs=16374

Show
Dirk Olmes added a comment - 05/Jan/10 09:04 AM merge to 3.0-M2 release branch: http://fisheye.codehaus.org/changelog/mule/?cs=16374
Hide
Permalink
Ittai Balaban added a comment - 05/Jan/10 09:18 AM

Sounds good.

Could there be some bad interaction between spring scripting, and the groovy version? Looking at the spring 2.5 docs, it states it requires groovy 1.5.x

Show
Ittai Balaban added a comment - 05/Jan/10 09:18 AM Sounds good. Could there be some bad interaction between spring scripting, and the groovy version? Looking at the spring 2.5 docs, it states it requires groovy 1.5.x
Hide
Permalink
Dirk Olmes added a comment - 05/Jan/10 09:32 AM

Possibly. I have no idea about spring-scripting, though.

This smells like your chance for community participation Please file a new JIRA with your findings.

Show
Dirk Olmes added a comment - 05/Jan/10 09:32 AM Possibly. I have no idea about spring-scripting, though. This smells like your chance for community participation Please file a new JIRA with your findings.

People

Vote (2)
Watch (2)

Dates

  • Created:
    23/Feb/09 09:21 AM
    Updated:
    05/Jan/10 09:32 AM
    Resolved:
    05/Jan/10 09:04 AM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.