Thanks for that detailed post, but it's still not what I asked for :-(
I just finished the transition of ALL of the projects of a large international
bank from Ant to Maven. In parallell
what was initially about 70 more or less separate projects, that were assembled
to one huge monolithic applic
Wasn't the option to add dependencies programatically by a plugin removed in
3.3.9? At least this is causing quite some problems with my FLexmojos plugin :-(
Chris
Von: Thomas Broyer
Gesendet: Samstag, 9. Januar 2016 16:03
An: users@maven.apache.org; rwh
But yes ... it's exactly what I want ... a "replace-with" option. But with
exlucdes and includes I thought it should be possible to implement with the
least impact on the rest of the Maven ecosystem.
Chris
Von: Thomas Broyer
Gesendet: Samstag, 9. Januar
HI,
On 1/9/16 10:59 AM, Christofer Dutz wrote:
Everyone that has worked for a Bank knows you can't
> just go there and tell them what the standard is,
> cause they'll tell you what their standard is ;-)
Unfortunately true...
So in the end we prohibited (by maven plugin) providing the ver
I was not expecting that you could adopt our solution completely.
I does sound like you have a lot of it already incorporated into your
processes.
The aggregated POMs would probably fix your remaining issue with
exclusions and version conflicts and would be easy to add to your
existing practic
cy to "artifact-a" leave away
"half-apis:jms" and add "javax.jms:jms:1.1" instead.
Chris
Von: Karl Heinz Marbaise
Gesendet: Samstag, 9. Januar 2016 13:39
An: Maven Users List
Betreff: Re: AW: AW: AW: How to manage dependency &q
