maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <>
Subject Re: Module b needs jar from from Module a but needs to keep it _out_ of the classpath
Date Sun, 19 May 2013 21:51:59 GMT
Closest I can think is add a dependency of type "pom" to fix the build
order and use dependency:copy to grab the jar

On Sunday, 19 May 2013, Benson Margulies wrote:

> I'm faced with a situation I've met before.
> I have a multi-module project.
> 'Module A' builds a jar file. That jar file is a plugin for Apache Solr.
> 'Module B' is an integration test. It needs to copy that Module A jar
> file into a Solr installation tree and start Solr. It really, really,
> needs to not have that Module A jar file in its classpath.
> Is there a right way to do that?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: <javascript:;>
> For additional commands, e-mail:<javascript:;>

Sent from my phone

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message