Is that patch still pending, or has it been applied? I can grab it
and process it if necessary...
-john
On Aug 14, 2007, at 3:34 PM, Jason van Zyl wrote:
On 14 Aug 07, at 9:30 PM 14 Aug 07, Paul Gier wrote:
Kenney Westerhof wrote:
Brian E. Fox wrote:
Sure. I've been thinking that the standard rules should come out
of the
plugin into a separate module too. The thing I'd ultimately like
to do
is be able to release the rules separate from the plugin since the
majority of changes occur to the rules.
The problem is that I'd like to be able to default the enforcer
to the
current ruleset at release time (for ease of use), but somehow
allow the
users to be able to change the ruleset version if they wanted. I
think
if a plugin sets a dependency, then it's not possible to
override it
during use. Any ideas how this could be accomplished?
I think plugin deps _should_ be overridable in the dependencies
section
within the plugin tag.
Perhaps adding a depMgt for those deps works too - it works as an
override
for transitive deps, and if the current pom is used as the start of
plugin resolution it will be applied, but i'm not sure..
To get this to work in a nice way maven will need to be fixed, I
think.
-- Kenney
+1
Can this ability be added in maven 2.1 ? It seems like it makes
sense to treat plugin dependencies like regular dependencies
meaning that you should be able to exclude or override certain
plugin dependencies. It would help with a few of the projects
within JBoss.
Eric actually patched it back to do that a while ago and I think we
can do it 2.0.8. It used to work and is infinitely useful. Not sure
when it got crippled.
-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Tuesday,
August 14, 2007 8:09 AM
To: Maven Developers List
Subject: Enforcer Sources
Brian,
Can we follow the same pattern we use for Surefire, and the
Release tools where they are all collected together under one
umbrella. I was playing around with the enforcer and then
noticed I need something from shared and looking at them
together is hard, one being in a plugin and one being in
shared. Can we put them together and follow the same pattern
for a toolset?
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
