Hi all-- I have a 3rd-party jar I am trying to install into my maven repository. The repository is filled with various jars installed by our company, and our current project references these with no problem.
I installed this jar with mvn install-file, and it shows up as expected in the local repository. I then added the dependency to my pom.xml. This 3rd-party jar is called "reactor.jar" and has a namespace edu.bsallas. When I modify my test script--which references the other repository jars no problem---to include an "import edu.bsallas.*", then the compilation fails, claiming no such package exists. However, right above it is an "import junit.framework.*", which references a locally-installed .jar (in our case) in the repository. The weird part is that maven, in building the test, seems to correctly reference the jar, because if I change the name of the jar in the repository to something bogus, then maven bombs that a dependency was not found. So the main issue for me: how can a jar be found while building, and then not found while running? I verified that the reactor.jar looks good: directory structure is correct ( top level is edu, then bsallas, then the class files ). I also tried another .jar file for a commercial product ( p6spy ) and am getting the same problems: class not found errors. Thanks if you have any ideas! Isaac -- View this message in context: http://www.nabble.com/locally-installed-jars-are-not-found-in-classpath-tp16786887s177p16786887.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
