Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject

2013-03-20 Thread Tomek Kaczanowski
thank you, this is exactly what I did based on the description from https://issues.jenkins-ci.org/browse/JENKINS-13465 -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an

Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject

2013-03-20 Thread Jeff
I hit that also and applied the patched m2 release plugin .HPI file attached to that defect. I use GIT + SSH and when I do a release, I have NO options checked when I do the release. On Wed, Mar 20, 2013 at 1:01 AM, Tomek Kaczanowski kaczanowski.to...@gmail.com wrote: thank you, this is

Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject

2013-03-19 Thread teilo
On Monday, 18 March 2013 18:44:18 UTC, Tomek Kaczanowski wrote: Hi James, thanks for the quick response! the simplest quick fix is to downgrade Jenkins... yeah, sure it is What version did you upgrade from - and what options/parameters are you using? 1.496 what

jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject

2013-03-18 Thread Tomek Kaczanowski
after upgrading to 1.506 when trying to do a maven release via https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin ver 0.9.1 I get this: Status Code: 500Exception: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Stacktrace:

Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject

2013-03-18 Thread teilo
the simplest quick fix is to downgrade Jenkins... What version did you upgrade from - and what options/parameters are you using? /James On Monday, 18 March 2013 16:30:28 UTC, Tomek Kaczanowski wrote: after upgrading to 1.506 when trying to do a maven release via

Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject

2013-03-18 Thread Tomek Kaczanowski
Hi James, thanks for the quick response! the simplest quick fix is to downgrade Jenkins... yeah, sure it is What version did you upgrade from - and what options/parameters are you using? 1.496 what options/parameters you are asking about? -- Regards, Tomek Kaczanowski -- You received