Schema registry build failed, Failed to execute goal org.apache.maven.plugins:maven-plugin-plugin - maven-plugin

Build of schema-registry failed at maven-plugin
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor
(default-descriptor) on project kafka-schema-registry-maven-plugin:
Execution default-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor failed:
syntax error #[1,1] in
file:/Users/.../#Kafka_Study/schema-registry/maven-plugin/src/main/java/io/confluent/kafka/schemaregistry/maven/SchemaRegistryMojo.java
Can someone help identify the issue. Any help is appreciated.

Related

Getting "Invalid value type" error when trying to execute yarn in my react-rails project

I am getting:
error An unexpected error occurred: "Invalid value type 2:0 in /Users/myname/Desktop/work2/reservations_fully_paid/Foggle/yarn.lock".
info If you think this is a bug, please open a bug report with the information provided in "/Users/myname/Desktop/work2/reservations_fully_paid/Foggle/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
When trying to execute yarn in my react-rails project

How to fix the error "the flink application failed to deploy on yarn"

The following is the error message snapshot.
Increasing max open files would fix the issue.

Failed to read key from store Invalid keystore format codenameone

I am failing create a build online for release on Playstore. This is the build error message that i am facing.
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':packageRelease'.
Failed to read key essap from store "/tmp/build8775516520051228608xxx/EssentialService/keyStore": Invalid keystore format
Try:
Run with --debug option to get more log output. Run with --scan to get full insights.
Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':packageRelease'.
I used the codenameone settings application to generate. Its found right click project -> codename one -> Settings

unable toncomplete build on adding android certificate

I just finished building my app and I sent a build with no certificate and it worked...now on adding an android certificate, it reports a build error on my codename one dashboard. A help will be appreciated.
FAILURE: Build failed with an exception. * What went wrong: Execution
failed for task '
:transformClassesAndResourcesWithProguardForRelease'. >
java.io.IOException: Please correct the above warnings first.
Warning: Exception while processing task java.io.IOException: Please correct the above warnings first.
:transformClassesAndResourcesWithProguardForRelease FAILED
:transformClassesAndResourcesWithProguardForRelease (Thread[Daemon
worker,5,main]) completed. Took 4.163 secs.
I will need the full error as that point is already too low. I recall seeing some failures when punctuation was used in one of the certificate properties as Android chokes on that. It should appear in the error logs.

Error on sonar-maven-plugin when analyzing csharp projects

I got an error when analyzing csharp projects in sonar 3.1.1
It fails to execute sonar-maven-plugin. Here is my log file data.
[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on
project MyProject: Can not execute Sonar: Error occured while reading Visual Studio files.
Could not evaluate the expression com.sun.org.apache.xpath.internal.jaxp.XPathExpressionImpl#ec73b9 on project
D:\projects\MyProject\src\framework\MyPro\MyPro.csproj: XPathExpressionException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration
cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read
the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVE/MojoExecutionException
please help me to solve this issue...
You have probably added an extra JAR that is messing up the classpath. You should try to make a fresh install and everything should be OK.

Resources