Error reading Bundle-SymbolicName from OSGi manifest file when using Maven module cics-bundle about cics-bundle-maven HOT 4 CLOSED

Hey James,

Are you able to upload the projects so we can try it? I think that might be easier than a back and forward!

If that's not possible, then I think what is being said here is that the cics-bundle-maven-plugin is trying to build the projects that are declared as its dependencies - one of them I think is an OSGi bundle but it can't read the Bundle-SymbolicName attrribute from the MANIFEST.MF file.

I think you're following these instructions - https://github.com/IBM/cics-bundle-maven#create-a-cics-bundle-in-a-separate-module-using-cics-bundle-maven-plugin - I wonder what dependencies you've set.

from cics-bundle-maven.

I can share them with you internally. I am indeed following those instructions. The "Maven Module for the CICS bundle" has no dependencies, but the parent does. @davenice

from cics-bundle-maven.

We have a similar problem. We use the maven-bundle-plugin to build our OSGi bundles, and this plugin writes the manifest after the compile phase (it has to, as it analyzes the class files). The OSGi bundles and CICS bundles are part of the same multi-module project.
When running "mvn compile" on such a project, building the CICS bundle fails with the aforementioned error. "mvn install" works fine. When opening the project in Eclipse, it also shows the error, although it disappears after running "mvn install".

from cics-bundle-maven.

It turns out this was a little bit of user error, which we've managed to rectify now.

@holgerknoche thank you for your comment. This looks like it is likely to be a different issue. Please could you raise a new issue, with your diagnostics in? Thank you.

from cics-bundle-maven.