You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Randy Watler (JIRA)" <je...@portals.apache.org> on 2009/04/29 17:24:30 UTC
[jira] Created: (JS2-982) Use MANIFEST.MF resident build
number/timestamp in PAM instead of computing checksums for deployment
version
Use MANIFEST.MF resident build number/timestamp in PAM instead of computing checksums for deployment version
------------------------------------------------------------------------------------------------------------
Key: JS2-982
URL: https://issues.apache.org/jira/browse/JS2-982
Project: Jetspeed 2
Issue Type: Improvement
Affects Versions: 2.1.4, 2.2.0
Environment: Maven builds
Jetspeed V[PAM], (PortletApplicationManager)
Reporter: Randy Watler
Assignee: Randy Watler
Priority: Minor
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-982) Use MANIFEST.MF resident build
number/timestamp in PAM instead of computing checksums for deployment
version
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated JS2-982:
-----------------------------
Fix Version/s: (was: 2.2.2)
(was: 2.1.4)
> Use MANIFEST.MF resident build number/timestamp in PAM instead of computing checksums for deployment version
> ------------------------------------------------------------------------------------------------------------
>
> Key: JS2-982
> URL: https://issues.apache.org/jira/browse/JS2-982
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Assembly/Configuration, Deployment, Portlet Registry
> Affects Versions: 2.1.4, 2.2.0
> Environment: Maven builds
> Jetspeed V[PAM], (PortletApplicationManager)
> Reporter: Randy Watler
> Assignee: Randy Watler
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-982) Use MANIFEST.MF resident build
number/timestamp in PAM instead of computing checksums for deployment
version
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated JS2-982:
-----------------------------
Component/s: Portlet Registry
Deployment
Assembly/Configuration
Aggregation
> Use MANIFEST.MF resident build number/timestamp in PAM instead of computing checksums for deployment version
> ------------------------------------------------------------------------------------------------------------
>
> Key: JS2-982
> URL: https://issues.apache.org/jira/browse/JS2-982
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Assembly/Configuration, Deployment, Portlet Registry
> Affects Versions: 2.1.4, 2.2.0
> Environment: Maven builds
> Jetspeed V[PAM], (PortletApplicationManager)
> Reporter: Randy Watler
> Assignee: Randy Watler
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-982) Use MANIFEST.MF resident build
number/timestamp in PAM instead of computing checksums for deployment
version
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated JS2-982:
-----------------------------
Affects Version/s: (was: 2.2.2)
Fix Version/s: 2.2.2
2.1.4
> Use MANIFEST.MF resident build number/timestamp in PAM instead of computing checksums for deployment version
> ------------------------------------------------------------------------------------------------------------
>
> Key: JS2-982
> URL: https://issues.apache.org/jira/browse/JS2-982
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Assembly/Configuration, Deployment, Portlet Registry
> Affects Versions: 2.1.4, 2.2.0
> Environment: Maven builds
> Jetspeed V[PAM], (PortletApplicationManager)
> Reporter: Randy Watler
> Assignee: Randy Watler
> Priority: Minor
> Fix For: 2.1.4, 2.2.2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-982) Use MANIFEST.MF resident build
number/timestamp in PAM instead of computing checksums for deployment
version
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated JS2-982:
-----------------------------
Affects Version/s: 2.2.2
> Use MANIFEST.MF resident build number/timestamp in PAM instead of computing checksums for deployment version
> ------------------------------------------------------------------------------------------------------------
>
> Key: JS2-982
> URL: https://issues.apache.org/jira/browse/JS2-982
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Assembly/Configuration, Deployment, Portlet Registry
> Affects Versions: 2.1.4, 2.2.0
> Environment: Maven builds
> Jetspeed V[PAM], (PortletApplicationManager)
> Reporter: Randy Watler
> Assignee: Randy Watler
> Priority: Minor
> Fix For: 2.1.4, 2.2.2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-982) Use MANIFEST.MF resident build
number/timestamp in PAM instead of computing checksums for deployment
version
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated JS2-982:
-----------------------------
Component/s: (was: Aggregation)
> Use MANIFEST.MF resident build number/timestamp in PAM instead of computing checksums for deployment version
> ------------------------------------------------------------------------------------------------------------
>
> Key: JS2-982
> URL: https://issues.apache.org/jira/browse/JS2-982
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Assembly/Configuration, Deployment, Portlet Registry
> Affects Versions: 2.1.4, 2.2.0
> Environment: Maven builds
> Jetspeed V[PAM], (PortletApplicationManager)
> Reporter: Randy Watler
> Assignee: Randy Watler
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org