Thinking out loud...
The rules would have to be shared amongst thousands of projects. I guess I
could put the plugin in some shared parent POM.
The groupId/artifact naming convention for categories will be tough. I have no
control over that.
What would be cool is if we could add additional i
On Fri, Oct 1, 2010 at 12:56 PM, Alan D. Cabrera wrote:
> Is there some way to categorize jars and restrict the dependencies between
> categories of those jars? At least maybe reports dependency violations?
>
> For example let's say I have two categories, api and impl. Impl can depend
> on Api
maybe you could enhance that rule to do regexp matching on each maven
coordinate component and implement your category concept using a naming
convention?
david jencks
On Oct 1, 2010, at 10:51 AM, Alan D. Cabrera wrote:
> It's close but not exactly what I need. I don't want to maintain rules o
It's close but not exactly what I need. I don't want to maintain rules on
artifacts. I want to maintain restrictions between categories of artifacts.
Regards,
Alan
On Oct 1, 2010, at 10:22 AM, Rex Hoffman wrote:
> I haven't used it: but this, and profiles, should do the trick.
> http://maven
I haven't used it: but this, and profiles, should do the trick.
http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html
I'm just trying to get some contributions in to maven (other enforcer
rules) but still feel the need to say you probably should have asked
this on the user mailin
Is there some way to categorize jars and restrict the dependencies between
categories of those jars? At least maybe reports dependency violations?
For example let's say I have two categories, api and impl. Impl can depend on
Api but not others' impl. Api can rely on Api. When I perform a b
