Open GoogleCodeExporter opened 9 years ago
Taking a look now.
Original comment by keith.cl...@gmail.com
on 5 Jan 2015 at 11:41
I'm confused. I don't see any file changes.
Original comment by paul.bac...@arcusglobal.com
on 5 Jan 2015 at 12:03
A solution is to use the ant-salesforce.jar that's under this projects /lib/
directory.
As documented it looks like the API has changed so if you use the latest from
(salesforce_ant_32.zip) salesforce it just silently fails.
Original comment by paul.bac...@arcusglobal.com
on 5 Jan 2015 at 12:18
[deleted comment]
[deleted comment]
Yeah the ant-deploy-with-xml-report-task-1.4.jar code outputs the test results
by replacing and then calling a method with this signature:
public void handleResponse(MetadataConnection metadataConnection, AsyncResult response) throws ConnectionException
but the API 32 ant-salesforce.jar has changed the signature used in the call to
this (so the above method is never called):
public void handleResponse(MetadataConnection metadataConnection, SFDCMDAPIAntTask.StatusResult response) throws ConnectionException
Using an earlier version of ant-salesforce.jar is the easiest workaround.
Original comment by keith.cl...@gmail.com
on 5 Jan 2015 at 12:45
Original comment by keith.clarke.claimvantage@gmail.com
on 5 Jan 2015 at 1:04
That older version of the ant-salesforce.jar doesn't appear to support resuming
a job by re-calling with the sf.asyncRequestId property populated. It just
gives me a "Invalid id specified for sf.asyncRequestId".
Any ideas how to work around that? I do nightly runs of all our bulk-test
cases, and I need to be able to retry if they time-out.
Original comment by dexter.d...@gmail.com
on 8 Jan 2015 at 6:14
The code change to work with the latest ant-salesforce.jar looks simple enough.
I'll hopefully find the time to try it over the next few days.
Original comment by keith.clarke.claimvantage@gmail.com
on 8 Jan 2015 at 6:38
@keith, could you please provide idea which code change should be applied to
recompile this jar for latest ant-salesforce.jar. Thanks in advance.
Original comment by natallia...@gmail.com
on 2 Feb 2015 at 1:35
Took a more careful look this morning and the code change is more awkward than
I thought because SFDCMDAPIAntTask.StatusResult has package visibility set.
That means that the task must be located in the same package so instead of the
task being com.claimvantage.force.ant.DeployWithXmlReportTask it will have to
be instead something like
com.salesforce.ant.ClaimVantageDeployWithXmlReportTask and so a change will be
needed to your build.xml files. (There is nothing in Java that stops you adding
classes to packages that use someone else's name but it is relatively unusual.)
I've tried it out and it works OK. Thoughts anyone?
Original comment by keith.clarke.claimvantage@gmail.com
on 2 Feb 2015 at 1:41
My build.xml is 95% handwritten anyways, so that sounds just fine to me.
Original comment by dexter.d...@gmail.com
on 3 Feb 2015 at 3:02
Any update on this issue? Would love to have a fix. Regressing my
ant-salesforce to the older version (in this project's lib directory) gives me
the error
"Failed to login: Unexpected element. Parser was expecting element
urn:partner.soap.sforce.com:orgAttachmentFileSizeLimit' but found
'urn:partner.soap.sforce.com:orgDefaultCurrencyIsoCode'"
Original comment by jer...@dashcord.com
on 13 May 2015 at 6:47
Original issue reported on code.google.com by
paul.bac...@arcusglobal.com
on 31 Dec 2014 at 3:17