Matthias Wessendorf [EMAIL PROTECTED] schrieb:
On Jan 21, 2008 12:03 AM, Simon Kitching [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] schrieb:
-removed redundant versions as well...
plugin
-groupIdorg.apache.myfaces.trinidadbuild/groupId
-
Simon Kitching schrieb:
Ah, should have my eyes checked!
I do not like using pluginManagement (or dependencyManagement) to manage
artifact versions. I think it is obscure, and would much rather see the
actual version attached to each use (as it originally was).
Yes, the above
Bernd Bohmann [EMAIL PROTECTED] schrieb:
Simon Kitching schrieb:
Yes, the above approach will work. But it is worrying to look at a pom and
see something without a version attached. It requires work to confirm that
this is valid (ie that a parent does define a version). And it
Hello Simon,
I think a multi module project should define the common configuration of
plugins and dependencies in the management section.
For example: If you define different versions of the commons-logging
api. The dependency mechanism is not using the most recent version of
commons-logging,
[EMAIL PROTECTED] schrieb:
-removed redundant versions as well...
plugin
-groupIdorg.apache.myfaces.trinidadbuild/groupId
-artifactIdmaven-faces-plugin/artifactId
-version1.2.6-SNAPSHOT/version
+groupIdorg.apache.myfaces.buildtools/groupId
+
On Jan 21, 2008 12:03 AM, Simon Kitching [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] schrieb:
-removed redundant versions as well...
plugin
-groupIdorg.apache.myfaces.trinidadbuild/groupId
-artifactIdmaven-faces-plugin/artifactId
-
