maven dependency issue (sqljdbc4.jar not picked up during junit test)
etc/ folder. - Once there (and without any pom dependency) it runs without any issues. Don't understand why this is a problem - other components I've worked on that connects to MS SQL Server 12 using sqljdbc4.jar (v4.0) works perfectly. Using sqljdbc4.jar as part of my pom dependency prevents the WEB-INF/test-web-application-context.xml to be resolved But by adding the sqljdbc4.jar to the JAVA_HOME/jre/lib/etc/ folder works! - Why Is this something linked to the v3.0 or...? Bottom line is that I don't want developers to be forced to tweak their local java environment like this where I would expect maven to sort the pom dependency, but it doesn't! The component is built using ... * jdk1.6.0_33 * apache-maven-3.0.4 * Junit 4.11 * spring 3.0.4.RELEASE * hibernate 3.5.6-Final - good @ being sucked @ -- View this message in context: http://maven.40175.n5.nabble.com/maven-dependency-issue-sqljdbc4-jar-not-picked-up-during-junit-test-tp5807497.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Java SSL dependency issue
woops wrong group, sorry On Mon, Aug 18, 2014 at 1:46 PM, james northrup wrote: > does anyone have select(), read, handshake, NIO code with sslengine to > draw from? > > the examples in the wild done to illustrate the sslengine never seem to > tie back to an actual fsm that could be made into something useful > > > On Mon, Aug 18, 2014 at 11:49 AM, Martin Gainty > wrote: > >> You should be able to locate the >> https://www.bouncycastle.org/latest_releases.html security jars you need >> from >> http://openjdk.java.net/groups/security >> >> what provider are you using? >> I recommend BouncyCastle >> https://www.bouncycastle.org/latest_releases.html >> >> Sounds like an interesting app..would like to hear more when you get a >> chance >> >> Martin Gainty >> ___ >> >> >> > From: joshualbai...@gmail.com >> > Subject: Java SSL dependency issue >> > Date: Thu, 7 Aug 2014 13:02:00 -0500 >> > To: users@maven.apache.org >> > >> > I have two branches of code. One compiles without a hitch, the other >> complains about this: >> > >> > Failed to execute goal >> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >> (default-compile) on project thebookgrove-catalog: Compilation failure: >> Compilation failure: >> > [ERROR] >> /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[40,23] >> package sun.security.ssl does not exist >> > [ERROR] >> /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[147,29] >> cannot find symbol >> > >> > I couldn't find any help with Google, so you are my last resort :( >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> >> > > > > -- > Jim Northrup * (408) 837-2270 * > -- Jim Northrup * (408) 837-2270 *
Re: Java SSL dependency issue
does anyone have select(), read, handshake, NIO code with sslengine to draw from? the examples in the wild done to illustrate the sslengine never seem to tie back to an actual fsm that could be made into something useful On Mon, Aug 18, 2014 at 11:49 AM, Martin Gainty wrote: > You should be able to locate the > https://www.bouncycastle.org/latest_releases.html security jars you need > from > http://openjdk.java.net/groups/security > > what provider are you using? > I recommend BouncyCastle > https://www.bouncycastle.org/latest_releases.html > > Sounds like an interesting app..would like to hear more when you get a > chance > > Martin Gainty > ___ > > > > From: joshualbai...@gmail.com > > Subject: Java SSL dependency issue > > Date: Thu, 7 Aug 2014 13:02:00 -0500 > > To: users@maven.apache.org > > > > I have two branches of code. One compiles without a hitch, the other > complains about this: > > > > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > (default-compile) on project thebookgrove-catalog: Compilation failure: > Compilation failure: > > [ERROR] > /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[40,23] > package sun.security.ssl does not exist > > [ERROR] > /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[147,29] > cannot find symbol > > > > I couldn't find any help with Google, so you are my last resort :( > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > -- Jim Northrup * (408) 837-2270 *
RE: Java SSL dependency issue
You should be able to locate the https://www.bouncycastle.org/latest_releases.html security jars you need from http://openjdk.java.net/groups/security what provider are you using? I recommend BouncyCastle https://www.bouncycastle.org/latest_releases.html Sounds like an interesting app..would like to hear more when you get a chance Martin Gainty ___ > From: joshualbai...@gmail.com > Subject: Java SSL dependency issue > Date: Thu, 7 Aug 2014 13:02:00 -0500 > To: users@maven.apache.org > > I have two branches of code. One compiles without a hitch, the other > complains about this: > > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > (default-compile) on project thebookgrove-catalog: Compilation failure: > Compilation failure: > [ERROR] > /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[40,23] > package sun.security.ssl does not exist > [ERROR] > /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[147,29] > cannot find symbol > > I couldn't find any help with Google, so you are my last resort :( > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: Java SSL dependency issue
On 8 August 2014 03:32, Joshua Bailey wrote: > I have two branches of code. One compiles without a hitch, the other > complains about this: > > Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > (default-compile) on project thebookgrove-catalog: Compilation failure: > Compilation failure: > [ERROR] > /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[40,23] > package sun.security.ssl does not exist > [ERROR] > /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[147,29] > cannot find symbol > > I couldn't find any help with Google, so you are my last resort :( Option 1) It's been a while since I tinkered in the security spaces but... Are you sure you should be using sun.* packages? These are normally internal implementation stuff. You should be using the java.* interfaces instead. (http://openjdk.java.net/groups/security/ sums this up - and http://docs.oracle.com/javase/7/docs/api/ doesn't like JavaDoc for sun.* stuff) Option 2) Guesses are that the two branches are using different environments. Run mvn -X on both branches piping output to a file. You can start with diff to see whether you get lucky and spot the problems. Otherwise, its a line by line comb to see what the differences are and whether these are the cause of your problems. Are you building with a non-Oracle jdk in the second branch - which obviously wont have the sun.* implementation stuff.
Java SSL dependency issue
I have two branches of code. One compiles without a hitch, the other complains about this: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project thebookgrove-catalog: Compilation failure: Compilation failure: [ERROR] /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[40,23] package sun.security.ssl does not exist [ERROR] /Users/joshua/Desktop/Data/TheBookGrove/Platform/thebookgrove-catalog/src/main/java/com/thebookgrove/catalog/InternetConnectionAgent.java:[147,29] cannot find symbol I couldn't find any help with Google, so you are my last resort :( - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [m2] yet another cyclic dependency issue
Thanks. Stephen Connolly wrote: create a generator-test module for testing the generator 2009/10/1 Adrian Herscu Hi all, (I already read all post regarding cyclic dependencies) My project has two modules: 1) generator -- depends on the "samples" for testing 2) sample -- depends on the "generator" for building I used to unpack the samples artifact into the target directory of the generator before running the generator's test. Any "clean" way out of this cyclic dependency? TIA, Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [m2] yet another cyclic dependency issue
create a generator-test module for testing the generator 2009/10/1 Adrian Herscu > Hi all, > > > (I already read all post regarding cyclic dependencies) > > My project has two modules: > 1) generator -- depends on the "samples" for testing > 2) sample -- depends on the "generator" for building > > I used to unpack the samples artifact into the target directory of the > generator before running the generator's test. > > Any "clean" way out of this cyclic dependency? > > TIA, > Adrian. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
[m2] yet another cyclic dependency issue
Hi all, (I already read all post regarding cyclic dependencies) My project has two modules: 1) generator -- depends on the "samples" for testing 2) sample -- depends on the "generator" for building I used to unpack the samples artifact into the target directory of the generator before running the generator's test. Any "clean" way out of this cyclic dependency? TIA, Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
tricky cyclic dependency issue ...
hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon at test scope) ProjectX-Core: main implementations (depends on API and also on TestCommon at test scope) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to clients of ProjectX and it also acts as single entry point for all test-scoped dependencies e.g. JUnit 4.x Now the problem is that while I need TestCommon for implementing the test suites in API and Core modules, TestCommon needs to depend on API and eventually on the Core module too. e.g. ProjectX-TestCommon defines a reusable AbstractTestSingleton to test Singleton types. ProjectX-API defines the ISingleton abstraction and also defines some concrete Singleton instances. AbstractTestSingleton that resides in ProjectX-TestCommon needs to depend on ProjectX-API and JUnit 4.x at the same time. Possibilities: - Moving AbstractTestSingleton to ProjectX-API is not possible because ProjectX-API should not depend on anything else, especially not on JUnit 4.x that AbstractTestSingleton requires (it extends TestCase) - Having module ProjectX-TestCommon depend on ProjectX-API does not work because ProjectX-API already depends on ProjectX-TestCommon (to test the concrete Singletons and more) and Maven reports a cyclic dependency. I tried many alternatives e.g. exclusion (excluding ProjectX-API when ProjectX-API declares dependency on ProjectX-TestCommon), changing scope to provided, etc. Any other ideas how to resolve this? TIA, Best regards, Giovanni - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
tricky cyclic dependency issue ...
hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon) ProjectX-Core: main implementations (depends on API and transitively on TestCommon) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to clients of ProjectX and it also acts as single entry point for all test-scoped dependencies e.g. JUnit 4.x Now the problem is that while I need TestCommon for implementing the test suites in API and Core modules, TestCommon needs to depend on API and eventually on the Core module too. e.g. ProjectX-TestCommon defines a reusable AbstractTestSingleton to test Singleton types. ProjectX-API defines the ISingleton abstraction and also defines some concrete Singleton instances. AbstractTestSingleton that resides in ProjectX-TestCommon needs to depend on ProjectX-API and JUnit 4.x at the same time. Possibilities: - Moving AbstractTestSingleton to ProjectX-API is not possible because ProjectX-API should not depend on anything else, especially not on JUnit 4.x that AbstractTestSingleton requires (it extends TestCase) - Having module ProjectX-TestCommon depend on ProjectX-API does not work because ProjectX-API already depends on ProjectX-TestCommon (to test the concrete Singletons and more) and Maven reports a cyclic dependency. I tried many alternatives e.g. exclusion (excluding ProjectX-API when ProjectX-API declares dependency on ProjectX-TestCommon), changing scope to provided, etc. Any other ideas how to resolve this? TIA, Best regards, Giovanni - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: tricky cyclic dependency issue ...
Move the concrete impls of your API interfaces into a seperate module. The only solution to cyclical dependencies is not to have them. Justin On Mar 25, 2009, at 8:21 AM, "Giovanni Azua" wrote: hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon at test scope) ProjectX-Core: main implementations (depends on API and also on TestCommon at test scope) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to clients of ProjectX and it also acts as single entry point for all test-scoped dependencies e.g. JUnit 4.x Now the problem is that while I need TestCommon for implementing the test suites in API and Core modules, TestCommon needs to depend on API and eventually on the Core module too. e.g. ProjectX-TestCommon defines a reusable AbstractTestSingleton to test Singleton types. ProjectX-API defines the ISingleton abstraction and also defines some concrete Singleton instances. AbstractTestSingleton that resides in ProjectX-TestCommon needs to depend on ProjectX-API and JUnit 4.x at the same time. Possibilities: - Moving AbstractTestSingleton to ProjectX-API is not possible because ProjectX-API should not depend on anything else, especially not on JUnit 4.x that AbstractTestSingleton requires (it extends TestCase) - Having module ProjectX-TestCommon depend on ProjectX-API does not work because ProjectX-API already depends on ProjectX-TestCommon (to test the concrete Singletons and more) and Maven reports a cyclic dependency. I tried many alternatives e.g. exclusion (excluding ProjectX-API when ProjectX-API declares dependency on ProjectX- TestCommon), changing scope to provided, etc. Any other ideas how to resolve this? TIA, Best regards, Giovanni - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
tricky cyclic dependency issue ...
hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon at test scope) ProjectX-Core: main implementations (depends on API and also on TestCommon at test scope) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to clients of ProjectX and it also acts as single entry point for all test-scoped dependencies e.g. JUnit 4.x Now the problem is that while I need TestCommon for implementing the test suites in API and Core modules, TestCommon needs to depend on API and eventually on the Core module too. e.g. ProjectX-TestCommon defines a reusable AbstractTestSingleton to test Singleton types. ProjectX-API defines the ISingleton abstraction and also defines some concrete Singleton instances. AbstractTestSingleton that resides in ProjectX-TestCommon needs to depend on ProjectX-API and JUnit 4.x at the same time. Possibilities: - Moving AbstractTestSingleton to ProjectX-API is not possible because ProjectX-API should not depend on anything else, especially not on JUnit 4.x that AbstractTestSingleton requires (it extends TestCase) - Having module ProjectX-TestCommon depend on ProjectX-API does not work because ProjectX-API already depends on ProjectX-TestCommon (to test the concrete Singletons and more) and Maven reports a cyclic dependency. I tried many alternatives e.g. exclusion (excluding ProjectX-API when ProjectX-API declares dependency on ProjectX-TestCommon), changing scope to provided, etc. Any other ideas how to resolve this? TIA, Best regards, Giovanni - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
tricky cyclic dependency issue
hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon at test scope) ProjectX-Core: main implementations (depends on API and also on TestCommon at test scope) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to clients of ProjectX and it also acts as single entry point for all test-scoped dependencies e.g. JUnit 4.x Now the problem is that while I need TestCommon for implementing the test suites in API and Core modules, TestCommon needs to depend on API and eventually on the Core module too. e.g. ProjectX-TestCommon defines a reusable AbstractTestSingleton to test Singleton types. ProjectX-API defines the ISingleton abstraction and also defines some concrete Singleton instances. AbstractTestSingleton that resides in ProjectX-TestCommon needs to depend on ProjectX-API and JUnit 4.x at the same time. Possibilities: - Moving AbstractTestSingleton to ProjectX-API is not possible because ProjectX-API should not depend on anything else, especially not on JUnit 4.x that AbstractTestSingleton requires (it extends TestCase) - Having module ProjectX-TestCommon depend on ProjectX-API does not work because ProjectX-API already depends on ProjectX-TestCommon (to test the concrete Singletons and more) and Maven reports a cyclic dependency. I tried many alternatives e.g. exclusion (excluding ProjectX-API when ProjectX-API declares dependency on ProjectX-TestCommon), changing scope to provided, etc. Any other ideas how to resolve this? TIA, Best regards, Giovanni -- View this message in context: http://www.nabble.com/tricky-cyclic-dependency-issue-tp22700195p22700195.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: POM dependency issue (Reactor)
Oh yeah, I forgot. Define two profiles, both active unless things say otherwise. Put parentPom1 as a module defined in profile 1 Put parentPom2 as a module defined in profile 2. If you do nothing, compiling bigParent will compile everything if you do mvn -Pprofile_1 then (as specifying an active profile deactivates all profiles that are active by default) you'd only compile common and parentPom1 2008/12/4 Wayne Fay <[EMAIL PROTECTED]> > > Can I configure my POM hierarchies in another way to be able to compile > ONLY > > parentPOM1 and common OR ONLY parentPOM2 and common > > Sure, with profiles. > > Wayne > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: POM dependency issue (Reactor)
Alternatively, you could do. cd common mvn install cd ../parentPOM1 mvn install 2008/12/4 Rusty Wright <[EMAIL PROTECTED]> > If you haven't looked at it yet, try this: > > http://books.sonatype.com/maven-book/reference/multimodule-web-spring.html > > > solo1970 wrote: > >> This is my dilemna, ca anyone shed some light? >> >> I have the following configuration of POMs >> >> bigparentPOM ---> common >> > parentPOM 1 (depends on common) >> > parentPOM 2 (depends on common) >> >> ParentPOM 1 and 2 are dependent on common, but sometimes they also need to >> be compiled separately. I I want to build only parentPOM1 and need to >> recompile common, how can I do it??? For now we have to recompile >> everything from bigparentPOM. >> >> Can I configure my POM hierarchies in another way to be able to compile >> ONLY >> parentPOM1 and common OR ONLY parentPOM2 and common >> >> Thanks in advance for your help >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: POM dependency issue (Reactor)
> Can I configure my POM hierarchies in another way to be able to compile ONLY > parentPOM1 and common OR ONLY parentPOM2 and common Sure, with profiles. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM dependency issue (Reactor)
If you haven't looked at it yet, try this: http://books.sonatype.com/maven-book/reference/multimodule-web-spring.html solo1970 wrote: This is my dilemna, ca anyone shed some light? I have the following configuration of POMs bigparentPOM ---> common > parentPOM 1 (depends on common) > parentPOM 2 (depends on common) ParentPOM 1 and 2 are dependent on common, but sometimes they also need to be compiled separately. I I want to build only parentPOM1 and need to recompile common, how can I do it??? For now we have to recompile everything from bigparentPOM. Can I configure my POM hierarchies in another way to be able to compile ONLY parentPOM1 and common OR ONLY parentPOM2 and common Thanks in advance for your help - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
POM dependency issue (Reactor)
This is my dilemna, ca anyone shed some light? I have the following configuration of POMs bigparentPOM ---> common > parentPOM 1 (depends on common) > parentPOM 2 (depends on common) ParentPOM 1 and 2 are dependent on common, but sometimes they also need to be compiled separately. I I want to build only parentPOM1 and need to recompile common, how can I do it??? For now we have to recompile everything from bigparentPOM. Can I configure my POM hierarchies in another way to be able to compile ONLY parentPOM1 and common OR ONLY parentPOM2 and common Thanks in advance for your help -- View this message in context: http://www.nabble.com/POM-dependency-issue-%28Reactor%29-tp20836626p20836626.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Weird Dependency Issue
Ah! I wondered what that "system" was all about. Thanks much! Mick Knutson wrote: You need to add it as a "System" dependency from where you have your JRE installed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Weird Dependency Issue
You need to add it as a "System" dependency from where you have your JRE installed. On Mon, Nov 24, 2008 at 3:08 PM, David C. Hicks <[EMAIL PROTECTED]> wrote: > A colleague was getting an unsatisfied dependency error. While helping him > debug the problem, I came across a really odd situation. The artifact in > question is: > > com.sun:tools:jar:1.5.0:system > > This jar is not in either of our repositories, yet when we execute Maven on > the command line we don't see this unsatisfied error. When I run "mvn > dependency:list" I can see that it is required - apparently by an > OpenSymphony artifact. > > How is it possible for this artifact to be a dependency (transitive or > otherwise) and not have been pulled into my local repository? > > Dave > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thank You… Mick Knutson BASE Logic, inc. (415) 685-4233 Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Vacation Rental: http://tahoe.baselogic.com coming soon: 866-BLiNC-411: (254-6241-1) ---
Weird Dependency Issue
A colleague was getting an unsatisfied dependency error. While helping him debug the problem, I came across a really odd situation. The artifact in question is: com.sun:tools:jar:1.5.0:system This jar is not in either of our repositories, yet when we execute Maven on the command line we don't see this unsatisfied error. When I run "mvn dependency:list" I can see that it is required - apparently by an OpenSymphony artifact. How is it possible for this artifact to be a dependency (transitive or otherwise) and not have been pulled into my local repository? Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency issue
Thanks Jeudy, I used this and it worked, but the only concern for me is that I have to traverse through all the transitive dependencies of all the dependencies and then I have to add exclusions for each. Regards, Shakun Jeudy, Guillaume wrote: Shakun, try using ... on one of them. mvn dependency:tree will give you details of all dependencies for your project. From: Shakun Gupta [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 6:30 AM To: Maven Users List Subject: Dependency issue Hi, I am using two dependencies, both are dependent upon apache-comons-collections, but of different versions. So, my final jar / war contains two versions of commons-collections, is there a way to stop this. Regards, Shakun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dependency issue
Shakun, try using ... on one of them. mvn dependency:tree will give you details of all dependencies for your project. From: Shakun Gupta [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 6:30 AM To: Maven Users List Subject: Dependency issue Hi, I am using two dependencies, both are dependent upon apache-comons-collections, but of different versions. So, my final jar / war contains two versions of commons-collections, is there a way to stop this. Regards, Shakun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependency issue
Hi, I am using two dependencies, both are dependent upon apache-comons-collections, but of different versions. So, my final jar / war contains two versions of commons-collections, is there a way to stop this. Regards, Shakun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: question about dependency issue in maven
hm this is weird, can you tell me which/ I'm very sure they all have poms. did you try to checkout the code? The url for this is svn co https://binbase.svn.sourceforge.net/svnroot/binbase/trunk/binbase binbase thx for your help. g. On Sun, Jul 13, 2008 at 4:55 AM, Siarhei Dudzin <[EMAIL PROTECTED]> wrote: > I didn't find pom's in some of your submodules... > > Siarhei > -- - gert wohlgemuth blog: http://berlinguyinca.blogspot.com/ work: http://fiehnlab.ucdavis.edu/staff/wohlgemuth - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: question about dependency issue in maven
I didn't find pom's in some of your submodules... Siarhei
question about dependency issue in maven
hello, I just got a short question about maven and depedencies. Basically I got a project with several sub projects which got more subprojects and so on. The exact structure can be seen here: http://binbase.fiehnlab.ucdavis.edu:8060/browse/BinBase/trunk/binbase including all the needed poms. Now my problem is if I build this project from the top path it keeps complaining that some projects are missing. Now if I go into the path of the missing modules and build + install them there and go back to the top module and start the build again everything works till it comes to another artifact and i have to repeat this step again. This error only happes for a couple of sub modules. hirachy of the artifacts in the project binbase -> binbase-core, pom is here: http://binbase.fiehnlab.ucdavis.edu:8060/browse/~raw,r=411/BinBase/trunk/binbase/binbase-core/pom.xml --->uctask --->sjp --->clusterservice --->bci <-- fails, pom is here: http://binbase.fiehnlab.ucdavis.edu:8060/browse/~raw,r=375/BinBase/trunk/binbase/binbase-core/bci/pom.xml --> bci-core --> bci-sar --> bci-ear --> ... --->bdi --->binbase <-- fails -->... -->... ->... my current workaround is a small script which looks like this: http://binbase.fiehnlab.ucdavis.edu:8060/browse/~raw,r=549/BinBase/trunk/binbase/build.sh and basically goes into the folders and executes the commands there. It is an uggly workaround. so anybody got an idea where the problem lays? thank you very much! -- - gert wohlgemuth blog: http://berlinguyinca.blogspot.com/ work: http://fiehnlab.ucdavis.edu/staff/wohlgemuth - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ojdbc Dependency Issue
I do want to point out that "14" is not the version of "ojdbc". It's the J2SE version that that jar supports; "classes12" is for java 1.2, ojdbc14 is for java 1.4, ojdbc5 and ojdbc 6 are for java 5 and 6 respectively. You should probably be referencing the jars as com.oracle ojdbc14 10.2.0.3.0 But as mentioned above you will need to deploy the jar to a repository that you control. Short of that is creating a simple batch / shell script that developers can run to install the jar to their local repositories. On Mon, Mar 10, 2008 at 12:12 PM, TJ Greenier <[EMAIL PROTECTED]> wrote: > I am trying to find the Oracle Ojdbc14.jar file in the maven repository so > that I can successfully add this as a dependency in my pom.xml. I have > searched online and through the archives and all references point to the > following: > > > ojdbc > ojdbc > 14 > > > However, when I browse the repo ( > http://repo1.maven.org/maven2/ojdbc/ojdbc/14/) the pom file exists, but not > the jar file. Likewise I considered using classes12.jar and found the same > problem. The pom file exists but there is no jar file. > > Am I going about this the right way? Does anyone know of a repository where > this file exists? I did use the install plugin to push the file locally, > but I want to simplify the process for my development team. Any thoughts > would be appreciated. > > Thanks, > TJ > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : Ojdbc Dependency Issue
Use com.oracle:ojdbc14: instead of ojdbc:ojdbc:14 because ojdbc14 is different according to your Oracke RDBMS version ___ Christophe DENEUX / Capgemini Sud / Méditerranée Technical Leader Tel: + 33 4 93 95 55 92 / www.capgemini.com <http://www.capgemini.com/> Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE Join the Collaborative Business Experience ___ Please consider the environment and do not print this email unless absolutely necessary. Capgemini encourages environmental awareness. De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Date: lun. 10/03/2008 17:18 À: Maven Users List Objet : Re: Ojdbc Dependency Issue TJ Greenier schrieb: > I am trying to find the Oracle Ojdbc14.jar file in the maven repository so > that I can successfully add this as a dependency in my pom.xml. I have > searched online and through the archives and all references point to the > following: > > > ojdbc > ojdbc > 14 > > > However, when I browse the repo ( > http://repo1.maven.org/maven2/ojdbc/ojdbc/14/) the pom file exists, but not > the jar file. Likewise I considered using classes12.jar and found the same > problem. The pom file exists but there is no jar file. > > Am I going about this the right way? Does anyone know of a repository where > this file exists? I did use the install plugin to push the file locally, > but I want to simplify the process for my development team. Any thoughts > would be appreciated. > The normal reason why there is a pom in the repo but no jar is because the jar has a license that does not permit it to be redistributed by anyone but the producer. I expect this is the case here, ie that it is not legal for the oracle jars to be distributed from the apache servers. In this situation, the only thing that can be done is to manually install the file into your own repository. But then at least the apache-provided pom gets downloaded so the maven metadata gets properly set up for you. You could try discussing this with your Oracle sales representative. Or move to an open-source database. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Ojdbc Dependency Issue
TJ Greenier schrieb: > I am trying to find the Oracle Ojdbc14.jar file in the maven repository so > that I can successfully add this as a dependency in my pom.xml. I have > searched online and through the archives and all references point to the > following: > > > ojdbc > ojdbc > 14 > > > However, when I browse the repo ( > http://repo1.maven.org/maven2/ojdbc/ojdbc/14/) the pom file exists, but not > the jar file. Likewise I considered using classes12.jar and found the same > problem. The pom file exists but there is no jar file. > > Am I going about this the right way? Does anyone know of a repository where > this file exists? I did use the install plugin to push the file locally, > but I want to simplify the process for my development team. Any thoughts > would be appreciated. > The normal reason why there is a pom in the repo but no jar is because the jar has a license that does not permit it to be redistributed by anyone but the producer. I expect this is the case here, ie that it is not legal for the oracle jars to be distributed from the apache servers. In this situation, the only thing that can be done is to manually install the file into your own repository. But then at least the apache-provided pom gets downloaded so the maven metadata gets properly set up for you. You could try discussing this with your Oracle sales representative. Or move to an open-source database. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ojdbc Dependency Issue
I am trying to find the Oracle Ojdbc14.jar file in the maven repository so that I can successfully add this as a dependency in my pom.xml. I have searched online and through the archives and all references point to the following: ojdbc ojdbc 14 However, when I browse the repo ( http://repo1.maven.org/maven2/ojdbc/ojdbc/14/) the pom file exists, but not the jar file. Likewise I considered using classes12.jar and found the same problem. The pom file exists but there is no jar file. Am I going about this the right way? Does anyone know of a repository where this file exists? I did use the install plugin to push the file locally, but I want to simplify the process for my development team. Any thoughts would be appreciated. Thanks, TJ
Re: [maven-release-plugin] release-prepare does not update parent-SNAPSHOT-dependency. issue?
Hi , have you already create a new issue in JIRA ??? Bye dhoffer wrote: > > I do/did understand you meant to say "release:prepare". > > I do however see this message when using 2.0.8 w/ release-plugin > 2.0-beta-7 and I do NOT have SNAPSHOT dependencies. What I do have are > dependencies using version ranges w/o SNAPSHOTS. I suspect I am getting > tripped up by the never-ending maven version range bugs. > > > Daniel Niklas wrote: >> >> Hi Dave, >> >> >> dhoffer wrote: >>> >>> Just wondering, did you figure this out? I too have this problem and I >>> don't have any snapshot dependencies parent or otherwise. >>> >> >> I wrongly wrote "release-perform", but in fact i talked about >> "release:prepare"! Sorry for the confusion! If you don't have any >> SNAPSHOT dependencies, you cannot have this problem, because this problem >> ist about resolving SNAPSHOT dependencies by the goal *release:prepare*. >> >> >> dhoffer wrote: >>> >>> I would like to know what was intended by this feature. I have never >>> seen it before 2.0-beta-7 and I can find no documentation of it. I >>> would go back and use 2.0-beta-6 but that does not work with maven 2.0.8 >>> if using version ranges. >>> >> You will see this feature when you run *release:prepare* and you have >> SNAPSHOT dependencies in your pom. The plugin then asks you: >> >> "There are still some remaining snapshot dependencies.: Do you want to >> resolve them now? (yes/no) no: : " >> >> Any other suggestions? >> >> Daniel >> >> >> >> > > -- View this message in context: http://www.nabble.com/-maven-release-plugin--release-perform-does-not-update-parent-SNAPSHOT-dependency.-issue--tp14917104s177p15268887.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven-release-plugin] release-prepare does not update parent-SNAPSHOT-dependency. issue?
I do/did understand you meant to say "release:prepare". I do however see this message when using 2.0.8 w/ release-plugin 2.0-beta-7 and I do NOT have SNAPSHOT dependencies. What I do have are dependencies using version ranges w/o SNAPSHOTS. I suspect I am getting tripped up by the never-ending maven version range bugs. Daniel Niklas wrote: > > Hi Dave, > > > dhoffer wrote: >> >> Just wondering, did you figure this out? I too have this problem and I >> don't have any snapshot dependencies parent or otherwise. >> > > I wrongly wrote "release-perform", but in fact i talked about > "release:prepare"! Sorry for the confusion! If you don't have any SNAPSHOT > dependencies, you cannot have this problem, because this problem ist about > resolving SNAPSHOT dependencies by the goal *release:prepare*. > > > dhoffer wrote: >> >> I would like to know what was intended by this feature. I have never >> seen it before 2.0-beta-7 and I can find no documentation of it. I would >> go back and use 2.0-beta-6 but that does not work with maven 2.0.8 if >> using version ranges. >> > You will see this feature when you run *release:prepare* and you have > SNAPSHOT dependencies in your pom. The plugin then asks you: > > "There are still some remaining snapshot dependencies.: Do you want to > resolve them now? (yes/no) no: : " > > Any other suggestions? > > Daniel > > > > -- View this message in context: http://www.nabble.com/-maven-release-plugin--release-perform-does-not-update-parent-SNAPSHOT-dependency.-issue--tp14917104s177p14996188.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven-release-plugin] release-prepare does not update parent-SNAPSHOT-dependency. issue?
Hi Dave, dhoffer wrote: > > Just wondering, did you figure this out? I too have this problem and I > don't have any snapshot dependencies parent or otherwise. > I wrongly wrote "release-perform", but in fact i talked about "release:prepare"! Sorry for the confusion! If you don't have any SNAPSHOT dependencies, you cannot have this problem, because this problem ist about resolving SNAPSHOT dependencies by the goal *release:prepare*. dhoffer wrote: > > I would like to know what was intended by this feature. I have never seen > it before 2.0-beta-7 and I can find no documentation of it. I would go > back and use 2.0-beta-6 but that does not work with maven 2.0.8 if using > version ranges. > You will see this feature when you run *release:prepare* and you have SNAPSHOT dependencies in your pom. The plugin then asks you: "There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : " Any other suggestions? Daniel -- View this message in context: http://www.nabble.com/-maven-release-plugin--release-perform-does-not-update-parent-SNAPSHOT-dependency.-issue--tp14917104s177p14994831.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven-release-plugin] release-perform does not update parent-SNAPSHOT-dependency. issue?
.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > de.continentale.vu.maven.plugins > maven-patch-plugin > > 1.0 > > maven-plugin > Ein Plugin zum Patchen von externen Jars. > Maven Patch Plugin > > > de.continentale.vu.common > main-pom > > 1-SNAPSHOT > > > ... > > > > > new pom in trunk > === > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > de.continentale.vu.maven.plugins > maven-patch-plugin > > 1.1-SNAPSHOT > > maven-plugin > Ein Plugin zum Patchen von externen Jars. > Maven Patch Plugin > > > de.continentale.vu.common > main-pom > 1-SNAPSHOT > > > ... > > > > > What is going wrong here? Is this a bug? > > Best regards and thanks in advance > Daniel Niklas > -- View this message in context: http://www.nabble.com/-maven-release-plugin--release-perform-does-not-update-parent-SNAPSHOT-dependency.-issue--tp14917104s177p14974142.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven-release-plugin] release-perform does not update parent-SNAPSHOT-dependency. issue?
u.maven.plugins maven-patch-plugin 1.1-SNAPSHOT maven-plugin Ein Plugin zum Patchen von externen Jars. Maven Patch Plugin de.continentale.vu.common main-pom 1-SNAPSHOT ... What is going wrong here? Is this a bug? Best regards and thanks in advance Daniel Niklas -- View this message in context: http://www.nabble.com/-maven-release-plugin--release-perform-does-not-update-parent-SNAPSHOT-dependency.-issue--tp14917104s177p14917104.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-har multiple module dependency issue
Hi, I am not entirely sure this is the correct mailing list to post on for this plugin. The net.sf.mavin-har seems to have no posts. But I will continue on with my problem anyway. If there is a better place please let me know! I have a multiple module project The first module contains my hibernate xml files and data java beans and packages as har. The second module defines my DAO classes. This module has a dependancy on data java beans with in the har and is defined in pom.xml. The first module compiles, packages and installs fine into my local repository. The problem is when the second modules attempts to compile test case it has a problem finding the packages and class defined in my har module. I get the following output from running mvn install package com.jaymen.vextor.database.pojo does not exist and build fails. I have noticed that if I change the packaging and dependency to use the jar instead it can compile and execute the test cases fine. I have goggled for an answer but can't seem to find a solution. I know this must be a fairly common issue and must have been encountered before, so I must be missing something. If you can point me in the right direction that would be very helpful. I have attached the pom.xml files I am current using. http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.jaymen.vextor vextor pom vextor 1.0-SNAPSHOT http://maven.apache.org vextor-database vextor-gui vextor-core vextor-struts http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> vextor com.jaymen.vextor 1.0-SNAPSHOT 4.0.0 com.jaymen.vextor.database vextor-database har 1.0-SNAPSHOT vextor-database postgresql postgresql 8.2-504.jdbc3 maven-antrun-plugin generate-sources run org.codehaus.mojo hibernate3-maven-plugin 2.0-alpha-2 true generate-sources hbm2java hbm2cfgxml jdbcconfiguration conf/jboss hbm2hbmxml src/main/resources jdbcconfiguration hbm2java src/main/java jdbcconfiguration /conf/maven/database.properties com.jaymen.vextor.database.pojo /conf/maven/hibernate.reveng.xml true false maven-compiler-plugin 1.4 1.4 net.sf.maven-har maven-har-plugin 1.0 true postgresql postgresql 8.2-504.jdbc3 org.hibernate hibernate-annotations 3.3.0.ga org.hibernate hibernate 3.2.5.ga commons-pool commons-pool 20030825.183949 http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> vextor com.jaymen.vextor 1.0-SNAPSHOT 4.0.0 com.jaymen.vextor.core vextor-core vextor-core 1.0-SNAPSHOT http://maven.apache.org junit junit 3.8.1 test commons-dbcp commons-dbcp 20030825.184428 org.springframework spring 2.0.2 org.springframework spring-mock 2.0.5 com.jaymen.vextor.database vextor-database 1.0-SNAPSHOT har - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven dependency issue
Hi We are using maven2.0.6. If i add some dependency for my war file then it would include all the dependencies on which this particular dependency is dependent but i don't require those dependencies. So could anyone please tell me how to get away from this issue. One thing that i can do is use the exclusion tag in the dependecy which would exclude those transitive dependencies. But the problem is my dependent jar is dependent upon so many other jars.Thats why i need some optimal solution for this problem. Regards Vishal.
Re: Dependency issue (war and jar) in multimodule project
Anand:
I can't really understand your "dependency". Why not configure dependency
like this:
test
child2
1.0-SNAPSHOT
And when you have dependency on war file, you should use
maven-warpath-plugin.
Thanks,
Juven
On Nov 27, 2007 4:51 PM, Anand Rathi <[EMAIL PROTECTED]> wrote:
> Yes. I have included war in dependency declaration. Below is
> a pom snapshot.
> * POM - START *
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> test
> child2
> 1.0-SNAPSHOT
> child2
> war
> child2
>
> test
> parent
> 1.0-SNAPSHOT
> ../parent/pom.xml
>
>
>
>
>src/main/resources
>
>
>src/main/java
> true
>
> **/*.properties
>
>
>
>
>
>
> src/test/resources
>
>
>**/*.properties
>**/*.xml
>
>
>
>
>
>org.apache.maven.plugins
>maven-jar-plugin
>2.1
>
>
>
> target/classes
> child2-1.0-SNAPSHOT
> target
>
> package
> Create JAR in project
>
> jar
>
>
>
>
>
>org.apache.maven.plugins
>maven-war-plugin
>2.0.2-SNAPSHOT
>
> false
>
>
>
> ${basedir}/src/main/config/torque
>
>
>**/*model
>
> WEB-INF/data
>
>
>
> ${basedir}/src/main/resources
>
>
>**/hibernate.properties
>
> WEB-INF/classes
>
>
>
> WEB-INF/classes/hibernate.properties
>
>
>
> validate
> copy jars
>
> exploded
>
>
>
>
>
>org.apache.maven.plugins
>maven-install-plugin
>2.2
>
>
>
> target/child2-1.0-SNAPSHOT.war
> default
> test
> child2
> 1.0-SNAPSHOT
> war
> true
>
> install
> install WAR in M2 repos
>
> install-file
>
>
>
>
> target/child2-1.0-SNAPSHOT.jar
> default
> test
> child2
> 1.0-SNAPSHOT
> jar
> true
>
> install
> install JAR in M2 repos
>
> install-file
>
>
>
>
>
>
>org.apache.maven.plugins
>maven-surefire-plugin
>2.3-SNAPSHOT
>
>
>
> true
>
>
>
> maven-clean-plugin
>
>
>
> ${basedir}/src/main/etc
>
>setup.properties
>*.tmp
>utils/**
>
> false
>
>
> ${basedir}/src/main/webapp/WEB-INF/classes
> false
>
>
> ${basedir}/src/main/java
>
> report.om.generation
>
>
>
>
>
>
>
>
>
>
> test
> child1
> 1.0-SNAPSHOT
> war
>
>
>
>
>
>org.apache.maven.plugins
>maven-surefire-report-plugin
>
>
>org.apache.maven.plugins
>maven-javadoc-plugin
>
> 128m
> 512m
>
>
>
>
>
>
> * POM - END *
>
> thanks,
> Anand
>
> - Original Message
> From: Wayne Fay <[EMAIL PROTECTED]>
> To: Maven Users List
> Sent: Tuesday, 27 November, 2007 12:32:13 PM
> Subject: Re: Dependency issue (war and jar) in multimodule project
>
> In your dependency declaration, did you include war for
> the child1 dep in the child2 pom? Or how are you declaring the
> dependency?
>
> Perhaps show us your pom(s).
>
> Wayne
>
> On 11/26/07, Anand Rathi <[EMAIL PROTECTED]> wrote:
> > Hi Juven,
> > I removed child1 jar dependency and only kept child1 war dependency but
> while building child2 project, it is still expanding child1 jar file instead
> of child1 war file. Also it is picking up 'child1-1.0-SNAPSHOT.jar' from
> 'child1\target' folder instead of repository. This is happening only in
> multi-module build environment. If I build child2 seperately, it is building
> successfully
Re: Dependency issue (war and jar) in multimodule project
Yes. I have included war in dependency declaration. Below is a pom
snapshot.
* POM - START *
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
test
child2
1.0-SNAPSHOT
child2
war
child2
test
parent
1.0-SNAPSHOT
../parent/pom.xml
src/main/resources
src/main/java
true
**/*.properties
src/test/resources
**/*.properties
**/*.xml
org.apache.maven.plugins
maven-jar-plugin
2.1
target/classes
child2-1.0-SNAPSHOT
target
package
Create JAR in project
jar
org.apache.maven.plugins
maven-war-plugin
2.0.2-SNAPSHOT
false
${basedir}/src/main/config/torque
**/*model
WEB-INF/data
${basedir}/src/main/resources
**/hibernate.properties
WEB-INF/classes
WEB-INF/classes/hibernate.properties
validate
copy jars
exploded
org.apache.maven.plugins
maven-install-plugin
2.2
target/child2-1.0-SNAPSHOT.war
default
test
child2
1.0-SNAPSHOT
war
true
install
install WAR in M2 repos
install-file
target/child2-1.0-SNAPSHOT.jar
default
test
child2
1.0-SNAPSHOT
jar
true
install
install JAR in M2 repos
install-file
org.apache.maven.plugins
maven-surefire-plugin
2.3-SNAPSHOT
true
maven-clean-plugin
${basedir}/src/main/etc
setup.properties
*.tmp
utils/**
false
${basedir}/src/main/webapp/WEB-INF/classes
false
${basedir}/src/main/java
report.om.generation
test
child1
1.0-SNAPSHOT
war
org.apache.maven.plugins
maven-surefire-report-plugin
org.apache.maven.plugins
maven-javadoc-plugin
128m
512m
* POM - END *
thanks,
Anand
- Original Message
From: Wayne Fay <[EMAIL PROTECTED]>
To: Maven Users List
Sent: Tuesday, 27 November, 2007 12:32:13 PM
Subject: Re: Dependency issue (war and jar) in multimodule project
In your dependency declaration, did you include war for
the child1 dep in the child2 pom? Or how are you declaring the
dependency?
Perhaps show us your pom(s).
Wayne
On 11/26/07, Anand Rathi <[EMAIL PROTECTED]> wrote:
> Hi Juven,
> I removed child1 jar dependency and only kept child1 war dependency but while
> building child2 project, it is still expanding child1 jar file instead of
> child1 war file. Also it is picking up 'child1-1.0-SNAPSHOT.jar' from
> 'child1\target' folder instead of repository. This is happening only in
> multi-module build environment. If I build child2 seperately, it is building
> successfully.
>
> Following message is shown in log:
> [DEBUG] Processing: child1-1.0-SNAPSHOT.war
> [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into
> D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT
>
> thanks,
> Anand
>
>
> - Original Message
> From: Juven Xu <[EMAIL PROTECTED]>
> To: Maven Users List
> Sent: Tuesday, 27 November, 2007 7:01:59 AM
> Subject: Re: Dependency issue (war and jar) in multimodule project
>
> Hi, Anand:
>
> If child2 has a dependency on child1 war, I think you don't need to make
> dependency on child1 jar. Cause all the xml file and class file will be
> inherited.
>
> Thanks,
> Juven
>
> On Nov 26, 2007 3:34 PM, Anand Rathi <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I have a multimodule project as shown below:
> > - parent (pom)
> >- child1 (war)
> >- child2 (war)
> >
> > child2 project has a dependency on child1 jar as well as war. This is
> > required because child1 war contains some xml files which I need at the
> > c
Re: Dependency issue (war and jar) in multimodule project
In your dependency declaration, did you include war for the child1 dep in the child2 pom? Or how are you declaring the dependency? Perhaps show us your pom(s). Wayne On 11/26/07, Anand Rathi <[EMAIL PROTECTED]> wrote: > Hi Juven, > I removed child1 jar dependency and only kept child1 war dependency but while > building child2 project, it is still expanding child1 jar file instead of > child1 war file. Also it is picking up 'child1-1.0-SNAPSHOT.jar' from > 'child1\target' folder instead of repository. This is happening only in > multi-module build environment. If I build child2 seperately, it is building > successfully. > > Following message is shown in log: > [DEBUG] Processing: child1-1.0-SNAPSHOT.war > [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into > D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT > > thanks, > Anand > > > - Original Message > From: Juven Xu <[EMAIL PROTECTED]> > To: Maven Users List > Sent: Tuesday, 27 November, 2007 7:01:59 AM > Subject: Re: Dependency issue (war and jar) in multimodule project > > Hi, Anand: > > If child2 has a dependency on child1 war, I think you don't need to make > dependency on child1 jar. Cause all the xml file and class file will be > inherited. > > Thanks, > Juven > > On Nov 26, 2007 3:34 PM, Anand Rathi <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I have a multimodule project as shown below: > > - parent (pom) > >- child1 (war) > >- child2 (war) > > > > child2 project has a dependency on child1 jar as well as war. This is > > required because child1 war contains some xml files which I need at the > > child2 war creation time. > > > > I am building this project from parent folder using 'mvn clean install' > > command. It builds child1 module successfully and installs jar as well as > > war in repository. > > > > But while building child2 module, it fails because while expanding war > > files, it is expanding child1 jar file instead of child1 war file. > > > > Following message shown in log file > > [DEBUG] Processing: child1-1.0-SNAPSHOT.war > > [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into > > D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT > > > > thanks, > > Anand > > > > > > Chat on a cool, new interface. No download required. Go to > > http://in.messenger.yahoo.com/webmessengerpromo.php > > > Download prohibited? No problem. CHAT from any browser, without > download. Go to http://in.messenger.yahoo.com/webmessengerpromo.php/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency issue (war and jar) in multimodule project
Hi Juven, I removed child1 jar dependency and only kept child1 war dependency but while building child2 project, it is still expanding child1 jar file instead of child1 war file. Also it is picking up 'child1-1.0-SNAPSHOT.jar' from 'child1\target' folder instead of repository. This is happening only in multi-module build environment. If I build child2 seperately, it is building successfully. Following message is shown in log: [DEBUG] Processing: child1-1.0-SNAPSHOT.war [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT thanks, Anand - Original Message From: Juven Xu <[EMAIL PROTECTED]> To: Maven Users List Sent: Tuesday, 27 November, 2007 7:01:59 AM Subject: Re: Dependency issue (war and jar) in multimodule project Hi, Anand: If child2 has a dependency on child1 war, I think you don't need to make dependency on child1 jar. Cause all the xml file and class file will be inherited. Thanks, Juven On Nov 26, 2007 3:34 PM, Anand Rathi <[EMAIL PROTECTED]> wrote: > Hi, > > I have a multimodule project as shown below: > - parent (pom) >- child1 (war) >- child2 (war) > > child2 project has a dependency on child1 jar as well as war. This is > required because child1 war contains some xml files which I need at the > child2 war creation time. > > I am building this project from parent folder using 'mvn clean install' > command. It builds child1 module successfully and installs jar as well as > war in repository. > > But while building child2 module, it fails because while expanding war > files, it is expanding child1 jar file instead of child1 war file. > > Following message shown in log file > [DEBUG] Processing: child1-1.0-SNAPSHOT.war > [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into > D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT > > thanks, > Anand > > > Chat on a cool, new interface. No download required. Go to > http://in.messenger.yahoo.com/webmessengerpromo.php Download prohibited? No problem. CHAT from any browser, without download. Go to http://in.messenger.yahoo.com/webmessengerpromo.php/
Re: Dependency issue (war and jar) in multimodule project
Hi, Anand: If child2 has a dependency on child1 war, I think you don't need to make dependency on child1 jar. Cause all the xml file and class file will be inherited. Thanks, Juven On Nov 26, 2007 3:34 PM, Anand Rathi <[EMAIL PROTECTED]> wrote: > Hi, > > I have a multimodule project as shown below: > - parent (pom) >- child1 (war) >- child2 (war) > > child2 project has a dependency on child1 jar as well as war. This is > required because child1 war contains some xml files which I need at the > child2 war creation time. > > I am building this project from parent folder using 'mvn clean install' > command. It builds child1 module successfully and installs jar as well as > war in repository. > > But while building child2 module, it fails because while expanding war > files, it is expanding child1 jar file instead of child1 war file. > > Following message shown in log file > [DEBUG] Processing: child1-1.0-SNAPSHOT.war > [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into > D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT > > thanks, > Anand > > > Chat on a cool, new interface. No download required. Go to > http://in.messenger.yahoo.com/webmessengerpromo.php
Dependency issue (war and jar) in multimodule project
Hi, I have a multimodule project as shown below: - parent (pom) - child1 (war) - child2 (war) child2 project has a dependency on child1 jar as well as war. This is required because child1 war contains some xml files which I need at the child2 war creation time. I am building this project from parent folder using 'mvn clean install' command. It builds child1 module successfully and installs jar as well as war in repository. But while building child2 module, it fails because while expanding war files, it is expanding child1 jar file instead of child1 war file. Following message shown in log file [DEBUG] Processing: child1-1.0-SNAPSHOT.war [INFO] Expanding: D:\temp\child1\target\child1-1.0-SNAPSHOT.jar into D:\temp\child2\target\war\work\child1-1.0-SNAPSHOT thanks, Anand Chat on a cool, new interface. No download required. Go to http://in.messenger.yahoo.com/webmessengerpromo.php
RE: [m2] Multi-project dependency issue
Thanks, I'll carry on looking for the weirdness. You've confirmed my
understanding of how it should work though.
I've done a build with -X - very verbose. I'll try to look through that
to see if it gives me any hints on the decisions being made.
Ian
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: 08 June 2007 17:37
> To: Maven Users List
> Subject: Re: [m2] Multi-project dependency issue
>
> Ian, you must be doing something weird/wrong, or you're doing
> something more complex than you're describing here, or you've
> got dependencies declared wrong. There are a lot of us doing
> exactly what you're describing with absolutely no problems at all.
>
> Tell us the packaging of the children and any plugins you're
> running during the compilation phase.
>
> Wayne
>
> On 6/8/07, Orford, Ian <[EMAIL PROTECTED]> wrote:
> > Yes to both.
> > Not only that, in the parent pom, the modules are listed in
> the order
> > I want them built - ie A,B,C,D
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Vandermeeren, Jo
> > > Sent: 08 June 2007 14:21
> > > To: Maven Users List
> > > Subject: Re: [m2] Multi-project dependency issue
> > >
> > > On 6/8/07, Orford, Ian <[EMAIL PROTECTED]> wrote:
> > > >
> > > > P is the parent POM that has modules A, B, C and D.
> > > > P defines A, B, C and D in A has P
> > > as a parent
> > > > and no dependencies at all.
> > > > B has P as a parent and defines A in C
> has P as a
> > > > parent and defines A and B in D has P as a
> > > parent and
> > > > defines C in
> > > >
> > > > Mvn install compiles A, then B. The trouble starts
> because it then
> > > > moves onto D. Since C hasn't been installed, it fails.
> > >
> > >
> > >
> > > Hi Ian,
> > >
> > > Are you building from the directory that contains the
> parent pom.xml?
> > > Are modules A,B,C,D listed as modules in the parent pom.xml?
> > >
> > > Cheers
> > > Jo
> > >
> >
> >
> > --
> > This e-mail is confidential and the information contained
> in it may be privileged. It should not be read, copied or
> used by anyone other than the intended recipient. If you
> have received it in error, please contact the sender
> immediately by telephoning +44 (0)20 7623 8000 or by return
> email, and delete the e-mail and do not disclose its contents
> to any person. We believe, but do not warrant, that this
> e-mail and any attachments are virus free, but you must take
> full responsibility for virus checking. Please refer to
> http://www.dresdnerkleinwort.com/disc/email/ and read our
> e-mail disclaimer statement and monitoring policy.
> >
> > Dresdner Kleinwort is the trading name of the investment
> banking division of Dresdner Bank AG, and operates through
> Dresdner Bank AG, Dresdner Kleinwort Limited, Dresdner
> Kleinwort Securities Limited and their affiliated or
> associated companies. Dresdner Bank AG is a company
> incorporated in Germany with limited liability and registered
> in England (registered no. FC007638, place of business 30
> Gresham Street, London EC2V 7PG), and is authorised by the
> German Federal Financial Supervisory Authority and by the
> Financial Services Authority ('FSA') and regulated by the FSA
> for the conduct of designated business in the UK. Dresdner
> Kleinwort Limited is a company incorporated in England
> (registered no. 551334, registered office 30 Gresham Street,
> London EC2V 7PG), and is authorised and regulated by the FSA.
> Dresdner Kleinwort Securities Limited is a company
> incorporated in England (registered no. 1767419, registered
> office 30 Gresham Street, London EC2V 7PG), and is authorised
> and regulated by the FSA.
> >
> >
> >
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient. If you have received it in error, please contact
Re: [m2] Multi-project dependency issue
Ian, you must be doing something weird/wrong, or you're doing
something more complex than you're describing here, or you've got
dependencies declared wrong. There are a lot of us doing exactly what
you're describing with absolutely no problems at all.
Tell us the packaging of the children and any plugins you're running
during the compilation phase.
Wayne
On 6/8/07, Orford, Ian <[EMAIL PROTECTED]> wrote:
Yes to both.
Not only that, in the parent pom, the modules are listed in the order I
want them built - ie A,B,C,D
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Vandermeeren, Jo
> Sent: 08 June 2007 14:21
> To: Maven Users List
> Subject: Re: [m2] Multi-project dependency issue
>
> On 6/8/07, Orford, Ian <[EMAIL PROTECTED]> wrote:
> >
> > P is the parent POM that has modules A, B, C and D.
> > P defines A, B, C and D in A has P
> as a parent
> > and no dependencies at all.
> > B has P as a parent and defines A in C has P as a
> > parent and defines A and B in D has P as a
> parent and
> > defines C in
> >
> > Mvn install compiles A, then B. The trouble starts because it then
> > moves onto D. Since C hasn't been installed, it fails.
>
>
>
> Hi Ian,
>
> Are you building from the directory that contains the parent pom.xml?
> Are modules A,B,C,D listed as modules in the parent pom.xml?
>
> Cheers
> Jo
>
--
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient. If you have received it in error, please contact the
sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and
delete the e-mail and do not disclose its contents to any person. We believe,
but do not warrant, that this e-mail and any attachments are virus free, but
you must take full responsibility for virus checking. Please refer to
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer
statement and monitoring policy.
Dresdner Kleinwort is the trading name of the investment banking division of
Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort
Limited, Dresdner Kleinwort Securities Limited and their affiliated or
associated companies. Dresdner Bank AG is a company incorporated in Germany
with limited liability and registered in England (registered no. FC007638,
place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the
German Federal Financial Supervisory Authority and by the Financial Services
Authority ('FSA') and regulated by the FSA for the conduct of designated
business in the UK. Dresdner Kleinwort Limited is a company incorporated in
England (registered no. 551334, registered office 30 Gresham Street, London
EC2V 7PG), and is authorised and regulated by the FSA. Dresdner Kleinwort
Securities Limited is a company incorporated in England (registered no.
1767419, registered office 30 Gresham Street, London EC2V 7PG), and is
authorised and regulated by the FSA.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Multi-project dependency issue
Yes to both.
Not only that, in the parent pom, the modules are listed in the order I
want them built - ie A,B,C,D
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Vandermeeren, Jo
> Sent: 08 June 2007 14:21
> To: Maven Users List
> Subject: Re: [m2] Multi-project dependency issue
>
> On 6/8/07, Orford, Ian <[EMAIL PROTECTED]> wrote:
> >
> > P is the parent POM that has modules A, B, C and D.
> > P defines A, B, C and D in A has P
> as a parent
> > and no dependencies at all.
> > B has P as a parent and defines A in C has P as a
> > parent and defines A and B in D has P as a
> parent and
> > defines C in
> >
> > Mvn install compiles A, then B. The trouble starts because it then
> > moves onto D. Since C hasn't been installed, it fails.
>
>
>
> Hi Ian,
>
> Are you building from the directory that contains the parent pom.xml?
> Are modules A,B,C,D listed as modules in the parent pom.xml?
>
> Cheers
> Jo
>
--
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient. If you have received it in error, please contact the
sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and
delete the e-mail and do not disclose its contents to any person. We believe,
but do not warrant, that this e-mail and any attachments are virus free, but
you must take full responsibility for virus checking. Please refer to
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer
statement and monitoring policy.
Dresdner Kleinwort is the trading name of the investment banking division of
Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort
Limited, Dresdner Kleinwort Securities Limited and their affiliated or
associated companies. Dresdner Bank AG is a company incorporated in Germany
with limited liability and registered in England (registered no. FC007638,
place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the
German Federal Financial Supervisory Authority and by the Financial Services
Authority ('FSA') and regulated by the FSA for the conduct of designated
business in the UK. Dresdner Kleinwort Limited is a company incorporated in
England (registered no. 551334, registered office 30 Gresham Street, London
EC2V 7PG), and is authorised and regulated by the FSA. Dresdner Kleinwort
Securities Limited is a company incorporated in England (registered no.
1767419, registered office 30 Gresham Street, London EC2V 7PG), and is
authorised and regulated by the FSA.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Multi-project dependency issue
On 6/8/07, Orford, Ian <[EMAIL PROTECTED]> wrote: P is the parent POM that has modules A, B, C and D. P defines A, B, C and D in A has P as a parent and no dependencies at all. B has P as a parent and defines A in C has P as a parent and defines A and B in D has P as a parent and defines C in Mvn install compiles A, then B. The trouble starts because it then moves onto D. Since C hasn't been installed, it fails. Hi Ian, Are you building from the directory that contains the parent pom.xml? Are modules A,B,C,D listed as modules in the parent pom.xml? Cheers Jo
[m2] Multi-project dependency issue
I'm using maven 2.0.6.
I have a multi-module project.
P is the parent POM that has modules A, B, C and D.
P defines A, B, C and D in
A has P as a parent and no dependencies at all.
B has P as a parent and defines A in
C has P as a parent and defines A and B in
D has P as a parent and defines C in
Mvn install compiles A, then B. The trouble starts because it then moves
onto D. Since C hasn't been installed, it fails.
Any gotchas in this area I should be aware of?
Thanks, Ian
--
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient. If you have received it in error, please contact the
sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and
delete the e-mail and do not disclose its contents to any person. We believe,
but do not warrant, that this e-mail and any attachments are virus free, but
you must take full responsibility for virus checking. Please refer to
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer
statement and monitoring policy.
Dresdner Kleinwort is the trading name of the investment banking division of
Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort
Limited, Dresdner Kleinwort Securities Limited and their affiliated or
associated companies. Dresdner Bank AG is a company incorporated in Germany
with limited liability and registered in England (registered no. FC007638,
place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the
German Federal Financial Supervisory Authority and by the Financial Services
Authority ('FSA') and regulated by the FSA for the conduct of designated
business in the UK. Dresdner Kleinwort Limited is a company incorporated in
England (registered no. 551334, registered office 30 Gresham Street, London
EC2V 7PG), and is authorised and regulated by the FSA. Dresdner Kleinwort
Securities Limited is a company incorporated in England (registered no.
1767419, registered office 30 Gresham Street, London EC2V 7PG), and is
authorised and regulated by the FSA.
RE: Maven 2.0 Classpath Dependency Issue
Wayne - Thank you very much - this worked well. You just saved me a lot of headaches :) Jim -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 1:26 PM To: Maven Users List Subject: Re: Maven 2.0 Classpath Dependency Issue I would move those dependencies to the project-level instead of plugin-level: Generally I don't attach dependencies to a plugin unless they are truly dependencies of the plugin itself... In this case, these are dependencies of the code, and as such should be moved to the project-level. Wayne On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote: > Sorry...that is a typo. I get the same error with compile or no tag. > > > > > -Original Message- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 18, 2006 12:57 PM > To: Maven Users List > Subject: Re: Maven 2.0 Classpath Dependency Issue > > On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote: > > I am new to Maven. I am trying to compile commons-discovery with JDK > > 1.5, but the dependent jars don't seem to be in my classpath. Here is > > my pom.xml: > ... > > compiler > > Unless that's a typo, it should either be 'compile' or just left out > entirely since 'compile' is the default scope. > > See: > http://maven.apache.org/guides/introduction/introduction-to-dependency-m > echanism.html > > -- > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0 Classpath Dependency Issue
I would move those dependencies to the project-level instead of plugin-level: Generally I don't attach dependencies to a plugin unless they are truly dependencies of the plugin itself... In this case, these are dependencies of the code, and as such should be moved to the project-level. Wayne On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote: Sorry...that is a typo. I get the same error with compile or no tag. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 12:57 PM To: Maven Users List Subject: Re: Maven 2.0 Classpath Dependency Issue On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote: > I am new to Maven. I am trying to compile commons-discovery with JDK > 1.5, but the dependent jars don't seem to be in my classpath. Here is > my pom.xml: ... > compiler Unless that's a typo, it should either be 'compile' or just left out entirely since 'compile' is the default scope. See: http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2.0 Classpath Dependency Issue
Sorry...that is a typo. I get the same error with compile or no tag. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 12:57 PM To: Maven Users List Subject: Re: Maven 2.0 Classpath Dependency Issue On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote: > I am new to Maven. I am trying to compile commons-discovery with JDK > 1.5, but the dependent jars don't seem to be in my classpath. Here is > my pom.xml: ... > compiler Unless that's a typo, it should either be 'compile' or just left out entirely since 'compile' is the default scope. See: http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0 Classpath Dependency Issue
On 10/18/06, Devine, James <[EMAIL PROTECTED]> wrote: I am new to Maven. I am trying to compile commons-discovery with JDK 1.5, but the dependent jars don't seem to be in my classpath. Here is my pom.xml: ... compiler Unless that's a typo, it should either be 'compile' or just left out entirely since 'compile' is the default scope. See: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2.0 Classpath Dependency Issue
I am new to Maven. I am trying to compile commons-discovery with JDK 1.5, but the dependent jars don't seem to be in my classpath. Here is my pom.xml: 4.0.0 org.apache.commons commons-discovery 0.2 C:\maven\commons-discovery-0.2-src\discovery\src\java org.apache.maven.plugins maven-compiler-plugin true C:\Java\1.5\jdk\bin\javac 1.5 1.5 commons-logging commons-logging 1.0.3 jar compiler junit junit 3.8.1 jar compiler The error I get is: [INFO] Compilation failure C:\maven\commons-discovery-0.2-src\discovery\src\java\org\apache\commons \discovery\tools\ClassUtils.java:[72,34] package org.apache.commons.logging does not exist This package is in commons-logging.1.0.3.jar. I can see that the jar is succesfully retrieved from http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.3/ but it is not in my classpath. What else do I need to do to get this into my compile classpath? Thank you, Jim
Re: test\resources dependency issue
Take a look here: http://maven.apache.org/guides/mini/guide-attached-tests.html You can deploy the tests (which include resources) for a model, then depend on that as well. On 8/18/06, Kapil Gupta(CT) <[EMAIL PROTECTED]> wrote: Hi, I have a multi module project with two modules A and B (depends on A). Can I use a resource (XML) file which is available in test\resources folder of module A while running test cases of module B? I receive FileNotFoundException on loading the XML from module B. I tried to use test scope instead of default compile while setting dependency on A in the pom of module B but without any luck. The problem goes away if I copy the resource file in the target\classes folder of module A instead of target\test-classes? Does it mean that target\test-classes folder is not added in classpath while building a multi-module project? Thanks Kapil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
test\resources dependency issue
Hi, I have a multi module project with two modules A and B (depends on A). Can I use a resource (XML) file which is available in test\resources folder of module A while running test cases of module B? I receive FileNotFoundException on loading the XML from module B. I tried to use test scope instead of default compile while setting dependency on A in the pom of module B but without any luck. The problem goes away if I copy the resource file in the target\classes folder of module A instead of target\test-classes? Does it mean that target\test-classes folder is not added in classpath while building a multi-module project? Thanks Kapil
RE: [m2] Need help with dependency issue + Eclipse Plugin + Displaytag + beanutils
It looks like the problem was that I was explicitly listing commnons-digester-1.5 as a dependency, and it appears to depend on beanutils-1.6. Removing that dependency (I think struts brings it in as well) fixed the problem. K.C. -Original Message- From: KC Baltz [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 26, 2006 10:01 AM To: Maven Users List (E-mail) Subject: [m2] Need help with dependency issue + Eclipse Plugin + Displaytag + beanutils I'm having a strange difficulty involving the Eclipse plugin, displaytag-1.1, and beanutils. The displaytag-1.1 tag library depends on beanutils 1.7. When I run: mvn -U -Dmaven.test.skip=true clean compile eclipse:clean eclipse:eclipse -Dwtpversion=1.0 -DdownloadSources=false it produces a .classpath for my web project that references beanutils-1.6 and not 1.7. However, if I then do a: mvn clean package I get commons-beanutils-1.7 and not 1.6 in the WEB-INF/lib directory of my generated webapp. Can someone help me resolve this discrepancy? K.C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Need help with dependency issue + Eclipse Plugin + Displaytag + beanutils
I'm having a strange difficulty involving the Eclipse plugin, displaytag-1.1, and beanutils. The displaytag-1.1 tag library depends on beanutils 1.7. When I run: mvn -U -Dmaven.test.skip=true clean compile eclipse:clean eclipse:eclipse -Dwtpversion=1.0 -DdownloadSources=false it produces a .classpath for my web project that references beanutils-1.6 and not 1.7. However, if I then do a: mvn clean package I get commons-beanutils-1.7 and not 1.6 in the WEB-INF/lib directory of my generated webapp. Can someone help me resolve this discrepancy? K.C.
