Closed qspin closed 11 years ago
A solution for this issue is being implemented in "releases-versioning" branch.
All QTaste modules will take the same snapshot version and when a new iteration is ready to release, all pom file will be updated and commited. This could be achieved by running the new script releaseAll. Please check this for further deteiled information.
Please check the implementation proposed "releases-versioning" branch. Here in root you have a script called releaseAll (available both for Linux and Win). All steps taken by the script are explained in the script file.
Usage: releaseAll.sh [-snapshot]
Note: when using this script without snapshot option, the script will commit and push to remote Github on current branch - releases-versioning.
Feature commited in "master" branch
Today, it becomes complicate to produce a new version of qtaste due to the huge number of pom.xml file containing the version of QTaste ....
This version should be only set in one file and other files should inherit of the version ....
Example like that have been found in the following files: (in this example, QTaste version is 1.2.1)
./kernel/pom.xml:1.2.1
./izpack/pom.xml: 1.2.1
./plugins/tools/pom.xml: 1.2.1
./plugins/recorder/pom.xml: 1.2.1
./plugins/recorder/pom.xml: 1.2.1
./plugins/javagui/pom.xml: 1.2.1
./plugins/javagui/pom.xml: 1.2.1
./demo/testapi/pom.xml: 1.2.1
./demo/testapi/pom.xml: 1.2.1
./toolbox/testapi/pom.xml: 1.2.1
./toolbox/pom.xml: 1.2.1
./testapi-parent/testapi-deploy/pom.xml: 1.2.1
./testapi-parent/pom.xml: 1.2.1
./pom.xml: 1.2.1
./pom.xml: 1.2.1
./pom.xml: 1.2.15
./pom.xml: 1.2.1