Non-reactor bundles fail to deploy if classifier is not set about cics-bundle-maven HOT 2 CLOSED

I'll use bundle-war below to mean all the bundle-war, bundle-ear, etc goals.

I think the thing here is that the bundle-war goal default to it being cics-bundle, but the deploy goal doesn't default to that because it could be being used to deploy a bundle created by either a bundle-war goal (where classifier will be cics-bundle or another classifier as specified) or a build goal (where there will be no classifier, at least not without explicitly setting it).

I think this will need to be a documentation fix and logging fix - not sure I can see a fix that makes it 'just work' for all combinations. Perhaps it's possible to work out which goals have run ahead of the deploy goal? @stewartfrancis

However, we could do the following:

• in the README, in the Deploy a CICS bundle section, mention that you should also use the <classifier> configuration option to select the bundle, in the case where you're deploying a bundle-war-built bundle.
• in the log messages for the deploy goal, print out the file that we're deploying. This'll make it more obvious when it ends .war instead of .zip.

Any other ideas?

from cics-bundle-maven.

Would definitely be good to fix it though because I fall over it every time I create a new project! 😆

from cics-bundle-maven.