| 1 | Dependencies and licenses...
|
|---|
| 2 |
|
|---|
| 3 | pcollections : MIT license,
|
|---|
| 4 | http://opensource.org/licenses/mit-license.php
|
|---|
| 5 | need to distribute license with product
|
|---|
| 6 | clj-ds
|
|---|
| 7 | EPL (Eclipse), https://github.com/krukow/clj-ds/blob/master/epl-v10.html,
|
|---|
| 8 | distribute license with code
|
|---|
| 9 | cvc3
|
|---|
| 10 | http://www.cs.nyu.edu/acsys/cvc3/doc/LICENSE.html
|
|---|
| 11 | uses zchaff which has limiting license
|
|---|
| 12 | antlr-runtime
|
|---|
| 13 | BSD license: http://antlr.org/license.html
|
|---|
| 14 | libgmp: LGPL
|
|---|
| 15 |
|
|---|
| 16 |
|
|---|
| 17 | include licenses in distribution
|
|---|
| 18 |
|
|---|
| 19 | include version number and civl revision?
|
|---|
| 20 |
|
|---|
| 21 | CIVL/
|
|---|
| 22 | lib/
|
|---|
| 23 | civl-0.1-r239.jar
|
|---|
| 24 | civl.jar -> civl-0.1-r239.jar
|
|---|
| 25 | etc.
|
|---|
| 26 | LICENSE
|
|---|
| 27 | bin/
|
|---|
| 28 | doc/
|
|---|
| 29 |
|
|---|
| 30 | Stable releases: each with complete distributions or just jar,
|
|---|
| 31 | different OS types
|
|---|
| 32 |
|
|---|
| 33 | Unstable release: just give the latest, complete distribution and
|
|---|
| 34 | just the civl jar.
|
|---|
| 35 |
|
|---|
| 36 | Process for unstable latest: automate in build script
|
|---|
| 37 | ant should do "release" target: create directory called
|
|---|
| 38 | "release" with whatever you want, copy it over. waste.
|
|---|
| 39 |
|
|---|
| 40 | worker should perform perl substitutions, bundle everything
|
|---|
| 41 | up into one directory called build-r256 (e.g.)
|
|---|
| 42 |
|
|---|
| 43 | preparing release: create directories, copy jar and dependencies,
|
|---|
| 44 | create symlinks, tar, gzip
|
|---|
| 45 |
|
|---|
| 46 | prepare stable release: goes in tags, leave out revision number
|
|---|
| 47 |
|
|---|
| 48 | how to tell which version you are in. Put in repository a file
|
|---|
| 49 | called VERSION. That is it.
|
|---|
| 50 |
|
|---|
| 51 | Stable: leave off r part. put in tags directory
|
|---|
| 52 |
|
|---|
| 53 |
|
|---|
| 54 | release_civl
|
|---|
| 55 | stable_release_civl
|
|---|
| 56 |
|
|---|
| 57 | put VERSION file in CIVL main directory.
|
|---|
| 58 | manager needs to copy jar file over (civl.jar) and rename it?
|
|---|
| 59 | manager needs to know what it is called.
|
|---|
| 60 |
|
|---|
| 61 |
|
|---|
| 62 | civl/
|
|---|
| 63 | test/
|
|---|
| 64 | trunk/
|
|---|
| 65 | latest@
|
|---|
| 66 | r98/
|
|---|
| 67 | r99/
|
|---|
| 68 | release/
|
|---|
| 69 | civl.jar@->
|
|---|
| 70 | CIVL.tgz@->
|
|---|
| 71 | civl-trunk_99.jar
|
|---|
| 72 | CIVL-trunk_99.tgz (untars to CIVL-trunk-r99/, and inside there is
|
|---|
| 73 | civl-trunk-r99.jar and in bin civl, which is a script that references the
|
|---|
| 74 | directory /Applications/CIVL-trunk-r99 ... ) This way user can have multiple
|
|---|
| 75 | CIVL versions installed at once and set path appropriately.
|
|---|
| 76 | 1.0/
|
|---|
| 77 | latest@
|
|---|
| 78 | r100/
|
|---|
| 79 | r101/
|
|---|
| 80 | civl-1.0_101.jar
|
|---|
| 81 | CIVL-1.0_101.tgz
|
|---|
| 82 |
|
|---|
| 83 | web/
|
|---|
| 84 | r123/
|
|---|
| 85 | junit/
|
|---|
| 86 | coverage/
|
|---|
| 87 | javadoc/
|
|---|
| 88 | release/
|
|---|
| 89 | CIVL-1.0-osx-r279.tgz
|
|---|
| 90 | CIVL-1.0-linux-r279.tgz
|
|---|
| 91 | civl.jar
|
|---|
| 92 |
|
|---|
| 93 |
|
|---|
| 94 |
|
|---|
| 95 | give some examples usages.
|
|---|
| 96 |
|
|---|
| 97 | documentation must be included.
|
|---|
| 98 |
|
|---|
| 99 | command line options.
|
|---|
| 100 |
|
|---|
| 101 |
|
|---|
