• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • groovy-plugin
    • None

      Currently @Grab works only in Groovy scripts run on a forked JVM. In a Script Console and System Groovy Scripts it ends with:

      FATAL: org/apache/ivy/core/report/ResolveReport
      java.lang.NoClassDefFoundError: org/apache/ivy/core/report/ResolveReport
      

      It is sometimes useful to be able to extend script abilities with external libs (like HTTP Builder).

          [JENKINS-18349] Allow to use @Grab in a Script Console

          Marcin Zajączkowski created issue -

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          changelog.html
          pom.xml
          http://jenkins-ci.org/commit/jenkins/2ad427f6c3d187c5b330151b85e1a578e340cf2a
          Log:
          [FIXED JENKINS-18349 JENKINS-18405]

          Integrated the fix toward 1.521.

          Compare: https://github.com/jenkinsci/jenkins/compare/0b8917b34479...2ad427f6c3d1

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/2ad427f6c3d187c5b330151b85e1a578e340cf2a Log: [FIXED JENKINS-18349 JENKINS-18405] Integrated the fix toward 1.521. Compare: https://github.com/jenkinsci/jenkins/compare/0b8917b34479...2ad427f6c3d1

          I'm not seeing any fix for @Grab Grape support in the github links from the previous comment.
          The same issue was fixed in job-dsl-plugin, see https://issues.jenkins-ci.org/browse/JENKINS-16361
          There's also a document about embedding groovy here http://groovy.codehaus.org/Embedding+Groovy

          It would be great if groovy grape support is added to Jenkins.

          Simona Avornicesei added a comment - I'm not seeing any fix for @Grab Grape support in the github links from the previous comment. The same issue was fixed in job-dsl-plugin, see https://issues.jenkins-ci.org/browse/JENKINS-16361 There's also a document about embedding groovy here http://groovy.codehaus.org/Embedding+Groovy It would be great if groovy grape support is added to Jenkins.
          vjuranek made changes -
          Assignee Original: vjuranek [ vjuranek ] New: Lucie Votypkova [ lvotypkova ]

          Daniel Beck added a comment -

          Not a bug.

          Daniel Beck added a comment - Not a bug.
          Daniel Beck made changes -
          Issue Type Original: Bug [ 1 ] New: New Feature [ 2 ]
          Patrice Matignon made changes -
          Link New: This issue is related to JENKINS-15512 [ JENKINS-15512 ]

          Daniel Beck added a comment -

          Is this about the Groovy plugin (Groovy and system Groovy build steps), or core (Script Console in /manage and for each slave)?

          Daniel Beck added a comment - Is this about the Groovy plugin (Groovy and system Groovy build steps), or core (Script Console in /manage and for each slave)?

          This is about the Script Console and pretty much every place but the Groovy Plug-in and Groovy build step. Perhaps most importantly moving forward, this issue impacts scripts run by the Workflow plug-in.

          Kenneth Baltrinic added a comment - This is about the Script Console and pretty much every place but the Groovy Plug-in and Groovy build step. Perhaps most importantly moving forward, this issue impacts scripts run by the Workflow plug-in.

          Daniel Beck added a comment -

          kbaltrinic: To clarify, the 'Groovy script' build step is not affected (unsurprising, as it's a straightforward groovy invocation), but the 'system Groovy script' build step in Groovy plugin is?

          Regarding scope, did you contact the reporter or is that your interpretation of this report? (Note that not too long ago, component names did not have the '-plugin' suffix making it difficult to tell in some cases whether a report is about the "something" related features in Jenkins, or the "something plugin".)

          I'm asking because I'd like to split this into one issue per component. This way (IMO) the issues have a change to actually get implemented by the respective plugins'/core maintainers.

          Daniel Beck added a comment - kbaltrinic : To clarify, the 'Groovy script' build step is not affected (unsurprising, as it's a straightforward groovy invocation), but the 'system Groovy script' build step in Groovy plugin is? Regarding scope, did you contact the reporter or is that your interpretation of this report? (Note that not too long ago, component names did not have the '-plugin' suffix making it difficult to tell in some cases whether a report is about the "something" related features in Jenkins, or the "something plugin".) I'm asking because I'd like to split this into one issue per component. This way (IMO) the issues have a change to actually get implemented by the respective plugins'/core maintainers.

            vjuranek vjuranek
            emszpak Marcin Zajączkowski
            Votes:
            12 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated: