Re: AW: AW: AW: How to manage dependency "includes"?

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

Re: AW: AW: How to manage dependency "includes"?

IIUC, what you really want is a "replace with" rule. Couldn't that be done by a plugin? You could then configure it in the parent POM and have it executed everywhere. Le sam. 9 janv. 2016 10:59, Christofer Dutz a écrit : > Thanks for that detailed post, but it's

AW: AW: AW: AW: How to manage dependency "includes"?

Well the maven-dependency-plugin has a goal "analyze-only" (https://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html) which reports dependencies, that are used, but not declared and that reports unused, but declared dependencies. We are simply using this. We had problems

Re: Combination of deployAtEnd and installAtEnd does not seem to work

Hi Alexander, On 1/9/16 2:13 PM, Alexander Kriegisch wrote: Hi community. This inquiry relates to [1] https://issues.apache.org/jira/browse/MRELEASE-664 [2] https://issues.apache.org/jira/browse/MDEPLOY-157 [3] https://issues.apache.org/jira/browse/MINSTALL-93 [4]

Re: AW: AW: AW: How to manage dependency "includes"?

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

Combination of deployAtEnd and installAtEnd does not seem to work

Hi community. This inquiry relates to [1] https://issues.apache.org/jira/browse/MRELEASE-664 [2] https://issues.apache.org/jira/browse/MDEPLOY-157 [3] https://issues.apache.org/jira/browse/MINSTALL-93 [4] https://issues.apache.org/jira/browse/MDEPLOY-168 where [2] and [3] are kinda

Re: How to manage dependency "includes"?

That is essentially what we do and was included in my earlier recommendation We use several projects to keep things organized and bit modular. It makes risk assessment a bit easier to know that projectA does not have a dependency on Tomcat, MySql or Hibernate so a change to the versions in the

Re: How to use 5 digit version numbers with Maven ?

in fact, the way the issue is described is misleading: "How to use 5 digit version numbers with Maven ?" and "Maven only handles 3 digit version numbers using the versions-maven-plugin" it should be phrased: "How to use 5 digit version numbers with versions-maven-plugin?" and

Re: How to manage dependency "includes"?

One solution would be to create a separate project that contains all the dependencies that work for all the applications. Deploy that project to the server such that all the dependency jars are deployed to a single lib directory (see

AW: AW: AW: How to manage dependency "includes"?

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