I'm having a build failure, on rawhide only, of a Java package that is built with maven. When I run maven from the command line, if I give it more than one -DXXX option, it always complains that the second one is not a valid target. I took a tip from a web site that mentions this problem and tried this (where the first 3 -DXXX options are from /usr/bin/mvn-jpp, and the 4th is the recommended way of using mvn-jpp in a spec file):

$ export MAVEN_OPTS="-Dmaven2.offline.mode -Dmaven2.ignore.versions -Dmaven2.usejppjars -Dmaven.repo.local=$MAVEN_REPO_LOCAL" $ mvn install That worked. Is this an expected change? If so, both the /usr/bin/mvn-jpp script and the wiki description of how to use maven will have to be changed. If not, does anyone have any idea why multiple -DXXX options aren't working for me? Again, this is on Rawhide only. Thanks, -- Jerry James http://loganjerry.googlepages.com/ -- fedora-devel-list mailing list fedora-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, Jan 9, 2009 at 1:00 PM, Deepak Bhole <dbhole(a)redhat.com&gt; wrote: > Can you post the exact command that you are running (when it fails) and > what the resulting log is? This is an attempted rebuild of the jsr-305 package. It's a pretty small download, if anybody wants to try it. The spec file contains this: export MAVEN_REPO_LOCAL=$(pwd)/.m2/repository mkdir -p $MAVEN_REPO_LOCAL mvn-jpp -Dmaven.repo.local=$MAVEN_REPO_LOCAL install The mvn-jpp invocation produces this output: /usr/lib/jvm/java [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] JSR 305: Annotations for Software Defect Detection in Java [INFO] JSR 305 Implementation [INFO] JSR 305 Test Cases [INFO] JSR 305 Sample Use Cases [INFO] JSR 305 Proposed Annotations [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Invalid task 'maven2.ignore.versions': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Sat Jan 10 13:02:47 MST 2009 [INFO] Final Memory: 2M/7M [INFO] ------------------------------------------------------------------------ I have tried extracting out the bits of the mvn-jpp script and running them directly in the shell, culminating in a line like this: $ mvn -Dmaven2.offline.mode -Dmaven2.ignore.versions -Dmaven2.usejppjars -Dmaven.repo.local=$MAVEN_REPO_LOCAL install This produces the same output. If I change the order of the -D arguments, maven always complains about the second one. Is anybody else seeing this? Again, this is only on Rawhide. F-9 and F-10 build with no problems. I just updated my Rawhide installation and tried again with the same result.

-- Jerry James http://loganjerry.googlepages.com/

No. I did update with yum from F-10 instead of installing Rawhide directly, because I was unable to get the installer to complete (see https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00014.html). But I have not installed anything but Fedora packages on this machine. It looks to me like maven's command-line processing is busted.

I'm having a build failure, on rawhide only, of a Java package that is built with maven. When I run maven from the command line, if I give it more than one -DXXX option, it always complains that the second one is not a valid target.

Currently none of the packages using maven will compile. See below: https://bugzilla.redhat.com/show_bug.cgi?id=480093

Hello Deepak, Jerry, Jerry James wrote: > I'm having a build failure, on rawhide only, of a Java package that is > built with maven. When I run maven from the command line, if I give > it more than one -DXXX option, it always complains that the second one > is not a valid target. The same issue has occurred for my package ini4j during the mass rebuilds. [1] It is extremely simple package (15 java classes) that uses the maven specfile template [2] "as is". See [3]. Do you have a solution or any new ideas how to fix it? [1] http://koji.fedoraproject.org/koji/getfile?taskID=1167498&name=build.log [2] https://fedoraproject.org/wiki/Packaging:Java#maven_2 [3] http://cvs.fedoraproject.org/viewvc/rpms/ini4j/devel/ini4j.spec?view=log

Thanks, Victor