You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (Commented) (JIRA)" <ji...@apache.org> on 2011/11/04 18:21:51 UTC
[jira] [Commented] (WOOKIE-255) Change file names to not include
version numbers in features
[ https://issues.apache.org/jira/browse/WOOKIE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144180#comment-13144180 ]
Scott Wilson commented on WOOKIE-255:
-------------------------------------
I can't see any more versioned libs used in features; I think we should put feature versioning as a possible requirement for WOOKIE-226 (feature dependency) and close this issue
> Change file names to not include version numbers in features
> ------------------------------------------------------------
>
> Key: WOOKIE-255
> URL: https://issues.apache.org/jira/browse/WOOKIE-255
> Project: Wookie
> Issue Type: Improvement
> Components: Feature Management
> Affects Versions: 0.9.1
> Reporter: Scott Wilson
> Assignee: Scott Wilson
> Fix For: 0.9.2
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> If the name of a file such as a JS or CSS in a feature contains a version number, e..g jquery-1.6.4.js, this makes it much more difficult to update the feature to use a new version, as existing widgets will continue to point to the file name originally injected, which may no longer be installed on the server.
> To avoid this we should make sure resources used in features use generic filenames, or stick to major version names (e.g. "1.0","2.0") and not minor or beta version identifiers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira