Description of problem: $SUBJECT Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Create a repository 2. Scroll down, upload a js script 3. select type of "Serverside CLI Script" 4. Click "Create Package" button Actual results: exception complaining that a sha256 hash is not an OSGi version string (which it isn't) Expected results: upload should work Additional info: This exception is most likely caused by the validation the CLI package type performs on the version string. Not sure what the solution should be here though. Using sha256 as a version string makes a lot of sense (as we've seen lately) but at the same time the validation (of CLI package type versions )that is in place right now does a good deal of user visible version validation. Maybe we could just change the validator to check the display version instead of the version field?
Stefan, what is your opinion on this?
The uploading using the CLI alert notification definition popup while defining an alert definition still works though...
triage 2/27/2012 mfoley, asantos, crouch, loleary
Targeting for *consideration* for JON3.1.0
As per triage, targeting for JON3.2.0
Closing as duplicate of later bug 840650. The later version has the same details along with the workaround. *** This bug has been marked as a duplicate of bug 840650 ***
Unclosing this because BZ 840650 doesn't provide a fully functional workaround for this. See comment 3 @ BZ 840650 https://bugzilla.redhat.com/show_bug.cgi?id=840650#c3