1. s-ramp-distro-assembly contains multiple assemblies to produce different zips. Can this be split into different modules e.g. s-ramp-distro-assembly s-ramp-distro-assembly-cli s-ramp-distro-assembly-demos so that each zip can be deployed? 2. Can the deployment be enabled (even if via a profile) as that would mean we wouldn't have to patch the code.
I'm in favor of enabling deployment in all cases - no reason not to have the .zip in nexus. I think we were trying to prevent large deployments from showing up there, but we should reconsider.
This has been done. Additionally I moved the s-ramp-demos project up to the root of s-ramp, so it's now a direct child of s-ramp.
Verified in FSW 6.0.0.ER8