Re: [VOTE] Release Maven Assembly Plugin version 2.2

2010-10-01 Thread Hervé BOUTEMY
+1 Hervé Le mercredi 29 septembre 2010, John Casey a écrit : > Hi, > > *** NOTE *** > This release depends on the pending 1.3 release of > maven-common-artifact-filters. You will need BOTH of the staging > repositories listed below in order to build the maven-assembly-plugin. > > We solved 92 i

Re: [VOTE] Release Maven Common Artifact Filters version 1.3

2010-10-01 Thread Hervé BOUTEMY
+1 Hervé Le mercredi 29 septembre 2010, John Casey a écrit : > Hi, > > We solved 1 issue: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=15 > 582 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mod

Re: Release plugin snapshot dependency resolution

2010-10-01 Thread Dennis Lundberg
On 2010-09-29 15:50, Brett Porter wrote: > Hi, > > The release plugin has a mode where it can assist you in updating snapshot > dependencies at release time. A lot of this is better manipulated with the > versions plugin now, but it seems a useful feature to have at release time if > you can. >

Re: Dependency policies

2010-10-01 Thread Alan D. Cabrera
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

Re: Dependency policies

2010-10-01 Thread Wendy Smoak
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

Inflexibility of --also-make w.r.t. unusual goals

2010-10-01 Thread Jesse Glick
While working on IDE support for running Maven on multi-module projects [1] I have run up against what seems to be a fundamental limitation of --also-make. This "reactor mode" works fine when the specified goal is standard across all lifecycles in the tree, such as 'install' or 'package'. But fr

Re: Dependency policies

2010-10-01 Thread David Jencks
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

Re: Dependency policies

2010-10-01 Thread Alan D. Cabrera
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

Re: Dependency policies

2010-10-01 Thread Rex Hoffman
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

Dependency policies

2010-10-01 Thread Alan D. Cabrera
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