:> i'll get it cleared. the people in charge have already left..Rev 1.3 <-> Rev 1.5 if there is NO Rev 1.4 ?
true. I would need to implement 'something' to do that.Rev branch 1.2.1.2.1.1 <-> Rev branch 1.2.1.3
is true (and vice-versa); and that is going to be quite difficult to program without some master table of valid versions.
: this versioning system doesnt have a version like 1.3.1.What about:
Rev 1.3 <-> Rev branch 1.3.1
: can this happen that a version is not there??Rev 1.3 <-> Rev 1.5 if there is NO Rev 1.4 ?
--> NoCan versions be lettered
-> 1.9.1.1 can be made after 1.10 but when doing comparison, it is not needed to be compared. 1.10 will b e compared aganist 1.9 and 1.9.1.1 aganist 1.9.Are you guaranteed that there can't be a 1.9.1 made after 1.10 (
Should return trueRev 1.9 <-> 1.10
returns false.1.2 <-> 1.3.1
: My understanding was versioning is done in a series, not that one version of the file is 1.2 and then comes 1.4.Can a number be skipped, i.e. you have a 1.1 and a 1.3, but not a 1.2?
are you guaranteed to have a 1.3 before you have a 1.3.1?
fred rosenberger wrote:Bob,
the original post asked about all java PROJECTS, not programs. I have worked on many PROJECTS that didn't have a main.