I am using Angular and Ionic to create hybrid application.
Gradle 7.4.2
Java: java 17.0.2 2022-01-18 LTS
Ionic: 5.0.0
Angular CLI: 13.2.4
Node: 16.14.0
Package Manager: npm 8.3.1
OS: win32 x64
Here is the console snippet for better understanding.
Checking Java JDK and Android SDK versions
ANDROID_SDK_ROOT=C:\SDK (recommended setting)
ANDROID_HOME=C:\SDK (DEPRECATED)
Using Android SDK: C:\SDK
Subproject Path: CordovaLib
Subproject Path: app
Starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons could not be reused, use --status for details
FAILURE: Build failed with an exception.
Where:
Settings file 'C:\Users\Alok Sarkar\Desktop\WBMDMS\WBMDMS\platforms\android\settings.gradle'
What went wrong:
Could not compile settings file 'C:\Users\Alok Sarkar\Desktop\WBMDMS\WBMDMS\platforms\android\settings.gradle'.
startup failed:
General error during conversion: Unsupported class file major version 61
java.lang.IllegalArgumentException: Unsupported class file major version 61
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:189)
[ERROR] An error occurred while running subprocess cordova.
cordova.cmd build android exited with exit code 1.
We have been trying to get Pipeline working on Jenkins 2.107 however it keeps coming up with an error that i have struggled to locate online. We have a Windows 2008 R2 server with Jenkins running as a service.
I have installed the pipeline plugin and set up the Hello World provided to test it. As soon s it starts to build it throws this error to the console.
Running in Durability level: MAX_SURVIVABILITY [BFA] Scanning build
for known causes... [BFA] No failure causes found [BFA] Done. 0s
java.lang.ClassNotFoundException:
org.kohsuke.groovy.sandbox.GroovyInterceptor at
jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374)
at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327)
at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) Caused:
java.lang.NoClassDefFoundError:
org/kohsuke/groovy/sandbox/GroovyInterceptor at
org.jenkinsci.plugins.workflow.cps.CpsGroovyShellFactory.makeClassLoader(CpsGroovyShellFactory.java:113)
at
org.jenkinsci.plugins.workflow.cps.CpsGroovyShellFactory.build(CpsGroovyShellFactory.java:119)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:556)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:520)
at
org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:319)
at
hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
We are running Java 8 and i have set Jenkins to use Java 8 in the config file. I have researched this error but can't seem to find something similar.
We have another server which runs pipeline fine however the differences are that this is windows 2012 server and it is running an older version of Jenkins and Java. Other than the two differences all plugins and config match.
I had this error and resolved it by upgrading the Script Security plugin to version 1.44 (had 1.41).
I'm trying to run an application in Grails but I have a problem with the execution. I'm using grails version 2.5.4 and Java version 1.7.
I checked my enviroment variables and they turned out to be OK.
This is the error:
Error occurred during initialization of VM agent library failed to init: instrument.
Error opening zip file or JAR manifest missing : C:\Program%20Files\Grails\grails-2.5.4\lib\org.springframework\springloaded\jars\springloaded-1.2.4.RELEASE.jar
Error | Forked Grails VM exited with error
What's going on?
I have a webapp with a web service in it and little else being converted from RAD 8 to RAD 9. I go to publish this app, and I get the following warning. Yet, the app does publish, although it needs a restart. I created the web service and everything in RAD. I am not running these tools manually. I don't really understand what I am supposed to do with this error.
Publishing failed
deployFailure
Deploying eNotesApp
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer had errors:
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer had errors:
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer had errors:
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer had errors:
Errors occurred during wsgen.
Errors occurred during wsgen.
error: compilation failed, errors should have been reported
warning: The apt tool and its associated API are planned to be
removed in the next major JDK release. These features have been
superseded by javac and the standardized annotation processing API,
javax.annotation.processing and javax.lang.model. Users are
recommended to migrate to the annotation processing features of
javac; see the javac man page for more information.
Note: ap round: 1
Problem encountered during annotation processing;
see stacktrace below for more information.
java.lang.NullPointerException
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalType(WebServiceVisitor.java:794)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalParameter(WebServiceVisitor.java:694)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalMethod(WebServiceVisitor.java:661)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceVisitor.methodsAreLegal(WebServiceVisitor.java:611)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceVisitor.isLegalImplementation(WebServiceVisitor.java:529)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceVisitor.shouldProcessWebService(WebServiceVisitor.java:332)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceVisitor.visitClassDeclaration(WebServiceVisitor.java:123)
at com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl.accept(ClassDeclarationImpl.java:125)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceAP.buildModel(WebServiceAP.java:329)
at com.ibm.jtc.jax.tools.ws.processor.modeler.annotation.WebServiceAP.process(WebServiceAP.java:270)
at com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:83)
at com.sun.tools.apt.comp.Apt.main(Apt.java:492)
at com.sun.tools.apt.main.AptJavaCompiler.compile(AptJavaCompiler.java:282)
at com.sun.tools.apt.main.Main.compile(Main.java:1139)
at com.sun.tools.apt.main.Main.compile(Main.java:1001)
at com.sun.tools.apt.Main.processing(Main.java:125)
at com.sun.tools.apt.Main.process(Main.java:115)
at com.sun.tools.apt.Main.process(Main.java:97)
at com.ibm.jtc.jax.tools.ws.wscompile.WsgenTool.buildModel(WsgenTool.java:223)
at com.ibm.jtc.jax.tools.ws.wscompile.WsgenTool.run(WsgenTool.java:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:76)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:607)
at com.ibm.ast.ws.jaxws.emitter.jws22.v85.command.AbstractWsGenCommand.execute(AbstractWsGenCommand.java:134)
at com.ibm.ast.ws.jaxws.emitter.command.WebServiceAPCommand.execute(WebServiceAPCommand.java:50)
at com.ibm.ast.ws.jaxws.deployer.JAXWSWebServiceAPInvoker.executeWSAPForProject(JAXWSWebServiceAPInvoker.java:141)
at com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer.execute(JAXWSDeployer.java:98)
at org.eclipse.jst.j2ee.internal.deploy.J2EEDeployOperation.deploy(J2EEDeployOperation.java:183)
at org.eclipse.jst.j2ee.internal.deploy.J2EEDeployOperation.execute(J2EEDeployOperation.java:113)
at com.ibm.etools.server.task.ejbdeploy.internal.JEEDeployPublisher.execute(JEEDeployPublisher.java:207)
at org.eclipse.wst.server.core.internal.Publisher.execute(Publisher.java:176)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.executePublishers(ServerBehaviourDelegate.java:1277)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:960)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3153)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
OK
OK
OK
Bizarrely, this seems to be the result of some leftover artifacts from when I was working with policy sets in RAD 8. The result was that the META-INF directory had some files to describe the policy sets (though they were set to inoccuous settings). Once removed, the warning went away. Evidently something about these RAD 8 generated files triggered the behavior, even though they did not do so in RAD 8.
We're running play 1.2.4 (mbknor-3 version) on our ubuntu CI server, Java 7.
Today, for no apparent reason, we started getting these errors on all branches, even those where no code was committed, and a previous build had completed successfully.
The error is happening when I do play start and then curl localhost:9000. I've tried running play clean and play deps --sync, and rebooting the server, and also verified the server didn't run out of harddrive space.
Any idea what could cause this? How to debug it?
2012-06-11 08:47:51,255 INFO (play) ~ Starting /home/ubuntu/programs/teamcity/buildAgent/work/a9561c50f06f33d5/portal/src
2012-06-11 08:47:51,259 INFO (play) ~ Module less is available (/home/ubuntu/programs/teamcity/buildAgent/work/a9561c50f06f33d5/portal/src/modules/less-0.9)
2012-06-11 08:47:51,260 INFO (play) ~ Module secure is available (/home/ubuntu/programs/play/play-1.2.4-mbknor-3/modules/secure)
2012-06-11 08:47:51,261 INFO (play) ~ Module crud is available (/home/ubuntu/programs/play/play-1.2.4-mbknor-3/modules/crud)
2012-06-11 08:47:53,608 DEBUG (com.asual.lesscss.LessEngine) ~ Initializing LESS Engine.
2012-06-11 08:47:53,945 DEBUG (com.asual.lesscss.LessEngine) ~ Using implementation version: Rhino 1.7 release 3 2011 07 19
2012-06-11 08:47:55,396 WARN (play) ~ You're running Play! in DEV mode
2012-06-11 08:47:55,716 INFO (play) ~ Listening for HTTP on port 9000 (Waiting a first request to start) ...
2012-06-11 08:48:04,566 ERROR (play) ~
#6ajlb3agi
Internal Server Error (500) for request GET /
Oops: ExceptionInInitializerError
An unexpected error occured caused by exception ExceptionInInitializerError: null
play.exceptions.UnexpectedException: Unexpected Error
at play.Invoker$Invocation.onException(Invoker.java:244)
at play.Invoker$Invocation.run(Invoker.java:286)
at Invocation.HTTP Request(Play!)
Caused by: java.lang.ExceptionInInitializerError
at play.templates.TemplateLoader.load(TemplateLoader.java:78)
at play.mvc.Router.parse(Router.java:162)
at play.mvc.Router.parse(Router.java:190)
at play.mvc.Router.parse(Router.java:164)
at play.mvc.Router.load(Router.java:48)
at play.mvc.Router.detectChanges(Router.java:219)
... 1 more
Caused by: groovy.lang.MissingFieldException: No such field: metaClass for class: java.lang.Class
at groovy.lang.MetaClassImpl.getAttribute(MetaClassImpl.java:1074)
at groovy.lang.MetaClassImpl.getStaticProperty(MetaClassImpl.java:1308)
at groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:707)
at org.codehaus.groovy.runtime.Invoker.getProperty(Invoker.java:727)
at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:206)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:295)
at Script1.run(Script1.groovy:1)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:521)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:496)
at play.templates.GroovyTemplate.<clinit>(GroovyTemplate.java:62)
... 7 more
2012-06-11 08:48:04,569 ERROR (play) ~ Error during the 500 response generation
java.lang.NoClassDefFoundError: Could not initialize class play.templates.GroovyTemplate
at play.templates.TemplateLoader.load(TemplateLoader.java:78)
at play.templates.TemplateLoader.load(TemplateLoader.java:172)
at play.server.PlayHandler.serve500(PlayHandler.java:778)
at play.server.PlayHandler$NettyInvocation.run(PlayHandler.java:237)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
This is a weird problem, but I have a resolution.
The problem seems to be caused by a jar collision with the - groovy -> groovy-all-1.0-jsr 05 dependency.
I added this dependency to my project a long time ago, in order to run groovy scripts from my project.
Since then, it seems this dependency is no longer necessary for my project.
In fact, my project's build has been ignoring this dependency for quite some time:
:: problems summary :: :::: WARNINGS
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: groovy#groovy-all-1.0-jsr;05: java.text.ParseException:
inconsistent module descriptor file found in
'http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/05/groovy-all-1.0-jsr-05.pom':
bad module name: expected='groovy-all-1.0-jsr' found='groovy-all'; bad
revision: expected='05' found='1.0-jsr-05';
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS mavenCentral: bad module name found in
http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/05/groovy-all-1.0-jsr-05.pom:
expected='groovy-all-1.0-jsr found='groovy-all'
mavenCentral: bad revision found in
http://repo1.maven.org/maven2/groovy/groovy-all-1.0-jsr/05/groovy-all-1.0-jsr-05.pom:
expected='05 found='1.0-jsr-05'
Yesterday, for some voodoo reason, on our CI machine (and no other machine), this dependency started resolving correctly, fetching this file, and causing class loading issues. This is rather unsettling, as I still don't know what has changed, and I'm a bit concerned this could happen to our production machines.
The resolution was getting rid of this dependency.