> Our project depends on various corporate libraries which are not > "Mavenized". In order to use these libraries, we frequently use > deploy:deploy-file to drop them on our repository, with a fixed version > (given that new versions are duly tested and obsolete older versions).
I want to be sure that I understand what you are saying here. The versions are DIFFERENT each time you run deploy-file, right? It is a basic premise of Maven and most sane build systems that that a given artifact with a particular version number must be immutable. Otherwise you have no idea if your file versioned 2.3.2 is the "right one" vs another file with version 2.3.2 that exists somewhere else. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
