Re: Overriding the local repository
Use your settings.xml and add something like this: path to my local repository On 8/24/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On 8/24/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > > Is there a way to control what the local repository is? I've done > > some searching found -Dmaven.repo.local, but it doesn't work: > > It works for me. It's what I use to test 'does this build with a > clean local repo' to make sure all necessary dependencies are > available in a remote repo. > > > [INFO] > > > [ERROR] BUILD ERROR > > [INFO] > > > [INFO] Failed to resolve artifact. > > > > Missing: > > -- > > 1) org.codehaus.plexus:plexus-utils:jar:1.1 > > Strange, since it's right there: > http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/ > > In the build output, I don't see it downloading anything at all, as if > it can't connect to any remote repos. > > That it works if you don't specify a different local repo makes > sense-- it already has the artifacts in the local repo and doesn't > need to download them. > > (BTW, I opened MNG-3165 to publish the 2.0.7 reference docs. I'm ssh > key-less at the moment, haven't moved everything over to the new > laptop yet.) > > -- > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Overriding the local repository
On 8/24/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Is there a way to control what the local repository is? I've done > some searching found -Dmaven.repo.local, but it doesn't work: It works for me. It's what I use to test 'does this build with a clean local repo' to make sure all necessary dependencies are available in a remote repo. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > > Missing: > -- > 1) org.codehaus.plexus:plexus-utils:jar:1.1 Strange, since it's right there: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/ In the build output, I don't see it downloading anything at all, as if it can't connect to any remote repos. That it works if you don't specify a different local repo makes sense-- it already has the artifacts in the local repo and doesn't need to download them. (BTW, I opened MNG-3165 to publish the 2.0.7 reference docs. I'm ssh key-less at the moment, haven't moved everything over to the new laptop yet.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Copying a resource verse a dependency?
You could unpack that module. In the current snapshot 2.0-alpha-5-SNAPSHOT, you can filter the unpack so you could pull out only that one file and drop it where you need it. -Original Message- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Friday, August 24, 2007 8:32 PM To: maven Subject: [m2] Copying a resource verse a dependency? I am using the maven-dependency-plugin to copy dependencies for my module, I am wondering how I would copy a resource from once module to another? -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Copying a resource verse a dependency?
I am using the maven-dependency-plugin to copy dependencies for my module, I am wondering how I would copy a resource from once module to another? -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
RE: provided dependencies
I've never found that to be perfectly clear either. Would you mind filing a jira with a patch? -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Friday, August 24, 2007 2:35 PM To: Maven Users List Subject: Re: provided dependencies Hi, the description of the dependency scope table referenced below would be clearer (at least in my opinion) if it would read: "Each of the scopes affects transitive dependencies in different ways, as is demonstrated in the table below. If a dependency is set to the scope in the left column, __transitive dependencies of that dependency__ with the scope across the top row will result in a dependency in the main project with the scope listed at the intersection. If no scope is listed, it means the dependency will be omitted." So what is most probably happening is that you have declared another non-provided-scoped dependency (to commons-logging for example) which depends on the servlet-api non-transitively (see the pom of commons-logging [1]). Therefore the servlet-api gets pulled in though your direct dependency has scope provided. So as Tommy wrote your best chance is to use the dependency-plugin to print your dependency tree and see which other dependency depends on the servlet-api and then exclude it from that dependency. -Tim [1] http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1/common s-logging-1.1.pom DM schrieb: > Thanks for the reply. Maybe I'm not understanding the documentation correctly, but in the table of the "Dependency Scope" section of this page: > http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html > > it seems to say that a provided dependency is transitively provided, so doesn't that mean it still should not be copied to WEB-INF\lib? > > - Original Message > From: Tommy Knowlton <[EMAIL PROTECTED]> > To: Maven Users List > Sent: Friday, 24 August, 2007 1:29:38 PM > Subject: Re: provided dependencies > > > my guess would be that both modules depend transitively on the > javax.servlet in the runtime scope. > > but, since guessing is not likely to be very helpful, may I recommend > the maven-dependency-plugin, which can give you a report that may > help you to locate the actual dependency chain that ends up bringing > those in. Then, you should decide whether to use > elements in the declarations of those things that ended > up bringing it in. > > Hope that helps, > \Tommy > > On 24 Aug 2007, at 11:12 , DM wrote: > >> Hi, >> >> I have two maven modules, policy-core and policy-webapp. policy- >> webapp depends on policy-core, and they are packaged as a war and >> jar respectively. Both modules have the following dependency: >> >> >> javax.servlet >> servlet-api >> 2.3 >> provided >> >> >> When I package policy-webapp, I get both the following JARs in WEB- >> INF\lib >> >> servlet-api-2.5-6.0.1.jar >> servlet-api-2.3.jar >> >> Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase >> they should be provided by the container - this is why I set the >> scope to 'provided'. >> Both policy-core and policy-webapp extend the same POM, but their >> parent POM doesn't mention servlet-api, so I don't think this is >> particularly relevant. >> >> Any idea why these JARs are being copied to WEB-INF\lib and how I >> can prevent this? >> >> Thanks in Advance, >> DM >> >> >> ___ >> Yahoo! Answers - Got a question? Someone out there knows the >> answer. Try it >> now. >> http://uk.answers.yahoo.com/ >> >> - >> 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] > > > ___ > Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html > > - > 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 Version Issues
On 8/24/07, Mike Darretta <[EMAIL PROTECTED]> wrote: > I've tried all maven versions from 2.0.3 through 2.0.7. 2.0.6 and 7 > failed to build at all. 2.0.3-5 built but my EJBs failed to deploy. I > get this error message: > > javax.ejb.EJBException: RuntimeException; CausedByException is: > createBeanClassInstanceCommand == null It's less likely to be the version of Maven (which you didn't change) than one of the plugins that auto-updated. Unless you are specifying for every plugin, Maven will grab the latest plugin release when run with -U or if it can't find the plugin in your local repo. Can you get on irc? It's #maven on irc.codehaus.org, and there is a web interface here: http://irc.codehaus.org/ -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Version Issues
I've tried all maven versions from 2.0.3 through 2.0.7. 2.0.6 and 7 failed to build at all. 2.0.3-5 built but my EJBs failed to deploy. I get this error message: javax.ejb.EJBException: RuntimeException; CausedByException is: createBeanClassInstanceCommand == null Before I'm asked to consult the JBoss experts, know that no code changes were made to create this error. We have been successfully deploying EJBs using the current poms for two years. The only thing I can think of was that maven pulled in some new/updated libraries that are no longer compatible with my pom configurations. We are supposed to be beta testing for an early September release, so this strange thing has occurred at the most frustrating time. If anyone has any clues as to what may be happening (even guesses), please feel free to chime in. Thank you. Mike Darretta wrote: We are nearing deployment, but now I have found myself in a black hole trying to resolve version discrepancies with current vs. prior Maven builds. Starting on Tuesday, our build broke without any changes to the source code. The only suspect we have are updated libraries downloaded via Maven 2.0.2. I made a very slight modification to the poms that properly (I think) create the build. Now, our EJBs fail to deploy properly. I tried upgrading to Maven 2.0.7, but cannot build our EJBs at all (spec 2.0, using JBoss 3.2.5). I realize that much of our libraries are out of date, but the time constraints forbid us from making the many mods to get in sync with latest releases. My basic question is that does anyone know which post-2.0.2 version of Maven should be safe to use for building and deploying EJB 2.0 (specifically for JBoss 3.2.5). I will be downloading Maven 2.0.x incrementally and going through the task of building and deploying for each. Any help is appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike Darretta VRAM Project Lead Computer Sciences Corporation (CSC) (o) 831.656.4324 (c) 209.814.2774 [EMAIL PROTECTED] This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven insist to fetch sibling module from repository
On 8/24/07, Zarick Lau <[EMAIL PROTECTED]> wrote: > I know what 'install' mean in maven, but running mvn at the "parent" module > doesn't require "installing" all sub-module first. > > And indeed, [Off topic] if running "install" in each individual module > is pre-req, > even though I run mvn at "parent" module, it looks a little bit > strange for me... I haven't constructed an experiment to confirm with the latest version, but my experience has been that if you build from the top, Maven "knows" about all the sub-modules and can generally find and use the artifacts. If you drop into a subdirectory, it only "knows" about that module and the ones beneath it. And possibly the parent pom. But it won't know about sibling modules or their children, so it will try to resolve those from the repository. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven insist to fetch sibling module from repository
> > Can you paste the error message? > > I can reproduce the issue, if sub-module-b packaing == jar, no error. > My error occur only when packagin == ear... Do you happen to have assembly in there somewhere to? I have a similar error where an non-jar dependency (a zip file) is included in a module and when the non-jar dependency gets built it will fail because it cant find the artifact for the module that assembles. i.e. Root - A (depends on B in an assembly) - B (depends on nothing) When B builds it will give an error that the dependency A is not available (if it has not previously been installed) I haven't had the time to investigate these further, I believe it is an issue with reactor builds and incorrect resolution of dependencies. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Version Issues
We are nearing deployment, but now I have found myself in a black hole trying to resolve version discrepancies with current vs. prior Maven builds. Starting on Tuesday, our build broke without any changes to the source code. The only suspect we have are updated libraries downloaded via Maven 2.0.2. I made a very slight modification to the poms that properly (I think) create the build. Now, our EJBs fail to deploy properly. I tried upgrading to Maven 2.0.7, but cannot build our EJBs at all (spec 2.0, using JBoss 3.2.5). I realize that much of our libraries are out of date, but the time constraints forbid us from making the many mods to get in sync with latest releases. My basic question is that does anyone know which post-2.0.2 version of Maven should be safe to use for building and deploying EJB 2.0 (specifically for JBoss 3.2.5). I will be downloading Maven 2.0.x incrementally and going through the task of building and deploying for each. Any help is appreciated. -- Mike Darretta VRAM Project Lead Computer Sciences Corporation (CSC) (o) 831.656.4324 (c) 209.814.2774 [EMAIL PROTECTED] This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can maven 1.x run Junit 4 tests ?
Hi all, I want to include Junit4 unit tests for my project which uses maven 1.1. Currently, I am getting test failures when I try to run those with the following failure error - Testsuite: com.HibernateMappingsTest Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.328 sec Testcase: warning(junit.framework.TestSuite$1):FAILED No tests found in com.HibernateMappingsTest junit.framework.AssertionFailedError: No tests found in com.HibernateMappingsTest My project.xml includes the following plugin - maven-junit-report-plugin Is it possible to run junit4 tests in maven 1.1 ? If so, what plugin do I need to use or what configuration am I missing ? Please help.. thanks, manali
Specifying the jar name in profiles
I have two profiles that I am using. I'm trying to figure out if there is a way to make it so that when I package up a jar file I can specify the name of the jar file so that it is identifiable for that profile. TIA, Ben -- View this message in context: http://www.nabble.com/Specifying-the-jar-name-in-profiles-tf4325808s177.html#a12319940 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: provided dependencies
no, sorry, that was miscommunicated: try running it like this: mvn -U project-info-reports:dependencies ... should run the whole lifecycle, producing a target/site/ subdir that contains the relevant info. HTH, \Tommy On 24 Aug 2007, at 14:29 , DM wrote: Thanks for all the suggestions. So I can't download and install this plugin using the usual mvn commands (can't remember what they are)? - Original Message From: Tommy Knowlton <[EMAIL PROTECTED]> To: Maven Users List Sent: Friday, 24 August, 2007 4:03:26 PM Subject: Re: provided dependencies Wayne, I see what you mean. I'm wondering whether the maven- dependency-plugin has been changing lately, I seem to recall using a plugin some months ago (I thought I remembered it was maven- dependency-plugin, it looks like I was wrong) that generates a report that shows what deps were (transitively) included, and why... Aha, here it is: http://maven.apache.org/plugins/maven-project-info- reports-plugin/dependencies-mojo.html Sorry, it's in a different plugin than I earlier mentioned. \Tommy On 24 Aug 2007, at 12:39 , Wayne Fay wrote: Of course, since the tree mojo is not available in any released dependency version (yet), this means pulling the code down from SVN and "mvn install" locally or adding the Codehaus Snapshot repo to your pom... So hopefully you have some idea what you're doing. ;-) Wayne On 8/24/07, Tim Kettler <[EMAIL PROTECTED]> wrote: Hi, the description of the dependency scope table referenced below would be clearer (at least in my opinion) if it would read: "Each of the scopes affects transitive dependencies in different ways, as is demonstrated in the table below. If a dependency is set to the scope in the left column, __transitive dependencies of that dependency__ with the scope across the top row will result in a dependency in the main project with the scope listed at the intersection. If no scope is listed, it means the dependency will be omitted." So what is most probably happening is that you have declared another non-provided-scoped dependency (to commons-logging for example) which depends on the servlet-api non-transitively (see the pom of commons-logging [1]). Therefore the servlet-api gets pulled in though your direct dependency has scope provided. So as Tommy wrote your best chance is to use the dependency- plugin to print your dependency tree and see which other dependency depends on the servlet-api and then exclude it from that dependency. -Tim [1] http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1/ commons-logging-1.1.pom DM schrieb: Thanks for the reply. Maybe I'm not understanding the documentation correctly, but in the table of the "Dependency Scope" section of this page: http://maven.apache.org/guides/introduction/introduction-to- dependency-mechanism.html it seems to say that a provided dependency is transitively provided, so doesn't that mean it still should not be copied to WEB-INF\lib? - Original Message From: Tommy Knowlton <[EMAIL PROTECTED]> To: Maven Users List Sent: Friday, 24 August, 2007 1:29:38 PM Subject: Re: provided dependencies my guess would be that both modules depend transitively on the javax.servlet in the runtime scope. but, since guessing is not likely to be very helpful, may I recommend the maven-dependency-plugin, which can give you a report that may help you to locate the actual dependency chain that ends up bringing those in. Then, you should decide whether to use elements in the declarations of those things that ended up bringing it in. Hope that helps, \Tommy On 24 Aug 2007, at 11:12 , DM wrote: Hi, I have two maven modules, policy-core and policy-webapp. policy- webapp depends on policy-core, and they are packaged as a war and jar respectively. Both modules have the following dependency: javax.servlet servlet-api 2.3 provided When I package policy-webapp, I get both the following JARs in WEB- INF\lib servlet-api-2.5-6.0.1.jar servlet-api-2.3.jar Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase they should be provided by the container - this is why I set the scope to 'provided'. Both policy-core and policy-webapp extend the same POM, but their parent POM doesn't mention servlet-api, so I don't think this is particularly relevant. Any idea why these JARs are being copied to WEB-INF\lib and how I can prevent this? Thanks in Advance, DM ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ -- - -- 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: provided dependencies
Thanks for all the suggestions. So I can't download and install this plugin using the usual mvn commands (can't remember what they are)? - Original Message From: Tommy Knowlton <[EMAIL PROTECTED]> To: Maven Users List Sent: Friday, 24 August, 2007 4:03:26 PM Subject: Re: provided dependencies Wayne, I see what you mean. I'm wondering whether the maven- dependency-plugin has been changing lately, I seem to recall using a plugin some months ago (I thought I remembered it was maven- dependency-plugin, it looks like I was wrong) that generates a report that shows what deps were (transitively) included, and why... Aha, here it is: http://maven.apache.org/plugins/maven-project-info- reports-plugin/dependencies-mojo.html Sorry, it's in a different plugin than I earlier mentioned. \Tommy On 24 Aug 2007, at 12:39 , Wayne Fay wrote: > Of course, since the tree mojo is not available in any released > dependency version (yet), this means pulling the code down from SVN > and "mvn install" locally or adding the Codehaus Snapshot repo to your > pom... So hopefully you have some idea what you're doing. ;-) > > Wayne > > On 8/24/07, Tim Kettler <[EMAIL PROTECTED]> wrote: >> Hi, >> >> the description of the dependency scope table referenced below >> would be >> clearer (at least in my opinion) if it would read: >> >> "Each of the scopes affects transitive dependencies in different >> ways, >> as is demonstrated in the table below. If a dependency is set to the >> scope in the left column, __transitive dependencies of that >> dependency__ >> with the scope across the top row will result in a dependency in the >> main project with the scope listed at the intersection. If no >> scope is >> listed, it means the dependency will be omitted." >> >> So what is most probably happening is that you have declared another >> non-provided-scoped dependency (to commons-logging for example) which >> depends on the servlet-api non-transitively (see the pom of >> commons-logging [1]). Therefore the servlet-api gets pulled in though >> your direct dependency has scope provided. >> >> So as Tommy wrote your best chance is to use the dependency-plugin to >> print your dependency tree and see which other dependency depends >> on the >> servlet-api and then exclude it from that dependency. >> >> -Tim >> >> [1] >> http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1/ >> commons-logging-1.1.pom >> >> DM schrieb: >>> Thanks for the reply. Maybe I'm not understanding the >>> documentation correctly, but in the table of the "Dependency >>> Scope" section of this page: >>> http://maven.apache.org/guides/introduction/introduction-to- >>> dependency-mechanism.html >>> >>> it seems to say that a provided dependency is transitively >>> provided, so doesn't that mean it still should not be copied to >>> WEB-INF\lib? >>> >>> - Original Message >>> From: Tommy Knowlton <[EMAIL PROTECTED]> >>> To: Maven Users List >>> Sent: Friday, 24 August, 2007 1:29:38 PM >>> Subject: Re: provided dependencies >>> >>> >>> my guess would be that both modules depend transitively on the >>> javax.servlet in the runtime scope. >>> >>> but, since guessing is not likely to be very helpful, may I >>> recommend >>> the maven-dependency-plugin, which can give you a report that may >>> help you to locate the actual dependency chain that ends up bringing >>> those in. Then, you should decide whether to use >>> elements in the declarations of those things that >>> ended >>> up bringing it in. >>> >>> Hope that helps, >>> \Tommy >>> >>> On 24 Aug 2007, at 11:12 , DM wrote: >>> Hi, I have two maven modules, policy-core and policy-webapp. policy- webapp depends on policy-core, and they are packaged as a war and jar respectively. Both modules have the following dependency: javax.servlet servlet-api 2.3 provided When I package policy-webapp, I get both the following JARs in WEB- INF\lib servlet-api-2.5-6.0.1.jar servlet-api-2.3.jar Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase they should be provided by the container - this is why I set the scope to 'provided'. Both policy-core and policy-webapp extend the same POM, but their parent POM doesn't mention servlet-api, so I don't think this is particularly relevant. Any idea why these JARs are being copied to WEB-INF\lib and how I can prevent this? Thanks in Advance, DM ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: provided dependencies
Wayne, I see what you mean. I'm wondering whether the maven- dependency-plugin has been changing lately, I seem to recall using a plugin some months ago (I thought I remembered it was maven- dependency-plugin, it looks like I was wrong) that generates a report that shows what deps were (transitively) included, and why... Aha, here it is: http://maven.apache.org/plugins/maven-project-info- reports-plugin/dependencies-mojo.html Sorry, it's in a different plugin than I earlier mentioned. \Tommy On 24 Aug 2007, at 12:39 , Wayne Fay wrote: Of course, since the tree mojo is not available in any released dependency version (yet), this means pulling the code down from SVN and "mvn install" locally or adding the Codehaus Snapshot repo to your pom... So hopefully you have some idea what you're doing. ;-) Wayne On 8/24/07, Tim Kettler <[EMAIL PROTECTED]> wrote: Hi, the description of the dependency scope table referenced below would be clearer (at least in my opinion) if it would read: "Each of the scopes affects transitive dependencies in different ways, as is demonstrated in the table below. If a dependency is set to the scope in the left column, __transitive dependencies of that dependency__ with the scope across the top row will result in a dependency in the main project with the scope listed at the intersection. If no scope is listed, it means the dependency will be omitted." So what is most probably happening is that you have declared another non-provided-scoped dependency (to commons-logging for example) which depends on the servlet-api non-transitively (see the pom of commons-logging [1]). Therefore the servlet-api gets pulled in though your direct dependency has scope provided. So as Tommy wrote your best chance is to use the dependency-plugin to print your dependency tree and see which other dependency depends on the servlet-api and then exclude it from that dependency. -Tim [1] http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1/ commons-logging-1.1.pom DM schrieb: Thanks for the reply. Maybe I'm not understanding the documentation correctly, but in the table of the "Dependency Scope" section of this page: http://maven.apache.org/guides/introduction/introduction-to- dependency-mechanism.html it seems to say that a provided dependency is transitively provided, so doesn't that mean it still should not be copied to WEB-INF\lib? - Original Message From: Tommy Knowlton <[EMAIL PROTECTED]> To: Maven Users List Sent: Friday, 24 August, 2007 1:29:38 PM Subject: Re: provided dependencies my guess would be that both modules depend transitively on the javax.servlet in the runtime scope. but, since guessing is not likely to be very helpful, may I recommend the maven-dependency-plugin, which can give you a report that may help you to locate the actual dependency chain that ends up bringing those in. Then, you should decide whether to use elements in the declarations of those things that ended up bringing it in. Hope that helps, \Tommy On 24 Aug 2007, at 11:12 , DM wrote: Hi, I have two maven modules, policy-core and policy-webapp. policy- webapp depends on policy-core, and they are packaged as a war and jar respectively. Both modules have the following dependency: javax.servlet servlet-api 2.3 provided When I package policy-webapp, I get both the following JARs in WEB- INF\lib servlet-api-2.5-6.0.1.jar servlet-api-2.3.jar Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase they should be provided by the container - this is why I set the scope to 'provided'. Both policy-core and policy-webapp extend the same POM, but their parent POM doesn't mention servlet-api, so I don't think this is particularly relevant. Any idea why these JARs are being copied to WEB-INF\lib and how I can prevent this? Thanks in Advance, DM ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ --- -- 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] ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html - 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: provided dependencies
> So what is most probably happening is that you have declared another > non-provided-scoped dependency (to commons-logging for example) which > depends on the servlet-api non-transitively Preumably you mean "...which depende on the servlet-api non-providedly"? ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Overriding the local repository
Is there a way to control what the local repository is? I've done some searching found -Dmaven.repo.local, but it doesn't work: $ mvn install -Dmaven.repo.local=~/.m2/alt-repository [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Mediabank Liberte Master Project [INFO] MBCore [INFO] MBData [INFO] MBBusinessCore [INFO] MBCoreUI [INFO] MBComm [INFO] MBAnalogBusiness [INFO] MBLiberteBusiness [INFO] MBLiberteClient [INFO] MBLiberteServer [INFO] Mediabank Application Launcher [INFO] Mediabank QA Staging Downloading: http://mgdevsupport.mbxg.internal/maven-repository/org/apache/maven/wagon/wagon-ftp/1.0-beta-2/wagon-ftp-1.0-beta-2.pom Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ftp/1.0-beta-2/wagon-ftp-1.0-beta-2.pom Downloading: http://mgdevsupport.mbxg.internal/maven-repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom Downloading: http://mgdevsupport.mbxg.internal/maven-repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar Downloading: http://mgdevsupport.mbxg.internal/maven-repository/org/apache/maven/wagon/wagon-ftp/1.0-beta-2/wagon-ftp-1.0-beta-2.jar Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ftp/1.0-beta-2/wagon-ftp-1.0-beta-2.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.codehaus.plexus:plexus-utils:jar:1.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-utils \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-utils \ -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) com.mediabank.liberte:liberte-project:pom:1.0.0-SNAPSHOT 2) org.codehaus.plexus:plexus-utils:jar:1.1 2) org.apache.maven.wagon:wagon-ftp:jar:1.0-beta-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-ftp \ -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-ftp \ -Dversion=1.0-beta-2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) com.mediabank.liberte:liberte-project:pom:1.0.0-SNAPSHOT 2) org.apache.maven.wagon:wagon-ftp:jar:1.0-beta-2 -- 2 required artifacts are missing. for artifact: com.mediabank.liberte:liberte-project:pom:1.0.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), mgdevsupport (http://mgdevsupport.mbxg.internal/maven-repository) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Fri Aug 24 12:35:42 PDT 2007 [INFO] Final Memory: 1M/3M [INFO] ~/datatech-workspace/liberte $ The build works great if I don't specify a local repository (and it uses the default), but if I try to overrride that, Maven acts as if the remote artifacts were not available. This is Maven 2.0.7 on Mac OS X. -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Getting the source code for a dependency
Hi Alex, I know if you use the Eclipse plugin, you can put this in your parent pom: ... org.apache.maven.plugins maven-eclipse-plugin true true ... And then run "mvn eclipse:eclipse" (or don't add the plugin tag, and run "mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true"). Then you'll be able to see the source for those that can be found. Dave On 8/24/07, Alex Worden <[EMAIL PROTECTED]> wrote: > > Hi, > > Please can someone tell me if there is a way to ask Maven 2 to download > the > source code for a dependency... and if so, where will it put it? Also it > would be useful to know if there is any definitive way to determine which > dependency a referenced class comes from. For instance, I'm looking for > the > documentation on of: > > org.springframework.transaction.annotation.Transactional > > so I can read what the @Transactional annotation means > > My guess is that it is downloaded in the pom.xml config section: > > > org.springframework > spring-core > 2.0.1 > test > > > but.. there is no way of determining this. I can only guess that I have to > use a utility to trawl through all the jars in the .m2/repository to find > this class. > > That aside... my main question is this: Is there some xml element I can > add > to that will download the source code for this version of the > JAR? > > Many thanks, > > Alex >
Getting the source code for a dependency
Hi, Please can someone tell me if there is a way to ask Maven 2 to download the source code for a dependency... and if so, where will it put it? Also it would be useful to know if there is any definitive way to determine which dependency a referenced class comes from. For instance, I'm looking for the documentation on of: org.springframework.transaction.annotation.Transactional so I can read what the @Transactional annotation means My guess is that it is downloaded in the pom.xml config section: org.springframework spring-core 2.0.1 test but.. there is no way of determining this. I can only guess that I have to use a utility to trawl through all the jars in the .m2/repository to find this class. That aside... my main question is this: Is there some xml element I can add to that will download the source code for this version of the JAR? Many thanks, Alex
Child poms and eclipse projects
Hi - I have the following flat project layout: workspace/parent-proj/pom.xml workspace/child1/pom.xml (artifactId = child-project-1) workspace/child2/pom.xml (artifactId = childProject2) workspace/child3/pom.xml etc. When I run mvn eclipse:eclipse on the parent-proj, it writes out the project files properly, with one exception: it's using the artifactId as the project directory name for each artifact. So say child1 depends on artifactId childProject2, but the directory that artifact is in is actually child2. Well the eclipse .project file has a reference to childProject1. Is there any way to tell the plugin to use the correct directory name, or am I forced to always use the same directory name as the artifactId? I can do the latter, but it's not very practical - I'd rather configure the eclipse plugin in the parent pom or something. The Eclipse projects are inconsistently named, but I want to keep the artifactIds consistent. With the incorrect directory name, Eclipse shows errors in the Problems tab and won't recompile during debug sessions etc. as a result. Thanks in advance. Dave
Re: Filesystem Users, Groups and Permissions
Ok, i'll look at doing that. For the record i've got it all working ok now. There was a couple of extra things i had to do to get it working on tomcat (6.x), the nastiest was upgrading to redback-xwork-integration-1.0-alpha-3-20070816.220359-1.jar to fix the login issue when running under tomcat which essentially makes it completely unusable since you can never gain access to the repository through http. I also just found that the file\directory permissions are set in your maven settings.xml config in the definition. One thing which has me a bit perplexed is that when using the proxy connectors sometimes a build fails if it needs a new artifact not yet in the repository however on the next run it works fine. Cam On 8/24/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 8/24/07, Cameron Jones <[EMAIL PROTECTED]> wrote: > > > I've got archiva installed under tomcat and running as a tomcat user. > > We've had multiple reports of problems running Archiva on Tomcat, if > you've got it working, please share your setup and tips here: > http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat > > (Or just post to the list if that's easier and someone can update the page.) > > > Is there a way to get tomcat to write files under a different user or > > group, or set the permissions on the new files? I've got a few things > > running under tomcat so i don't really want to provide full access to > > the repository but i'm not sure if there is any way of doing this. > > Not that I know of... I'd probably give Archiva its own Tomcat > instance with separate permissions. > > -- > Wendy >
Re: provided dependencies
Of course, since the tree mojo is not available in any released dependency version (yet), this means pulling the code down from SVN and "mvn install" locally or adding the Codehaus Snapshot repo to your pom... So hopefully you have some idea what you're doing. ;-) Wayne On 8/24/07, Tim Kettler <[EMAIL PROTECTED]> wrote: > Hi, > > the description of the dependency scope table referenced below would be > clearer (at least in my opinion) if it would read: > > "Each of the scopes affects transitive dependencies in different ways, > as is demonstrated in the table below. If a dependency is set to the > scope in the left column, __transitive dependencies of that dependency__ > with the scope across the top row will result in a dependency in the > main project with the scope listed at the intersection. If no scope is > listed, it means the dependency will be omitted." > > So what is most probably happening is that you have declared another > non-provided-scoped dependency (to commons-logging for example) which > depends on the servlet-api non-transitively (see the pom of > commons-logging [1]). Therefore the servlet-api gets pulled in though > your direct dependency has scope provided. > > So as Tommy wrote your best chance is to use the dependency-plugin to > print your dependency tree and see which other dependency depends on the > servlet-api and then exclude it from that dependency. > > -Tim > > [1] > http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1/commons-logging-1.1.pom > > DM schrieb: > > Thanks for the reply. Maybe I'm not understanding the documentation > > correctly, but in the table of the "Dependency Scope" section of this page: > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > > > it seems to say that a provided dependency is transitively provided, so > > doesn't that mean it still should not be copied to WEB-INF\lib? > > > > - Original Message > > From: Tommy Knowlton <[EMAIL PROTECTED]> > > To: Maven Users List > > Sent: Friday, 24 August, 2007 1:29:38 PM > > Subject: Re: provided dependencies > > > > > > my guess would be that both modules depend transitively on the > > javax.servlet in the runtime scope. > > > > but, since guessing is not likely to be very helpful, may I recommend > > the maven-dependency-plugin, which can give you a report that may > > help you to locate the actual dependency chain that ends up bringing > > those in. Then, you should decide whether to use > > elements in the declarations of those things that ended > > up bringing it in. > > > > Hope that helps, > > \Tommy > > > > On 24 Aug 2007, at 11:12 , DM wrote: > > > >> Hi, > >> > >> I have two maven modules, policy-core and policy-webapp. policy- > >> webapp depends on policy-core, and they are packaged as a war and > >> jar respectively. Both modules have the following dependency: > >> > >> > >> javax.servlet > >> servlet-api > >> 2.3 > >> provided > >> > >> > >> When I package policy-webapp, I get both the following JARs in WEB- > >> INF\lib > >> > >> servlet-api-2.5-6.0.1.jar > >> servlet-api-2.3.jar > >> > >> Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase > >> they should be provided by the container - this is why I set the > >> scope to 'provided'. > >> Both policy-core and policy-webapp extend the same POM, but their > >> parent POM doesn't mention servlet-api, so I don't think this is > >> particularly relevant. > >> > >> Any idea why these JARs are being copied to WEB-INF\lib and how I > >> can prevent this? > >> > >> Thanks in Advance, > >> DM > >> > >> > >> ___ > >> Yahoo! Answers - Got a question? Someone out there knows the > >> answer. Try it > >> now. > >> http://uk.answers.yahoo.com/ > >> > >> - > >> 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] > > > > > > ___ > > Want ideas for reducing your carbon footprint? Visit Yahoo! For Good > > http://uk.promotions.yahoo.com/forgood/environment.html > > > > - > > 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: provided dependencies
Hi, the description of the dependency scope table referenced below would be clearer (at least in my opinion) if it would read: "Each of the scopes affects transitive dependencies in different ways, as is demonstrated in the table below. If a dependency is set to the scope in the left column, __transitive dependencies of that dependency__ with the scope across the top row will result in a dependency in the main project with the scope listed at the intersection. If no scope is listed, it means the dependency will be omitted." So what is most probably happening is that you have declared another non-provided-scoped dependency (to commons-logging for example) which depends on the servlet-api non-transitively (see the pom of commons-logging [1]). Therefore the servlet-api gets pulled in though your direct dependency has scope provided. So as Tommy wrote your best chance is to use the dependency-plugin to print your dependency tree and see which other dependency depends on the servlet-api and then exclude it from that dependency. -Tim [1] http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1/commons-logging-1.1.pom DM schrieb: Thanks for the reply. Maybe I'm not understanding the documentation correctly, but in the table of the "Dependency Scope" section of this page: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html it seems to say that a provided dependency is transitively provided, so doesn't that mean it still should not be copied to WEB-INF\lib? - Original Message From: Tommy Knowlton <[EMAIL PROTECTED]> To: Maven Users List Sent: Friday, 24 August, 2007 1:29:38 PM Subject: Re: provided dependencies my guess would be that both modules depend transitively on the javax.servlet in the runtime scope. but, since guessing is not likely to be very helpful, may I recommend the maven-dependency-plugin, which can give you a report that may help you to locate the actual dependency chain that ends up bringing those in. Then, you should decide whether to use elements in the declarations of those things that ended up bringing it in. Hope that helps, \Tommy On 24 Aug 2007, at 11:12 , DM wrote: Hi, I have two maven modules, policy-core and policy-webapp. policy- webapp depends on policy-core, and they are packaged as a war and jar respectively. Both modules have the following dependency: javax.servlet servlet-api 2.3 provided When I package policy-webapp, I get both the following JARs in WEB- INF\lib servlet-api-2.5-6.0.1.jar servlet-api-2.3.jar Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase they should be provided by the container - this is why I set the scope to 'provided'. Both policy-core and policy-webapp extend the same POM, but their parent POM doesn't mention servlet-api, so I don't think this is particularly relevant. Any idea why these JARs are being copied to WEB-INF\lib and how I can prevent this? Thanks in Advance, DM ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - 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] ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html - 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: provided dependencies
Yes, I interpret that table to mean the same thing that you said. Sorry, I can see how my earlier response would be irrelevant. I wonder whether it's possible your -war and -core POM's have the javax.servlet declaration duplicated, such that it appears somewhere else in your with non-provided ? That's just another guess, and failing that, I think I'm out of guesses. Sorry. Good luck, \Tommy On 24 Aug 2007, at 11:52 , DM wrote: Thanks for the reply. Maybe I'm not understanding the documentation correctly, but in the table of the "Dependency Scope" section of this page: http://maven.apache.org/guides/introduction/introduction-to- dependency-mechanism.html it seems to say that a provided dependency is transitively provided, so doesn't that mean it still should not be copied to WEB- INF\lib? - Original Message From: Tommy Knowlton <[EMAIL PROTECTED]> To: Maven Users List Sent: Friday, 24 August, 2007 1:29:38 PM Subject: Re: provided dependencies my guess would be that both modules depend transitively on the javax.servlet in the runtime scope. but, since guessing is not likely to be very helpful, may I recommend the maven-dependency-plugin, which can give you a report that may help you to locate the actual dependency chain that ends up bringing those in. Then, you should decide whether to use elements in the declarations of those things that ended up bringing it in. Hope that helps, \Tommy On 24 Aug 2007, at 11:12 , DM wrote: Hi, I have two maven modules, policy-core and policy-webapp. policy- webapp depends on policy-core, and they are packaged as a war and jar respectively. Both modules have the following dependency: javax.servlet servlet-api 2.3 provided When I package policy-webapp, I get both the following JARs in WEB- INF\lib servlet-api-2.5-6.0.1.jar servlet-api-2.3.jar Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase they should be provided by the container - this is why I set the scope to 'provided'. Both policy-core and policy-webapp extend the same POM, but their parent POM doesn't mention servlet-api, so I don't think this is particularly relevant. Any idea why these JARs are being copied to WEB-INF\lib and how I can prevent this? Thanks in Advance, DM ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - 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] ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html - 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: provided dependencies
Thanks for the reply. Maybe I'm not understanding the documentation correctly, but in the table of the "Dependency Scope" section of this page: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html it seems to say that a provided dependency is transitively provided, so doesn't that mean it still should not be copied to WEB-INF\lib? - Original Message From: Tommy Knowlton <[EMAIL PROTECTED]> To: Maven Users List Sent: Friday, 24 August, 2007 1:29:38 PM Subject: Re: provided dependencies my guess would be that both modules depend transitively on the javax.servlet in the runtime scope. but, since guessing is not likely to be very helpful, may I recommend the maven-dependency-plugin, which can give you a report that may help you to locate the actual dependency chain that ends up bringing those in. Then, you should decide whether to use elements in the declarations of those things that ended up bringing it in. Hope that helps, \Tommy On 24 Aug 2007, at 11:12 , DM wrote: > Hi, > > I have two maven modules, policy-core and policy-webapp. policy- > webapp depends on policy-core, and they are packaged as a war and > jar respectively. Both modules have the following dependency: > > > javax.servlet > servlet-api > 2.3 > provided > > > When I package policy-webapp, I get both the following JARs in WEB- > INF\lib > > servlet-api-2.5-6.0.1.jar > servlet-api-2.3.jar > > Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase > they should be provided by the container - this is why I set the > scope to 'provided'. > Both policy-core and policy-webapp extend the same POM, but their > parent POM doesn't mention servlet-api, so I don't think this is > particularly relevant. > > Any idea why these JARs are being copied to WEB-INF\lib and how I > can prevent this? > > Thanks in Advance, > DM > > > ___ > Yahoo! Answers - Got a question? Someone out there knows the > answer. Try it > now. > http://uk.answers.yahoo.com/ > > - > 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] ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: provided dependencies
my guess would be that both modules depend transitively on the javax.servlet in the runtime scope. but, since guessing is not likely to be very helpful, may I recommend the maven-dependency-plugin, which can give you a report that may help you to locate the actual dependency chain that ends up bringing those in. Then, you should decide whether to use elements in the declarations of those things that ended up bringing it in. Hope that helps, \Tommy On 24 Aug 2007, at 11:12 , DM wrote: Hi, I have two maven modules, policy-core and policy-webapp. policy- webapp depends on policy-core, and they are packaged as a war and jar respectively. Both modules have the following dependency: javax.servlet servlet-api 2.3 provided When I package policy-webapp, I get both the following JARs in WEB- INF\lib servlet-api-2.5-6.0.1.jar servlet-api-2.3.jar Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase they should be provided by the container - this is why I set the scope to 'provided'. Both policy-core and policy-webapp extend the same POM, but their parent POM doesn't mention servlet-api, so I don't think this is particularly relevant. Any idea why these JARs are being copied to WEB-INF\lib and how I can prevent this? Thanks in Advance, DM ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - 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]
provided dependencies
Hi, I have two maven modules, policy-core and policy-webapp. policy-webapp depends on policy-core, and they are packaged as a war and jar respectively. Both modules have the following dependency: javax.servlet servlet-api 2.3 provided When I package policy-webapp, I get both the following JARs in WEB-INF\lib servlet-api-2.5-6.0.1.jar servlet-api-2.3.jar Obviously I don't want any servlet-api JARs in WEB-INF\lib becuase they should be provided by the container - this is why I set the scope to 'provided'. Both policy-core and policy-webapp extend the same POM, but their parent POM doesn't mention servlet-api, so I don't think this is particularly relevant. Any idea why these JARs are being copied to WEB-INF\lib and how I can prevent this? Thanks in Advance, DM ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build Error
Hi, This kind of error is most often caused by maven not being able to connect to the repository due to a missing or wrong proxy configuration [1] in settings.xml ore some firewall issues. -Tim [1] http://maven.apache.org/guides/mini/guide-proxies.html theozaf schrieb: Hi guys I a really new to alla that maven thing, so I come up with some silly, for many of you, questions :) . Well I download the server and run it on my PC, then configuring all the settings.xml file and I think it's correct. I am testing by mvn --version which at least means the server runs. But when I am trying any other command lets say mvn instal just for testing I got the following error message. Any suggestion at least what should I check. I am trying to upload the plugins but I think I missing a point. [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Fri Aug 24 19:10:41 EEST 2007 [INFO] Final Memory: 1M/2M [INFO] Theo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bundle plugin misses its own dependencies
On 25/08/07, Richard S. Hall <[EMAIL PROTECTED]> wrote: > > Arash Amiri wrote: > > Hi, > > um... > > sometimes (I say "sometimes" because I really dont know what the cause > > is), a bundle, that I create with the maven-bundle-plugin, misses, > > once deployed, its own packages. > > > > e.g. I have a package "org.myapp.meta" in my maven project. > > I configure the maven bundle plugin (in the same project) the > > following way: > > ... > > org.myapp.*;resolution:=optional > > org.myapp.* > > ... > > > > when I deploy it in equinox, it gives me an error such as: > > Missing imported package org.myapp.meta > > I dont get this, since the jar file contains the package. > > > > Yet, I have to admit that the bundle has other dependencies which are > > not (yet) satifsfied. > > e.g. the org.myapp.meta package uses "org.openrdf.elmo" which is in a > > bundle not yet deployed (since I have to create it first). if the 'org.myapp.meta' package depends on a non-deployed package then this could explain the equinox error (although it could be clearer!) if you still see the error with 'org.openrdf.elmo' deployed then please provide a testcase (or at least the poms + manifests + diag output). > > > my question: > > Is it a maven bundle plugin configuration issue or is it simply > > Equinox that refuses to import packages which have unresolved > references? > > Just a guess, since I don't really know how Equinox' resolver works, but > it could be that it is trying to resolve the bundle to its own export > since you import/export the same package, but it is unable to do so > because it cannot resolve the bundle itself, so the error message says > it cannot find the package because it cannot resolve the provider of the > package, which just happens to be the same bundle in this case. This > could potentially happen, depending on how Equinox handles bundles > importing their own packages. > > One question for you, why are you importing the same packages you are > exporting with an "optional" directive. Seems kind of strange and it > might be meaningless since the bundle will always have access to the > package since it exports them. > > Also, shouldn't this be on the Felix users mailing list? > > -> richard > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
Re: bundle plugin misses its own dependencies
Hi, the maven-bundle-plugin's job is to package the bundle and create the bundle manifest. So if all packages/classes you expect are included in the bundle jar and the manifest content matches what you configured in the plugin configuration the plugin has done it's job. If you have a specific osgi related question about the correct manifest content for your use-case or the behaviour of an osgi implementation you might have more luck to get this answered on a more osgi related mailinglist (like that of the implementation you are using). -Tim Arash Amiri schrieb: Hi, um... sometimes (I say "sometimes" because I really dont know what the cause is), a bundle, that I create with the maven-bundle-plugin, misses, once deployed, its own packages. e.g. I have a package "org.myapp.meta" in my maven project. I configure the maven bundle plugin (in the same project) the following way: ... org.myapp.*;resolution:=optional org.myapp.* ... when I deploy it in equinox, it gives me an error such as: Missing imported package org.myapp.meta I dont get this, since the jar file contains the package. Yet, I have to admit that the bundle has other dependencies which are not (yet) satifsfied. e.g. the org.myapp.meta package uses "org.openrdf.elmo" which is in a bundle not yet deployed (since I have to create it first). my question: Is it a maven bundle plugin configuration issue or is it simply Equinox that refuses to import packages which have unresolved references? greetings, arash - 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: bundle plugin misses its own dependencies
Richard S. Hall schrieb: Arash Amiri wrote: Hi, um... sometimes (I say "sometimes" because I really dont know what the cause is), a bundle, that I create with the maven-bundle-plugin, misses, once deployed, its own packages. e.g. I have a package "org.myapp.meta" in my maven project. I configure the maven bundle plugin (in the same project) the following way: ... org.myapp.*;resolution:=optional org.myapp.* ... when I deploy it in equinox, it gives me an error such as: Missing imported package org.myapp.meta I dont get this, since the jar file contains the package. Yet, I have to admit that the bundle has other dependencies which are not (yet) satifsfied. e.g. the org.myapp.meta package uses "org.openrdf.elmo" which is in a bundle not yet deployed (since I have to create it first). my question: Is it a maven bundle plugin configuration issue or is it simply Equinox that refuses to import packages which have unresolved references? Just a guess, since I don't really know how Equinox' resolver works, but it could be that it is trying to resolve the bundle to its own export since you import/export the same package, but it is unable to do so because it cannot resolve the bundle itself, so the error message says it cannot find the package because it cannot resolve the provider of the package, which just happens to be the same bundle in this case. This could potentially happen, depending on how Equinox handles bundles importing their own packages. One question for you, why are you importing the same packages you are exporting with an "optional" directive. Seems kind of strange and it might be meaningless since the bundle will always have access to the package since it exports them. Also, shouldn't this be on the Felix users mailing list? thanks for the quick reply. I never know where to post maven-bundle-plugin issues, since I see lots of them being posted to this list as well. Anyway, I hope that creating the other bundles solves my problem and that equinox is simply not resolving those bundles. cheers, arash -> richard - 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: bundle plugin misses its own dependencies
Arash Amiri wrote: Hi, um... sometimes (I say "sometimes" because I really dont know what the cause is), a bundle, that I create with the maven-bundle-plugin, misses, once deployed, its own packages. e.g. I have a package "org.myapp.meta" in my maven project. I configure the maven bundle plugin (in the same project) the following way: ... org.myapp.*;resolution:=optional org.myapp.* ... when I deploy it in equinox, it gives me an error such as: Missing imported package org.myapp.meta I dont get this, since the jar file contains the package. Yet, I have to admit that the bundle has other dependencies which are not (yet) satifsfied. e.g. the org.myapp.meta package uses "org.openrdf.elmo" which is in a bundle not yet deployed (since I have to create it first). my question: Is it a maven bundle plugin configuration issue or is it simply Equinox that refuses to import packages which have unresolved references? Just a guess, since I don't really know how Equinox' resolver works, but it could be that it is trying to resolve the bundle to its own export since you import/export the same package, but it is unable to do so because it cannot resolve the bundle itself, so the error message says it cannot find the package because it cannot resolve the provider of the package, which just happens to be the same bundle in this case. This could potentially happen, depending on how Equinox handles bundles importing their own packages. One question for you, why are you importing the same packages you are exporting with an "optional" directive. Seems kind of strange and it might be meaningless since the bundle will always have access to the package since it exports them. Also, shouldn't this be on the Felix users mailing list? -> richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
bundle plugin misses its own dependencies
Hi, um... sometimes (I say "sometimes" because I really dont know what the cause is), a bundle, that I create with the maven-bundle-plugin, misses, once deployed, its own packages. e.g. I have a package "org.myapp.meta" in my maven project. I configure the maven bundle plugin (in the same project) the following way: ... org.myapp.*;resolution:=optional org.myapp.* ... when I deploy it in equinox, it gives me an error such as: Missing imported package org.myapp.meta I dont get this, since the jar file contains the package. Yet, I have to admit that the bundle has other dependencies which are not (yet) satifsfied. e.g. the org.myapp.meta package uses "org.openrdf.elmo" which is in a bundle not yet deployed (since I have to create it first). my question: Is it a maven bundle plugin configuration issue or is it simply Equinox that refuses to import packages which have unresolved references? greetings, arash - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Performance issues with multiple continuum instances on single server
As far as build timeouts are concerned, are you referring to a timeout that can be set in continuum, in the maven pom, or that we should handle in our custom python scripts? As far as the maven2 project setup, I can actually set the projects up with no problem but when I run some of them I get the following exception: org.apache.maven.continuum.store.ContinuumObjectNotFoundException: Could not find object. Type 'org.apache.maven.continuum.model.project.BuildDefinition'. Id: '47'. at org.apache.maven.continuum.store.JdoContinuumStore.getObjectById(JdoCont inuumStore.java:579) at org.apache.maven.continuum.store.JdoContinuumStore.getObjectById(JdoCont inuumStore.java:567) at org.apache.maven.continuum.store.JdoContinuumStore.getBuildDefinition(Jd oContinuumStore.java:505) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction .java:56) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Unknown Source) I assume this means it's looking in the database for build definition id 47 and can't find it. I have never seen this error with the Shell projects that I've set up. Then again I set a different project up as a maven 2 project and ran a build without a problem. This seems like a bug in 1.0.3 to me. I searched JIRA but wasn't able to find a similar bug report. Eric -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Friday, August 24, 2007 9:18 AM To: [EMAIL PROTECTED] Subject: Re: Performance issues with multiple continuum instances on single server first part...is just kinda weird... second part, do the builds have timeouts setup for them? lastly, what were the problems you had with maven2 project setup? jesse On 8/21/07, Eric Roberts <[EMAIL PROTECTED]> wrote: > > Anyone have any suggestions? > > -Original Message- > From: Eric Roberts [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 16, 2007 12:00 PM > To: [EMAIL PROTECTED] > Subject: Performance issues with multiple continuum instances on > single server > > I am currently running 2 instances of continuum as windows services on > a single Windows 2003 server (running as a VMware virtual machine). > The first instance was installed about 6 months ago and has run pretty well. > I just installed a second instance and have noticed a problem with its > performance and availability. When a build is running on the first > instance, this generally causes the second instance to become > unresponsive almost every time (i.e. I get a 404 not found message > when I try to access it in my browser). The service will eventually > come back on its own after a few minutes but If I look in the > wrapper.log I see messages like the following > > ERROR | wrapper | 2007/08/09 09:27:50 | JVM appears hung: Timed out > waiting for signal from JVM. > ERROR | wrapper | 2007/08/09 09:27:50 | JVM did not exit on request, > terminated STATUS | wrapper | 2007/08/09 09:27:55 | Launching a JVM... > INFO | jvm 5| 2007/08/09 09:27:57 | Wrapper (Version 3.1.2) > http://wrapper.tanukisoftware.org > > Another issue that has been occurring on the second server is that > builds often run indefinitely. It's almost as if the build process > has died somehow but continuum never noticed so the clock just keeps > ticking. I am able to clean these builds up directly in the database > but I can't figure out why it keeps happening. > > A little background about the environment. I have set up all projects > in both continuum instances as shell projects but the builds > themselves use Maven 2. We were unable to get the Maven 2.0 project > type to work correctly and the shell project type worked so we went > with it. The maven build is executing some python scripts which are > used to process and transform XML documentation using XSLT (a little > convoluted I know but I inherited it). The transformation is done > using the Java Saxon library which tends to require a lot of memory > and CPU. I have a strong hunch that both of my issues are somehow > interrelated but am not sure where to start. > > Java 1.5.0_10 > Maven 2.0.4 > Python 2.4.1 > Saxon 6.5.5 > Windows 2003 server running as a VMWare virtual machine on Intel Xeon > 3GHz CPU w/ 3.75G RAM > > Any help or suggestions are greatly appreciated, > > Eric > -- jesse mcconnell [EMAIL PROTECTED]
Build Error
Hi guys I a really new to alla that maven thing, so I come up with some silly, for many of you, questions :) . Well I download the server and run it on my PC, then configuring all the settings.xml file and I think it's correct. I am testing by mvn --version which at least means the server runs. But when I am trying any other command lets say mvn instal just for testing I got the following error message. Any suggestion at least what should I check. I am trying to upload the plugins but I think I missing a point. [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Fri Aug 24 19:10:41 EEST 2007 [INFO] Final Memory: 1M/2M [INFO] Theo -- View this message in context: http://www.nabble.com/Build-Error-tf4324489s177.html#a12315549 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Properties && pom.xml
My project uses a lot of properties. I use those properties both for
filtering resources and inside the pom.xml as argument for plugin. Problem
is that I have to duplicate my props definition.
I have tried several solution, none of them works.
1- Use filters:
filter.properties
In that case properties are not know in the pom.xml. As I use it for my
plugin configuration it does not works.
2- Use properties
${jboss.server.home.dir}/conf/my.keystore
ps
...
In that case I'd like that ${jboss.server.home.dir} will not be replace as
it is not a defined properties. Maven replace not set properties by null.
Consequently the value becomes
http://www.nabble.com/Propertiespom.xml-tf4324308s177.html#a12314910
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: 5 minute quickstart: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found
Guillaume Bilodeau wrote: > > > Wendy Smoak-3 wrote: >> >> On 8/17/07, Guillaume Bilodeau <[EMAIL PROTECTED]> wrote: >> >>> I am behind no firewall, I have setup no mirrors - this is a clean >>> install. >>> It's obviously a network error as the SocketException shows. Actually, >>> ibiblio.org has a hard time redirecting to mirrors.ibiblio.org - takes 1 >>> or >>> 2 minutes to do so in a web browser. Could this be the problem? >> >> If it's a completely clean install, it shouldn't be talking to ibiblio >> at all... the central repo is at repo1.maven.org/maven2 . >> >> Can you clarify whether this happens with an empty local repository? >> (I'm not sure if this is a fresh install of Maven, or a completely >> clean new machine.) >> >> Try deleting the local repository and/or adding -U to the command line. >> >> -- >> Wendy >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > It's a fresh, clean install and the repository is empty. This was already > executed with the -U -X options. Strange isn't it? > Even stranger: running mvn -U install on a project with new dependencies works ONCE per day. After this successful run, the above message comes up again. Changing the system date has no effect whatsoever. Surely this must be a firewall issue - I should have mentioned that I am behind a firewall, but not behind a proxy. Is this possible? -- View this message in context: http://www.nabble.com/5-minute-quickstart%3A-The-plugin-%27org.apache.maven.plugins%3Amaven-archetype-plugin%27-does-not-exist-or-no-valid-version-could-be-found-tf4045296s177.html#a12313790 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: Having trouble using maven-ejb-plugin -- can't get Class-Path in manifest
Tim,
I think you are right. The project set up has more than I need for EJB. I
will double check the dependencies. But I still the plugin provides some
sort of selection mechanism.
J
Tim Kettler wrote:
>
> I don't know a way to do this. Why do you want to do this at all? Either
> your jar depends on a other jar, then you declare it in a dependency and
> it ends up in the classpath entry or you dont't depend on it, then just
> don't declare the dependency at all.
>
> -Tim
>
> jzhang schrieb:
>> Tim,
>>
>> You are right. I had jar instead of
>> ejb so the ejb-plugin did not get executed. Now
>> all
>> dependencies are in calss-path. Is there anyway I can select some of
>> them? I
>> don't think works here.
>>
>> Thanks,
>>
>> J
>>
>>
>>
>> jzhang wrote:
>>> I am using Maven 2.0.7. In my ear file, I have a ejb jar (called
>>> core.jar)
>>> that depends on common.jar. They are all in the same ear. I want to have
>>> core.jar manifest.mf file have Class-Path entry for common.jar. But I
>>> can
>>> not get that work. I follow maven-ejb-plugin instruction:
>>>
>>>
>>> org.apache.maven.plugins
>>> maven-ejb-plugin
>>>
>>>
>>>
>>> true
>>>
>>>
>>>
>>>
>>>
>>>
>>> And I ran: mvn install. The new generated ejb jar file's manifest does
>>> not
>>> have Class-Path entry. Besides, I want to add common.jar to this path.
>>> Then I add:
>>>
>>>
>>> ${pom.groupId}
>>> my-common
>>> ${pom.version}
>>>
>>>
>>> true
>>>
>>>
>>>
>>>
>>> Then I got 'org.apache.maven.reactor.MavenExecutionException: Parse
>>> error
>>> reading POM. Reason: Unrecognised tag: 'properties' (position: START_TAG
>>> seen ...\r\n... @18:25' error.
>>>
>>> It seems I can not put tag in element. What is
>>> wrong?
>>>
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Having-trouble-using-maven-ejb-plugincan%27t-get-Class-Path-in-manifest-tf4312954s177.html#a12313575
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: mvn.bat and error_code (Maven 2.0.7 and Windows XP)
Thank you! Any idea when Maven 2.0.8 might be out? Andreas -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, August 23, 2007 4:23 PM To: Maven Users List Subject: Re: mvn.bat and error_code (Maven 2.0.7 and Windows XP) http://jira.codehaus.org/browse/MNG-3084 On 8/23/07, Andreas Guther <[EMAIL PROTECTED]> wrote: > Maven 2.0.7 mvn.bat errorlevel return code problem. > > Hi > I am failing to capture the mvn.bat return code. > > > Basically I have a batch file that calls mvn several times. In case of > an error I would like to stop calling following mvn calls. > > > > Example > > call mvn clean:clean > IF ERRORLEVEL 0 GOTO CONTINUE > GOTO CLEANERROR > ... and so on... > > The error level seems not to be propagated to my batch file. > > If I use "SET MAVEN_TERMINATE_CMD=on" in my batch file then in case of > an error my batch file is terminated. > > There must be a way to capture the return code and handle it from a > calling batch file, but which??? > > Thanks in advance for any help > > - > 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 plugin alternative to assembly plugin
thanks, saved my day!
one little correction and suggestion (and a last question for maven-jar
plugin):
...
${artifactId}-*.jar
${basedir}/target
${groupId}-${artifactId}-${version}-${classifier}.${extension}
lib
...
for
${groupId}-${artifactId}-${version}-${classifier}.${extension}
i need to adjust the classpath string in MANIFEST.MF. unfortunately making
lib/${groupId}-${artifactId}-${version}-${classifier}.${extension}.
does not work, because it is interpreted as a directory.
how is it possible to set the classpath equal to the library names in lib/
folder configured in assembly plugin?
--
View this message in context:
http://www.nabble.com/maven-plugin-alternative-to-assembly-plugin-tf4262116s177.html#a12311490
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: assembly plugin: transitive dependencies do not get included
thought that this tweak makes pattern of include/exclude be imported to transitive dependencies (see http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet). never the less i tried it, but still same issue :( Stephane Nicoll-2 wrote: > > sorry. > > On 8/23/07, aldana <[EMAIL PROTECTED]> wrote: >> >> where do i set option includeTransitiveDeps to true? cannot find it in >> assembly descriptor schema. >> >> >> Stephane Nicoll-2 wrote: >> > >> > Mmm. This might be a bug. Check that includeTransitiveDeps is set to >> true. >> > >> > HTH, >> > Stéphane >> > >> > On 8/23/07, aldana <[EMAIL PROTECTED]> wrote: >> >> >> >> hi, >> >> >> >> i am using assembly plugin with standard descriptor >> >> jar-with-dependencies. >> >> problem is that transitive dependencies do not get included. >> >> >> >> pom.xml from project A: >> >> ... >> >> a >> >> a >> >> 1.0 >> >> >> >> >> >> tran >> >> dep >> >> 1.0 >> >> >> >> >> >> ... >> >> >> >> >> >> pom.xml from project B: >> >> ... >> >> b >> >> b >> >> 1.0 >> >> >> >> ... enabling assembly-plugin with jar-with-dependencies... >> >> >> >> >> >> >> >> a >> >> a >> >> 1.0 >> >> >> >> >> >> ... >> >> >> >> i am doing assembly:assembly on b:b. now tran:dep does not get >> included >> >> though it is defined in a:a. that means: if i open the assembled >> jar-file >> >> (from b:b) i cannot see any artifacts from tran:dep. >> >> >> >> what is going wrong here? thought that default behaviour of >> >> jar-with-dependencies includes everything as told in >> >> >> http://www.nabble.com/-M2--How-to-include-transitive-dependencies-with-Assembly-plugin-tf2177453s177.html#a6020485? >> >> >> >> i am using plugin in version 2.2-beta-1. >> >> >> >> thanks for your help. >> >> >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/assembly-plugin%3A-transitive-dependencies-do-not-get-included-tf4317601s177.html#a12293820 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > -- >> > Large Systems Suck: This rule is 100% transitive. If you build one, >> > you suck" -- S.Yegge >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/assembly-plugin%3A-transitive-dependencies-do-not-get-included-tf4317601s177.html#a12301837 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Large Systems Suck: This rule is 100% transitive. If you build one, > you suck" -- S.Yegge > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/assembly-plugin%3A-transitive-dependencies-do-not-get-included-tf4317601s177.html#a12308820 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WTP, Eclipse, and Maven with APP-INF/lib
Hello I have an ear which in turn has dependencies that need to be furnished to all sub projects (a few EJBs, a few WARs). The maven build itself is configured to do the right thing and, in the resulting .ear, yeilds an APP-INF/lib director with all non ejb/war/car dependencies. I can even run mvn eclipse:eclipse with the wtp support and get a pretty useful setup inside of eclipse. I also setup maven to not generate -SNAPSHOT-1.0.jar on the artifacts, which makes the application.xml something we can keep in source. This in turn makes eclipse happy because it can let us use the WTP facilities for an EAR. However, when we take the ear project and add it to a server (JBoss), and then publish that eclipse project, eclipse builds an ear (amazingly !) that works just like if mvn had built it EXCEPT for /APP-INF/lib/*jar at the root of the ear project. Apparently this has something to do with the EAR Libraries library, but I'm unsure of how to accomodate this. Plus, it ideally should be correctly configured by the mavne plugin. Does anyone have any way around this? A custom mojo I might bind to the eclipse:eclipse phase? Insight on how this would be configured in the low level eclipse .settings stufff? Anything at all would be appreciated. Thanks, Josh Long - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Phase to validate source for 'processed files'
Dear users and developers, I'm playing the xml-maven-plugin:validate (codehaus). I try to use it to validate all XMLs (JavaEE, spring), however, I come across a problem: I use filters to filter XML files under src/main/resources Most XML are "filtered" during process-resources. (std maven way) If I would like to validate my XML files, (against the published schema), the input to the validation is only available after "process-resources". Then, which phase should I bind the 'validate' goal into? I originally bind the validate goal with 'validate' phase, but validate phase execute before "process-resources", hence, validate will always failed. Then, I would try to bind the validate goal with "verify" phase, with that, I still have to direct the plugin to search for files under "target/" folder. This caused another two problems: 1. In a multi-module setup, the parent module (packaging==pom) will not have /target folder, and the plugin will failed (IMO, it is bug of the plugin) 2. Asking a plugin to process files in "/target" looks ugly (what do you think?) After all, I think, one of the best strengths of Maven for me is, convention over customization. And 'validating' XML files can be thought as a very common goals for most project, than, what should be the answer for this task in "maven way"?? Thanks! Best regards, Zarick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven insist to fetch sibling module from repository
On 8/24/07, Barrie Treloar <[EMAIL PROTECTED]> wrote: > On 8/24/07, Zarick Lau <[EMAIL PROTECTED]> wrote: > > Dear Users and Developers, > > > > In a multi-module project (1 parent with 2 sub-module), > > sub-module-b deps on sub-module-a, when I run maven under > > the top-level (parent), > > > > mvn process-resources > > > > Maven will try to grab sub-module-a from repository, as I > > haven't install / deploy sub-module-a, the build failed. > > > > However, if I invoke maven with: > > > > mvn package > > > > The whole build completed without error.. > > > > Any clues why this strange behavior happens? > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > > However you need "install" to get your artifacts into the local > repository and package is _prior_ to install. I know what 'install' mean in maven, but running mvn at the "parent" module doesn't require "installing" all sub-module first. And indeed, [Off topic] if running "install" in each individual module is pre-req, even though I run mvn at "parent" module, it looks a little bit strange for me... > > It doesn't make sense that process-resources should work when package does. Yes, I think so :) > > Maybe one of your plugins is failing because it is being run in a > phase before process-resources but requires some resolution available > in a later phase. > > Can you paste the error message? I can reproduce the issue, if sub-module-b packaing == jar, no error. My error occur only when packagin == ear... Thanks! Best regards, Zarick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly plugin - how to copy resulting archives ?
Hi, you can use the antrun-plugin [1] and the ftp/scp/sshexec tasks to this. -Tim [1] http://maven.apache.org/plugins/maven-antrun-plugin/ houzecl schrieb: Hello, Artefacts are stored into Maven repositories. ok When we've got war or ear artefacts, they can be deployed via Cargo plugin on application servers. ok However, whent you produce zip, tar, etc. with assembly plugin, they can be stored into repositories as well, but is there any plugin that allows to perform something like an ftp copy ... unzip ... exec on a target machine ? thanks for any info/suggestion Christian-Luc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly plugin: transitive dependencies do not get included
sorry. On 8/23/07, aldana <[EMAIL PROTECTED]> wrote: > > where do i set option includeTransitiveDeps to true? cannot find it in > assembly descriptor schema. > > > Stephane Nicoll-2 wrote: > > > > Mmm. This might be a bug. Check that includeTransitiveDeps is set to true. > > > > HTH, > > Stéphane > > > > On 8/23/07, aldana <[EMAIL PROTECTED]> wrote: > >> > >> hi, > >> > >> i am using assembly plugin with standard descriptor > >> jar-with-dependencies. > >> problem is that transitive dependencies do not get included. > >> > >> pom.xml from project A: > >> ... > >> a > >> a > >> 1.0 > >> > >> > >> tran > >> dep > >> 1.0 > >> > >> > >> ... > >> > >> > >> pom.xml from project B: > >> ... > >> b > >> b > >> 1.0 > >> > >> ... enabling assembly-plugin with jar-with-dependencies... > >> > >> > >> > >> a > >> a > >> 1.0 > >> > >> > >> ... > >> > >> i am doing assembly:assembly on b:b. now tran:dep does not get included > >> though it is defined in a:a. that means: if i open the assembled jar-file > >> (from b:b) i cannot see any artifacts from tran:dep. > >> > >> what is going wrong here? thought that default behaviour of > >> jar-with-dependencies includes everything as told in > >> http://www.nabble.com/-M2--How-to-include-transitive-dependencies-with-Assembly-plugin-tf2177453s177.html#a6020485? > >> > >> i am using plugin in version 2.2-beta-1. > >> > >> thanks for your help. > >> > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/assembly-plugin%3A-transitive-dependencies-do-not-get-included-tf4317601s177.html#a12293820 > >> Sent from the Maven - Users mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > -- > > Large Systems Suck: This rule is 100% transitive. If you build one, > > you suck" -- S.Yegge > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/assembly-plugin%3A-transitive-dependencies-do-not-get-included-tf4317601s177.html#a12301837 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Assembly plugin - how to copy resulting archives ?
Hello, Artefacts are stored into Maven repositories. ok When we've got war or ear artefacts, they can be deployed via Cargo plugin on application servers. ok However, whent you produce zip, tar, etc. with assembly plugin, they can be stored into repositories as well, but is there any plugin that allows to perform something like an ftp copy ... unzip ... exec on a target machine ? thanks for any info/suggestion Christian-Luc -- View this message in context: http://www.nabble.com/Assembly-plugin---how-to-copy-resulting-archives---tf4322070s177.html#a12307739 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: Having Problem in creating new project in Maven
Hi, there is indeed something wrong in the repository. 1.0-alpha-5 is not released yet and should not be in the repository. As a workaround until this is fixed just tell maven the exact version of the plugin to use: mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-4:create -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=com.devsid.app -DartifactId=my-app -Tim Siddharth Godbole schrieb: Hi, I am new user to Maven and was going through guide to start creating a smalls project. I have installed Maven version: 2.0.7 and i am using it with Java version: 1.4.2_06 on red hat linux. mvn --version shows the right version so i am assuming maven is installed correctly. I tried doing following: mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes-DgroupId= com.devsid.app -DartifactId=my-app But its failing with: Reason: Unable to download the artifact from any repository org.apache.maven.archetype:maven-archetype:pom:1.0-alpha-5 from the specified remote repositories: central (http://repo1.maven.org/maven2) I checked the repository manually and found out there is nothing like 1.0-alpha-5 version on repository so i tried supplying -DarchetypeVersion= 1.0-alpha-4 also but its still not working. Please let me know if i have missed any settings or what should i do to get this working ? Sid - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
