Hello, I am trying to use the GWT maven plugin which relies on java source
files. My project works when I run mvn install from my gwt application
module's pom.  The classloader correctly references the sibling module's jar
and sources-jar from my local maven repository.  

When I run mvn install from the parent's pom, instead of the class loader
looking for the sibling module's dependencies in my local maven repository,
it is referencing the module's target/classes folder directly.  By doing
this, my source files are not in target/classes and my gwt build fails.  

Is there any way to force maven to use the repository instead of local
project folders? I do not want to have to manually copy the sources files
into the output directory.

parent
  |-gwt application
  |  |-src/main/java/...
  |  |-pom.xml
  |-other source files (generates jar and sources-jar)
  |  |-src/main/java/...
  |  |-pom.xml
  |-pom.xml
-- 
View this message in context: 
http://www.nabble.com/Classloader-issues-with-source-files-in-an-aggregate-build-tp20343191p20343191.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]

Reply via email to