[
https://issues.apache.org/jira/browse/UNOMI-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376566#comment-15376566
]
Serge Huber commented on UNOMI-42:
----------------------------------
This was fixed by creating a new setenv.sh script that can contain common
version numbers.
The project version number is resolved dynamically so we won't have to update
it anymore.
> Fix version numbers in build scripts
> ------------------------------------
>
> Key: UNOMI-42
> URL: https://issues.apache.org/jira/browse/UNOMI-42
> Project: Apache Unomi
> Issue Type: Improvement
> Components: build, core
> Affects Versions: 1.0.1-incubating
> Reporter: Serge Huber
> Assignee: Serge Huber
> Labels: easyfix
> Fix For: 1.0.1-incubating
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> We currently have not updated the build scripts to use the new versions.
> Instead of this we should put the version numbers in a setenv file or even
> better find a way to update them dynamically from the pom.xml file (if
> possible)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
