What version of maven are you using? It looks like the 301 error saved to a pom file is a maven bug that has been fixed (though I can't tell which version it should be fixed in): https://issues.apache.org/jira/browse/MNG-4734
You'd also have to clean the bad files out of your local maven repo (~/.m2/repository). Also those site options aren't necessary, so you can just use mvn clean package -DskipTests. On Tue, Aug 18, 2015 at 9:35 PM, Matthew Hayes < [email protected]> wrote: > Hi, > > I'm trying to build with: > > mvn clean site:site site:stage package -DskipTests > > But, I get an error: " Non-parseable POM" about "jvnet-parent-1.pom". > Looking at this file it just contains an HTML response for "301 Moved > Permanently". Is there some trick to configuring Maven to build this > project that I'm unaware of? I'm not much of a Maven user and I couldn't > find anything helpful by searching online. > > Thanks, > Matt >
