Corwin Joy wrote: > Ryan Lee wrote: >> I did notice that the Sesame SNAPSHOT jars shouldn't be coming from > the >> Simile Maven proxy server. Certainly that would be one reason why >> dependency mismatches arise as our proxied SNAPSHOTs probably reflect > a >> dependency state that's months old. I'm not sure why that's happening >> though; which version of Maven are you using, and which command did > you >> run for the build? > > I am using maven version 2.0.7 (which is the latest release). > To build longwell I gave the command: > > mvn package > > as per the docs. > Honestly, I'm pretty sure that if you grab the longwell-2.5.1.zip > release on a windows box and run "mvn package" you will see the same > effect I did since I did this with a clean maven environment.
I did and got a successful build. As noted earlier, the issue is that Maven is leaning on the SIMILE repository proxy for snapshots that should really be coming from the Aduna repository. Your initial report contained this line: [WARNING] repository metadata for: 'snapshot org.openrdf:openrdf-queryresult-api:2.0-SNAPSHOT' could not be retrieved from repository: aduna-snapshot-repo due to an error: Error transferring file This makes me think that, for whatever reason, your connection to the Aduna snapshot repository is being blocked or otherwise corrupted (that repository is unnecessary for Longwell 2.4.2). Can you see http://repository.aduna-software.org/maven2-snapshots ? Could you try the build from a different network? -- Ryan Lee [EMAIL PROTECTED] MIT CSAIL Research Staff http://simile.mit.edu/ http://people.csail.mit.edu/ryanlee/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
