Bundleparts are not added to the target bundle folder when configuring an existing WAR project to build a CICS bundle about cics-bundle-maven HOT 3 CLOSED

This is a good point. The 'existing WAR project' option was intended as a lightweight way to 'bundleify' an existing project.

I don't think it makes sense to allow people to put arbitrary bundle parts into src/main/resources - I think this should contain artifacts related to the WAR project.

So I think this behaviour is correct and we should document this. Ledina did mention in discussion that it was difficult to discern when to use which approach, so we could beef the documentation for this up a bit.

from cics-bundle-maven.

@vera-chan did we ever update the documentation for this?

from cics-bundle-maven.

This way of building a CICS bundle modifies an existing Java module to make it also build the CICS bundle. This makes it more lightweight, but it has limitations - the CICS bundle can only contain one Java bundlepart, and can't contain any extra bundleparts such as FILE or URIMAP.

I'm happy that this is documented and we can close this.

from cics-bundle-maven.