Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin:2.5.2:single: java.lang.ExceptionInInitializerError: null #8

Open
AshishKmrSingh opened this issue May 6, 2021 · 2 comments

Comments

@AshishKmrSingh
Copy link

An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin:2.5.2:single: java.lang.ExceptionInInitializerError: null

Issue occurs on running mvn install in goal 'single' of mvn-assembly-plugin in jwt-modules module.

Had to change the version of maven-assembly-plugin to 3.3.0 and maven-war-plugin to 3.3.1 to create the successful build.
Have I done it correct?

@AshishKmrSingh
Copy link
Author

Is their any documentation available as well. In the other thread, you mentioned to create it. I am wondering if it exists? Also, my application is deployed as an ear file having EJB services on Wildfly itself. Also, the Picketbox security is currently configured on the Wildfly server and I cannot do way with it since I need the JWT authentication for one of the services which will work as the proxy to forward requests/responses to/from EJB services. Can i use this module on top of that just for that service. I am deploying that service as war file inside the same ear file.

@AshishKmrSingh
Copy link
Author

After successful build, there is no .tar.gz or .zip file present in /target directory. But, .tar.gz and .zip files are present in jwt-modules/target directory. Which one should I refer?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant