Sorry for all the noise... I have this working now. The only real issue here was that there was a m-site-p definition in the company pom build section. Everything else is working as it should be. Time to take the rest of the day off!
Thanks for listenting :) -Ryan On Sun, Jan 9, 2011 at 12:22 PM, Ryan Connolly <[email protected]> wrote: > OK, I've discovered part of the problem I was having here. The company pom > defined the m-site-p in the build section which was invoking it when it > should not have been. Now I have the m-site-p configured in the company pom > in the pluginManagement section only and am getting much closer to the > desired outcome. The problem now is that the new dev version of the site is > being deployed even though the maven logs are saying otherwise. > > Is anyone else seeing anything like this on m3 with m-site-p:3.0-beta-2 and > m-release-p:2.1? > > It would seem that my current configuration should actually do what I want > but there seems to be something amiss between using ${project.version} in > the site.url and the actual version that gets uploaded. > > I'll continue to investigate but if anyone has any input I would be > grateful. > > -Ryan > > > > > > > > On Sun, Jan 9, 2011 at 11:24 AM, Ryan Connolly <[email protected]> wrote: > >> Hello: >> I am trying to update my company pom to include a m-release-p >> configuration for all other internal projects to use and in the process I am >> hoping to get site deployment to upload just the released version of >> javadocs upon release. It would appear that using the default release goals >> of "deploy site-deploy" is uploading the current SNAPSHOT version of the >> site on prepare and the updated dev version on perform. What I would like >> to have happen is for the site-deploy goal to be run from the checkout >> directory resulting in one site deployment of the released site. Is there >> any way to do this by configuring the m-release-p and a site >> distributionManagement element only or would this require a release profile >> and perhaps antrun? I also don't want to require my team to remember to cd >> into the checkout directory and run site-deploy there in order to get >> released site deployments working. >> >> I'm hoping to end up with a structure on my webserver after performing >> releases to project1 and project2 as follows: >> >> project1 >> - 1.0 >> - 1.1 >> project2 >> - 1.0 >> - 1.1 >> >> I have defined the site distributionManagement as follows in each POM: >> <distributionManagement> >> <site> >> <id>site</id> >> <name>API Documentation</name> >> >> <url>${site.deploy.url}/${project.artifactId}/${project.version}</url> >> </site> >> </distributionManagement> >> >> Does anyone have any ideas on how I might get this to work out? >> >> Thanks in advance, >> -Ryan >> > >
