• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • other
    • None
    • Platform: All, OS: All

      upgrade groovy to recent version

      old:

      <dependency>
      <groupId>org.codehaus.groovy</groupId>
      <artifactId>groovy</artifactId>
      <version>1.1-rc-2</version>
      </dependency>

      new:

      <dependency>
      <groupId>org.codehaus.groovy</groupId>
      <artifactId>groovy-all</artifactId>
      <version>1.5.6</version>
      </dependency>
      <dependency>

      i tried it with the trunk and the 'script console'
      seems to work fine, but i dont know where else
      groovy is used in hudson ...

          [JENKINS-2191] upgrade groovy to recent version

          Is there any particular reason why you use groovy-all, as opposed to the plain
          groovy?

          Kohsuke Kawaguchi added a comment - Is there any particular reason why you use groovy-all, as opposed to the plain groovy?

          hdenk added a comment -

          groovy-all.jar and groovy-all-minimal.jar are dedicated for embedded use of
          groovy and contain all dependencys in a way, that no conflicts can appear
          (done by package-renaming).

          this is esp. usefull for projects, that dont use a
          dependency-management in their build or use conflicting 3rd-party-libs.
          as hudson uses maven, i think you are free which one too use
          as long as you have no unresolvable conflicts.

          may be groovy-all-minimal.jar is the best choice for hudson, probably
          depends on hudsons needs and the consequences of going minimal.

          [i will try to get detail-information about difference between
          groovy-all.jar and groovy-all-minimal.jar ...]

          hdenk added a comment - groovy-all.jar and groovy-all-minimal.jar are dedicated for embedded use of groovy and contain all dependencys in a way, that no conflicts can appear (done by package-renaming). this is esp. usefull for projects, that dont use a dependency-management in their build or use conflicting 3rd-party-libs. as hudson uses maven, i think you are free which one too use as long as you have no unresolvable conflicts. may be groovy-all-minimal.jar is the best choice for hudson, probably depends on hudsons needs and the consequences of going minimal. [i will try to get detail-information about difference between groovy-all.jar and groovy-all-minimal.jar ...]

          hdenk added a comment -

          groovy-all.jar versus groovy-all-minimal.jar

          here is the answer:

          http://www.nabble.com/forum/ViewPost.jtp?post=18888927

          i hope, that helps

          hdenk added a comment - groovy-all.jar versus groovy-all-minimal.jar here is the answer: http://www.nabble.com/forum/ViewPost.jtp?post=18888927 i hope, that helps

          Code changed in hudson
          User: : kohsuke
          Path:
          trunk/hudson/main/core/pom.xml
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=13567
          Log:
          [FIXED JENKINS-2191] upgraded to Groovy 1.5.7

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: trunk/hudson/main/core/pom.xml trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=13567 Log: [FIXED JENKINS-2191] upgraded to Groovy 1.5.7

            Unassigned Unassigned
            hdenk hdenk
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: