You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like its impossible for the bundle not to have version (as <bundle_id>_<bundle_version>.war). It doesn't seem to help defining "${project.artifactId}" in "".
For us, when we deploy the bundle, the URL of the project is the war file name, and as cool it is to have that in development, when we are deploying to "production" the version number just makes the URL complicated.
There seems to be piece of code that no matter what takes the version and appends it to the file name.
It seems like its impossible for the bundle not to have version (as <bundle_id>_<bundle_version>.war). It doesn't seem to help defining "${project.artifactId}" in "".
For us, when we deploy the bundle, the URL of the project is the war file name, and as cool it is to have that in development, when we are deploying to "production" the version number just makes the URL complicated.
There seems to be piece of code that no matter what takes the version and appends it to the file name.
(cics-bundle-maven-plugin/src/main/java/com/ibm/cics/cbmp/PackageCICSBundleMojo.java static File createCICSBundle())
Would it be possible to add clause that checks if finalName is defined, and if so, use that and don't add version?
The text was updated successfully, but these errors were encountered: