Re: Jococo report using Jenkins without the need to configure jacoco-maven-plugin? possible?
Now I have a better understanding of jacoco, jenkins, and maven integration. Thank your both. It works!!! -D On Wed, Aug 6, 2014 at 7:59 AM, Arnaud Héritier wrote: > something like this works for me : > > mvn org.jacoco:jacoco-maven-plugin:0.7.1.201405082137:prepare-agent verify > > + > > sonar runner as post build > > > > On Wed, Aug 6, 2014 at 4:31 PM, Justin Georgeson > wrote: > > > I believe you still need to configure jacoco-maven-plugin so that your > > tests are run with instrumentation, but you don't need to do the > reporting > > part with maven. Jenkins will read the .exec file that Jacoco generates > > during test execution and publish reports from that. > > > > > -Original Message- > > > From: Dan Tran [mailto:dant...@gmail.com] > > > Sent: Tuesday, August 05, 2014 9:31 PM > > > To: Maven Users List > > > Subject: Jococo report using Jenkins without the need to configure > > jacoco- > > > maven-plugin? possible? > > > > > > Hello, > > > > > > I have an impression that I dont need bring in jacoco-maven-plugin to > my > > > poms, and just have Jenkins to run it at post build and magic will > > happen at > > > Jenkins page. > > > > > > So far, I have no luck with that > > > > > > Any got this working? > > > > > > Thanks > > > > > > -Dan > > > > -- > > This e-mail, including any attached files, may contain confidential and > > privileged information for the sole use of the intended recipient. Any > > review, use, distribution, or disclosure by others is strictly > prohibited. > > If you are not the intended recipient (or authorized to receive > > information for the intended recipient), please contact the sender by > reply > > e-mail and delete all copies of this message. > > > > > > -- > - > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier >
Re: maven-release-plugin: multi module project with multiple git repositories
Short answer: no, that's not possible. The plugin assumes that every svn-folder or git-repository is a complete project with its own release-cycle. thanks, Robert Op Wed, 06 Aug 2014 18:24:42 +0200 schreef Henning Moll : Hi, i wonder if it's possible to use the maven-release-plugin for a project where each child project is served by a different git repository: root - pom.xml [stored in git1] child1 - pom.xml [stored in git2] child2 - pom.xml [stored in git3] I searched the web for hours because there are some promising (?) comments in https://jira.codehaus.org/browse/MRELEASE-627?focusedCommentId=247308&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-247308 Unfortunately all my experiments so far failed... I am subscribed to the list. Best regards Henning - 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: local repository permissions
> How can I get maven to create directories and files with world writeable > permissions > when it is downloading or installing to the local ~/.m2 repository ? Most likely you are attempting to do something that Maven does not want you to do - the ~/.m2 repo is not designed to be shared. Describe your use case more. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-release-plugin: multi module project with multiple git repositories
Hi, i wonder if it's possible to use the maven-release-plugin for a project where each child project is served by a different git repository: root - pom.xml [stored in git1] child1 - pom.xml [stored in git2] child2 - pom.xml [stored in git3] I searched the web for hours because there are some promising (?) comments in https://jira.codehaus.org/browse/MRELEASE-627?focusedCommentId=247308&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-247308 Unfortunately all my experiments so far failed... I am subscribed to the list. Best regards Henning - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Jococo report using Jenkins without the need to configure jacoco-maven-plugin? possible?
something like this works for me : mvn org.jacoco:jacoco-maven-plugin:0.7.1.201405082137:prepare-agent verify + sonar runner as post build On Wed, Aug 6, 2014 at 4:31 PM, Justin Georgeson wrote: > I believe you still need to configure jacoco-maven-plugin so that your > tests are run with instrumentation, but you don't need to do the reporting > part with maven. Jenkins will read the .exec file that Jacoco generates > during test execution and publish reports from that. > > > -Original Message- > > From: Dan Tran [mailto:dant...@gmail.com] > > Sent: Tuesday, August 05, 2014 9:31 PM > > To: Maven Users List > > Subject: Jococo report using Jenkins without the need to configure > jacoco- > > maven-plugin? possible? > > > > Hello, > > > > I have an impression that I dont need bring in jacoco-maven-plugin to my > > poms, and just have Jenkins to run it at post build and magic will > happen at > > Jenkins page. > > > > So far, I have no luck with that > > > > Any got this working? > > > > Thanks > > > > -Dan > > -- > This e-mail, including any attached files, may contain confidential and > privileged information for the sole use of the intended recipient. Any > review, use, distribution, or disclosure by others is strictly prohibited. > If you are not the intended recipient (or authorized to receive > information for the intended recipient), please contact the sender by reply > e-mail and delete all copies of this message. > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
RE: Jococo report using Jenkins without the need to configure jacoco-maven-plugin? possible?
I believe you still need to configure jacoco-maven-plugin so that your tests are run with instrumentation, but you don't need to do the reporting part with maven. Jenkins will read the .exec file that Jacoco generates during test execution and publish reports from that. > -Original Message- > From: Dan Tran [mailto:dant...@gmail.com] > Sent: Tuesday, August 05, 2014 9:31 PM > To: Maven Users List > Subject: Jococo report using Jenkins without the need to configure jacoco- > maven-plugin? possible? > > Hello, > > I have an impression that I dont need bring in jacoco-maven-plugin to my > poms, and just have Jenkins to run it at post build and magic will happen at > Jenkins page. > > So far, I have no luck with that > > Any got this working? > > Thanks > > -Dan -- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
Shade plugin: Shade more than one artifact
Hi there, first, apologies, if I am on the wrong list for this topic, maybe there is a more specific list, so feel free to point me towards it. I am currently trying to persuade the shade plugin to actually shade more than one artifact. My goal is to create two different test jars. One, which contains only the needed infrastructure to use in other projects and another one, that includes all the tests of the current project, so I can take that jar, unpack it in another project and run all the tests in the scope of that project (this is used for a plugin the main project, to make sure, that this plugin does not accidentally remove features needed for normal functioning). The plugin cannot be merged or created as a sub-module of the main project, from which I want to create the jars. My current (non-working) workflow is to create two jars using the maven-jar-plugin and let the shade plugin do its work, which it does only with the default jar. My current workaround is to have a default mvn profile which creates the slim test jar and another one, which creates the fat test jar - however I would like to built both at the same time and deploy them. The pom.xml from my current workaround can be found at https://github.com/spinscale/elasticsearch/blob/build/test-jar-profiles/pom.xml#L1501-L1632 I'd love to get some feedback if this is possible at all using the shade plugin, or if my approach is bad and I am supposed to do something completely different. Thanks a lot and have a nice day! --Alex
Re: How to avoid unzip of large test data on each "mvn test"
Thanks Graham, this makes a lot of sense and I totally agree this would be the best. But as I also have to convince colleagues and to make compromises I hope maybe someone knew a magical plugin ;) and no, the data I work with is large and a whole and people do not want to work with a small subset :/ -- View this message in context: http://maven.40175.n5.nabble.com/How-to-avoid-unzip-of-large-test-data-on-each-mvn-test-tp5801435p5801741.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
