4 weeks ago - last edited 4 weeks ago
facing below error while setting up sap commerce cloud 2211 locally windows
[groovyc] org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
[groovyc] General error during conversion: class groovy.transform.AnnotationCollectorMode cannot be cast to class groovy.transform.AnnotationCollectorMode (groovy.transform.AnnotationCollectorMode is in unnamed module of loader groovy.lang.GroovyClassLoader @3a2b459a; groovy.transform.AnnotationCollectorMode is in unnamed module of loader org.apache.tools.ant.AntClassLoader @26c89563)
[groovyc]
[groovyc] java.lang.ClassCastException: class groovy.transform.AnnotationCollectorMode cannot be cast to class groovy.transform.AnnotationCollectorMode (groovy.transform.AnnotationCollectorMode is in unnamed module of loader groovy.lang.GroovyClassLoader @3a2b459a; groovy.transform.AnnotationCollectorMode is in unnamed module of loader org.apache.tools.ant.AntClassLoader @26c89563)
[groovyc] at org.codehaus.groovy.transform.ASTTransformationCollectorCodeVisitor.lambda$findCollectedAnnotations$1(ASTTransformationCollectorCodeVisitor.java:187)
[groovyc] at java.base/java.util.Optional.map(Optional.java:260)
[groovyc] at org.codehaus.groovy.transform.ASTTransformationCollectorCodeVisitor.findCollectedAnnotations(ASTTransformationCollectorCodeVisitor.java:187)
[groovyc] at org.codehaus.groovy.transform.ASTTransformationCollectorCodeVisitor.visitAnnotations(ASTTransformationCollectorCodeVisitor.java:93)
tried with playing around with below configurations but did not help
groovyc.fork=false
<extname>.groovyc.fork=false
build.parallel=false
not sure if its log path issue. current hybris installation directory path
C:\dl\core-customize\hybris\bin\custom
The problem may be related to the gradle version used. The platform requires version 7.3.3 for the build. If you installed 8.x on your machine or use and IDE such as IntelliJ, which uses gradle 8.x by default, you will get errors like that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can delete the offending script each time you get an error but that will be a very long process given how much time the build spends in executing those groovy scripts. When someone falls in the situation that you are then I tell them to delete all groovy scripts! A bit drastic but have no choice until SAP acknowledge the issue and provide a permanent solution. I wish there was a switch to skip the execution of those groovy scripts.
__PRESENT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
30 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.