You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/12/24 02:41:14 UTC

[jira] [Closed] (TAP5-1838) The Tapestry maven archetype should automatically update APPLICATION_VERSION in the AppModule

     [ https://issues.apache.org/jira/browse/TAP5-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1838.
--------------------------------------
    Resolution: Won't Fix

The changes in Tapestry 5.4 ... per-asset fingerprinting ... mean that this is no longer so important. Forgetting to change the version number will not impact clients.

> The Tapestry maven archetype should automatically update APPLICATION_VERSION in the AppModule
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1838
>                 URL: https://issues.apache.org/jira/browse/TAP5-1838
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Adam
>
> Currently the archetype generates APPLICATION_VERSION once. If someone does not pay attention to changing it manually at the right times, they will encounter asset caching issues (see the long 5.3 JSONArray Error mailing list thread).
> It would be nice if the archetype instead included some maven plugin that automatically matched it with the version of your pom. The builtin resource processing plugin can do this for example, the "<build><resources>" and the "<filtering>" tag allows you to reference maven variables from files and have them filled in at build time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)