On Fri, 2004-06-11 at 14:32, Bielby, Randy J wrote: > I have a situation that I don't believe is unique but I can't seem to > find all the info I'm looking for. I have several projects with a > number of dependent jars. The development team is anywhere from 10-30 > developers depending upon the project. We are using WSAD and have as > one of the projects in our workspace a webapp. This webapp contains all > the dependent jars within the WEB-INF/lib folder. All the other project > within the workspace are included as dependent jars in the EAR. I would > prefer that the compile uses the jars in the lib folder. This is the > ensure that the deployed runtime code is the same as what the developers > have developed against. I know this goes against Maven's perferred > method of retrieving dependencies for the repository. I know that I can > override this behavior, but I'm struggling with how to go about it.
Could you override the dependency retrieving by setting "maven.jar.override=true" in your project.properties and then listing the path to each of the JARs explicitly? In this case, the "structure" does not have to respect the regular repo structure since you're not overriding maven.repo.remote. > Also, due to corporate defined standards, my jar names cannot contain > the version number (don't ask). So I also need my jar dependencies to > be something like, log4j.jar instead of log4j-1.2.6.jar. I have tried > eliminating the version from the dependency but I get, log4j-.jar > instead. If you use the <jar> tag you can specify the filename explicitly. - Julian -- Julian C. Dunn, B.A.Sc. <[EMAIL PROTECTED]> Software Developer, CBC New Media Operations Office: 2C310-I * Tel.: (416) 205-3311 x5592 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
