Description of problem: Artifacts deployed to S-RAMP via maven should be immutable. They represent a canonical version of a built binary object and therefore should not be updateable. When maven is used to try and deploy the same artifact again, it should fail rather than update the existing artifact in s-ramp. Version-Release number of selected component (if applicable): FSW 6.0.0 GA How reproducible: Always Steps to Reproduce: 1. Use Maven to deploy an artifact into s-ramp 2. Try to deploy the same artifact using maven a 2nd time 3. Note that the maven build succeeded (and it updated the last-modified-time of the artifact in s-ramp). Actual results: The maven build succeeds and the artifact is updated. Expected results: The maven build fails.
I have commited a fix for this to the product branch in s-ramp for FSW 6.0.
Hi Eric, Can you please supply a commit id? Thanks, Rick
https://github.com/jboss-integration/s-ramp/commit/01a8be22f0e8bf50664a69dbab41bbb9ce8afaca
Hi Eric, Can you please merge these fixes on top of the previous tag and give us a new tag that we can build from? Thanks, George.