Re: Programmatically adding dependencies to a MavenProject

2009-01-26 Thread Costin Caraivan
Jason van Zyl-5 wrote: > > This is a bad idea and don't count on Maven 3.x supporting this > because it makes determining what the dependencies are black magic. > The dependency tree and visualization tools won't work. In Maven 3.x > we are likely to make the dependency set immutable post

Re: Precedence of direct dependencies with equal conflict id

2009-01-26 Thread Brian Fox
Good point, I didn't consider things in a repo. We'll have to take the last one in that case. --Brian (mobile) On Jan 26, 2009, at 6:21 PM, Brett Porter wrote: On 26/01/2009, at 12:17 PM, Brian E. Fox wrote: It should be a validation error if we find duplicated entries. +1 when buildi

Re: Precedence of direct dependencies with equal conflict id

2009-01-26 Thread Brett Porter
On 26/01/2009, at 12:17 PM, Brian E. Fox wrote: It should be a validation error if we find duplicated entries. +1 when building a project. Probably not when encountered in the repository (but changing the first would reduce the impact over time). - Brett -Original Message- Fro

Skinny War

2009-01-26 Thread Timothy Twelves
Hi, I am new to maven development and have been tackling the "skinny" war problem (http://docs.codehaus.org/display/MAVENUSER/Solving+the+Skinny+Wars+problem). After a few attempts and considering pros and cons of various solutions and their implementations I am resigned to the fact that the o

Re: Programmatically adding dependencies to a MavenProject

2009-01-26 Thread Jason van Zyl
The alpha-2 will be released when we get the last couple issues done. As for the final release date, no idea yet. On 26-Jan-09, at 12:53 PM, Tom Huybrechts wrote: On Mon, Jan 26, 2009 at 9:23 PM, Maarten Storm wrote: Yes it is a bad idea to add add dependencies programatically, I had a RTF

Re: Programmatically adding dependencies to a MavenProject

2009-01-26 Thread Tom Huybrechts
On Mon, Jan 26, 2009 at 9:23 PM, Maarten Storm wrote: > Yes it is a bad idea to add add dependencies programatically, I had a > RTFM thing :-( . The Pom must be the project model in all cases. Oeps > and sorry for that. I fixed the issue by using the scope import stated > somewhere in the conversa

Re: Programmatically adding dependencies to a MavenProject

2009-01-26 Thread Maarten Storm
Yes it is a bad idea to add add dependencies programatically, I had a RTFM thing :-( . The Pom must be the project model in all cases. Oeps and sorry for that. I fixed the issue by using the scope import stated somewhere in the conversation. Maybe a stupid question when will Maven 3 be released? K

Re: [vote] release mercury-1.0.0-alpha-3

2009-01-26 Thread Hervé BOUTEMY
+1 Hervé Le samedi 24 janvier 2009, Oleg Gusakov a écrit : > I feel I owe an explanation about what was going with the release. As we > tried to refactor out jetty server code out of the transport provider, > we hit a few bumps on the road. But with the help from Jetty community, > who were kind

RE: Precedence of direct dependencies with equal conflict id

2009-01-26 Thread Brian E. Fox
It should be a validation error if we find duplicated entries. -Original Message- From: Shane Isbell [mailto:shane.isb...@gmail.com] Sent: Monday, January 26, 2009 1:58 PM To: Maven Developers List Subject: Re: Precedence of direct dependencies with equal conflict id We can support this

Re: Precedence of direct dependencies with equal conflict id

2009-01-26 Thread Shane Isbell
We can support this behavior in 3.x. PomTransformer.transformToModelProperties occurs before general inheritance. We could put the rule in there to remove the first dependency before we apply inheritance. Shane On Mon, Jan 26, 2009 at 10:51 AM, Benjamin Bentmann < benjamin.bentm...@udo.edu> wrote

Precedence of direct dependencies with equal conflict id

2009-01-26 Thread Benjamin Bentmann
Hi, Shane and I found some other oddity. Consider this POM snippet extracted from [0] that declares two direct dependencies on commons-collection but with different versions: commons-collections commons-collections 2.0 commons-collections common

Re: Programmatically adding dependencies to a MavenProject

2009-01-26 Thread Jason van Zyl
This is a bad idea and don't count on Maven 3.x supporting this because it makes determining what the dependencies are black magic. The dependency tree and visualization tools won't work. In Maven 3.x we are likely to make the dependency set immutable post resolution phase. I don't feel t

RE: [vote] release mercury-1.0.0-alpha-3

2009-01-26 Thread Brian E. Fox
+1 -Original Message- From: John Casey [mailto:jdca...@commonjava.org] Sent: Monday, January 26, 2009 11:25 AM To: Maven Developers List Subject: Re: [vote] release mercury-1.0.0-alpha-3 +1 Oleg Gusakov wrote: > I feel I owe an explanation about what was going with the release. As we >

Re: [vote] release mercury-1.0.0-alpha-3

2009-01-26 Thread John Casey
+1 Oleg Gusakov wrote: I feel I owe an explanation about what was going with the release. As we tried to refactor out jetty server code out of the transport provider, we hit a few bumps on the road. But with the help from Jetty community, who were kind enough to fix it and release jetty 6.1.15

Re: Programmatically adding dependencies to a MavenProject

2009-01-26 Thread Costin Caraivan
Maarten Storm-2 wrote: > > Hello all, > I would like to add programmatically dependencies to the MavenProject. > I have looked in the mail archives but I could not find info on this > topic.Is there a possible solution for this? > Kind regards, > Maarten Storm > Hello, I'm also interested by t