[JS2-982] Use MANIFEST.MF resident build number/timestamp in PAM instead of computing checksums for deployment version

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.1.4, 2.2.0
• Component/s: Assembly/Configuration, Deployment, Portlet Registry
• Environment: Maven builds; Jetspeed V[PAM], (PortletApplicationManager)
• Assignee: W. Randall Watler
• Reporter: W. Randall Watler
• Created: 29/Apr/09 15:24
• Updated: 18/Feb/10 16:46

Description

Computing checksums of portlet.xml, jetspeed-portlet.xml and web.xml to determine version of portlet application is not viable in some containers that rewrite these files. Adding a build number and/or timestamp field in the portlet application war MANIFEST.MF file may provide a stable analog.

This feature could be used to unify VPAM and PAM implementations. Note that VPAM uses a pa_version field in jetspeed-portlet.xml to determine version; this option/mode must be preserved for more stable production environment. The proposed build number/timestamp implementation is well suited for a development or automated environment since every new version of a portlet app will be [re]registered.

See the buildnumber-maven-plugin for implementation.