[GRADLE-574] Make it easier to use ant optional tasks from a build Created: 29/Jul/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Won't Fix Votes: 6


 Comments   
Comment by Luke Taylor [ 20/Jan/10 ]

Not sure if something has changed since this issue was opened, but all I had to do to use the ant scp and sshexec tasks was drop the ant-jsch.jar into gradle's lib dir. This made ant.scp() and ant.sshexec() immediately available. The jsch jar itself already appears to be present (not sure why).

Comment by mark petrovic [ 29/Mar/13 ]

If one drives the build with the Wrapper, then where is "gradle's lib dir"?

I have ANT_HOME set in the environment, with the jsch jar present in ANT_HOME/lib, and the scp Ant task still will not run. I get this

"
Build file '/Users/petrovic/Projects/xoom/qa/prod/ws-server/build.gradle' line: 147

  • What went wrong:
    Execution failed for task ':ws-server:tar'.
    > Problem: failed to create task or type scp
    Cause: the class org.apache.tools.ant.taskdefs.optional.ssh.Scp was not found.
    This looks like one of Ant's optional components.
    Action: Check that the appropriate optional JAR exists in
    -ANT_HOME/lib
    -the IDE Ant configuration dialogs

Do not panic, this is a common problem.
The commonest cause is a missing JAR.

This is not a bug; it is a configuration problem

"

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:33:25 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.