We faced something similar except it was our beast, not a 3rd party. The good news is I bet a high % of those hundreds of other jars do have versions and are in maven repos...so the job may be to just create a pom type pom that lists each of these dependencies with their real versions. If one is found that isn't in a public maven repo, just add it to your own corporate repo...such as Artifactory.
-Dave On Tue, Mar 30, 2010 at 12:03 PM, Tom C <[email protected]> wrote: > Good day - > > I have a third party jar that depends on hundreds of other jars. The > third party jar does not use maven and the dependencies do not have > version numbers. Is there a method to manage the dependencies without > install:install-file each dependency? > > Thanks in advance. > > ~ Tom > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
