I'm not a big fan of all minor releases needing to append '.ga' (i.e.
3.1.3.ga.jar). I really wish there was a way to define ordering amongst
"qualifiers".
AFAIK these conventions are for package names and not necessarily
library names?
it's the version branded into the application - meaning what goes into
MANIFEST.MF and
distribution name; for me it would make sense to have that on the jar file
too...
And yes, would be great with an "ordering" that said 3.1.3 is "newer" than
3.1.3.alpha, 3.1.3.beta..but what is 3.1.3.2 then ?
p.s. i'm planning on following this in the eclipse plugins too since it
actually is
very usefull there to have the update manager functionallity work together
with alpha/beta/etc.
/max
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
