Closed timhandler closed 4 years ago
Hi Tim. The intent of including the contents of the src/main/resources
folder is to allow you to add other bundle parts to your bundle by manually putting them in there. Obviously this doesn't play nice with other plugins which are using src/main/resources
for their own purposes. I think it'd make sense to change this to src/main/bundleparts
and have it user-configurable, before we do a v 1.0.0 release, which would avoid issues like this. @tom-foyle @ind1go what do you guys think?
src/main/bundleparts
I wondered if the name should include CICS as bundle is a very overloaded term. eg.cicsresources
orcicsbundleparts
. It would be nice to copy/include non CICS bundle parts in the future which may influence the choice of name.
Hi Tim. The intent of including the contents of the
src/main/resources
folder is to allow you to add other bundle parts to your bundle by manually putting them in there. Obviously this doesn't play nice with other plugins which are usingsrc/main/resources
for their own purposes. I think it'd make sense to change this tosrc/main/bundleparts
and have it user-configurable, before we do a v 1.0.0 release, which would avoid issues like this. @tom-foyle @ind1go what do you guys think?
Yes I agree. And we should ideally update the Maven plugin to match.
I don't mind too much on the name. cicsbundleparts
would match the terminology used in build.gradle. But it's a bit long, and not ideal if there is a chance of including non-CICS bundle parts in the future.
This fix is now available in release 1.0.1.
Hi,
I noticed when building a Spring Boot application artifacts within the Java project (src/main/resources directory) are being included within the newly built CICS bundle directory.
I have attached the output from the build using the --info option. In there you can see the file application.properties being added to the CICS bundle in error.
Thanks, Tim Handler