Yes, that is what I'm looking for I think. I will give it a go in the
coming week.
On Sat, Dec 27, 2008 at 1:36 AM, Maarten Storm wrote:
> Yes I can add the dependencies using import (did not know that this
> was a scope...) and no, that is not possible since all the parent
> poms are poms that
Yes I can add the dependencies using import (did not know that this
was a scope...) and no, that is not possible since all the parent
poms are poms that have packaging pom, maven does not except these. I
try to fool Maven by adding a empty jar per pom and that worked, but
thats not the good way (f
On Dec 26, 2008, at 4:11 PM, Maarten Storm wrote:
Hello,
The reason why I would like to add dependencies programmaticaly is the
following: In my open source project I have 3 subprojects that do not
share the same parent pom. I'm working on a new packaging strategy
called dpom. This Dependency P
Can't you achieve this using the import scope? This would allow you to
declare the dependencyManagement of all your jars in one pom and effectively
import that into the projects that need it, thus synchronizing the
dependencies across them all.
On 12/26/08 7:11 PM, "Maarten Storm" wrote:
> Hell
Hello,
The reason why I would like to add dependencies programmaticaly is the
following: In my open source project I have 3 subprojects that do not
share the same parent pom. I'm working on a new packaging strategy
called dpom. This Dependency Pom is just like a normal pom but it
synchronized proje
My opinion :
- We have to follow what we promote (conventions more particularly).
- Our conventions can evolve, and we have to ensure that above all, they are
improving teams productivity (it's a too important problem in java before
others like consistency, readability and maintainability).
My 2 c
On 26-Dec-08, at 2:55 AM, Ralph Goers wrote:
On Dec 25, 2008, at 7:02 PM, Jason van Zyl wrote:
On 25-Dec-08, at 4:27 PM, Ralph Goers wrote:
Jason,
I'm surprised you don't remember this discussion since we've had
it so many times.
The only thing I wanted to make sure you weren't doi
From the Maven 1.x days where we did this and realized that if the
model of your dependencies not explicit in your pom.xml file then it's
not clear to anyone where dependencies are coming from and leads to
problems.
On 24-Dec-08, at 6:53 PM, Maarten Storm wrote:
Hello all,
I would like to
Hi,
2008/12/26 Vincent Siveton :
> Hi Oleg,
>
> 2008/12/25, Oleg Gusakov :
>> Vincent Siveton wrote:
>>
>> > Hi,
>> >
>> > 2008/12/24, Oleg Gusakov :
>> >
>> > [SNIP]
>> >
>> >
>> >
>> > > Can you name one single reason why moving this file away and creating 6
>> > > additional folders on the way
don't do that. Among other things it will mess up the IDE integration.
The project model shall be declarative.
Milos
On Fri, Dec 26, 2008 at 6:08 PM, Ralph Goers wrote:
> Under certain circumstances this could be done but I would need to
> understand the use case to tell you how.
>
> On Dec 24,
Hi Oleg,
2008/12/25, Oleg Gusakov :
> Vincent Siveton wrote:
>
> > Hi,
> >
> > 2008/12/24, Oleg Gusakov :
> >
> > [SNIP]
> >
> >
> >
> > > Can you name one single reason why moving this file away and creating 6
> > > additional folders on the way that would not exist otherwise is
> beneficial?
>
Under certain circumstances this could be done but I would need to
understand the use case to tell you how.
On Dec 24, 2008, at 3:53 PM, Maarten Storm wrote:
Hello all,
I would like to add programmatically dependencies to the MavenProject.
I have looked in the mail archives but I could not fi
lets say if "x.y.z.w" represents a path in a version tree, then specifying
"x.y.z.*" as dependency version should mean dependency resolution only
within the leafs of "z". my organization is not satisfied with linear
"ranges" for dependency resolution and they want a "tree-based" instead
(which to
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
-
To
> -Original Message-
> From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu]
> Sent: dinsdag 23 december 2008 17:29
> To: Maven Developers List
> Subject: Re: Invoking maven in a plugin?
>
> De Smet Ringo wrote:
>
> > What is the best way for a plugin to spawn Maven again in a
>
Ralph Goers wrote:
I understand what you are suggesting, although the example above
doesn't seem to match since the asm and platform tags are used outside
the scope.
Maybe because we understand the scope a little differently? For me scope
is just a name - it does not have any attributes. So
On Dec 25, 2008, at 6:08 PM, Oleg Gusakov wrote:
Ralph,
If we start walking this road - let's generalize starting from
existing model, so that it could still be a subset of the the
solution.
I'm fine with that.
more complex (or simple :) spec is:
qa
[2.0,3.0)
[!win,linux]
B
17 matches
Mail list logo
