* Orion Poplawski <orion@xxxxxxxxxxxxx> [2010-08-26 16:55]: > On 08/26/2010 02:40 PM, Deepak Bhole wrote: > >After lots of poking, I think I finally found the problem. It comes down > >to this file: > > > >http://svn.apache.org/repos/asf/maven/shared/tags/maven-shared-components-15/maven-invoker/src/main/java/org/apache/maven/shared/invoker/MavenCommandLineBuilder.java > > > >That line builds the mvn command that gets executed and what is > >happening is that it is setting maven.repo.local based on the parent > >(mvn-jpp) call which has it set. However, there is a bug in the > >setEnvironmentPaths() function which causes it to provide the "-D" and > >"maven.repo.local..." as 2 separate args instead of one. > > > >Outside of patching the above file, afaik here is no way to fix > >this and you are probably better off just disabling the > >integration tests. > > Thanks for looking at this, but working concurrently, it appears > that using test.properties files with: > > maven.jpp.mode=1 > > in them does what I want. > Ah cool. How did you manage to get it to see the right repo though? Deepak > After further examination it looks like mavenOpts are really java > options (e.g. -Xms32m) to be used when running maven. > > -- > Orion Poplawski > Technical Manager 303-415-9701 x222 > NWRA/CoRA Division FAX: 303-415-9702 > 3380 Mitchell Lane orion@xxxxxxxxxxxxx > Boulder, CO 80301 http://www.cora.nwra.com -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
