search

IBM / cics-bundle-maven

The plugin to build and deploy CICS bundles in a Maven build.
https://ibm.github.io/cics-bundle-maven/plugin-info.html
Eclipse Public License 2.0
18 stars 25 forks source link

Package CICS resources outside src/main/resources #198

Open holgerknoche opened 2 years ago

holgerknoche commented 2 years ago

We use a custom Maven plugin to generate program definitions from annotations in the Java classes. Being generated, we would like to store them somewhere in target/generated-resources. However, the plugin only allows to specify resource paths in src/main/resources. Could we get an option to also include CICS resources in an arbitrary location inside the project (or at least in target/generated-resources)?

ind1go commented 2 years ago

Thanks for raising this issue.

Your custom Maven plugin, is that generating program definitions that could not be generated using the @CICSProgram annotation? Just checking that you are aware of that option and it's not available to you for some reason.

holgerknoche commented 2 years ago

Thanks for your comment! As far as I know, the @CICSProgram annotation only works for EARs and WARs deployed to Liberty, but not for OSGi bundles in a JVM server, which is what we mainly use.

ind1go commented 2 years ago

Ah yes, I understand. Using @CICSProgram for OSGi bundles is announced in CICS TS 6.1, which will be available soon.

We'll look further into this.

ind1go commented 2 years ago

Just to check I have the correct understanding, do you mean the src/main/bundleParts directory (instead of src/main/resources)? Have you been able to use the bundlePartsDirectory property?

holgerknoche commented 2 years ago

Yes, that's the one. The bundlePartsDirectory property does not really help here, because it is restricted to paths within src/main. Unlike target, these paths are usually under version control, and since we don't want to commit our generated artifacts, we have to manually exclude them.