[Harish wrote:] > so can you find any other solution. Here is how we are managing our application server libraries and server shared libraries on my current project.
We have internal corporate repositories (several - one per environment. E.g. unit, dev, test, release, etc.) We have an additional repository (third-party) We load the third-party jars using a script in the same manner posted to this thread earlier. We define the artifact version in the script to match the product version. There is no maintanance here (which I think you objected to) - leave that version in place indefinitely. When a new third-party product version is released, then run the script again with the new version. Projects declare their dependencies on a particular third-party dependency version and scope is "provided". When you migrate an application to the next version (update the dependency declarations in your pom files.) This works for us. Our only nit right now is how to build for multiple target product versions and reduce some maintenance. We are beginning to wrap these third-party dependencies into profiles so we can build for varying target appservers, content management systems, or whatever the set of third-party dependencies is for.) hth --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
