Re: Modifying classifiers of transitive dependencies

n them and load them into our private > repository. I am using a classifier to indicate the signed ones. For > example, signed. Those are pulled properly. > However, those dependencies have many transitive dependencies that are > signed as well, but not pulled. The reason is because in the

Modifying classifiers of transitive dependencies

ones. For example, signed. Those are pulled properly. However, those dependencies have many transitive dependencies that are signed as well, but not pulled. The reason is because in the original pom, they point to the unsigned ones. What is the best (maven) way to resolve this? I can simply ignore

Re: maven-shade-plugin: excluding transitive dependencies from shade jar but having them appear in the pom.xml for the shade jar?

> The aim is not to include Jackson and other classes from transitive > dependencies of Avro but that the pom file for the new jar would include > the transitive dependencies from Avro. > > My PR is at https://github.com/apache/hadoop-thirdparty/pull/21 > > Neither the pom.xml nor t

Re: maven-shade-plugin: excluding transitive dependencies from shade jar but having them appear in the pom.xml for the shade jar?

x27;m looking to shade Apache Avro jar, relocating the > avro classes to a new package name. > This new jar would be published to Maven Central and used by Hadoop. > The aim is not to include Jackson and other classes from transitive > dependencies of Avro but that the pom file f

maven-shade-plugin: excluding transitive dependencies from shade jar but having them appear in the pom.xml for the shade jar?

The aim is not to include Jackson and other classes from transitive dependencies of Avro but that the pom file for the new jar would include the transitive dependencies from Avro. My PR is at https://github.com/apache/hadoop-thirdparty/pull/21 Neither the pom.xml nor the dependency-reduced-pom.xm

Re: plexus-cipher missing from transitive dependencies of maven-core 3.8.2/3.8.3

Thanks (köszönöm) Tamás! Much appreciated for the PR, our dependencies were quite old as we haven't touched our plugin internals for ages. Thanks for being a maven community ambassador! Kind regards, Srdan On 2021/10/09 07:57:49, Tamás Cservenák wrote: > Zdravo Srdjane, > > Here is a PR that

Re: plexus-cipher missing from transitive dependencies of maven-core 3.8.2/3.8.3

Zdravo Srdjane, Here is a PR that does what you want: https://github.com/schrepfler/jira-maven-plugin/pull/178 With PR, plugins works okay with 3.8.3 but also 3.8.2. HTH Yamas On Fri, Oct 8, 2021 at 7:56 PM Srđan Šrepfler wrote: > Hi, > I too have a dependency on > org.apache.maven.plugin-tes

Re: plexus-cipher missing from transitive dependencies of maven-core 3.8.2/3.8.3

Hi, I too have a dependency on org.apache.maven.plugin-testing:maven-plugin-testing-harness:3.3.0 After upgrading the project's Maven dependencies to Maven 3.8.3 which addressed this issue I got this error message when running the tests 1) Error injecting constructor, java.lang.NoSuchMethodErro

Re: plexus-cipher missing from transitive dependencies of maven-core 3.8.2

Am 2021-08-18 um 22:13 schrieb Nils Breunese: Michael Osipov wrote: Please file an issue. I will add this to the known issues list then. Thanks for confirming this regression, I’ve filed it as a bug here: https://issues.apache.org/jira/browse/MNG-7219 Thanks, will take care soon. This one

Re: plexus-cipher missing from transitive dependencies of maven-core 3.8.2

Michael Osipov wrote: > Please file an issue. I will add this to the known issues list then. Thanks for confirming this regression, I’ve filed it as a bug here: https://issues.apache.org/jira/browse/MNG-7219 Nils. - To unsubsc

Re: plexus-cipher missing from transitive dependencies of maven-core 3.8.2

Am 2021-08-17 um 13:44 schrieb Nils Breunese: Hi, I have a project that uses org.apache.maven.plugin-testing:maven-plugin-testing-harness:3.3.0 for testing a Maven plugin. After upgrading the project’s Maven dependencies to Maven 3.8.2 I got this error message when running tests: Error

plexus-cipher missing from transitive dependencies of maven-core 3.8.2

Hi, I have a project that uses org.apache.maven.plugin-testing:maven-plugin-testing-harness:3.3.0 for testing a Maven plugin. After upgrading the project’s Maven dependencies to Maven 3.8.2 I got this error message when running tests: Error injecting: org.sonatype.plexus.components.sec.

optional dependency and its relationship to transitive dependencies requireing the same dependency

me grown aether resolution logic*). Now an argument could be made that as optionality was declared at A that it trumps transitive dependencies, but this is not in dependencyManangement - hence the surprise. I would also expect the only way to remove a transitive dependency that was in scope would be

Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

> >> ... > >> This works fine, however I have an issue with regards to these specific > >> JARs being present on the classpath during the build and runtime > >> depending on the I assign to them within the dependency > >> definition. > >>

Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

tion. >> If I mark the scope as 'runtime', the dependencies are added to the >> normal classpath which I do not want, as the purpose here is dynamic >> classloading via user input. >> On the other hand, if I define the dependency scope as 'provided' t

Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

lasspath during the build and runtime depending > on the I assign to them within the dependency definition. > If I mark the scope as 'runtime', the dependencies are added to the normal > classpath which I do not want, as the purpose here is dynamic classloading > via user inp

[Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory

es are added to the normal classpath which I do not want, as the purpose here is dynamic classloading via user input. On the other hand, if I define the dependency scope as 'provided' then no transitive dependencies are acquired hence I encounter java.lang.NoClassDefFoundError as although

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

Transitive dependencies and version management

Greetings, I was wondering if someone might be able to help with a Maven version management problem we've encountered. We have several interdependent, legacy Java projects, that have recently been re-cast as Maven projects. Now that we have the first iteration done, it's apparent that one salient

Spring Boot starter POMs misusing transitive dependencies

boot-starter-data-jpa dependency in your project, and you are good to go. The starters contain a lot of the dependencies that you need to get a project up and running quickly and with a consistent, supported set of managed transitive dependencies. >From this documentation and elsewhere it seem

Re: Excluding transitive dependencies of plugins

Any pointers please? Thanks Gaurav On Mon, Sep 19, 2016 at 5:51 PM, Gaurav Gupta wrote: > Hi, > > I have a use case where I need to exclude transitive dependency of a > plugin. > I am using following plugin > > org.codehaus.mojo > cobertura-maven-plugin > 2.7 > > This has transitive dependency

Excluding transitive dependencies of plugins

Hi, I have a use case where I need to exclude transitive dependency of a plugin. I am using following plugin org.codehaus.mojo cobertura-maven-plugin 2.7 This has transitive dependency on logback-classic. To exclude this dependency, I tried following two options 1. org.codehaus.

Re: Excluding all transitive dependencies

I declare the exclusion */*. However, the path from (b) causes all the transitive dependencies of (a) to reappear in dependency:tree under the top-level description of (a), not under b/a. > > -- > Mark Derricutt > http://www.theoryinpractice.net > http://www.chaliceofblood.net >

Re: Excluding all transitive dependencies

On 7 Sep 2016, at 4:16, Benson Margulies wrote: > In fact, I think I've seen it work. However, today, with Maven 3.3.9, > it seems to be having no effect with the declaration below. Can anyone > suggest a way to explain/fix/repair? That appears to work for me in 3.3.9/3.4.0-SNAPSHOT. No other de

Excluding all transitive dependencies

The doc describes: * * is supposed to work to exclude all transitive dependencies. In fact, I think I've seen it work. However, today, with Maven 3.3.9, it seems to be having no effect with the declaration

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

Transitive dependencies starting from WAR files

Hi, Our solutions is composed of different war files. I would like, starting from the released artifacts that we deliver to our customer, to generate a dependency list. The goal is to be able to present an exhaustive list of dependencies we are relying on along with their licenses. The org.apa

RE: Finding transitive dependencies imported into our code

ce you are interested in the second category, at least in my case, I don't remember having any issues with it Alejandro -Original Message- From: Ben Podgursky [mailto:bpodgur...@gmail.com] Sent: Friday, August 7, 2015 08:17 AM To: Maven Users List Subject: Re: Finding transitive depend

Re: Finding transitive dependencies imported into our code

+1 dependency:analyze seems to be the one. Le 7 août 2015 2:17 PM, "Ben Podgursky" a écrit : > I think you want mvn dependency:analyze -DfailOnWarning=true > > > https://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html#failOnWarning > > On Fri, Aug 7, 2015 at 4:38 AM, Russell Go

Re: Finding transitive dependencies imported into our code

On 7 August 2015 at 04:14, James Green wrote: > See in-line > > On 7 August 2015 at 12:05, Björn Raupach > wrote: > >> hi, >> >> > On 07 Aug 2015, at 12:33, James Green wrote: >> > >> > Hi, >> > >> > I want to know about any imports within our package base that are >> resolved >> > by a transiti

Re: Finding transitive dependencies imported into our code

You IDE should do that if it is Maven aware. Foe example, Eclipse/STS, which the m2e plugin built-in, gives you a view in the POM editor that shows the origin of the need for each dependency and shows the whole chain of transitive dependencies. It shows what versions of dependencies will be

Re: Finding transitive dependencies imported into our code

I think you want mvn dependency:analyze -DfailOnWarning=true https://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html#failOnWarning On Fri, Aug 7, 2015 at 4:38 AM, Russell Gold wrote: > mvn -X compile > > Look at the listing; it will show you all of the dependencies. > > > On

Re: Finding transitive dependencies imported into our code

mvn -X compile Look at the listing; it will show you all of the dependencies. > On Aug 7, 2015, at 7:14 AM, James Green wrote: > > See in-line > > On 7 August 2015 at 12:05, Björn Raupach > wrote: > >> hi, >> >>> On 07 Aug 2015, at 12:33, James Green wrote: >>> >>> Hi, >>> >>> I want to

Re: Finding transitive dependencies imported into our code

See in-line On 7 August 2015 at 12:05, Björn Raupach wrote: > hi, > > > On 07 Aug 2015, at 12:33, James Green wrote: > > > > Hi, > > > > I want to know about any imports within our package base that are > resolved > > by a transitive dependency. > > > > There must be a command or tool for this

Re: Finding transitive dependencies imported into our code

hi, > On 07 Aug 2015, at 12:33, James Green wrote: > > Hi, > > I want to know about any imports within our package base that are resolved > by a transitive dependency. > > There must be a command or tool for this - I'm not sure I've ever seen one > though? Maybe this helps: mvn dependency:res

Finding transitive dependencies imported into our code

Hi, I want to know about any imports within our package base that are resolved by a transitive dependency. There must be a command or tool for this - I'm not sure I've ever seen one though? This probably should form a report of warnings during the build... Thanks, James

Re: dependency:list -DincludeScope=compile lists compile scope for transitive dependencies of test scope items

in 2.8 or with my > understanding of dependency scope? > > I run "mvn dependency:list -DincludeScope=compile" and see items which > are transitive dependencies of "test" scope items. > > My project depends on "org.apache.httpcomponents

dependency:list -DincludeScope=compile lists compile scope for transitive dependencies of test scope items

Hi all, Do I have a problem with maven-dependency-plugin 2.8 or with my understanding of dependency scope? I run "mvn dependency:list -DincludeScope=compile" and see items which are transitive dependencies of "test" scope items. My project depends on "org.apache.http

Re: Copy an artifact with its transitive dependencies to a specified location

Mon, 3 Jun 2013 19:46:11 +0200, /Baptiste MATHUS/: From my understanding of your need you should use dependency:get and use destination parameter. Seems like, but the transitive dependencies get only downloaded to the local repository and not copied to the specified `destination`, as far as

Re: Copy an artifact with its transitive dependencies to a specified location

tamenkov" a écrit : > I want to copy an artifact with its transitive dependencies to a specified > location. The artifact is not a dependency of the project the given build > step would be part of. > > I've tried the "copy" goal of the maven-dependency-plugin [1

Copy an artifact with its transitive dependencies to a specified location

I want to copy an artifact with its transitive dependencies to a specified location. The artifact is not a dependency of the project the given build step would be part of. I've tried the "copy" goal of the maven-dependency-plugin [1], but it doesn't have a "trans

Re: How to publishing artifact including transitive dependencies

Hi, It depends on how you declared dependencies inside A pom to those other deps. If they are not declared optional, the short answer is yes: B, C and D will also be needed by people using A. But anyway, if your A project really uses B,C and D, that's gonna be impossible to use A without ClassNot

Recall: How to publishing artifact including transitive dependencies

Katpally, SriharshaReddy would like to recall the message, "How to publishing artifact including transitive dependencies".

Re: When to manage transitive dependencies

What do you mean by "plain dependency management"? At the end of the day, what else do you do to get dependencies available at runtime for dependencies not provided by your container? -- View this message in context: http://maven.40175.n5.nabble.com/When-to-manage-transitive-de

Re: When to manage transitive dependencies

it seems that "excludes" on > transitive dependencies should eliminate at least one of your problems. > > Ron > > > On 21/11/2012 6:07 PM, danehammer wrote: >> >> I have two uberjars that I build with the maven-shade-plugin, we'll call >> the

Re: When to manage transitive dependencies

It looks a bit complex for my taste but it seems that "excludes" on transitive dependencies should eliminate at least one of your problems. Ron On 21/11/2012 6:07 PM, danehammer wrote: I have two uberjars that I build with the maven-shade-plugin, we'll call them "batch&q

When to manage transitive dependencies

he road? I need the data processing jars to stay in sync of course, and that's easy. But when those jars dependencies (that is, my uberjars' transitive dependencies) intersect with the uberjar's runtime's dependencies, I can have issues. If a more concrete example helps here it

Re: How to exclude transitive dependencies from war?

st of file names and not packages. E.g. WEB-INF/lib/openwebbeans-*,WEB-INF/lib/myfaces-api-*, ... LieGrue, strub > > From: Vincent Latombe >To: Maven Users List >Sent: Friday, September 28, 2012 6:27 PM >Subject: Re: How to exclude transit

Re: How to exclude transitive dependencies from war?

ugins/maven-war-plugin/examples/war-manifest-guide.html > regarding how to set the dependency as optional, which seems like it > might be the right solution, as I want the full war in the current > project but when used as an ear dependency I want it to exclude a > dependency (and all its transi

Re: Best practice declaring transitive dependencies used only for test

Hi Gabriel, I typically have large projects with many modules. This requires some way to manage test dependencies and infrastructure. My approach is to have one (or for complex scenarios multiple) test module(s). This test module(s) contain test dependencies (junit, easymock, xmlunit, dbunit, etc.

Best practice declaring transitive dependencies used only for test

Hi: In my last web app, I have the following dependency problem: Declared the following dependency in my pom: struts2-spring-plugin:2.3.1.2 with runtime scope, which have a transitive dependency to struts2-core:2.3.1.2 (runtime), which have a transivite dependency with commons-io:2.0.1 (run

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

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

://maven.40175.n5.nabble.com/Transitive-Dependencies-for-Unused-Artifact-tp5570805p5577176.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For

Re: Transitive Dependencies for Unused Artifact

that in fact D and E do not need ArtifacX, but need log4jX? Thank you in advance, kdobri -- View this message in context: http://maven.40175.n5.nabble.com/Transitive-Dependencies-for-Unused-Artifact-tp5570805p5570805.html Sent from the Maven - Users mailing list archiv

Transitive Dependencies for Unused Artifact

tifacX into the parent POM? Do not forget that in fact D and E do not need ArtifacX, but need log4jX? Thank you in advance, kdobri -- View this message in context: http://maven.40175.n5.nabble.com/Transitive-Dependencies-for-Unused-Artifact-tp5570805p5570805.html Sent from the Maven - Users mailing

Re: How to ensure proper transitive dependencies

Hi Leon, Leon Rosenberg wrote: > On Thu, Feb 2, 2012 at 6:10 PM, Jörg Schaible > wrote: >> Leon Rosenberg wrote: >> >>> Hello, >>> >>> I have following question, I don't quite understand how to solve >>> properly. I have 3 projects, A,B and C. >>> A depends on B and C, and B depends on C. >>> >>

Re: How to ensure proper transitive dependencies

Am 02.02.2012 21:16 schrieb "Leon Rosenberg" : > > On Thu, Feb 2, 2012 at 6:10 PM, Jörg Schaible > wrote: > > Leon Rosenberg wrote: > > > >> Hello, > >> > >> I have following question, I don't quite understand how to solve > >> properly. I have 3 projects, A,B and C. > >> A depends on B and C, and

Re: How to ensure proper transitive dependencies

Hello Stephen, thanks for your reply, more inlined. On Thu, Feb 2, 2012 at 5:29 PM, Stephen Connolly wrote: > On 2 February 2012 16:17, Leon Rosenberg wrote: >> Hello, >> >> I have following question, I don't quite understand how to solve >> properly. I have 3 projects, A,B and C. >> A depends

RE: How to ensure proper transitive dependencies

Define what version of what transitive dependencies you want to use in the dep management section of the war project. > -Original Message- > From: Leon Rosenberg [mailto:rosenberg.l...@gmail.com] > Sent: Thursday, February 02, 2012 3:16 PM > To: Maven Users List > Subj

Re: How to ensure proper transitive dependencies

On Thu, Feb 2, 2012 at 6:10 PM, Jörg Schaible wrote: > Leon Rosenberg wrote: > >> Hello, >> >> I have following question, I don't quite understand how to solve >> properly. I have 3 projects, A,B and C. >> A depends on B and C, and B depends on C. >> >> A requires at least C version 1.06. However,

Re: How to ensure proper transitive dependencies

Leon Rosenberg wrote: > Hello, > > I have following question, I don't quite understand how to solve > properly. I have 3 projects, A,B and C. > A depends on B and C, and B depends on C. > > A requires at least C version 1.06. However, after a while C got a new > feature which is now used in B. S

Re: How to ensure proper transitive dependencies

On 2 February 2012 16:17, Leon Rosenberg wrote: > Hello, > > I have following question, I don't quite understand how to solve > properly. I have 3 projects, A,B and C. > A depends on B and C, and B depends on C. > > A requires at least C version 1.06. However, after a while C got a new > feature w

How to ensure proper transitive dependencies

Hello, I have following question, I don't quite understand how to solve properly. I have 3 projects, A,B and C. A depends on B and C, and B depends on C. A requires at least C version 1.06. However, after a while C got a new feature which is now used in B. So in my situation A contains: B version

Re: Restricting versions of transitive dependencies

Why? What problem are you actually trying to solve? It sounds like you know the right way to do it already but don't want to. Ron On 15/01/2012 12:12 PM, Stuart Sierra wrote: Hello, list! I have a project A that has a dependency on library B. Library B has a dependency on library C with a ver

Re: Restricting versions of transitive dependencies

Am 15.01.2012 18:13 schrieb "Stuart Sierra" : > > Hello, list! > > I have a project A that has a dependency on library B. Library B has a > dependency on library C with a version range like [2.1,3.0). I want to > pin library C to a specific version in my project A. But I also want > to declare, in

Restricting versions of transitive dependencies

Hello, list! I have a project A that has a dependency on library B. Library B has a dependency on library C with a version range like [2.1,3.0). I want to pin library C to a specific version in my project A. But I also want to declare, in the POM, that library C is not a *direct* dependency of my

Effective scope of transitive dependencies when taking type into consideration?

what I can gather from doing a "mvn dependency:tree" all transitive dependencies under project B is omitted in project A? Is that correct behaviour? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org

Re: About transitive dependencies

Why do you declare a test (scope) dependency to B if you call it at runtime? AFIK, B should not be used when you compile C since you declared a test (scope) dependency. -- Guillaume Le 11/09/2011 08:25, JVerstry a écrit : I came across an issue I raised on StackOverflow: http://stackoverflow.

About transitive dependencies

I came across an issue I raised on StackOverflow: http://stackoverflow.com/questions/7373105/noclassdeffounderror-org-junit-afterclass-during-annotation-processing/7375380#7375380 I have a library B having a compile dependency (i.e. scope) on A. I have a library C having a test dependency (i.e.

Re: dependency:copy and transitive dependencies of artifactItems

t;> Chris Burroughs wrote: >>> I assumed from the frequent references to transitive dependencies at >>> <http://maven.apache.org/plugins/maven-dependency-plugin/index.html>; >>> that dependency:copy supported transitive dependencies of artifactItems. >>&g

Re: dependency:copy and transitive dependencies of artifactItems

s of the filters to get the artifacts you need > > Chris Burroughs wrote: >> I assumed from the frequent references to transitive dependencies at >> <http://maven.apache.org/plugins/maven-dependency-plugin/index.html>; >> that dependency:copy supported transitive d

Runtime scope and transitive dependencies question (maybe maven-ear-plugin bug?)

The Maven documentation says<http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope> : > Each of the scopes (except for import) affects transitive dependencies in > different ways, as is demonstrated in the table below. If a dependency

Re: How to download transitive dependencies

2.1 provided thanks for reply, I would like to know if the above transitive dependencies would have been in section rather that of maven-utils-parent-1.0.pom. Should I expect dependency:go-offline to download them too, when I am running this goal on projectA's pom.xml (that

Re: How to download transitive dependencies

;        javax.servlet.jsp >        jsp-api >        2.1 >        provided >       >     >   > > > thanks for reply, I would like to know if the above transitive dependencies > would have been in section rather that > of maven-utils-parent-1.0.pom. Should I expec

Re: How to download transitive dependencies

2.5 provided javax.servlet.jsp jsp-api 2.1 provided thanks for reply, I would like to know if the above transitive dependencies would have been in section rather that of maven-utils-parent-1.0.pom. Should I expect

Re: How to download transitive dependencies

On Fri, 3 Dec 2010 17:39:23 +0530 amaresh mourya wrote: > No, running dependency:go-offline didn't do the job. It just downloads > plug-ins and immediate dependencies. It downloads all dependencies, these are not dependencies. > > And this maven-utils-parent-1.0.pom (in my local repository) has

Re: How to download transitive dependencies

om] > Sent: 03 December 2010 11:21 > To: Maven Users List > Subject: How to download transitive dependencies > > Hi All, > > I have a project(A) containing pom.xml and that have a dependency of > > ca.grimoire.maven > maven-utils-parent > 1.0 >

RE: How to download transitive dependencies

would dependency:go-offline work? Regards -Original Message- From: amaresh mourya [mailto:amaresh.mou...@gmail.com] Sent: 03 December 2010 11:21 To: Maven Users List Subject: How to download transitive dependencies Hi All, I have a project(A) containing pom.xml and that have a

How to download transitive dependencies

Hi All, I have a project(A) containing pom.xml and that have a dependency of ca.grimoire.maven maven-utils-parent 1.0 pom And this maven-utils-parent-1.0.pom (in my local repository) has few dependencies in . Is it possible to download these dependencies via some

Re: problem with transitive dependencies

I have set all those. but when I expand the maven dependencies. I do not see the webServiceClient.jar in it. any more suggestions? -- View this message in context: http://maven.40175.n5.nabble.com/problem-with-transitive-dependencies-tp3275330p3276360.html Sent from the Maven - Users mailing

Re: problem with transitive dependencies

In Project properties under Java Build Path do you see the Maven Dependencies entry in the libraries? Did you tell Eclipse that you wanted to use Maven Dependencies (Right click on the Project header => Maven=>Use Maven Dependencies (or something like that). Do you have the Maven integration p

problem with transitive dependencies

blindly and then compile it compiles successfully and I can also deploy and use the app with out any issues. Any idea on resolving the above problem Regards, B. Ravi Shankar -- View this message in context: http://maven.40175.n5.nabble.com/problem-with-transitive-dependencies-tp3275330p3275330

Differences in how m2 and m3 add transitive dependencies?

I have a module with a dependency on another module which included commons-lang as a dependency: If I use dependency:tree from that module using m2 I get (parts trimmed to keep things concise) [INFO] [dependency:tree {execution: default-cli}] [INFO] com.foo:foo:jar:48-SNAPSHOT [INFO] +- com.foo:fo

Re: WAR type and transitive dependencies

If your code depends on activation, then you want to list it. What if mail changes their dependencies, you would not have it in your compile. If you import it, you need to specify it. You don't want your IDE looking through the whole dependency tree to resolve each import. Maven is running

Re: WAR type and transitive dependencies

Greetings, On Mon, Aug 30, 2010 at 5:30 AM, Ognjen Blagojevic wrote: > For instance, if you define javax.mail in pom.xml: > > >  javax.mail >  mail >  1.4.2 >  provided > > > mvn dependency:tree shows also transitive depndecy javax.activation: > > [INFO] +- javax.mail:mail:jar:1.4.2:provided (s

Re: WAR type and transitive dependencies

On 24.8.2010 23:41, skatz wrote: Is there a way to, when building a war, have a jar and all its dependencies be part of the compile time path, but not be included in the war file itself, without having to list each one in the pom.xml? That is the way Maven should behave by default. For instanc

WAR type and transitive dependencies

ded in the war file itself, without having to list each one in the pom.xml? thanks, skatz -- View this message in context: http://maven.40175.n5.nabble.com/WAR-type-and-transitive-dependencies-tp2651850p2651850.html Sent from the Maven - Users mailing

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

the drools-compiler >> dependency, but it shows up in the tree without any of *its* dependencies. >> That is, no janino shows up. >> >> If I run mvn dependency:tree on drools-compiler itself, I can see the janino >> dependency, marked correctly as compile scope. >>

Re: Transitive dependencies and snapshots

f, I can see the janino > dependency, marked correctly as compile scope. > > If I drop the drools version back to 5.0.1 (a release version), then the > transitive dependencies show up fine. > > Since I'm quite familiar with and used to tra

Transitive dependencies and snapshots

I can see the janino dependency, marked correctly as compile scope. If I drop the drools version back to 5.0.1 (a release version), then the transitive dependencies show up fine. Since I'm quite familiar with and used to transitive dependencies, what's going on here? Best, Laird

Re: Is there a way to disable transitive dependencies?

> >> >> >> >> Thanks >> Sunil >> >> >> ronatartifact wrote: >> > >> > >> > You can use exclusions to cut out transitive dependencies. >> > >> > In the following example, we want our lms-facades pack

Re: Is there a way to disable transitive dependencies?

1 inside it. Is there a way? > > > group_of_needed_dependecny > needed_dependecny > 1.8.1 > > > ALL?? > ALL?? > > > > > Thanks > Sunil > > > ronatartifact wrote: > > > > > > You can use exclusions to cut out transitive de

Re: Exclude all transitive dependencies by version?

Sorry, should be "Your original config would NOT affect that". /Anders On Wed, May 19, 2010 at 15:32, Anders Hammar wrote: > The dependency plugin has nothing to do with Maven's dependency management, > which is what you want to controll. Your original config would affect that. > > /Anders > >

  1   2   3   4   5   >