Stefano Mazzocchi wrote:
[EMAIL PROTECTED] wrote:
As an aside, one of the issues we had when coming up with Maven's
repository format, is that often artifacts (jars, wars, ears etc), will
get left on the filesystem outside of a repository.
Think rpms for example.
Having a file encode <project>-<artifact>-<version>.type has been very
useful for us.
Yes, it's often different from what the project creates and
distributes, but I (and others) have been bitten by
commons-logging.jar, struts.jar, junit.jar so many times, that seeing
log4j-1.2.5.jar is a godsend.
A big +1 to get version in jar file name :
For instance in jpackage we install all 'small jars in ' :
/usr/share/java/
And make use of symlink :
/usr/share/java/log4j-1.2.7.jar
/usr/share/java/log4j.jar -> /usr/share/java/log4j-1.2.7.jar
When there is many jars in a project, we're using subdir :
/usr/share/java/jsse/jcert-1.0.3.01.jar
/usr/share/java/jsse/jcert.jar -> jcert-1.0.3.01.jar
/usr/share/java/jsse/jnet-1.0.3.01.jar
/usr/share/java/jsse/jnet.jar -> jnet-1.0.3.01.jar
/usr/share/java/jsse/jsse-1.0.3.01.jar
/usr/share/java/jsse/jsse.jar -> jsse-1.0.3.01.jar
As such you could have many differents versions at the same time
in the repository :
ie :
tyrex-0.9.7.jar (for TC 4.0.x)
tyrex-1.0.jar (for TC 4.1.x)
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
