RE: How to skip tests during release:prepare?
mettez un release.properties sur le classpath qui contient les propriétés ajustées release.properties maven.test.skip=true fait cette aide? 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. > Date: Thu, 15 Jul 2010 16:57:01 -0700 > From: patrick.ren...@ericsson.com > To: users@maven.apache.org > Subject: How to skip tests during release:prepare? > > > This sounds very basic, but release:prepare insists on running the test phase > although I purposely set the -Dmaven.test.skip=true property. Problem is: I > don't want to run tests during a release and I cannot seem to find a way to > skip them. > > > Do you know of a way? > > > (Using the git scm provider) > > > Tx. > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-to-skip-tests-during-release-prepare-tp1223821p1223821.html > Sent from the Maven - Users mailing list archive at Nabble.com. _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
Re: How to skip tests during release:prepare?
Have you tried this?: -Darguments='-Dmaven.test.skip=true' -- View this message in context: http://maven.40175.n5.nabble.com/How-to-skip-tests-during-release-prepare-tp1223821p1223830.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
How to skip tests during release:prepare?
This sounds very basic, but release:prepare insists on running the test phase although I purposely set the -Dmaven.test.skip=true property. Problem is: I don't want to run tests during a release and I cannot seem to find a way to skip them. Do you know of a way? (Using the git scm provider) Tx. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-skip-tests-during-release-prepare-tp1223821p1223821.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Problem with uniqueVersion=false in 3.0 beta1
You recall correctly, uniqueSnapshots will always be true for M3 irrespective of what you try to set it to -Stephen P.S. I don't understand exactly why... I think it has something to do with Repository managers being sufficiently good that they can reclaim the disk space for you so the non-unique is no longer required. On 15 July 2010 20:28, Anders Hammar wrote: > IIRC Maven 3 only supports unique versioned snapshots (currently). There > was > some discussion easlier here on the mailing list regarding that. Search > some > archive for more info. > > /Anders > > On Thu, Jul 15, 2010 at 21:24, Adam Krieg > wrote: > > > I'm trying to configure Maven to not create unique snapshots. > > > > When using the following settings in Maven 2.2.1, this works: > > > > > >false > > > > > > > > However when I run with Maven 3.0 beta 1, I get autogenerated numbers > > appended, as if uniqueVersion was true. > > > > > > Is anyone else seeing this behavior? > > > > Disclaimer: http://pragmatrading.com/disclaimer.html > > >
Re: Problem with uniqueVersion=false in 3.0 beta1
IIRC Maven 3 only supports unique versioned snapshots (currently). There was some discussion easlier here on the mailing list regarding that. Search some archive for more info. /Anders On Thu, Jul 15, 2010 at 21:24, Adam Krieg wrote: > I'm trying to configure Maven to not create unique snapshots. > > When using the following settings in Maven 2.2.1, this works: > > >false > > > > However when I run with Maven 3.0 beta 1, I get autogenerated numbers > appended, as if uniqueVersion was true. > > > Is anyone else seeing this behavior? > > Disclaimer: http://pragmatrading.com/disclaimer.html >
Problem with uniqueVersion=false in 3.0 beta1
I'm trying to configure Maven to not create unique snapshots. When using the following settings in Maven 2.2.1, this works: false However when I run with Maven 3.0 beta 1, I get autogenerated numbers appended, as if uniqueVersion was true. Is anyone else seeing this behavior? Disclaimer: http://pragmatrading.com/disclaimer.html
Re: antrun plugin resolving properties referencing properties
it seems this is a known bug in maven-ant-tasks 2.1.0:
http://jira.codehaus.org/browse/MANTTASKS-179
please confirm that you don't have the problem when using maven-ant-tasks
2.0.9
Regards,
Hervé
Le jeudi 15 juillet 2010, Adam Krieg a écrit :
> I'm trying to access the project.build.directory property which is defined
> in my pom as
>
>
> ${project.basedir}/target
>
>
> In ant I have this setup:
>
>
>
> However when I run my ant build, outputdir is being set to the literal
> value "${project.basedir}/target" rather than antrun expanding the
> variable ${project.basedir}. Has anyone else run into this issue?
>
>
>
>
> Disclaimer: http://pragmatrading.com/disclaimer.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Running antrun plugin twice in same phase with another plugin in between?
That would mean I would have to call maven plugins from inside the maven antrun plugin. Seems odd and no idea if that is even possible? 2010/7/15 Ron Wheeler > Can't you order the tasks inside Ant? > > Ron > > On 15/07/2010 2:31 AM, Wim Deblauwe wrote: > >> I do not think this really a big improvement. In my usecase, I need to do >> 4 >> things in a defined order in the after-package, so you are just moving the >> problem. A real ordering of plugin execution during the phases is what I >> really need. I admit that I just recently had a need for it after using >> Maven 2 for more then 2 years on various (big) projects, so it is rare I >> think that you need it, but if you do, you *really* need it. >> >> 2010/7/14 Gorham-Engard, Frank >> >> Hello users, >>> I have an alternate suggestion to the phase/goal ordering issues that are >>> often raised here. >>> Allow for the specification of to include a 'before-' or 'after-' >>> prefix. >>> Users could specify the for a plugin execution to be, for >>> example, >>> 'before-deploy' or 'after-package'. This wouldn't break the life-cycle >>> model >>> while permitting a constrained method for expanding it. >>> Also, any 'after-' phases should be executed when the phase is the >>> target. >>> For example, if I specified a plugin for 'after-deploy' it would be >>> executed >>> (at the end) when the command line was 'mvn deploy'. >>> Perhaps even 'before-before-test' should be allowed as well? But not >>> 'before-after-test', let's not go there! >>> >>> >> From: Wim Deblauwe [mailto:wim.debla...@gmail.com] >>> Sent: Tuesday, July 13, 2010 5:10 AM >>> To: Maven Users List >>> Subject: Running antrun plugin twice in same phase with another plugin in >>> between? >>> >>> Hi, >>> >>> I need to run the antrun plugin twice in the packaging phase. I found >>> this >>> on the wiki: >>> http://docs.codehaus.org/display/MAVENUSER/MiniGuide-AntMultiPhase >>> >>> However, it speaks of different lifecycle phases. I tried with the same >>> phase and that works, however, I need to run another plugin in between. >>> Is >>> this possible? >>> >>> I was hoping that all plugins' executions would be sorted by their id. >>> That >>> way, i could use id's like 'step-1-do-something', >>> 'step-2-do-something-else', to force a certain order of plugin execution. >>> >>> regards, >>> >>> Wim >>> >>> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Running all tests in a package
On Thu, Jul 15, 2010 at 9:46 AM, Karan Malhi wrote: > I did try the naming pattern, something like > mvn test -Dtest=Check* > However, I have inner classes in my test cases and some of them start with > the word Check. Surefire starts thinking that the inner class is also a test > case and errors out because it cannot find a test method to run If you want to dig into the source, it probably wouldn't be too hard to add another parameter like -DtestPkg=..., or to modify the -Dtest=... one to understand a different pattern that means match on a package. -Dtest=pkg:org.example.stuff . See if there's already something in JIRA, if not you can add it and then post to the dev list to discuss it with the developers to see if they'd be receptive to such a patch. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven claims to try a repo, but doesn't
I would suggest moving to the free version of Nexus. This will greatly simplify your management of Maven. It only takes a couple of hours to get set up for a small development team. Ron On 15/07/2010 9:58 AM, Charles Brown wrote: All, I have two maven 2 repos, internal and external. internal holds my releases, while external holds artifacts mirrored from central. When I compile, maven try to download one of my internal artifacts and fails, printing this; Downloading: http://path/to/my/repository/external//path/to/my/artifact/version/pom [INFO] Unable to find resource 'path:to:my:artifact:version' in repository external (http://path/to/my/repository/external/) Downloading: http://path/to/my/repository/external//path/to/my/artifact/version/pom [INFO] Unable to find resource 'path:to:my:artifact:version' in repository internal (http://path/to/my/repository/internal/) When I build a URL from the printed information, my artifact is indeed in the internal repository at; http://path/to/my/repository/internal//path/to/my/artifact/version/pom That is, maven claims to have tried internal, but it didn't, really. It hit external twice. My repository configuration is detailed below. What am I doing wrong? My maven is Apache Maven 2.2.1 (rdebian-1) Java version: 1.6.0_20 My settings.xml has external http://path/to/my/repository/external/ external:* default true external External/Remote Repositories http://path/to/my/repository/external/ ... internal Internal/CM Repository http://path/to/my/repository/internal/ ... My pom.xml has ... internal http://path/to/my/repository/internal/ - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - - 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 claims to try a repo, but doesn't
On 15/07/2010, at 11:58 PM, Charles Brown wrote: > That is, maven claims to have tried internal, but it didn't, really. It hit > external twice. > > My repository configuration is detailed below. What am I doing wrong? > > My maven is > > Apache Maven 2.2.1 (rdebian-1) > Java version: 1.6.0_20 > > My settings.xml has > > > > external > http://path/to/my/repository/external/ > external:* > > You've mapped all repositories to external here. Note that "external:*" doesn't have any correlation to your IDs, it just means "any that aren't file://...". try external:*,!internal instead, or set up a repository manager at the mirror location and have it manage requests between the two. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven claims to try a repo, but doesn't
All, I have two maven 2 repos, internal and external. internal holds my releases, while external holds artifacts mirrored from central. When I compile, maven try to download one of my internal artifacts and fails, printing this; Downloading: http://path/to/my/repository/external//path/to/my/artifact/version/pom [INFO] Unable to find resource 'path:to:my:artifact:version' in repository external (http://path/to/my/repository/external/) Downloading: http://path/to/my/repository/external//path/to/my/artifact/version/pom [INFO] Unable to find resource 'path:to:my:artifact:version' in repository internal (http://path/to/my/repository/internal/) When I build a URL from the printed information, my artifact is indeed in the internal repository at; http://path/to/my/repository/internal//path/to/my/artifact/version/pom That is, maven claims to have tried internal, but it didn't, really. It hit external twice. My repository configuration is detailed below. What am I doing wrong? My maven is Apache Maven 2.2.1 (rdebian-1) Java version: 1.6.0_20 My settings.xml has external http://path/to/my/repository/external/ external:* default true external External/Remote Repositories http://path/to/my/repository/external/ ... internal Internal/CM Repository http://path/to/my/repository/internal/ ... My pom.xml has ... internal http://path/to/my/repository/internal/ - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Running all tests in a package
Thanks Wendy, I did try the naming pattern, something like mvn test -Dtest=Check* However, I have inner classes in my test cases and some of them start with the word Check. Surefire starts thinking that the inner class is also a test case and errors out because it cannot find a test method to run On Thu, Jul 15, 2010 at 9:29 AM, Wendy Smoak wrote: > On Thu, Jul 15, 2010 at 9:21 AM, Karan Malhi > wrote: > > Is it possible to only run all tests contained in a specific package? > > You can configure includes/excludes in the Surefire plugin. > > http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html > > I guess you want to do this on the command line though. I'm only > aware of -Dtest=... which iirc matches on the class, not the package. > > http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html > I suppose if you had a naming pattern per package you could get them > that way. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Karan Singh Malhi
Re: Using Eclipse without maven plugin (multiple module project)
Galileo - http://download.eclipse.org/releases/galileo This update site should already be set up for you. Just select Subversive The Subversive plug-in will help you get the connectors when you restart STS. Ron On 15/07/2010 6:50 AM, Bahadýr Konu wrote: I downloaded STS Eclipse. No SVN plugin is included it seems. Which SVN plugin are you using with STS? Subversive? Thanks. Bahadır --- On Tue, 7/13/10, Ron Wheeler wrote: From: Ron Wheeler Subject: Re: Using Eclipse without maven plugin (multiple module project) To: "Maven Users List" Date: Tuesday, July 13, 2010, 9:23 PM On 13/07/2010 2:19 PM, Antonio Petrelli wrote: 2010/7/13 Bahadýr Konu: I have created my multi-module project and checked in to SVN I checked out the project to a directory, ran "mvn eclipse:eclipse" then I import the project to Eclipse (import existing project) Try using m2eclipse, it's a life-saver. Remember to install the Subversion-m2eclipse integration that is available in the "extras" repository: http://m2eclipse.sonatype.org/ Checkout using "Check out as Maven project". Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org STS Eclipse has this already built-in. Ron - 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: Running all tests in a package
On Thu, Jul 15, 2010 at 9:21 AM, Karan Malhi wrote: > Is it possible to only run all tests contained in a specific package? You can configure includes/excludes in the Surefire plugin. http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html I guess you want to do this on the command line though. I'm only aware of -Dtest=... which iirc matches on the class, not the package. http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html I suppose if you had a naming pattern per package you could get them that way. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Running antrun plugin twice in same phase with another plugin in between?
Can't you order the tasks inside Ant? Ron On 15/07/2010 2:31 AM, Wim Deblauwe wrote: I do not think this really a big improvement. In my usecase, I need to do 4 things in a defined order in the after-package, so you are just moving the problem. A real ordering of plugin execution during the phases is what I really need. I admit that I just recently had a need for it after using Maven 2 for more then 2 years on various (big) projects, so it is rare I think that you need it, but if you do, you *really* need it. 2010/7/14 Gorham-Engard, Frank Hello users, I have an alternate suggestion to the phase/goal ordering issues that are often raised here. Allow for the specification of to include a 'before-' or 'after-' prefix. Users could specify the for a plugin execution to be, for example, 'before-deploy' or 'after-package'. This wouldn't break the life-cycle model while permitting a constrained method for expanding it. Also, any 'after-' phases should be executed when the phase is the target. For example, if I specified a plugin for 'after-deploy' it would be executed (at the end) when the command line was 'mvn deploy'. Perhaps even 'before-before-test' should be allowed as well? But not 'before-after-test', let's not go there!
Running all tests in a package
Is it possible to only run all tests contained in a specific package? -- Karan Singh Malhi
Maven release plugin (2.0) - mvn:rollback on flat multi-modules structure
Hi, I have a flat project layout, with one parent(parent-flat) and two modules (module1-flat and module2-flat). In my parent's pom, I have : ../module1-flat ../module2-flat + scm connection For each modules, I just have : parent-flat mygroupid 0.0.1-SNAPSHOT module1-flat My SVN structure looks like this : - branches - tags - trunk |-flat-multimodules |- module1-flat |- module2-flat |- parent-flat To make a release, I have to do mvn release:prepare -DcommitByProject=true (if I ommit commitByProject, it doesn't work) Then a mvn:release perform I obtain in SVN : - branches - tags |-parent-flat-0.0.1 |- module1-flat |- module2-flat |- parent-flat - trunk |-flat-multimodules |- module1-flat |- module2-flat |- parent-flat If I want to do a mvn release:rollback, I have the following error message : ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: '/workspace' is not a working copy I tried to add -DcommitByProject=true, but the result is the same. Have you an idea to solve this problem ? Thanks in advance. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using Eclipse without maven plugin (multiple module project)
I downloaded STS Eclipse. No SVN plugin is included it seems. Which SVN plugin are you using with STS? Subversive? Thanks. Bahadır --- On Tue, 7/13/10, Ron Wheeler wrote: From: Ron Wheeler Subject: Re: Using Eclipse without maven plugin (multiple module project) To: "Maven Users List" Date: Tuesday, July 13, 2010, 9:23 PM On 13/07/2010 2:19 PM, Antonio Petrelli wrote: > 2010/7/13 Bahadýr Konu: >> I have created my multi-module project and checked in to SVN >> I checked out the project to a directory, ran "mvn eclipse:eclipse" >> then I import the project to Eclipse (import existing project) > Try using m2eclipse, it's a life-saver. Remember to install the > Subversion-m2eclipse integration that is available in the "extras" > repository: > http://m2eclipse.sonatype.org/ > Checkout using "Check out as Maven project". > > Antonio > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > STS Eclipse has this already built-in. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
