We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From mhrye...@standard.com on February 03, 2010 12:29:08
It would be great to have an implementation version line in the manifest so that we can verify what version of ESAPI we are looking at. Example:
Manifest-Version: 1.0 Implementation-Version: 1.4.4
Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=106
The text was updated successfully, but these errors were encountered:
From manico.james@gmail.com on November 01, 2010 06:28:28
Status: Accepted Owner: chrisisbeef Labels: Milestone-Release2.0
Sorry, something went wrong.
From chrisisbeef on November 01, 2010 14:27:41
Labels: -Milestone-Release2.0 Release2.0 Build-Maven
From chrisisbeef on November 01, 2010 14:32:07
Labels: -Release2.0 Milestone-Release2.0
From chrisisbeef on November 06, 2010 01:04:53
I will get this added in tonite with the following meta-data
Manifest-Version: 1.0 Specification-Vendor: OWASP Specification-Title: Enterprise Security API Specification-Version: 2.0 Implementation-Vendor: OWASP Implementation-Version: Implementation-Url: http://www.esapi.org
From chrisisbeef on November 06, 2010 01:45:57
Latest SNAPSHOT Release in Sonatype Snapshot repository also will contain this information.
From chrisisbeef on November 06, 2010 01:46:27
This issue was closed by revision r1649 .
Status: Fixed
No branches or pull requests
From mhrye...@standard.com on February 03, 2010 12:29:08
It would be great to have an implementation version line in the manifest
so that we can verify what version of ESAPI we are looking at. Example:
Manifest-Version: 1.0
Implementation-Version: 1.4.4
Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=106
The text was updated successfully, but these errors were encountered: