You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2011/09/19 08:58:09 UTC

[jira] [Commented] (DIRSERVER-1659) the apacheds.sh/bat files contains a hard coded revision. This is not good

    [ https://issues.apache.org/jira/browse/DIRSERVER-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107654#comment-13107654 ] 

Pierre-Arnaud Marcelot commented on DIRSERVER-1659:
---------------------------------------------------

I agree we should try to have them generated instead of managing them by hand before and after each version change.

We could move them to 'src/main/resources' and have them filtered with the correct version by Maven during the build.
However, we won't have them anymore at the root of the 'service' project and we'll need to look at the filtered version in the target directory (nothing too complicated though).

> the apacheds.sh/bat files contains a hard coded revision. This is not good
> --------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1659
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1659
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M3
>            Reporter: Emmanuel Lecharny
>            Priority: Blocker
>             Fix For: 2.0.0-M4
>
>
> Currently, we have hard coded the revision in the two batch files (service/apacheds.sh/bat).
> When we cut a release, we will likely forget to change those versions. They should be generated while we process the release, before we push the files to the tags directory.
> I don't know if it's possible though... 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira