Well, it turned out to be the Maven version as Ian hinted. I have been using the embedded Maven (built from the 2.1 line, apparently) in http://m2eclipse.codehaus.org/ for many months now with no issues. However, the recent POM changes to Shindig must've exposed an incompatibility there, so I pointed the build to my external 2.0.9 Maven and it works now.
Sheesh! Thanks for your help, Dave -----Original Message----- From: Ben Smith [mailto:[email protected]] Sent: Tuesday, January 20, 2009 3:56 PM To: [email protected] Subject: Re: svn commit: r734708 - in /incubator/shindig/trunk/java: common/pom.xml common/src/main/java/org/apache/shindig/common/testing/ common/src/test/java/org/apache/shindig/common/testing/ gadgets/pom.xml social-api/pom.xml Same. Our internal hudson has built successfully and that will usually break at the first sign of a high wind! Ian Boston wrote: > As another data point: > java 1.5 > mvn 2.0.9 > OSX 10.5 > r736064 > rm -rf ~/.m2/repository/org/apache/shindig > mvn clean install > mvn -Psamples clean install > mvn -Prun > > All appear to build and run perfectly. > So it might be your environment, > I know the version of mvn is important, < 2.0.8 might not work. > > HTH > Ian > > On 20 Jan 2009, at 20:20, Citron, David wrote: > >> Paul, >> >> Am I right to assume that a clean trunk build works for you and the >> problem is somehow specific to my environment? >> >> Thanks! >> Dave >> >> -----Original Message----- >> From: Citron, David [mailto:[email protected]] >> Sent: Tuesday, January 20, 2009 2:40 PM >> To: [email protected] >> Subject: RE: svn commit: r734708 - in /incubator/shindig/trunk/java: >> common/pom.xml common/src/main/java/org/apache/shindig/common/testing/ >> common/src/test/java/org/apache/shindig/common/testing/ gadgets/pom.xml >> social-api/pom.xml >> >> I do not. Even after a clean/build cycle, in java/common/target I only >> have: >> >> shindig-common-1.1-SNAPSHOT-sources.jar >> shindig-common-1.1-SNAPSHOT-test-sources.jar >> shindig-common-1.1-SNAPSHOT.jar >> >> What would cause the common build not to generate the test.jar but still >> to succeed? >> >> Thanks! >> Dave >> >> -----Original Message----- >> From: Paul Lindner [mailto:[email protected]] >> Sent: Tuesday, January 20, 2009 2:27 PM >> To: [email protected] >> Subject: Re: svn commit: r734708 - in /incubator/shindig/trunk/java: >> common/pom.xml common/src/main/java/org/apache/shindig/common/testing/ >> common/src/test/java/org/apache/shindig/common/testing/ gadgets/pom.xml >> social-api/pom.xml >> >> Do you have this file: >> >> ./java/common/target/shindig-common-1.1-SNAPSHOT-tests.jar >> >> If not then maybe try a full build/clean cycle? >> >> On Jan 20, 2009, at 11:16 AM, Citron, David wrote: >> >>> This commit appears to have broken the build for me. Am I the only one >>> seeing this problem? >>> >>> [INFO] >>> [INFO] >>> [INFO] >>> >> ------------------------------------------------------------------------ >>> [INFO] Reactor Summary: >>> [INFO] >>> >> ------------------------------------------------------------------------ >>> [INFO] Apache Shindig Project ................................ SUCCESS >>> [8.328s] >>> [INFO] Apache Shindig Project Parent ......................... SUCCESS >>> [1.297s] >>> [INFO] Apache Shindig Common Code ............................ SUCCESS >>> [5.453s] >>> [INFO] Apache Shindig Gadget Renderer ........................ FAILED >>> [1.672s] >>> [INFO] Apache Shindig Social API ............................. NOT >>> BUILT >>> [INFO] Apache Shindig Features ............................... NOT >>> BUILT >>> [INFO] Apache Shindig Web App ................................ NOT >>> BUILT >>> [INFO] >>> >> ------------------------------------------------------------------------ >>> [ERROR] >>> >>> ... and then ... >>> >>> Error message: Missing: >>> ---------- >>> 1) org.apache.shindig:shindig-common:test-jar:tests:1.1-SNAPSHOT >>> >>> Try downloading the file manually from the project website. >>> >>> Then, install it using the command: >>> mvn install:install-file -DgroupId=org.apache.shindig >>> -DartifactId=shindig-common -Dversion=1.1-SNAPSHOT -Dclassifier=tests >>> -Dpackaging=test-jar -Dfile=/path/to/file >>> >>> Alternatively, if you host your own repository you can deploy the >>> file >>> there: >>> mvn deploy:deploy-file -DgroupId=org.apache.shindig >>> -DartifactId=shindig-common -Dversion=1.1-SNAPSHOT -Dclassifier=tests >>> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] >>> -DrepositoryId=[id] >>> >>> Path to dependency: >>> 1) org.apache.shindig:shindig-gadgets:jar:1.1-SNAPSHOT >>> 2) org.apache.shindig:shindig-common:test-jar:tests:1.1-SNAPSHOT >>> >>> ---------- >>> 1 required artifact is missing. >>> >>> for artifact: >>> org.apache.shindig:shindig-gadgets:jar:1.1-SNAPSHOT >>> >>> from the specified remote repositories: >>> oauth (http://oauth.googlecode.com/svn/code/maven), >>> central (http://repo1.maven.org/maven2), >>> apache.snapshots >>> (http://people.apache.org/repo/m2-snapshot-repository), >>> caja (http://google-caja.googlecode.com/svn/maven) >>> >>> Group-Id: org.apache.shindig >>> Artifact-Id: shindig-gadgets >>> Version: 1.1-SNAPSHOT >>> From file: C:\dev\shindig\java\gadgets\pom.xml >>> >> > >
