Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The easiest way of doing this is to change the problem. Instead of making the Any build do this for you, have whatever process that you're calling Ant calculate what the version number should be, and then pass that in as a property e.g.</p> <p>ant -Dbuild.version=1.2.3</p> <p>This has the flexibility of whatever build you're working with being able to take its cue from whatever, such as the SVN revision, the current date and time, or whatever.</p> <p>ant -Dbuild.version=<code>svnversion .</code></p> <p>ant -Dbuild.version=<code>date +"%Y%m%d%H%D"</code></p> <p>ant -Dbuild.version=${major}.<code>svnversion .</code>.<code>date +"%Y%m%d%H%D"</code></p> <p>etc. You can get pretty comprehensive if you want.</p> <p>If you want to have an ever incrementing number, then you can store it in a file and then pass that in at compile time. For example, you can do:</p> <p>VER=<code>cat build.version</code> VER=$((VER+1)) echo $VER > build.version</p> <p>Lastly, if you really want this to be in the build.xml file, the best thing to do is have a separate task to execute the increment-and-build option and fork off a nested ant build with your 'main' target. You'd thus end up with </p> <p>ant -> ant -Dbuild.version=1.2.3.4 -> ... </p> <p>In other words, given your build.xml with a (current) default of 'build', then change it to 'version' and have the ant 'version task do the calculation followed by a nested call to and build.</p> <p>Implementation is left as an exercise to the reader, as is translating the approach to a non-UNIX platform.</p>
    singulars
    1. This table or related slice is empty.
    1. POBuild numbers: major.minor.revision
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAlBlue
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COBear in mind that Git doesn't have the concept of an incrementing version number. Git revisions are SHA hashes and are non numeric (typically, they're represented in hex, though of course it does represent a number under the covers). However, the key important thing is that it's not an ever-increasing number, but rather takes disjoint hops (both up and down) across the numeric spectrum. In addition, the constraints you put on the requirement are inconsistent. You don't want any external dependencies, yet you've got Git, and presumably Ant as well.
      singulars
      1. PO
      1. USAlBlue
    2. COGit does have a concept of incrementing numbers. You tag (properly, using -s or -a) when you have a version that's interesting. You use `describe` to get a unique, human-readable version number from your tree.
      singulars
      1. PO
      1. USDustin
    3. CODustin, The version number obtained by git describe isn't unique across all distributed repositories; and in any case, is a combination of the tag and the number of commits to the (local) repository since then. Things like rebasing or squashing commits can result in identical numbers but different content.
      singulars
      1. PO
      1. USAlBlue
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload