On 5/6/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I have a project with multiple modules.
I'm keeping the version numbers synced.
This ends up with a lot of repetition of the version number:
<artifactId>tapestry-core</artifactId>
<packaging>jar</packaging>
<version>5.0.5-SNAPSHOT</version>
<parent>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-project</artifactId>
<version>5.0.5-SNAPSHOT</version>
<relativePath>../tapestry-project/pom.xml</relativePath>
</parent>
You can use ${project.version} in the poms.
Worse yet, those same version numbers are creeping into documentation and
into project archetypes.
I think you will still need to tie the archetype to a particular
version of your project. What's the issue with documentation?
How would I go about externalizing the version number so that it appears
just once? I'd love to have something like I used to do in Ant ... a
build.properties file that defines the version number.
Also, is there a general way to include POM properties inside APT documents
and/or site.xml?
The next version of the site plugin will do this, check the dev list
for more info. Right now it's too aggressive and filters everything,
which breaks existing sites that wanted the literal expression to be
displayed. Jason is going to change it so it only filters things in a
certain directory.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
