So if I back you up a bit, what is the problem you're actually trying to solve?
Put aside right now what Maven is doing and describe what you want ideally and
for what purpose? I can see the examples but I'm not sure what you're trying to
make easier and for who.
In Maven you've got a bunch of
Another possible solution would be to change the dependency versions in
the pom before deployment to the repository. So when you build
"yourproject" the pom is updated, maybe in the target directory, to
reflect the dependency versions that were used during the build, and the
imported depMgmt pom c
I should actually add that depMgmt actually happens at TWO levels in a
graph:
1. the top-level that enforces versions/scope/exclusions for the whole graph
2. the direct project (or parent) that declares the dependency to be managed
This makes sense, if you think about it: if you leave a versio
This is something I've seen in the wild in the past couple of weeks,
too. I had to mock it up and see it for myself before I believed the user.
Personally, option A makes the most sense to me. The reason is in
Geoffrey's third slide...I would expect MyProject to simply append the
dependency gr
Checking them out. It's not that I didn't agree with you the first time :-) It
really is a matter of how to introduce and not introduce any discrepancies in
behaviour. The general solution is to look at the dependencies of your final
runtime and constrain them in the depMgmt section that you con
On 19-05-13 17:18, Jason van Zyl wrote:
I can show you visually whats happening and it's not so much a bug (which I
think I explained to you when you showed me the slides initially) but the
current design.
I'd like to propose to review the current design.
Here are some idea's for an improved
On 19-05-13 17:05, Jason van Zyl wrote:
You have the POMs handy you made the slides from?
Yes :) Each puzzler in my presentation was tested out with this source code:
https://github.com/ge0ffrey/maven-dependency-puzzlers
That particular problem is in here:
https://github.com/ge0ffrey/maven-d
I can show you visually whats happening and it's not so much a bug (which I
think I explained to you when you showed me the slides initially) but the
current design.
On May 19, 2013, at 11:05 AM, Jason van Zyl wrote:
> You have the POMs handy you made the slides from?
>
> On May 17, 2013, at
You have the POMs handy you made the slides from?
On May 17, 2013, at 11:42 AM, Geoffrey De Smet wrote:
> I've always believed this is a bug, not a feature. I am still hoping to
> convince Jason etc of that.
>
> I talked about this last year already at Devoxx 2012 in my session "Maven
> depen
I've always believed this is a bug, not a feature. I am still hoping to
convince Jason etc of that.
I talked about this last year already at Devoxx 2012 in my session
"Maven dependency puzzlers".
I had several reactions that "this must be a bug".
Just look at 3 slides, and tell me maven 3.0.4
Yes when I analyzed the behavior, seeing it was here for long long time I
understood that it was probably done by design.
I had a look at our doc (
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management)
and we should probably detail more this be
This is how is was designed to work. Aether can do anything but the original
implementation is simply a map of GAs with a version preference. If the GA is
encountered then its version is overridden. This effectively gives you a target
platform like mechanism but is intended to be controlled from
On Tue, Apr 9, 2013 at 3:44 AM, Hervé BOUTEMY wrote:
> uh, really interesting case
>
I was sure you'll like it ;-)
>
> this gives me more interest in reimporting maven-aether-provider unit
> tests to
> reproduce and track the issue :)
>
>
+1
> I just tried the example, but the beta spring ar
uh, really interesting case
this gives me more interest in reimporting maven-aether-provider unit tests to
reproduce and track the issue :)
I just tried the example, but the beta spring artifact isn't in Spring: I
can't simply reproduce, will need to work more on it.
BTW, did you try with Mave
Hi all (and especially Herve, Jason and those who are working on Aether),
We are several to hit what we consider to be a bug but myself I don't
understand how we did to not see it before.
To be short the problem resides in depMgt usage. It is useful only in the
project you are building to enfo
15 matches
Mail list logo
