aXMLRPC icon indicating copy to clipboard operation
aXMLRPC copied to clipboard

Parser Exception

Open dhivya29 opened this issue 3 years ago • 4 comments

After the last update we are getting parser exception issue as of now we are using "com.github.gturri:aXMLRPC:master-SNAPSHOT " How do we resolve?

dhivya29 avatar Oct 16 '20 11:10 dhivya29

The latest commits may have brought some regressions. Sorry about that. I've reverted them until I get the time to look at it more closely and come up with a better fix. That being said, I have a few questions:

  • has your issue been fixed? (I guess it may take some time until it's fixed, because I'm not sure what is generating the master-SNAPSHOT artifact and when it runs)
  • could you give me more context on the error you had (ideally the stacktrace)? It would help me make sure I don't reintroduce this issue in the future
  • why do you reference the version master-SNAPSHOT instead of a released one (the latest being 1.12.0)? (using a released one would ensure you have deterministic build and run and would hence prevent such inconvenience)

Thanks in advance for your answers.

gturri avatar Oct 16 '20 17:10 gturri

Ok Thanks for the update.will Check andet you know.

On Fri, 16 Oct, 2020, 10:53 PM Guillaume Turri, [email protected] wrote:

The latest commits may have brought some regressions. Sorry about that. I've reverted them until I get the time to look at it more closely and come up with a better fix. That being said, I have a few questions:

  • has your issue been fixed? (I guess it may take some time until it's fixed, because I'm not sure what is generating the master-SNAPSHOT artifact and when it runs)
  • could you give me more context on the error you had (ideally the stacktrace)? It would help me make sure I don't reintroduce this issue in the future
  • why do you reference the version master-SNAPSHOT instead of a released one (the latest being 1.12.0)? (using a released one would ensure you have deterministic build and run and would hence prevent such inconvenience)

Thanks in advance for your answers.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gturri/aXMLRPC/issues/108#issuecomment-710262883, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEUY6A6NVEMXWIO77245CE3SLB6Q7ANCNFSM4STHLYLQ .

dhivya29 avatar Oct 16 '20 17:10 dhivya29

Can you please share the dependency

On Fri, 16 Oct, 2020, 11:08 PM Dhivya Balaji, [email protected] wrote:

Ok Thanks for the update.will Check andet you know.

On Fri, 16 Oct, 2020, 10:53 PM Guillaume Turri, [email protected] wrote:

The latest commits may have brought some regressions. Sorry about that. I've reverted them until I get the time to look at it more closely and come up with a better fix. That being said, I have a few questions:

  • has your issue been fixed? (I guess it may take some time until it's fixed, because I'm not sure what is generating the master-SNAPSHOT artifact and when it runs)
  • could you give me more context on the error you had (ideally the stacktrace)? It would help me make sure I don't reintroduce this issue in the future
  • why do you reference the version master-SNAPSHOT instead of a released one (the latest being 1.12.0)? (using a released one would ensure you have deterministic build and run and would hence prevent such inconvenience)

Thanks in advance for your answers.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gturri/aXMLRPC/issues/108#issuecomment-710262883, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEUY6A6NVEMXWIO77245CE3SLB6Q7ANCNFSM4STHLYLQ .

dhivya29 avatar Oct 16 '20 17:10 dhivya29

I'm not sure I understand which dependency you're talking about (in the sense that I've never released any master-SNAPSHOT artifact myself.

Could you use version 1.12.0 instead? Does it fix the issue you're experiencing?

gturri avatar Oct 16 '20 18:10 gturri