Hi all, Ortwin Glück wrote: > Other components (Xalan, Avalon, JUnit, JBoss etc.) use a class called > Version with a single static method in their base package. That version > number can be filled in automatically at build time.
A single class and build time versioning is also my preference. I'd like to include an official release number (if one is given to Maven) and a timestamp. But we can put in the SVN revision as well. Sebastian, thanks for the suggestion. My biggest concern are people hacking up modifications from a sourceball and compiling the resulting code. Release number (if taken from a file) and SVN revision wouldn't catch that, hence the timestamp. I'm also fine with Oleg's idea of taking this discussion to general in the future. I expect different projects to have different needs, though. For example I can easily imagine each commons-XXX to ship it's own Version class, but would prefer to have only one for all of HttpComponents. A common format for the properties files would still be welcome. Somebody's probably going to suggest a tool that automatically scans a bunch of JAR files for such version info :-) cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
