Re: Transitive dependencies and version management

What you would do is that you specify the version of C in dependencyManagement of A. When you then build A, the specified version of C will be used regardless of what version is specified in B. However, for thsi to work in runtime this requires the specified version of C to be compatible with the v

Re: Transitive dependencies and version management

Have you considered using snapshot versions for C? If both A and B depend on a snapshot, they will automatically take the latest version in the repository. https://stackoverflow.com/questions/5901378/what-exactly-is-a-maven-snapshot-and-why-do-we-need-it#5901460 > On Aug 17, 2017, at 8:34 PM, H

Re: Transitive dependencies starting from WAR files

Have you considered using a tool like dependency-check-maven (see the dependency-check site for more details about the tool and see a sample report

Re: Transitive dependencies starting from WAR files

Hi, Maven-license-plugin would be a good candidate. I did'nt really understand what do you mean by "maven-dependency-plugin does not display War dependencies". How exacly are you using maven-dependency-plugin? On Tue, May 24, 2016 at 9:12 PM, Karl Heinz Marbaise wrote: > Hi Steve, > > > Why

Re: Transitive dependencies starting from WAR files

Hi Steve, Why not running maven-dependency-plugin it within the war package module than you get all dependencies which have been packaged into the war file ? Kind regards Karl Heinz Marbaise On 5/24/16 2:07 PM, Hostettler, Steve wrote: Hi, Our solutions is composed of different war files. I

Re: Transitive Dependencies for Unused Artifact

Hi Roy! Right seems this is my best candidate to centralize the versions used among different modules. Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Transitive-Dependencies-for-Unused-Artifact-tp5570805p5586942.html Sent from the Maven - Users mailing list archive at

Re: Transitive Dependencies for Unused Artifact

not declare it as a dependency but does define the version to be used when it find the dependency declared. Sent from my Blackberry. - Original Message - From: kdobrik To: users@maven.apache.org Sent: Mon Mar 19 09:06:03 2012 Subject: Re: Transitive Dependencies for Unused Artifact Thank

Re: Transitive Dependencies for Unused Artifact

. - Original Message - From: kdobrik To: users@maven.apache.org Sent: Mon Mar 19 09:06:03 2012 Subject: Re: Transitive Dependencies for Unused Artifact Thank you for the answer. I will revisit my question. At the end of the day I need to centralize the versions used among all modules

Re: Transitive Dependencies for Unused Artifact

Thank you for the answer. I will revisit my question. At the end of the day I need to centralize the versions used among all modules. Nevertheless these modules do not share all the jars needed. I need to refresh my Maven knowledge :) Once again thank you! -- View this message in context: http:/

Re: Transitive Dependencies for Unused Artifact

Exclude is your friend. When declaring ArtifactX as a dependency exclude log4j and include the version of log4j that you need as a dependency. As long as ArtifactX will work with your version of log4j, you are OK. Ron On 16/03/2012 6:11 AM, kdobrik wrote: Hi guys, I have the following use ca

Re: Transitive dependencies and snapshots

The newer snapshots look fine, so it looks like they fixed it. Post your POM somewhere and I'll try it the same thing you are. On Jun 20, 2010, at 10:07 AM, Laird Nelson wrote: > On Sat, Jun 19, 2010 at 7:35 PM, Jason van Zyl wrote: > >> Actually the POMs are only missing for the older snapsho

Re: Transitive dependencies and snapshots

On Sat, Jun 19, 2010 at 7:35 PM, Jason van Zyl wrote: > Actually the POMs are only missing for the older snapshots, the newer ones > have them. So if you've got snapshots turned off and you've been manually > getting new ones with -U then maybe you have one of the version without a > POM. Or the

Re: Transitive dependencies and snapshots

Actually the POMs are only missing for the older snapshots, the newer ones have them. So if you've got snapshots turned off and you've been manually getting new ones with -U then maybe you have one of the version without a POM. Or the metadata is no good and is pointing at one of the crap versio

Re: Transitive dependencies and snapshots

I'll help you find the problem. Look in https://repository.jboss.org/nexus/content/repositories/snapshots/org/drools/drools-compiler/5.1.0.SNAPSHOT/ What's missing? On Jun 19, 2010, at 7:12 PM, Laird Nelson wrote: > I hope someone can explain this to me. > > I have a project that depends on o

Re: Transitive Dependencies: Is the parent or child dependency the "nearest dependency"?

On 02/10/2009, at 1:24 PM, Robert Winch wrote: Is this expected behavior (I would hope that it should be consistent since Maven aims at providing consistent builds)? Is this a bug in Maven 2.2.1? Is this a bug in m2eclipse (Maven 3)? Does this question belong on m2eclipse mailing list instead

Re: Transitive Dependencies: Is the parent or child dependency the "nearest dependency"?

Thanks to both of you for your responses. I am aware that it is preferred to add the dependency as a direct dependency to avoid such conflicts (thank you for that suggestion). Sorry to keep this going, but I am still puzzled to what is causing the discrepancy and would like to get to the bottom of

Re: Transitive Dependencies: Is the parent or child dependency the "nearest dependency"?

Neither. The parent is merged into the child before any of this is considered. In other words, the effective-pom is produced before nearest wins is even remotely considered. That said, a given value in the child overrides one defined in the parentbut this doesn't have anything directly to do wi

Re: Transitive Dependencies: Is the parent or child dependency the "nearest dependency"?

If you care, you should add the one that you want to the dependencyManagement element of your POM rather than trying to workaround this. As for Maven itself, I would have expected parent to come first - but it's not as simple the first level being first, it's rather which is encountered f

Re: Transitive dependencies in multi-module projects

On Tue, Aug 26, 2008 at 6:37 AM, Trevor Harmon <[EMAIL PROTECTED]> wrote: > As I said, I want to be able to go to appA's directory and type: > > mvn compile > > Since Maven knows appA's dependencies, it should be able to figure out that > if a source file in libB is out-of-date, it should compile

Re: Transitive dependencies in multi-module projects

On Aug 25, 2008, at 7:25 PM, Wendy Smoak wrote: If you establish a parent pom, and list all five of your projects as , Maven will figure out what order to build them in, and compile the changed sources. Thanks for your suggestion, but unfortunately it does not accomplish my goal. Adding a pa

Re: Transitive dependencies in multi-module projects

On Mon, Aug 25, 2008 at 4:15 PM, Trevor Harmon <[EMAIL PROTECTED]> wrote: > I've been reading that modules are the solution to this problem. There's a > write-up about them here: > http://docs.codehaus.org/display/MAVENUSER/Multi-modules+projects > However, the solution in the write-up doesn't see

RE: transitive dependencies

There is an unpack goal that you can use to specify the ones you want, or the unpack-dependencies to unpack all transitive of the current project. Is it something else you're trying to do? -Original Message- From: Kallin Nagelberg [mailto:[EMAIL PROTECTED] Sent: Saturday, December 22, 200

RE: Transitive dependencies of artifacts with classifiers

Paul Gier wrote on Tuesday, March 20, 2007 4:40 PM: > How are transitive dependencies handled when the artifacts have a > non-default classifier? For example, I have the following dependency > tree: A -> B > B -> C > > Now let's say I want to build a jdk1.4 version of A. So I depend on > B-jdk1

Re: Transitive Dependencies

No this will not error out. Transitive dependencies are added to the compile classpath, so compilation will succeed. However, it is best practice to explicitly declare all direct dependencies for a project. Yes, it's true but I think it's interesting to have a plugin that analyze your project

Re: Transitive Dependencies

No this will not error out. Transitive dependencies are added to the compile classpath, so compilation will succeed. However, it is best practice to explicitly declare all direct dependencies for a project. I think the *typically* in your reference refers to just this case. Typically a project

Re: Transitive Dependencies

Hello, I encountered the trouble, too. But my solution was installing jta-1.0.1B by manual. If you don't want to depend on jta when you use hibernate as dependency, you may try the following scripts, org.hibernate hibernate 3.1.3

Re: Transitive dependencies in war-plugin.

Thanks! I was not aware of the But, wont it be great to just turn-off the t-dependency by a element. com-server com-server-ejb 1 ejb-client false Zarar Siddiqi wrote: > > If you are using the maven-war-plugin, you can use the > elements to

Re: Transitive dependencies in war-plugin.

Hi, Dmystery wrote: > > IS there a way to turn off transitive dependencies while packaging a war > file? > I want my ejb-client in the war-packaging but it brings along all the > ejb-client dependencies. I've searched enough on this forum but cant find > a solution. > > My webapp pom has a depe

Re: Transitive dependencies in war-plugin.

it was not relevant. I am just trying to find better ways to manage the build maintenance process for items like names and version numbers that can be easy for a muilti-module project. On 10/16/06, Zarar Siddiqi <[EMAIL PROTECTED]> wrote: How is that relevant to the problem? It's defined in

Re: Transitive dependencies in war-plugin.

How is that relevant to the problem? It's defined in a property file which I read in through a plugin and then store them as project properties. A different propertly file is read for different environments (development, production etc). Mick Knutson-4 wrote: > > Where did you define ${app.

Re: Transitive dependencies in war-plugin.

Where did you define ${app.name} at? On 10/16/06, Zarar Siddiqi <[EMAIL PROTECTED]> wrote: If you are using the maven-war-plugin, you can use the elements to exclude jars from your war. They will still appear in the work directory (where the war is assembled) but once your war is bundled up

Re: Transitive dependencies in war-plugin.

If you are using the maven-war-plugin, you can use the elements to exclude jars from your war. They will still appear in the work directory (where the war is assembled) but once your war is bundled up, they won't be there. You should also look at . http://maven.apache.org/plugins/maven-war-pl

Re: Transitive dependencies and duplicate jars....

ssage From: Wayne Fay <[EMAIL PROTECTED]> To: Maven Users List Sent: Wednesday, May 3, 2006 1:24:12 PM Subject: Re: Transitive dependencies and duplicate jars Quickest/easiest fix is probably to add those dependencies to your WAR pom with scope provided. Sounds like a possible bug... if a

Re: Transitive dependencies and duplicate jars....

Quickest/easiest fix is probably to add those dependencies to your WAR pom with scope provided. Sounds like a possible bug... if a dep is declared as scope provided, then I'd think its dependencies should also come in as provided. Are you saying these are instead coming in as compile scope, and b

Re: Transitive dependencies and duplicate jars....

On 5/3/06, Sean McNamara <[EMAIL PROTECTED]> wrote: I need to get rid of the duplicates in the WEB-INF/lib directory, but am not sure quite how to accomplish this. Can anyone provide some direction? http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencie

RE: transitive dependencies? [ dueme Frage]

:[EMAIL PROTECTED] Sent: 17 October 2005 10:36 To: Maven Users List Subject: Re: transitive dependencies? [ dueme Frage] Transitivity is a property of some relationships. I was exposed to this term in maths, but assume it has wider meaning. Baically a relationship is transitive if that

Re: transitive dependencies? [ dueme Frage]

Transitivity is a property of some relationships. I was exposed to this term in maths, but assume it has wider meaning. Baically a relationship is transitive if that ralationship behaves as follows: say A relates to B and B relates to C then if A relates to C the relationship is transitive. equ

Re: transitive dependencies? [ dueme Frage]

Dependency mechanism in m2 is explained here: http://maven.apache.org/maven2/dependency-mechanism.html Regards, mika Pilgrim, Peter wrote: > What are transitive dependencies ? > > -- > Peter Pilgrim :: J2EE Software Development > Operations/IT - Credit Suisse First Boston, > Floor 15, 5 Canada

Re: transitive dependencies? [ dueme Frage]

In maven 1.x, if your project depends on jar A and jar A itself requires jar B, you have to manually add dependency to jar B. In maven 2, dependencies are *transitive*, this means your project will automatically be dependent to jar B. Maven 2 includes version conflicts algorithm so that it