There is no other way. You will need to deploy them to your internal remove repository.
If you already have internal repository setup ( do you have one? ) this is one one time setup. Just curious, you have 50 non public jars? If you are not willing to do that, i would suggest to stay with your current build. I got burned try to port a legacy intact to maven with file structure intact before. -D On 7/1/06, Punit Rathore <[EMAIL PROTECTED]> wrote:
This is another one of the "classpath question". Here is my problem. In my project I have to include a set of jar files that have been produced by another project(s) and have traditionally been deployed in nfs mounted path like /common/libs/prj1/lib. Now this path contains more than 50 jars that I need to include. After much googling and reading up on this mailing list, i found one potential solution was to dependency with system scope. However this means that I will have to define the dependency of each of the more than 50 jars. I find that very impractical. Another was to import it in to repository using mvn install:install-file. This approach had the same problem ( importing each of 50 jars). Is there another way of easily doing this ? Thanks, Punit
