Update, I tried to back this out to maven2 and a collection of old plugins, but I still can't get it working. Everything I try fails for this reason or something else telling me to update my plugins. I even totally re-created new project/modules in an effort to fix this. I'm totally stumped with this and starting to wonder if I am on a wild goose chase :'(
On Thu, Apr 14, 2011 at 9:14 AM, Andrew Hughes <[email protected]> wrote: > Lukas, > > Thanks for the answer. Unless I can fix this myself I had better shut up > about it. I guess the workaround here is to stay on maven 2 for the time > being (note that the pom <reporting> sections are different in m2 and m3 > pom.xml's ). > > Thanks for the info. > > > Steve, > > That's a really good point and a big "gotcha" for anyone trying to release > their project. Seems like m2 might be the only proper workaround to this (if > you really do want sites). In addition to this... a little off topic but > quite relevant to what you have said. I'm a big fan of sites, but I believe > site-deploy shouldn't be a goal that is run during a release. This is > because the site can be re-built and deployed anytime you want (post > release). It's convenient to have these run together, but let's say a > password has expired or the site's url host is turned off, or network > problems - I think it adds unnecessary risk to a release. Consequently we > turned this off... > > > <plugin> > <groupId> > org.apache.maven.plugins > </groupId> > <artifactId> > maven-release-plugin > </artifactId> > <configuration> > > <!-- > removed site-deploy > from the release goals, a failed site-deploy should not > hold up a release, it > can be manually deployed from ./target/checkout > after the > release:perform has finished or manually deployed later from the > scm tag > --> > > <goals> > deploy > </goals> > </configuration> > </plugin> > > > > I have a different opinion on this. I am a big fan of maven site's however > I don't believe that if something fails during > > > On Wed, Apr 13, 2011 at 5:09 PM, Stevo Slavić <[email protected]> wrote: > >> I'm also affected by this issue, when releasing project using >> maven-release-plugin, prepare goes well, perform fails as it detects >> site in distributionManagement and default goals run are "deploy >> site-deploy" so maven tries to generate and deploy site, but since >> site plugin tries to resolve something that's not installed/deployed >> yet, release:perform fails. >> >> One workaround could be to configure prepare mojo's >> >> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals >> to be "clean install" instead of default "clean verify", install is >> after verify, if verification fails install will not be performed, if >> verification is successful install will be performed and artifacts >> will be available in local repository, so as long as release:perform >> is run on same node/machine by same user as release:prepare, site >> should be generated and deployed; deploy will install/overwrite >> artifacts again in local repo and deploy them to remote repo. >> >> Regards, >> Stevo. >> >> On Wed, Apr 13, 2011 at 9:17 AM, Lukas Theussl <[email protected]> >> wrote: >> > >> > That's an old issue, see http://jira.codehaus.org/browse/MSITE-171 and >> > related tickets. >> > >> > -Lukas >> > >> > >> > Andrew Hughes wrote: >> >> >> >> Hi All, >> >> >> >> Before each of the following test, I delete my project/module artifacts >> >> from >> >> my local repo.... >> >> >> >> The following works :) >> >> >> >> *mvn clean install * >> >> *mvn site* >> >> >> >> >> >> The following fails :( >> >> >> >> *mvn clean install site* >> >> >> >> >> >> The following also fails :( >> >> >> >> *mvn clean install site:site* >> >> >> >> >> >> The error I consistently get is: >> >> >> >> [ERROR] Failed to execute goal >> >> org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site >> (default-site) >> >> on >> >> project acme-project: failed to get Reports: Failed to execute goal on >> >> project acme-project-d: Could not resolve dependencies for project >> >> com.acme.project:acme-project-module-d:ejb:5.1.0-SNAPSHOT: *Could not >> find >> >> artifact com.acme.project:acme-project-module-a:jar:5.1.0-SNAPSHOT* in >> >> archiva (http://acme.com/repository/all/) -> [Help 1] >> >> >> >> ...site appears to be running on the incorrect phase or build >> lifecycle. >> >> Consequently, the (module) dependencies have not been install/deployed >> to >> >> my >> >> local repository yet. >> >> >> >> Any idea's how I can fix this??? >> >> >> >> Cheers. >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
