David Newton wrote:I would have assumed that you'd need to manage that jar's dependencies just like any other Maven artifact--with a pom. Not entirely sure what you're doing, though--if you're compiling, I'd be almost certain that Maven controlled the compilation classpath.
I have a tool which is packaged as .jar . This tool has its own dependencies included in this jar but it's not managed by maven.
I want to use this tool in my project which is managed by Maven.
I installed manually this .jar file into my local repository and added a dependency to project I'm developing.
It looks like maven changed classpath of this jar. I don'w know how to make this jar work just like if I run it by command line.