On 22/03/2009, at 11:50 PM, Karl Heinz Marbaise wrote:
But on the other hand the web-site does not say a word about that ...
http://maven.apache.org/pom.html#Profiles to be more accurate they
are simply wrong, cause they are using:
<project xmlns ...
I think the docs should be updated...If i can help ?
Sure - please submit a JIRA ticket for the issue, and if you can later
patch against the APT documentation for that file.
A little difference has been comming up:
MVN 2.1.0 prints out a warning about an non activated profile
and about not configured copying encoding
(build is platform dependent)
But based on the above changes the build is working under MVN 2.1
and MVN 2.0.9...
These are just warnings. The first is because you used a -P argument
that was never actually activated because the profile doesn't exist.
The second comes from the resources plugin I think and indicates you
may get different build results on different machines if they have a
different system encoding.
- Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
