I tried that and it failed.... however I *think* there is another reason for this not working...
I have ./pom.xml (organization pom, with site.xml skin== acme-maven-site-skin e.t.a...) ./acme-maven-site-skin/pom.xml (this is the actual jar skin module) The reactor build order "install site" *appears *to try and build 1. parent (install) 2. parent (site) 3. acme-maven-site-skin (install) 4. acme-maven-site-skin (site) This fails at #2 because "acme-maven-site-skin (install)" has not been executed yet and the skin is not in the repository. Is it weird/wrong that I have a skin as a module under the organization pom? CHEERS HEAPS!!!! --AH On Wed, Apr 7, 2010 at 10:29 AM, Brett Porter <[email protected]> wrote: > Use ${project.version} as the value for the skin: > > > http://github.com/brettporter/centrepoint/blob/master/centrepoint/documentation/src/site/site.xml > > On 7 April 2010 09:53, Andrew Hughes <[email protected]> wrote: > > > Hi All, > > > > I've written a site skin (com.acme:acme-maven-site-skin-1.0.0-SNAPSHOT) > and > > of course I want "the site skin project" to use the skin for its site :) > > so.... > > > > ./src/site/site.xml: > > > > <skin> > > <groupId>com.acme</groupId> > > <artifactId>acme-maven-site-skin</artifactId> > > <version>1.0.0-SNAPSHOT</version> > > </skin> > > > > However, when I *release:prepare release:perform* the project the > > ${project.version} will become 1.0.0 but the site.xml's ${skin.version} > > will > > remain at 1.0.0-SNAPSHOT (unless I am wrong). > > > > How can I sync the ${project.version} and the skin.version when > performing > > a > > release? > > > > CHEERS :) > > > > > > -- > Brett Porter > http://brettporter.wordpress.com/ >
