maven-checkstyle-plugin does not include test resources
The documentation says it includes these resources by default, but apparently it never does. After examining the code, it seems CheckstyleViolationCheckMojo.execute() forgets to call request.setTestResources(), hence that is always null and skipped from audit. I wanted to file a report on JIRA, but it seems codehaus is shutting down and i cannot add new issues anymore. :S -- View this message in context: http://maven.40175.n5.nabble.com/maven-checkstyle-plugin-does-not-include-test-resources-tp5835797.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-checkstyle-plugin does not include test resources
On Monday, 25 May 2015 at 09:46, WonderCsabo wrote: The documentation says it includes these resources by default, but apparently it never does. After examining the code, it seems CheckstyleViolationCheckMojo.execute() forgets to call request.setTestResources(), hence that is always null and skipped from audit. I wanted to file a report on JIRA, but it seems codehaus is shutting down and i cannot add new issues anymore. :S FYI, you can log new issues at https://issues.apache.org/jira/browse/MCHECKSTYLE See also https://maven.apache.org/issue-tracking.html and https://maven.apache.org/plugins/index.html for updated links to the new JIRA projects -- View this message in context: http://maven.40175.n5.nabble.com/maven-checkstyle-plugin-does-not-include-test-resources-tp5835797.html Sent from the Maven - Users mailing list archive at Nabble.com (http://Nabble.com). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org (mailto:users-unsubscr...@maven.apache.org) For additional commands, e-mail: users-h...@maven.apache.org (mailto:users-h...@maven.apache.org)
Re: maven-checkstyle-plugin does not include test resources
Thanks! I created this https://issues.apache.org/jira/browse/MCHECKSTYLE-295 ticket. I guess the maven checkstyle plugin POM should be updated to refer to the new location of the JIRA.
what is the difference between failsafe's integration test and verify?
hi, I'm new to failsafe, i'm starting to move a test case from unit test to integration test, and i'm using plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-failsafe-plugin/artifactId executions execution idintegration-tests/id phaseintegration-test/phase goals goalintegration-test/goal goalverify/goal /goals /execution /executions in my pom. When I run mvn verify, I found my new integration test ran twice. I realized that both the integration-test and verify goal may contribute to it. Should I remove the line goalverify/goal in pom? But It seems most failsafe tutorials keeps both goals in their poms. The question is, what are these two goals for? The official explanation: *integration-test for running the integration tests.* *verify for checking the results of the integration tests.* seems so vague to me. Can any expert give me a concrete example? thanks! -- Regards, *Bin Mahone | 马洪宾* Apache Kylin: http://kylin.io Github: https://github.com/binmahone
Re: what is the difference between failsafe's integration test and verify?
failsafe:integration-test runs the tests and stores whether the tests passed or failed in a file failsafe:verify reads back that file and then if there were failing tests it fails the build. On 25 May 2015 at 15:06, hongbin ma mahong...@apache.org wrote: hi, I'm new to failsafe, i'm starting to move a test case from unit test to integration test, and i'm using plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-failsafe-plugin/artifactId executions execution idintegration-tests/id phaseintegration-test/phase goals goalintegration-test/goal goalverify/goal /goals /execution /executions in my pom. When I run mvn verify, I found my new integration test ran twice. I realized that both the integration-test and verify goal may contribute to it. Should I remove the line goalverify/goal in pom? But It seems most failsafe tutorials keeps both goals in their poms. The question is, what are these two goals for? The official explanation: *integration-test for running the integration tests.* *verify for checking the results of the integration tests.* seems so vague to me. Can any expert give me a concrete example? thanks! -- Regards, *Bin Mahone | 马洪宾* Apache Kylin: http://kylin.io Github: https://github.com/binmahone
Re: what is the difference between failsafe's integration test and verify?
To put the question in another way, what is being verified at all? -- Regards, *Bin Mahone | 马洪宾* Apache Kylin: http://kylin.io Github: https://github.com/binmahone
maven-stage-plugin clarification questions
Hi, I would like to know more on how to copy a specific artifact using the stage:copy goal of maven-stage-plugin. The usage example shows source/target repositories, repository IDs and a version number, but does not list an artifact. How do I specify the artifact? Seeing a pom file would help me a lot, I am not a regular maven user. Also, sometimes there are multiple artifacts under the same version. How do I specify that all of them should be copied? Lastly, the usage page says that everything from the source URL is copied. Is this still true? I am interested in having a single version of an artifact set being copied, not all of them. I am looking at the right plugin for what I attempt to do? Thanks, Martin
Re: maven-stage-plugin clarification questions
Hi Martin You may want to list out your use case without drilling into staging plugin. There are a number of plugins that can do the copy job -Dan On Mon, May 25, 2015 at 11:50 AM, d'Anjou, Martin mdan...@ciena.com wrote: Hi, I would like to know more on how to copy a specific artifact using the stage:copy goal of maven-stage-plugin. The usage example shows source/target repositories, repository IDs and a version number, but does not list an artifact. How do I specify the artifact? Seeing a pom file would help me a lot, I am not a regular maven user. Also, sometimes there are multiple artifacts under the same version. How do I specify that all of them should be copied? Lastly, the usage page says that everything from the source URL is copied. Is this still true? I am interested in having a single version of an artifact set being copied, not all of them. I am looking at the right plugin for what I attempt to do? Thanks, Martin
RE: maven-stage-plugin clarification questions
Hi Dan, I am trying to implement a build promotion script to promote a single version of an artifact set from one maven repository to another. The promotion phase does not build, it simply promotes existing artifacts. I also just found the http://mojo.codehaus.org/wagon-maven-plugin/, so I am looking at that too. Martin -Original Message- From: Dan Tran [mailto:dant...@gmail.com] Sent: May-25-15 2:57 PM To: Maven Users List Subject: Re: maven-stage-plugin clarification questions Hi Martin You may want to list out your use case without drilling into staging plugin. There are a number of plugins that can do the copy job -Dan On Mon, May 25, 2015 at 11:50 AM, d'Anjou, Martin mdan...@ciena.com wrote: Hi, I would like to know more on how to copy a specific artifact using the stage:copy goal of maven-stage-plugin. The usage example shows source/target repositories, repository IDs and a version number, but does not list an artifact. How do I specify the artifact? Seeing a pom file would help me a lot, I am not a regular maven user. Also, sometimes there are multiple artifacts under the same version. How do I specify that all of them should be copied? Lastly, the usage page says that everything from the source URL is copied. Is this still true? I am interested in having a single version of an artifact set being copied, not all of them. I am looking at the right plugin for what I attempt to do? Thanks, Martin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-stage-plugin clarification questions
There is very little work being done on the maven-stage-plugin. Repository managers such as Nexus and Artifactory provide staging support nowadays, which is what is used by Apache projects for example. I would therefore strongly suggest you look at that instead of using this plugin, as should you run into missing functionality (or a bug) a fix for that could take some time (if it will ever happen). Having said that, staging support in Nexus (and Artifactory I think) is only available in the commercial version not the free community version. /Anders On Mon, May 25, 2015 at 9:12 PM, d'Anjou, Martin mdan...@ciena.com wrote: Hi Dan, I am trying to implement a build promotion script to promote a single version of an artifact set from one maven repository to another. The promotion phase does not build, it simply promotes existing artifacts. I also just found the http://mojo.codehaus.org/wagon-maven-plugin/, so I am looking at that too. Martin -Original Message- From: Dan Tran [mailto:dant...@gmail.com] Sent: May-25-15 2:57 PM To: Maven Users List Subject: Re: maven-stage-plugin clarification questions Hi Martin You may want to list out your use case without drilling into staging plugin. There are a number of plugins that can do the copy job -Dan On Mon, May 25, 2015 at 11:50 AM, d'Anjou, Martin mdan...@ciena.com wrote: Hi, I would like to know more on how to copy a specific artifact using the stage:copy goal of maven-stage-plugin. The usage example shows source/target repositories, repository IDs and a version number, but does not list an artifact. How do I specify the artifact? Seeing a pom file would help me a lot, I am not a regular maven user. Also, sometimes there are multiple artifacts under the same version. How do I specify that all of them should be copied? Lastly, the usage page says that everything from the source URL is copied. Is this still true? I am interested in having a single version of an artifact set being copied, not all of them. I am looking at the right plugin for what I attempt to do? Thanks, Martin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
setup a (end user) website for maven project
What’s a simple way to set up a website for a couple of related maven projects that has documentation, examples, howtos, and the like? I don’t want to publish the gory details of the build there, but something “pretty” and informative for the end users of the libraries. I’m thinking of putting together a Makefile that invokes maven (for JavaDoc purposes), and jekyll (for the rest of the documentation) and knows how to rsync to the host. But I’m hoping there’s a simpler way. E.g. I would love to avoid having to write code that keeps JavaDoc output for different project versions in different directories (so users can choose which version of the JavaDoc to browse) etc. It seems I can’t be the first person who wants to do this? I looked at what the log4j guys do, but from what I can tell, maven only generates some of the content on that site. All pointers appreciated. Thanks, Johannes. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
