I think the title of John's proposal is actually a bit misleading - it
refers to the runtime behaviour of the existing POM, not any change to
the way you can use the POM itself.
- Brett
On 17/06/2008, at 5:12 PM, Gilles Scokart wrote:
I have seen recently some discussion about enhancing the dynamicity of
the pom. This is maybe a good thing for the build section in the
source pom.
I know that the discussion were about those part. But please, make
sure that this will not leak into the published pom.
When working on the dynamicity of the pom, please always remind you
that the published poms must be as simple as possible. The published
pom must be processable by XSLT, ivy, buildr, etc...
We already have enought problems with published pom using properties
like parent.version, project.groupId, pom.groupId, project.artifactId,
pom.artifactId, project.version, pom.version, version or other user
properties defined in the properties tag.
--
Gilles Scokart
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
