jdocbook

What is the way to exclude this fucking lame and useless jdocbook from build ?

Usage of self written plugin - Maven wants to download JAR of the parent

Hi, My collegue and me wrote a plugin to trigger a Jenkins Job (which runs in an external site and signs our artifact) and download the result artifact of that Jenkins build. When I configure that plugin into our productive build config, maven wants to download the jar artifact of the plugins

Re: Usage of self written plugin - Maven wants to download JAR of the parent

Have you added this parent pom as a dependency? Parent-poms ahould onlybe specified with tag parent and not via dependency.

Re: Emma coverage

If I add this configuration aggregatetrue/aggregate outputDirectory../target/outputDirectory /configuration I have the outut of the classes but not for the coverage.em produced in

Re: Emma coverage

probably the solution is : configuration forkModeonce/forkMode metadataFile../target/coverage.em/metadataFile

AW: Usage of self written plugin - Maven wants to download JAR of the parent

Hi, Nope, I even checked the transitive dependencies of my plugin. It just have third party/open source dependencies. Greetings Jens -Ursprüngliche Nachricht- Von: martin.eisengardt [mailto:martin.eisenga...@googlemail.com] Gesendet: Donnerstag, 14. Juni 2012 09:53 An: Maven Users

AW: Usage of self written plugin - Maven wants to download JAR of the parent

I found my problem... copy and paste error... just copied the parents artifactId/groupId instead of the plugins artifact and groupId. That was the last thing I thought what had happened. -Ursprüngliche Nachricht- Von: jens.baitin...@bosch-si.com [mailto:jens.baitin...@bosch-si.com]

Re: Emma coverage

But not produce coverage.ec after deploy on application server -- View this message in context: http://maven.40175.n5.nabble.com/Emma-coverage-tp5711249p5711296.html Sent from the Maven - Users mailing list archive at Nabble.com.

Re: Emma coverage

solved.. -- View this message in context: http://maven.40175.n5.nabble.com/Emma-coverage-tp5711249p5711297.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail:

Re: Emma coverage

Please tell us... How? Wayne On Thursday, June 14, 2012, cortes wrote: solved.. -- View this message in context: http://maven.40175.n5.nabble.com/Emma-coverage-tp5711249p5711297.html Sent from the Maven - Users mailing list archive at Nabble.com.

Re: jdocbook

And you may be polite ... The jdocbook plugin isn't developed by the ASF team but I confirm (at least before) that it was annoying to use because it defines a custom packaging, thus you need to configure it and it has no option to be skipped. The only solution is to skip its module by defining it

Re: jdocbook

ok this is too funny. had to share with the list. my reply resulted in a bounce back from a list subscriber @ cme group due to a naughty word which i changed so this email will not bounce again... -- Forwarded message -- From: forefrontserversecurity-smapexh...@cmegroup.com

Re: jdocbook

Yea. They can insult us but not in the other direction ;) Le 14 juin 2012 à 16:40, Wayne Fay wayne...@gmail.com a écrit : ok this is too funny. had to share with the list. my reply resulted in a bounce back from a list subscriber @ cme group due to a naughty word which i changed so

Re: jdocbook

Re-post Le 14 juin 2012 à 16:36, Arnaud Héritier aherit...@gmail.com a écrit : And you may be polite ... The jdocbook plugin isn't developed by the ASF team but I confirm (at least before) that it was annoying to use because it defines a custom packaging, thus you need to configure it and it

Plugin execution not covered by lifecycle configuration

I am using eclipse 3.7.1, with m2eclipse 1.0.1. I have followed this guide to create a maven-plugin: http://maven.apache.org/guides/plugin/guide-java-plugin-development.html In another maven project I test this plugin using: build plugins plugin groupIdsample.plugin/groupId

Re: Plugin execution not covered by lifecycle configuration

You should provide a small eclipse plugin that tells m2e what to do (for example simply execute the mojo). Everyone that wants to use your mojo should install this small plugin. The reason is simple: Some mojos are not executed by m2e. For example the java-compiler mojo is ignored and the