[JIRA] [subversion] (JENKINS-21712) Jenkins Update breaks Subversion credential configuration

2014-07-07 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 commented on  JENKINS-21712


Jenkins Update breaks Subversion credential configuration















Even reverting to version 1.54 of subversion plugin, problem persists ...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7

2014-06-16 Thread ingmartinlo...@java.net (JIRA)












































  
ingmartinlopez
 edited a comment on  JENKINS-22393


Problem deploying EAR to WAS 7
















These are the only two jars that I copied:

	com.ibm.ws.admin.client_7.0.0.jar
	com.ibm.ws.orb_7.0.0.jar



If you look at the stacktrace:
...
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(AnnotationsProcessorImpl.java:70)
at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.processAnnotations(WARFileImpl.java:302)
...
Code from jars has already been executed, so it's not a problem of the jdk version that compiled those jars (I've checked that, but unfortunately I could't find jdk version in manifest). I think the problem is that the code from those jars is trying to analyze EAR file to find deployment annotations.
I will try disable annotation scanning (http://orebmann.blogspot.com.ar/2013/08/reducing-annotation-scanning-in.html), and then I will let you know if I succeeded.
Thanks indeed! 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7

2014-06-16 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















These are the only two jars that I copied:

	com.ibm.ws.admin.client_7.0.0.jar
	com.ibm.ws.orb_7.0.0.jar
If you look at the stacktrace:
...
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(AnnotationsProcessorImpl.java:70)
at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.processAnnotations(WARFileImpl.java:302)
...
Code from jars has already been executed, so it's not a problem of the jdk version that compiled those jars (I've checked that, but unfortunately I could't find jdk version in manifest). I think the problem is that the code from those jars is trying to analyze EAR file to find deployment annotations.
I will try disable annotation scanning (http://orebmann.blogspot.com.ar/2013/08/reducing-annotation-scanning-in.html), and then I will let you know if I succeeded.
Thanks indeed! 





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-9057) Hability to disable slaves

2014-05-26 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 commented on  JENKINS-9057


Hability to disable slaves















Ok, thanks



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-9057) Hability to disable slaves

2014-05-25 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 commented on  JENKINS-9057


Hability to disable slaves















In my case it's needed on a per slave basis. Example: you have to do maintenance to one of the slaves (so you know that this particular slave is going to be offline for a while), but you want to know if one of the others (productive) are offline to take actions.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7

2014-04-15 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















I'm using Standard WebSphere version 7.0.0.13 ... maybe is there a way to skip annotation processing when deploying EARS?
Thanks!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7

2014-03-27 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















Yes, but I had to copy them to this directory:
/var/lib/jenkins/plugins/websphere-deployer/WEB-INF/lib
Instead of:
$USER_HOME/.jenkins/plugins/websphere-deployer/WEB-INF/lib
And then restarted jenkins, because it throwed classnotfoundexception when they where in the last directory.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7

2014-03-27 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 created  JENKINS-22393


Problem deploying EAR to WAS 7















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


websphere-deployer



Created:


27/Mar/14 8:17 PM



Description:


Hello. I'm having an issue: I can't deploy an EAR to a remote WebSphere, I'm getting this error:

Connecting to IBM WebSphere Application Server...
The following artifacts will be deployed in this order...
---
facturador-ear-1.0.30.ear
---
FATAL: Implementing class
java.lang.IncompatibleClassChangeError: Implementing class
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
	at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128)
	at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:704)
	at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299)
	at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355)
	at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315)
	at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
	at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128)
	at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:704)
	at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299)
	at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355)
	at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315)
	at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
	at com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(AnnotationsProcessorImpl.java:70)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.processAnnotations(WARFileImpl.java:302)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.getDeploymentDescriptor(WARFileImpl.java:248)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.getDeploymentDescriptor(WARFileImpl.java:178)
	at com.ibm.websphere.management.application.AppDeploymentUtil.getModuleVersion(AppDeploymentUtil.java:1458)
	at com.ibm.websphere.management.application.AppDeploymentUtil.isEE5SchemaDD(AppDeploymentUtil.java:1419)
	at com.ibm.ws.management.application.client.AppInstallHelper.checkIfEE5ModulesContainXMIBindings(AppInstallHelper.java:1098)
	at com.ibm.ws.management.application.client.AppInstallHelper.checkIfEE5ModulesContainXMIBindings(AppInstallHelper.java:1063)
	at com.ibm.ws.management.application.client.AppInstallHelper.checkForEE5Restrictions(AppInstallHelper.java:324)
	at com.ibm.ws.management.application.client.AppInstallHelper.getAppDeploymentInfo(AppInstallHelper.java:377)
	at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:100)
	at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:70)
	at com.ibm.websphere.management.application.client.AppDeploymentController.readArchive(AppDeploymentController.java:208)
	at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:108)
	at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:98)
	at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.getAppName(WebSphereDeployerPlugin.java:268)
	at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.createArtifact(WebSphereDeployerPlugin.jav

[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content

2013-02-05 Thread ingmartinlo...@java.net (JIRA)














































ingmartinlopez
 commented on  JENKINS-14551


an update which contains added files merged from a branch results in those files having doubled content















Same for me. (It's really annoying!). Jenkins 1.492 and Subversion 1.43



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.