> So, I changed the 'version' field to 2.2.1-SNAPSHOT in the wagon-http pom > file. > I had to force 2.2 for the parent. > I attempted to build: mvn install.
This is the correct way to run "mvn install" on such a project. > The build failed, because of a surefile test for HTTP Provider. > I decided this might be caused by a proxy configuration (?) so that I > decided to skip this. If you have problems running tests, then just skip them [1]. As an aside, I pulled down wagon-2.2 from the tag and had no issues building it and running tests. But I have no HTTP proxy in my home Internet connection (unless my ISP is running squid transparently). You should be able to just: svn checkout http://svn.apache.org/repos/asf/maven/wagon/tags/wagon-2.2 wagon cd wagon mvn clean package And things should just run. Then you can go in and adjust versions to 2.2.1-SNAPSHOT and run it again. > I tried next: mvn install::install Generally, you should not be invoking goals directly but rather depending on Maven's build lifecycle. > org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-cli) > on project wagon-provider-api: > The packaging for this project did not assign a file to the build artifact ... > Now, why was it not set, I didn't understand. Read the error message again. "The packaging for this project did not assign a file to the build artifact" That is why the file attribute was not set. [1] http://maven.apache.org/plugins/maven-surefire-plugin/examples/skipping-test.html Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
