-
Notifications
You must be signed in to change notification settings - Fork 80
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
Issue Building JAR with No-MANIFEST.MF dependency: Please verify if jar file is valid, the MANIFEST.MF #680
Comments
alexandrev
pushed a commit
to alexandrev/bw6-plugin-maven
that referenced
this issue
Oct 9, 2022
Open
Hello I am new with the maven plugin installation. Can you help me ? |
alexandrev
pushed a commit
to alexandrev/bw6-plugin-maven
that referenced
this issue
Feb 8, 2023
alexandrev
pushed a commit
to alexandrev/bw6-plugin-maven
that referenced
this issue
Feb 8, 2023
richardyam-tibco
added a commit
that referenced
this issue
Mar 13, 2023
Closing this ticket as Reported jira for this issue is closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BUG REPORT INFORMATION
Maven Plugin version: 2.9.2
Maven version: 3.6.3
Product : BW/BWCE
Product version: 2.8.1
Component: Maven build plugin
Caused by: java.lang.Exception: Failed to get Manifest for - javax.inject-1.jar. Please verify if jar file is valid, the MANIFEST.MF should be first or second entry in the jar file. Use Command - jar tf <Jar_File_Path> to verify.
at com.tibco.bw.maven.plugin.module.BWModulePackageMojo.addDependencies(BWModulePackageMojo.java:196)
at com.tibco.bw.maven.plugin.module.BWModulePackageMojo.execute(BWModulePackageMojo.java:115)
... 22 more
This is because we try to read the MANIFEST.MF to check if the module is a Shared Module or not, we should avoid the crash because no MANIFEST.MF, could not be a problem and we should work with it, and change the current code in case if Manifest is null instead of raising the Exception just considering this is not a Shared Module and move forward putting the dependency into the lib folder of the resulting JAR.
Regards,
The text was updated successfully, but these errors were encountered: