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

2014-09-15 Thread pandr...@bcbsm.com (JIRA)















































Pearl Andrew
 assigned  JENKINS-22393 to Pearl Andrew



Problem deploying EAR to WAS 7
















Change By:


Pearl Andrew
(15/Sep/14 6:48 PM)




Assignee:


GregPeters
PearlAndrew



























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-09-15 Thread pandr...@bcbsm.com (JIRA)














































Pearl Andrew
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















Which release is this fix part of?



























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-09-15 Thread pandr...@bcbsm.com (JIRA)















































Pearl Andrew
 assigned  JENKINS-22393 to Greg Peters



Problem deploying EAR to WAS 7
















Change By:


Pearl Andrew
(15/Sep/14 6:50 PM)




Assignee:


PearlAndrew
GregPeters



























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-08-28 Thread meng...@gmail.com (JIRA)












































 
mohamed amin mengat
 edited a comment on  JENKINS-22393


Problem deploying EAR to WAS 7
















Hi Greg;

Im facing the same problem deploying ear in WAS7, could you please let me know if the fix is available?!?

Caused by: com.ibm.websphere.management.application.client.AppDeploymentException:  Root exception is java.lang.IncompatibleClassChangeError: Implementing class
	at com.ibm.websphere.management.application.AppManagementFactory.handleException(AppManagementFactory.java:555)
	at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:123)
	at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:77)
	at com.ibm.websphere.management.application.client.AppDeploymentController.readArchive(AppDeploymentController.java:210)
	at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:108)
	... 13 more

Kind Regards

Mohamed Amin Mengat



























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-08-28 Thread meng...@gmail.com (JIRA)














































mohamed amin mengat
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















Hi Greg;

Im facing the same problem deploying in ear in WAS7, could you please let me know if the fix is available?!?

Caused by: com.ibm.websphere.management.application.client.AppDeploymentException:  Root exception is java.lang.IncompatibleClassChangeError: Implementing class
	at com.ibm.websphere.management.application.AppManagementFactory.handleException(AppManagementFactory.java:555)
	at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:123)
	at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:77)
	at com.ibm.websphere.management.application.client.AppDeploymentController.readArchive(AppDeploymentController.java:210)
	at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:108)
	... 13 more

Kind Regards

Mohamed Amin Mengat



























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-07-11 Thread gregpeter...@gmail.com (JIRA)















































Greg Peters
 resolved  JENKINS-22393 as Fixed


Problem deploying EAR to WAS 7
















Currently fixed in test. Will publish this change.





Change By:


Greg Peters
(11/Jul/14 7:02 PM)




Status:


InProgress
Resolved





Assignee:


GregPeters





Fix Version/s:


current





Resolution:


Fixed



























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-07-11 Thread gregpeter...@gmail.com (JIRA)














































Greg Peters
 started work on  JENKINS-22393


Problem deploying EAR to WAS 7
















Change By:


Greg Peters
(11/Jul/14 7:01 PM)




Status:


Open
InProgress



























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-07-11 Thread gregpeter...@gmail.com (JIRA)














































Greg Peters
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















Thank you Flo!



























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-07-10 Thread flow...@gmail.com (JIRA)














































Florent Moisson
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















Same issue with a WebSphere Application Server 8.0.0 but the stacktrace is different. 

I tried ...

	two different vendor JRE 6 : sun  openjdk.
	other version of ibm jars 8.5.5
	to delete the class "EJBModuleLocator" (class use line 272 in EjbJar30NoDDImportStrategyImpl) to see if 2 versions exists in the class loader, result : ClassNotFoundException.



It's really weird, does anyone have an idea?

Stacktrace :

Caused by: java.lang.IncompatibleClassChangeError: Implementing class
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
	at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138)
	at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:755)
	at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309)
	at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365)
	at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325)
	at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
	at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138)
	at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:755)
	at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309)
	at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365)
	at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325)
	at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.EjbJar30NoDDImportStrategyImpl$EjbJar30NoDDDiscriminator.hasContent(EjbJar30NoDDImportStrategyImpl.java:272)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.EjbJar30NoDDImportStrategyImpl$EjbJar30NoDDDiscriminator.canImport(EjbJar30NoDDImportStrategyImpl.java:114)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.openArchive(ArchiveTypeDiscriminatorImpl.java:215)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.openUsingChild(ArchiveTypeDiscriminatorImpl.java:252)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.openArchive(ArchiveTypeDiscriminatorImpl.java:209)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.openSpecificArchive(ArchiveTypeDiscriminatorImpl.java:435)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.RootEJBJarDescriminatorImpl.openSpecificArchive(RootEJBJarDescriminatorImpl.java:57)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.RootEJBJarDescriminatorImpl.openSpecificArchive(RootEJBJarDescriminatorImpl.java:31)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.ArchiveTypeDiscriminatorImpl.fullOpenArchive(ArchiveTypeDiscriminatorImpl.java:413)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.RootEJBJarDescriminatorImpl.fullOpenArchive(RootEJBJarDescriminatorImpl.java:52)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.CommonarchiveFactoryImpl.openEJBJarFile(CommonarchiveFactoryImpl.java:1614)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl.openNestedArchive(EARFileImpl.java:1445)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl.openNestedArchive(EARFileImpl.java:1381)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.openNestedArchive(LoadStrategyImpl.java:1113)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.createFile(LoadStrategyImpl.java:318)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.createFile(LoadStrategyImpl.java:245)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.ZipFileLoadStrategyImpl.getFiles(ZipFileLoadStrategyImpl.java:358)
	at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStrategyImpl.collectFiles(LoadStrategyImpl.java:681)
	at 

[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] [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-14 Thread gregpeter...@gmail.com (JIRA)














































Greg Peters
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















One of two things is happening here. The are duplicate classes in the WebSphere Deployer Plugin libs(i.e. you copied more jars than the instructions say). Or, the Java version of the websphere jar files are incompatible with this plugin. If you check the version of the websphere jar files (reference: http://stackoverflow.com/questions/4440896/java-which-version-was-a-jar-file-built-too). This plugin is compiled using JDK 1.6 (oracle).



























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-04-08 Thread gregpeter...@gmail.com (JIRA)














































Greg Peters
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















What type of WebSphere are you using? ND? Standard?



























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 

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

2014-03-27 Thread gregpeter...@gmail.com (JIRA)














































Greg Peters
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















Have you included the WebSphere jar libraries for the plugin?



























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.