RE: maven-compiler (any version)
Like any other maven dependency or plugin, it lives in an artifact repository. Specifically, in central [1]. There you'll see generally available versions. [1] http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/ -Original Message- From: Martin Gainty [mailto:mgai...@hotmail.com] Sent: Tuesday, August 18, 2009 9:17 AM To: users@maven.apache.org Subject: maven-compiler (any version) anyone know where maven-compiler (any version) is? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité 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. 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. _ With Windows Live, you can organize, edit, and share your photos. http://www.windowslive.com/Desktop/PhotoGallery -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: exclude transitive dependency
Check out http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html -Original Message- From: tubin gen [mailto:fachh...@gmail.com] Sent: Thursday, May 07, 2009 11:52 AM To: users@maven.apache.org Subject: exclude transitive dependency My project needs spring-modules-osworklow.jar , this module has dependency to spring-mock , the spring-mock has the same classes as spring-test and this has more classes , so I want to exclude transitive dependency for spring-mock , please tell me how to do this ? -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Exclude dependency from scope runtime test classpath
Can the tests be in a separate jar? If so they could include the original jar with the code to test but exclude dependencies as needed. Steven -Original Message- From: Henrik [mailto:hen...@team11.org] Sent: Thursday, May 07, 2009 6:04 AM To: users@maven.apache.org Subject: Exclude dependency from scope runtime test classpath Hi, I was wondering if there is a way to remove a dependency from the test classpath when using runtime I want to make sure that the jar file is only used when running the application and not when testing it. So it really comes down to, I want to have the dependency (jar file) but i don't want to add it to compile or test classpath. Thanks, Henrik - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: [maven-eclipse-plugin] Define compiler options in POM
You can actually configure maven-eclipse-plugin [1] to generate specific files into the .settings folder on eclipse:eclipse. I think you have to be able to specify the entire contents of the file being written, but here is an example: org.apache.maven.plugins maven-eclipse-plugin 2.5.1 ... .settings/org.eclipse.core.resources.prefs See the mojo ref for more specifics. [1] http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html -Original Message- From: Daniele Dellafiore [mailto:ilde...@gmail.com] Sent: Wednesday, March 04, 2009 8:31 AM To: Maven Users List Subject: Re: [maven-eclipse-plugin] Define compiler options in POM On Wed, Mar 4, 2009 at 3:24 PM, Todd Thiessen wrote: > I don't know if the plugin can do that. Have you tried passing in specific > compiler arguments in the configuration of the plugin? I have no idea on how to do this... > I use workspace settings to do what you are asking but I am curious if the > compiler plugin could do this at the project level too. yep, but to avoid reconfigure every machine on every new change, the best solution is to share in svn b y sharing eclipse .settings folders. Unfortunately, there is no options to avoid m-e-p to ignore the settings... > > --- > Todd Thiessen > > >> -Original Message- >> From: Daniele Dellafiore [mailto:ilde...@gmail.com] >> Sent: Wednesday, March 04, 2009 9:19 AM >> To: Maven Users List >> Subject: Re: [maven-eclipse-plugin] Define compiler options in POM >> >> That is easy, I am talking about all the others: >> >> org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning >> org.eclipse.jdt.core.compiler.problem.autoboxing=warning >> org.eclipse.jdt.core.compiler.problem.deprecation=warning >> org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedC >> ode=disabled >> >> and so on... >> >> On Wed, Mar 4, 2009 at 3:13 PM, Todd Thiessen >> wrote: >> > maven-compiler-plugin >> > >> > >> > maven-compiler-plugin >> > >> > 1.5 >> > 1.5 >> > >> > >> > >> > --- >> > Todd Thiessen >> > >> > >> >> -Original Message- >> >> From: Daniele Dellafiore [mailto:ilde...@gmail.com] >> >> Sent: Wednesday, March 04, 2009 9:10 AM >> >> To: Maven Users List >> >> Subject: [maven-eclipse-plugin] Define compiler options in POM >> >> >> >> Hi all. >> >> >> >> Hi have this issue: every time I run mvn eclipse:eclipse the >> >> .settings folder of the project is cleaned and I lose my project >> >> specific compiler settings. I would like to keep them or >> at least be >> >> able to define them in the POM. >> >> >> >> What solution do you suggest? I have not found any on the web... >> >> >> >> -- >> >> Daniele Dellafiore >> >> http://blog.ildella.net/ >> >> >> >> >> - >> >> 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 >> > >> > >> >> >> >> -- >> Daniele Dellafiore >> http://blog.ildella.net/ >> >> - >> 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 > > -- Daniele Dellafiore http://blog.ildella.net/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. - To unsubsc
RE: Re: Functional Test strategies with Maven
Trying to achieve consistency between organizations ahead of time could prove difficult. I would instead suggest trying for consistency within your organization and sharing notes about what worked and what didn't either on this mailing list or perhaps the Maven wiki. Perhaps that could help provide feedback for if/when integration testing is officially supported. /S -Original Message- From: martijnverb...@gmail.com [mailto:martijnverb...@gmail.com] Sent: Monday, March 02, 2009 11:26 AM To: users@maven.apache.org Subject: Re: Re: Functional Test strategies with Maven Hi David, > Martijn - I've seen this done a couple of different ways. I can't say > that there is any particular set of advantages/disadvantages that makes > one more attractive than another. I'm sure > you've already thought about these, but here they are, just the same: > #1 - The functional tests are named with a specific suffix (ex. _FT) so > that they can be included/excluded by profile. They still live in the > src/test/java tree alongside the unit tests. In > this case, you must explicitly include and/or exclude tests based on a > pattern matching their class names. > #2 - Place all of your functional tests in a different source tree (ex. > src/functionalTest/java). As with #1, you have to do some include/exclude > type work, but in this case, you only > have to do so on your profile that runs the functional tests. However, > you also have to make sure to include this tree on your compilation. > So, IMHO, there's no clear winner. I've been dealing with similar > problems lately for Integration Tests that actually start up my web app > and test it using Selenium. I have the same > set of problems. I think I read that there are plans to enhance Maven > with the knowledge of functional/integration tests, but I don't know what > the timing for any such change is. Thanks David, this helps (along with Ian's comments) confirm that there is currently no 'official' Maven life-cycle support for these types of tests (yet), hopefully as long as we're consistent in our approach any of the suggested solutions will be more than adequate :). Cheers, Martijn PS: I will also post separately about the 'true' integration tests scenario (where we have tests that can be JUnit run but involve many modules and/or projects and can also have 3rd party requirements such as a J2EE server up and running). > The specific purpose in this case is to ensure that we've wired up > messaging flow(s) within our module. This is done by sending a mocked > event > through the various routers/transformers etc that we have. They're not > unit > tests because they're not testing a discrete bit of functionality within a > Java class. > However, it is vital that these tests pass before we package that module, > so I we want to run them as part of a the test life-cycle (as opposed to > integration-test which is post package) or at least a life-cycle phase > that > is before package. > I agree that we could use profiles to run this group of tests separately, > but I'd like to understand where they should live in the source structure. > All of the Maven literature that I have read talks of > name>-->test-->src-->java being used for unit tests, but tests such as > mine > fall into a grey area? > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
