+++ This bug was initially created as a clone of Bug #794768 +++

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?

--- Additional comment from lkrejci on 2012-02-17 10:12:54 EST ---

Stefan, what is your opinion on this?

--- Additional comment from lkrejci on 2012-02-17 10:17:29 EST ---

The uploading using the CLI alert notification definition popup while defining an alert definition still works though...