Gabriel Roldán wrote: > know what? I've deployed back in October using the maven 2.0.5 with dav > support from here: > <http://lists.refractions.net/m2/_share/maven-2.0.5-SNAPSHOT-bin.zip> found > on this page: > <http://docs.codehaus.org/display/GEOT/How+to+add+a+3rd+party+jar"; > > may that help? (sorry didn't quite followed the whole thread in deep) > Thanks Gabriel - I have a couple of clues.... Using maven 2.0.5 or maven 2.0.8 the following fails when I just do it on the command line: > mvn deploy:deploy-file -DgroupId=com.vividsolutions -DartifactId=jts > -Dversion=1.9-RC6 -Dfile=C:\java\jts-1.9-RC6\lib\jts-1.9-RC6.jar > -Dpackaging=jar -DrepositoryId=refractions > -Durl=dav:http://lists.refractions.net/m2 If I go into a geotools directory (like modules\library\metadta) then it will succeed. So there is something in our pom.xml that is helping the deploy:deploy-file command to do its job? I was not aware that mvn deploy:deploy-file would check the pom.xml (since it does try to work from any directory) but there you go ...
Turns out that 2.0.8 will work when using the following command: mvn deploy -Dmaven.test.skip=true Previously I had been using "mvn deploy:deploy -Dmaven.test.skip=true"; hense the "The packaging for this project did not assign a file to the build artifact" error message. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
