[daisy] [JIRA] Created: (DSY-365) cvs TAGS not in sync with release numbers in debian package building

[Marc Portier (JIRA)]

cvs TAGS not in sync with release numbers in debian package building
--------------------------------------------------------------------

         Key: DSY-365
         URL: http://issues.cocoondev.org//browse/DSY-365
     Project: Daisy
        Type: Bug
    Versions: public - 1.5    
 Reporter: Marc Portier
    Priority: Minor


The maven project to build the distro/debian package in svn contains a resources/postinst script that has a hardcoded VERSION set in.

The values for that shell variable inside the tagged-release versions in svn are however NOT IN SYNC with the 

e.g. 
for 1.5.1: @http://svn.cocoondev.org/viewsvn/tags/RELEASE_1_5_1/daisy/distro/debian/resources/postinst?rev=3446&view=markup
  postinst shows: VERSION=2.0-dev

for 1.5.0: @http://svn.cocoondev.org/viewsvn/tags/RELEASE_1_5_0/daisy/distro/resources/debian/postinst?rev=3279&view=markup
  postinst shows: VERSION=1.5-M2

for 1.4.0: @http://svn.cocoondev.org/viewsvn/tags/RELEASE_1_4_0/daisy/distro/resources/debian/postinst?rev=2609&view=markup
  postinst shows: VERSION=1.4-dev

as a consequence: checking ou those tags don't result in actually building a useful debian package unless one manually fixes the checkout.


Suggested fix:
- update the release-building process to include that this file should be updated before checking in the tag
- automate the build by having the resources/* first ant-filter-copied translating some token %PROJECT.VERSION% on that line


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira