Do we have to have src/main/java project structure????
Hi When building a java project do we always have to have the project in this src/main/java structure Thank you V. Arvind -- View this message in context: http://maven.40175.n5.nabble.com/Do-we-have-to-have-src-main-java-project-structure-tp3422876p3422876.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven embedder examples
This message is too old. Anyway I post my solution here in case someone needs it: org.apache.maven maven-embedder 3.0-alpha-2 test The 3.0-alpha-2 version works for me :) -- View this message in context: http://maven.40175.n5.nabble.com/Maven-embedder-examples-tp89849p3422868.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Do we have to have src/main/java project structure????
Technically, no. You can configure Maven (and it's plugins) to use a different source path. However, I strongly discourage this as you could run into issues with badly written plugins. Also, the Maven standard path has became a best-practice in the industry (if you ask me) and is what most devs are used to today. /Anders On Thu, Mar 10, 2011 at 08:29, arvindv6 arvind.venugo...@verizonbusiness.com wrote: Hi When building a java project do we always have to have the project in this src/main/java structure Thank you V. Arvind -- View this message in context: http://maven.40175.n5.nabble.com/Do-we-have-to-have-src-main-java-project-structure-tp3422876p3422876.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Plugin for changing build output directory
Hello Maven users, Is there a plugin with a goal for changing build output directory? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin for changing build output directory
Don't think that is possible to do during the build. Why not just change it in the pom? /Anders On Thu, Mar 10, 2011 at 10:29, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, Is there a plugin with a goal for changing build output directory? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Bad mojo. Builds under maven2, fails under maven3.
shaun.t.erickson wrote: [INFO] --- maven-antrun-plugin:1.3:run (metrics-for-eclipse) @ ccl --- [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:jar:1.3: [DEBUG]org.apache.ant:ant-nodeps:jar:1.7.0:runtime [DEBUG]ant-contrib:ant-contrib:jar:1.0b3:runtime [DEBUG] ant:ant:jar:1.5:runtime [...] Caused by: java.lang.NoSuchMethodError: org.apache.tools.ant.util.FileUtils.close(Ljava/io/InputStream;)V The POM seems to manually add ant-contrib:1.0b3 to the plugin classpath which in turns pulls in ant:1.5 which lacks the method in question. Furthermore, the different groupIds used for ant (ant vs org.apache.ant) prevent Maven from detecting this version conflict. Either a newer version of ant-contrib that depends on ant:1.7+ needs to be used or an exclusion for ant:ant added to the dependency declaration for ant-contrib. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Bad mojo. Builds under maven2, fails under maven3.
I don't know whether this is fixed in newer versions of the Antrun plugin, but I noticed you use version 1.3, while version 1.6 is also available. You can give it a try and hopes it fixes your problem. With regards, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 12:35 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: antrun - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin for changing build output directory
It is possible to change build output directory during the build. E.g. cobertura-maven-plugin and emma-maven-plugin both have instrument goal which as side-effect changes build output directory with something like project.getBuild().setOutputDirectory( %some_path% ); where project is reference to MavenProject being built. They do that, but do not support configuration option to disable that behavior. Configuring build path in pom.xml won't help. Regards, Stevo. On Thu, Mar 10, 2011 at 10:49 AM, Anders Hammar and...@hammar.net wrote: Don't think that is possible to do during the build. Why not just change it in the pom? /Anders On Thu, Mar 10, 2011 at 10:29, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, Is there a plugin with a goal for changing build output directory? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven embedder examples
if this is a genuine maven-plugin where is the project hosted? Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Wed, 9 Mar 2011 23:16:12 -0800 From: nguyenhoai...@gmail.com To: users@maven.apache.org Subject: Re: Maven embedder examples This message is too old. Anyway I post my solution here in case someone needs it: org.apache.maven maven-embedder 3.0-alpha-2 test The 3.0-alpha-2 version works for me :) -- View this message in context: http://maven.40175.n5.nabble.com/Maven-embedder-examples-tp89849p3422868.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Missing links in site generation of multi-module project
Lukas, thanks for helping me out with this last month. Any chance 2.3 will be released soon (or a beta)? Thanks, Craig -Original Message- From: Harpel, Craig [mailto:char...@mitre.org] Sent: Wednesday, February 16, 2011 11:17 AM To: Maven Users List Subject: RE: Missing links in site generation of multi-module project Got it! Yes, I can confirm that 2.3-SNAPSHOT does indeed fix my problem. Thanks a lot!! Craig -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 11:01 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project http://maven.apache.org/guides/development/guide-testing-development-plugins.html HTH, -Lukas PS sorry, dense too :) Harpel, Craig wrote: Sorry for being dense, but I don't see a 2.3-SNAPSHOT; where can I grab it from? -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 7:49 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
No plugin descriptor found at META-INF/maven/plugin.xml
Any idea why I'm getting this error - Im using the latest Maven () Embedded 3.0-SNAPSHOT/0.12.1.20110112-1712) under Eclipse (Version: Helios Service Release 1)? I guess its some version issue - trying to find a mojo config. Thnx [ERROR] Failed to parse plugin descriptor for org.apache.maven.plugins:maven-ejb-plugin:1.7.3 (C:\Documents and Settings\robin.sharp\.m2\repository\org\apache\maven\plugins\maven-ejb-plugin\1.7.3\maven-ejb-plugin-1.7.3.jar): No plugin descriptor found at META-INF/maven/plugin.xml - [Help 1] org.apache.maven.plugin.PluginDescriptorParsingException: Failed to parse plugin descriptor for org.apache.maven.plugins:maven-ejb-plugin:1.7.3 (C:\Documents and Settings\robin.sharp\.m2\repository\org\apache\maven\plugins\maven-ejb-plugin\1.7.3\maven-ejb-plugin-1.7.3.jar): No plugin descriptor found at META-INF/maven/plugin.xml at org.apache.maven.plugin.internal.DefaultMavenPluginManager.extractPluginDescriptor(DefaultMavenPluginManager.java:212) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:147) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:192) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExections(DefaultLifecycleExecutionPlanCalculator.java:134) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116) at org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:92) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.io.IOException: No plugin descriptor found at META-INF/maven/plugin.xml at org.apache.maven.plugin.internal.DefaultMavenPluginManager.extractPluginDescriptor(DefaultMavenPluginManager.java:207) ... 23 more [ERROR] -- View this message in context: http://maven.40175.n5.nabble.com/No-plugin-descriptor-found-at-META-INF-maven-plugin-xml-tp3423313p3423313.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Multi Module Project Setup: When not to use?
Hi, I'd like to know your thoughts on when not to use a multi module project setup. For example for a typical 3-tier web application (ui+controllers/service/data-access), will a maven-archetype-webapp suffice for this setup, or would a multi-module project setup be more pragmatic? Thanks! -- Jojo
Re: No plugin descriptor found at META-INF/maven/plugin.xml
Javelin wrote: [ERROR] Failed to parse plugin descriptor for org.apache.maven.plugins:maven-ejb-plugin:1.7.3 You seem to be using a Maven 1.x plugin. So try updating to version 2.3: http://maven.apache.org/plugins/maven-ejb-plugin/ Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No plugin descriptor found at META-INF/maven/plugin.xml
org.apache.maven.plugin.PluginDescriptorParsingException: Failed to parse plugin descriptor for org.apache.maven.plugins:maven-ejb-plugin:1.7.3 (C:\Documents and Settings\robin.sharp\.m2\repository\org\apache\maven\plugins\maven-ejb-plugin\1.7.3\maven-ejb-plugin-1.7.3.jar): No plugin descriptor found at META-INF/maven/plugin.xml This seems to suggest that your cached m-ejb-p 1.7.3 artifact is possibly corrupt. Unpack the jar and see if it has a file at that location (META-INF/maven/plugin.xml). If it does not, there's your issue. Then you need to find out how you got a corrupted jar in your repo cache. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Where to host and publish a new plugin
Hello Everyone, I'm following the instructions given here to create a new maven plugin: http://maven.apache.org/guides/plugin/guide-java-plugin-development.html I think it would be useful to everyone when its done so I want to find out: 1) Where do you usually host the source for your plugins? svn? github? Which repository is popular and the accepted norm for active useful maven plugins? 2) How do you go on to promoting/publishing it on maven sonatype repo afterwards? Thanks! - Pulkit - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi Module Project Setup: When not to use?
On 10/03/2011 8:48 AM, Jojo Paderes wrote: Hi, I'd like to know your thoughts on when not to use a multi module project setup. For example for a typical 3-tier web application (ui+controllers/service/data-access), will a maven-archetype-webapp suffice for this setup, or would a multi-module project setup be more pragmatic? Thanks! -- Jojo Don't forget to extract out functional modules into separately tested modules that can be released on their own and used as libraries. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi Module Project Setup: When not to use?
For example for a typical 3-tier web application (ui+controllers/service/data-access), will a maven-archetype-webapp suffice for this setup, or would a multi-module project setup be more pragmatic? If the components of the app will never be used individually anywhere else (in another project etc) then a more basic webapp approach may be ok. This simplifies things by only having 1 version to deal with and 1 module etc. Especially for people new to Maven, this is probably the most comfortable approach since it mimics what they have done previously. If there is ever a possibility that you will want to turn things into components and reuse them in another project or version some parts independently, then you might as well bite the bullet and go multi-module. This is also the Maven way and people here (myself included) will make your life a little bit difficult when you start talking about problems you're having with Java source files or configuring ejbs in your webapp since that is not a best practice. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Where to host and publish a new plugin
A lot of the not-core plugins are hosted at Codehaus. They also have the infrastructure, like Subversion, Jira, snapshot repositories and deploying to central. Take a look here[1] to apply for a sandbox project. With regards, [1] http://mojo.codehaus.org/contribution/submitting-a-plugin.html Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 4:49 PM, Pulkit Singhal pulkitsing...@gmail.com wrote: Hello Everyone, I'm following the instructions given here to create a new maven plugin: http://maven.apache.org/guides/plugin/guide-java-plugin-development.html I think it would be useful to everyone when its done so I want to find out: 1) Where do you usually host the source for your plugins? svn? github? Which repository is popular and the accepted norm for active useful maven plugins? 2) How do you go on to promoting/publishing it on maven sonatype repo afterwards? Thanks! - Pulkit - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Central Repository IP Address Change?
Hi, It seems the IP address for repo1.maven.org has changed twice in as many days. Last week it appeared to be 38.97.124.18. Yesterday I noticed that it had changed to 63.246.20.112. Now today I see it is 207.223.240.88. $ nslookup repo1.maven.org 8.8.8.8 Server:8.8.8.8 Address:8.8.8.8#53 Non-authoritative answer: Name:repo1.maven.org Address: 207.223.240.88 Normally, this wouldn¹t be a problem, but the server on which my Nexus repository manager runs resides behind a firewall. My IT department requires that we firewall connections from our servers to the internet using the destination server¹s IP address. A shifting IP address requires that I keep bugging them to change the firewall rule, all while my developers are trying to download new dependencies. I wonder, was this IP address change planned? Will the IP address continue shifting in the next couple of days? How can I be notified of any changes in the future? Thanks, Paul
Re: Central Repository IP Address Change?
The ip change is part of some networking and hosting upgrades that we've undertaken to ensure the stability of the repository. We actually have 4 systems now that could be serving Central at any given time. There are 2 hosts in the UK and two virtual machines in the US (served from a 6 node cluster). The IP you see today is the one we intend to maintain going forward, but you should allow rules for the following IPs just in case things are failed over for any reason: 207.223.240.88 : US primary 207.223.240.92 : US staging / standby 89.167.251.252: UK Primary 89.167.251.253: UK standby On Thu, Mar 10, 2011 at 11:44 AM, Paul Brown paul.br...@nordstrom.com wrote: Hi, It seems the IP address for repo1.maven.org has changed twice in as many days. Last week it appeared to be 38.97.124.18. Yesterday I noticed that it had changed to 63.246.20.112. Now today I see it is 207.223.240.88. $ nslookup repo1.maven.org 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: repo1.maven.org Address: 207.223.240.88 Normally, this wouldn¹t be a problem, but the server on which my Nexus repository manager runs resides behind a firewall. My IT department requires that we firewall connections from our servers to the internet using the destination server¹s IP address. A shifting IP address requires that I keep bugging them to change the firewall rule, all while my developers are trying to download new dependencies. I wonder, was this IP address change planned? Will the IP address continue shifting in the next couple of days? How can I be notified of any changes in the future? Thanks, Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
? add dependencies to surefire plugin
Hi, I would like to add some dependencies to the surefire plugin like: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId inheritedtrue/inherited dependencies dependency groupIdorg.glassfish.appclient/groupId artifactIdgf-client/artifactId version3.1/version /dependency /dependencies /plugin /plugins /build The artifact gf-client is missing in the classpath. What is my mistake? Thanks for a tip. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ? add dependencies to surefire plugin
Does it need to be on the classpath of surefire or of your unittests? If it is the first you are on the good way. You can check with -X what the classpath for surefire is. For the second, add a normal dependency with scope test. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 9:04 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: f-client - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ? add dependencies to surefire plugin
Thanks Nick. I need the artifact in the runtime classpath for the unit test. If I declare this dependency normal with test scope, then maven (3.0.2) adds this artifact to the test-compiler classpath. Glassfishs gf-client has over hundred dependencies and so the compilation time is 500 % longer. :( On Thu, 10 Mar 2011 21:12:04 +0100 Nick Stolwijk nick.stolw...@gmail.com wrote: Does it need to be on the classpath of surefire or of your unittests? If it is the first you are on the good way. You can check with -X what the classpath for surefire is. For the second, add a normal dependency with scope test. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 9:04 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: f-client - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ? add dependencies to surefire plugin
There is an additionalClasspathElements parameter to Surefire, but I'm not sure if it will solve your problem. http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#additionalClasspathElements Hope that helps, Laird On Thu, Mar 10, 2011 at 3:22 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: Thanks Nick. I need the artifact in the runtime classpath for the unit test. If I declare this dependency normal with test scope, then maven (3.0.2) adds this artifact to the test-compiler classpath. Glassfishs gf-client has over hundred dependencies and so the compilation time is 500 % longer. :( On Thu, 10 Mar 2011 21:12:04 +0100 Nick Stolwijk nick.stolw...@gmail.com wrote: Does it need to be on the classpath of surefire or of your unittests? If it is the first you are on the good way. You can check with -X what the classpath for surefire is. For the second, add a normal dependency with scope test. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 9:04 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: f-client - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ? add dependencies to surefire plugin
Do you need all those dependencies on the runtime test classpath? The only solution I see is to use the gf-client as test dependency and start excluding all that you don't need. There is no such thing as a scope runtime-test and I don't know if this ever came up. Maybe search through Jira for it. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 9:22 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: Thanks Nick. I need the artifact in the runtime classpath for the unit test. If I declare this dependency normal with test scope, then maven (3.0.2) adds this artifact to the test-compiler classpath. Glassfishs gf-client has over hundred dependencies and so the compilation time is 500 % longer. :( On Thu, 10 Mar 2011 21:12:04 +0100 Nick Stolwijk nick.stolw...@gmail.com wrote: Does it need to be on the classpath of surefire or of your unittests? If it is the first you are on the good way. You can check with -X what the classpath for surefire is. For the second, add a normal dependency with scope test. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 9:04 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: f-client - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ? add dependencies to surefire plugin
Yes, I need this dependencies on the runtime test classpath. Thanks for the rapid help. I will try it. On Thu, 10 Mar 2011 21:30:21 +0100 Nick Stolwijk nick.stolw...@gmail.com wrote: Do you need all those dependencies on the runtime test classpath? The only solution I see is to use the gf-client as test dependency and start excluding all that you don't need. There is no such thing as a scope runtime-test and I don't know if this ever came up. Maybe search through Jira for it. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 9:22 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: Thanks Nick. I need the artifact in the runtime classpath for the unit test. If I declare this dependency normal with test scope, then maven (3.0.2) adds this artifact to the test-compiler classpath. Glassfishs gf-client has over hundred dependencies and so the compilation time is 500 % longer. :( On Thu, 10 Mar 2011 21:12:04 +0100 Nick Stolwijk nick.stolw...@gmail.com wrote: Does it need to be on the classpath of surefire or of your unittests? If it is the first you are on the good way. You can check with -X what the classpath for surefire is. For the second, add a normal dependency with scope test. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl On Thu, Mar 10, 2011 at 9:04 PM, Dipl.-Ing. Torsten Liermann l...@liermann-it.de wrote: f-client - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Dipl.-Ing. Torsten Liermann Tel: +49 151/11565077 Theodolindenplatz 2 Fax: +49 89/95449198 81545 München http://liermann-it.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
One project for jar,war and ear
Hello I have one Maven project which contains the java source code and webapp folder. Is there a way to build a JEE ear file using just this project? I have tried maven-ear-plugin but it does not work. Thanks Sonam
Ignore Parent Plugin Declaration
I have a project that needs to depend on a common root pom which declares a bunch of plugin executions that 80% of the projects need. I don't need some of the plugins though and they are slowing down my builds when running pointlessly. Some of the declare a massive amount of executions though and I don't want to have to redeclare each of them to invalid phases. I tried to use the combine.// syntax but that doesn't work: plugin groupIdorg.codehaus.mojo/groupId artifactIdsql-maven-plugin/artifactId executions combine.self=override/ // also tried with combine.children /plugin Is there any other way to do this?
Re: Ignore Parent Plugin Declaration
Many plugins have some sort of 'skip' flag you can put in the 20% cases. Or, you can rebind the execution to a nonexistent phase. On Thu, Mar 10, 2011 at 4:51 PM, Tim che...@gmail.com wrote: I have a project that needs to depend on a common root pom which declares a bunch of plugin executions that 80% of the projects need. I don't need some of the plugins though and they are slowing down my builds when running pointlessly. Some of the declare a massive amount of executions though and I don't want to have to redeclare each of them to invalid phases. I tried to use the combine.// syntax but that doesn't work: plugin groupIdorg.codehaus.mojo/groupId artifactIdsql-maven-plugin/artifactId executions combine.self=override/ // also tried with combine.children /plugin Is there any other way to do this? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ignore Parent Plugin Declaration
On Thu, Mar 10, 2011 at 4:51 PM, Tim che...@gmail.com wrote: I tried to use the combine.// syntax but that doesn't work: plugin groupIdorg.codehaus.mojo/groupId artifactIdsql-maven-plugin/artifactId executions combine.self=override/ // also tried with combine.children /plugin Interesting. Where did you hear of that? I can't find anything on the Maven site: http://www.google.com/search?q=combine.self+site:maven.apache.org -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ignore Parent Plugin Declaration
I've seen this. It was last discussed in terms of problems shifting from reporting to the new maven3 stuff. http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/ On Thu, Mar 10, 2011 at 5:19 PM, Wendy Smoak wsm...@gmail.com wrote: On Thu, Mar 10, 2011 at 4:51 PM, Tim che...@gmail.com wrote: I tried to use the combine.// syntax but that doesn't work: plugin groupIdorg.codehaus.mojo/groupId artifactIdsql-maven-plugin/artifactId executions combine.self=override/ // also tried with combine.children /plugin Interesting. Where did you hear of that? I can't find anything on the Maven site: http://www.google.com/search?q=combine.self+site:maven.apache.org -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
variable for poms. SOS
hello
i have some project, subprojects using maven.
several of them are libs for import as dependencies into my maven projects
and subprojects.
my problem is the next.
into my pom version i have the tipical 0.0.1-SNAPSHOT.
i heve 125 java project that i use frecuentry.
can i use one variable for setting it into one only place updating all the
pom files?
i have use into the setting.xml fine this:
my_projet_version1.0/my_projet_version
but if into my pom files i put the ${my_projet_version} variable it doesn't
sustitute the value
How can i make this?
i cannot change weeckly into the 125 pom files the version manually
Can yo help me?
thanks
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: ? add dependencies to surefire plugin
scope:
This element refers to the classpath of the task at
hand (compiling and runtime, testing, etc.) as well as how to limit the
transitivity of a depedency. There are five scopes available:compile
- this is the default scope, used if none is specified. Compile
dependencies are available in all classpaths. Furthermore, those
dependencies are propagated to dependent projects.provided
- this is much like compile, but indicates you expect the JDK or a
container to provide it at runtime. It is only available on the
compilation and test classpath, and is not transitive.runtime
- this scope indicates that the dependency is not required for
compilation, but is for execution. It is in the runtime and test
classpaths, but not the compile classpath.test - this
scope indicates that the dependency is not required for normal use of
the application, and is only available for the test compilation and
execution phases.system - this scope is similar to provided
except that you have to provide the JAR which contains it explicitly.
The artifact is always available and is not looked up in a
repository.systemPath:
is used only if the the dependency scope is system.
Otherwise, the build will fail if this element is set. The path must be
absolute, so it is recommended to use a property to specify the
machine-specific path (more on properties below), such as ${java.home}/lib.
Since it is assumed that system scope dependencies are installed a priori,
Maven will not check the repositories for the project, but instead
checks to ensure that the file exists. If not, Maven will fail the build
and suggest that you download and install it manually.optional:
Marks optional a dependency when this project itself is a dependency. Confused?
For example, imagine a project A that depends upon project B to compile a
portion of code that may not be used at runtime, then we may have no need for
project B for all project. So if project X adds project A as its own
dependency, then Maven will not need to install project B at all. Symbolically,
if = represents a required dependency, and -- represents optional, although
A=B may be the case when building A X=A--B would be the case when building
X.In the shortest terms, optional lets other projects know that, when you use
this project, you do not require this dependency in order to work correctly.
Nick is correct if you specify 'runtime' scope you indicate that the dependency
is not required for
compilation, but is for execution. It is in the runtime and test
classpaths, but not the compile classpath.
if you're expecting to integrate this dependency during src build... leave
scope as 'compile'
*Bedankt*
Martin
__
Note de déni et de confidentialité
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: l...@liermann-it.de
Subject: Re: ? add dependencies to surefire plugin
To: users@maven.apache.org
Date: Thu, 10 Mar 2011 21:36:32 +0100
Yes, I need this dependencies on the runtime test classpath.
Thanks for the rapid help. I will try it.
On Thu, 10 Mar 2011 21:30:21 +0100
Nick Stolwijk nick.stolw...@gmail.com wrote:
Do you need all those dependencies on the runtime test classpath? The
only solution I see is to use the gf-client as test dependency and
start excluding all that you don't need.
There is no such thing as a scope runtime-test and I don't know if
this ever came up. Maybe search through Jira for it.
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Mar 10, 2011 at 9:22 PM, Dipl.-Ing. Torsten Liermann
l...@liermann-it.de wrote:
Thanks Nick.
I need the artifact in the runtime classpath for the unit test. If I
declare this dependency normal with test scope, then maven (3.0.2) adds
this artifact to the test-compiler classpath. Glassfishs gf-client has
over hundred dependencies and so the compilation time is 500 % longer. :(
On Thu, 10 Mar 2011 21:12:04 +0100
Nick Stolwijk nick.stolw...@gmail.com wrote:
Does it need to be on the classpath of surefire or of your unittests?
If it is the first you are on the good way. You can check with -X what
the classpath for surefire is.
For the second, add a normal dependency with scope test.
Hth,
Nick Stolwijk
~Senior Java Developer~
iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl
On Thu, Mar 10, 2011 at 9:04 PM,
Re: Ignore Parent Plugin Declaration
yea I got that from another question that i asked on this list that Benjamin Bentmann helped me solve. I must have read that The combine.* attributes are however inherited along a hierarchy of POMs wrong, or was hoping it meant that I could use it with other elements beyond configuration but it doesn't seem to work here. Benson, yea I know that I could overwrite executions (thought I mentioned that in my OP) but unfortunately some of these have quite a few (5 or more) executions and overwriting them at this time doesn't guarantee that they won't add more later. On Thu, Mar 10, 2011 at 4:32 PM, Benson Margulies bimargul...@gmail.com wrote: I've seen this. It was last discussed in terms of problems shifting from reporting to the new maven3 stuff. http://www.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects/ On Thu, Mar 10, 2011 at 5:19 PM, Wendy Smoak wsm...@gmail.com wrote: On Thu, Mar 10, 2011 at 4:51 PM, Tim che...@gmail.com wrote: I tried to use the combine.// syntax but that doesn't work: plugin groupIdorg.codehaus.mojo/groupId artifactIdsql-maven-plugin/artifactId executions combine.self=override/ // also tried with combine.children /plugin Interesting. Where did you hear of that? I can't find anything on the Maven site: http://www.google.com/search?q=combine.self+site:maven.apache.org -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Missing links in site generation of multi-module project
Hi Craig, Unfortunately this depends on a couple of other releases that have to be done first (doxia, doxia-site-tools, shared-doxia-tools), so I'm afraid it's not going to happen tomorrow,... but we're working on it. Cheers, -Lukas Harpel, Craig wrote: Lukas, thanks for helping me out with this last month. Any chance 2.3 will be released soon (or a beta)? Thanks, Craig -Original Message- From: Harpel, Craig [mailto:char...@mitre.org] Sent: Wednesday, February 16, 2011 11:17 AM To: Maven Users List Subject: RE: Missing links in site generation of multi-module project Got it! Yes, I can confirm that 2.3-SNAPSHOT does indeed fix my problem. Thanks a lot!! Craig -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 11:01 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project http://maven.apache.org/guides/development/guide-testing-development-plugins.html HTH, -Lukas PS sorry, dense too :) Harpel, Craig wrote: Sorry for being dense, but I don't see a 2.3-SNAPSHOT; where can I grab it from? -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 7:49 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: variable for poms. SOS
this might be a different solution to your problem.
versions-maven-plugin@mojo
mvn versions:set -DnewVersion=...
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 10 Mar 2011 23:22, koxkorrita koxkorr...@laudio.info wrote:
hello
i have some project, subprojects using maven.
several of them are libs for import as dependencies into my maven projects
and subprojects.
my problem is the next.
into my pom version i have the tipical 0.0.1-SNAPSHOT.
i heve 125 java project that i use frecuentry.
can i use one variable for setting it into one only place updating all the
pom files?
i have use into the setting.xml fine this:
my_projet_version1.0/my_projet_version
but if into my pom files i put the ${my_projet_version} variable it
doesn't
sustitute the value
How can i make this?
i cannot change weeckly into the 125 pom files the version manually
Can yo help me?
thanks
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: variable for poms. SOS
koxkorrita wrote:
hello
i have some project, subprojects using maven.
several of them are libs for import as dependencies into my maven projects
and subprojects.
my problem is the next.
into my pom version i have the tipical 0.0.1-SNAPSHOT.
i heve 125 java project that i use frecuentry.
can i use one variable for setting it into one only place updating all the
pom files?
i have use into the setting.xml fine this:
my_projet_version1.0/my_projet_version
but if into my pom files i put the ${my_projet_version} variable it
doesn't sustitute the value
How can i make this?
i cannot change weeckly into the 125 pom files the version manually
Can yo help me?
You don't have to use variables at all. Please read
http://maven.apache.org/guides/introduction/introduction-to-dependency-
mechanism.html and in special the section about the dependencyManagement
tag.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: One project for jar,war and ear
I don't think so. You need to create a multi-module project, where you have at least one war module and one ear module. Preferably, you also move the java code to a separate jar module. /Anders On Thu, Mar 10, 2011 at 22:30, Sonam Nepali sonam.nep...@imail.org wrote: Hello I have one Maven project which contains the java source code and webapp folder. Is there a way to build a JEE ear file using just this project? I have tried maven-ear-plugin but it does not work. Thanks Sonam
