Francois Fernandes wrote: > Yes, you're right. But the problem is that our jar is not the only one > on the classpath. That means that it is hard to ensure that we're > loading the right manifest file to read the version. (btw. we're placing > version information already inside this jar.) > Loading resources even inside files causes us some trouble as we've got > to support applets in very restrictive environments and different VMs > (including Microsoft). That means that using a class is the most simple > and stable way to gain version information of our product.
Another idea would be to use the maven-exec-plugin as part of the build process to generate the version class. Or you could try and give the ant plugin a go ... -dirk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
