javacpp.presets does not compile on a fresh checkout

[GoogleCodeExporter]

Problem:
javacpp.presets is referencing "javacpp-0.6" which collides with the stable but 
outdated repo version. This results in symbol not found exceptions in maven.

Quick fix:
checkout javacpp source and run mvn install. 

Fix:
rename trunk versions to javacpp-0.6-SNAPSHOT. "-SNAPSHOT is not available" is 
a much cleaner error message.

Florian

Original issue reported on code.google.com by Florian....@gmail.com on 16 Dec 2013 at 5:36

[GoogleCodeExporter]

Yes, I've been wondering what to do about that. According to various sources, 
we should put the next version of the artifact, followed by -SNAPSHOT, and 
that's what the release plugin does too:
http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-rele
ase.html

But what do I know what the next version will be? The project isn't all that 
"managed" at this point in time. Does it really make sense to use the old 
version number followed by SNAPSHOT? I'm not sure. So I just leave it alone for 
now :)

Original comment by samuel.a...@gmail.com on 17 Dec 2013 at 1:46

• Changed state: Accepted

[GoogleCodeExporter]

If you don't want to make up a new version, I'd suggest just using the old 
version name with -SNAPSHOT or just make it javacpp-0.6.1-SNAPSHOT. I think the 
trade-off between giving users erroneous behavior and using a possibly wrong 
version number is well worth it.

Many projects have changed their revision numbering scheme at some point.

Original comment by Florian....@gmail.com on 17 Dec 2013 at 2:05

[GoogleCodeExporter]

If we use an old version with -SNAPSHOT, then some users would confuse that 
with older code, but on the other hand, if we bump the version, and that 
version never makes it to a stable version without -SNAPSHOT, then that's also 
confusing... Maybe adding some other qualifier could work, like 
0.6-???-SNAPSHOT, where by most user would understand this is newer than 0.6.

Let me know if you think of anything meaningful, thanks!

Original comment by samuel.a...@gmail.com on 17 Dec 2013 at 2:15

[GoogleCodeExporter]

I've thought about it and it doesn't seem to cause problems to bump the version 
up and append -SNAPSHOT, because we're going to release that version eventually 
anyway. And if we need a x.x.1 bug fix release or something, that can be done 
in another branch independent of the master branch, after the facts, so it 
shouldn't cause any problems. Git seems to follow a different pattern, so 
that's confusing, but I guess everyone is used to the inconsistencies by now, 
so I'll make sure to be consistently inconsistent from now on :)

Original comment by samuel.a...@gmail.com on 8 Jan 2014 at 1:23

• Changed state: Started

[GoogleCodeExporter]

I've started to use the -SNAPSHOT version qualifier and everything seems to be 
going well :) Thanks for the input!

Original comment by samuel.a...@gmail.com on 2 Mar 2014 at 3:35

• Changed state: Fixed