Closed glassfishrobot closed 16 years ago
@glassfishrobot Commented Reported by danl
@glassfishrobot Commented danl said: Please see issue #85.
@glassfishrobot Commented @edburns said: Fix checked in.
@glassfishrobot Commented Was assigned to jsf-extensions-issues
@glassfishrobot Commented This issue was imported from java.net JIRA JSF_EXTENSIONS-80
@glassfishrobot Commented Marked as fixed on Friday, December 7th 2007, 9:15:21 am
Although the JSF-Extensions jar names contain a version number (currently 0.1), there is no way to distinguish between release candidates. The manifest below does not indicate whether we're using rc2, rc3, etc.
Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: edburns Build-Jdk: 1.5.0_07
For reference, the Woodstock manifest file looks like this:
Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: Sun Microsystems Inc. Implementation-Title: Woodstock 4.1-200709201840-dev Implementation-Version: 4.1-200709201840-dev Implementation-Vendor: Sun Microsystems Inc. Implementation-Vendor-Id: com.sun Specification-Title: Woodstock Specification-Version: 4.1-dev Specification-Vendor: Sun Microsystems Inc.
Name: com/sun/webui/jsf/ X-SJWUIC-SWAED-Version: 4.0 X-SJWUIC-Components-Version: 4.1 X-SJWUIC-Components-Timestamp: 200709201840 X-SJWUIC-Theme-Version-Required: 4.1 X-SJWUIC-JSF-Version: 1.2 X-SJWUIC-Dependencies: dataprovider.jar/1.0, jhall.jar/2.0 X-SJWUIC-Dependencies-FileUpload: commons-fileupload.jar/1.0
Environment
Operating System: All Platform: Sun
Affected Versions
[current]