See https://bugs.eclipse.org/bugs/show_bug.cgi?id=375565 for the workaround.

I think there may be a bug in the Jenkins hpi plugin that isn't handling 
transitive hpi dependencies correctly

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of sdoca sdoca
Sent: 24 August 2012 22:57
To: jenkinsci-users@googlegroups.com
Subject: Looking for Help with M2 Release Plugin and Hudson

Hi,

I'm using Hudson and am looking for some help with the M2 Release Plugin 
(http://wiki.hudson-ci.org/display/HUDSON/M2+Release+Plugin) which is being 
maintained in the Jenkins space.  If there's a different list/forum that's more 
appropriate to ask questions about this plugin and Hudson, I'd appreciate a 
link.

I recently upgraded to Hudson 2.2.1 and tried to upgrade the M2 Release plugin 
from 0.8.1 to 0.9.1 but I get this error:

[#|2012-08-24T15:12:37.250-0600|SEVERE|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=72;_ThreadName=Thread-1;|WebModule[/hudson]Error
 while serving http://myserver:8080/hudson/pluginManager/install
    java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
            at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
            at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)

... [snip] ...

[#|2012-08-24T15:12:37.250-0600|SEVERE|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=72;_ThreadName=Thread-1;|WebModule[/hudson]Error
 while serving http://myserver:8080/hudson/pluginManager/install
    java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
            at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
            at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)

... [snip] ...

Is this a Hudson/plugin compatability issue?

Also, when I first installed the 0.8.1 version of the plugin, I was not able to 
use it because access issues to our SCM (Mercurial).  We've now fixed that and 
I'm trying to set up a Maven release job, but the directions on the plugin page 
(https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin) but my job 
configuration page doesn't have a "Build Environment" section, nor do I have a 
"Perform Maven Release" link.  I don't know if these are differences between 
Jenkins and Hudson, the plugin versions or if I never had the plugin installed 
correctly in the first place.

Any guidance is greatly appreciated!

________________________________


**************************************************************************************
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

Reply via email to