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

Package CICS resources outside src/main/resources #198

Open
holgerknoche opened this issue Apr 26, 2022 · 5 comments
Open

Package CICS resources outside src/main/resources #198

holgerknoche opened this issue Apr 26, 2022 · 5 comments

Comments

@holgerknoche
Copy link

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
Copy link
Member

ind1go commented Apr 26, 2022

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
Copy link
Author

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
Copy link
Member

ind1go commented Apr 26, 2022

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
Copy link
Member

ind1go commented Apr 26, 2022

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
Copy link
Author

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.

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

2 participants