[
https://issues.apache.org/jira/browse/WOOKIE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122863#comment-13122863
]
Ross Gardler commented on WOOKIE-255:
-------------------------------------
Conversely if we don't manage the versions of libraries that are introduced
then widget developers cannot control when their dependencies are updated. This
will (occasionally) result in broken widgets due to introduced bugs.
I've recently been thinking that features need to be versioned in order to
control this, but I've not thought it through. One for the mailing list before
this issue is closed I think.
> 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
> 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
