What kind of version are thinking about? JAR library metadata or some number in the class?

The former, preferably including rev.no.

We have to think of some kind of a standard way which would cover cases where we load our own code and when we load third-party libraries with components and plugins. As a single JAR file can contains several plugins which may have different versions I think the optimal approach would be to include some kind of a version field in the code, or better yet a public method returning version, so it would be a part of our public API.

However, from my experience I know that people often forget or do not care to update such stuff. At least for our own code we could create some kind of an automated system which could put SVN rev in to source code during compilation but this seems a bit awkward.

Any suggestions how to do it well?

I was thinking about reading from jar's manifest file Implementation-Version information if available. This can be updated upon building with maven automatically.

Related to #712, probably could be generalized to one task.

Duplicate to #712