Re: maven-eclipse-plugin - configure source and output-folders
Hi Andreas, Andreas Dolk wrote: Hi all, we have a rather complex project structure with a lot of projects and a couple of code generators that produce java classes for production and test. The challenge now is to configure the build files so that a mvn eclipse:eclipse run will create all required source folders and set the correct output folders, for example: src folder: src/main/code-gen out folder: (default) - target/classes src folder: src/test/code-gen out folder: target/test-classes Currently we use the maven build helper to set the source folders but I still don't know how to set the out dirs - now it creates a project config that compiles production and test classes into the same out folder which actually causes conflicts. Isn't that automatically done using build-helper:add-source vs. build- helper:add-test-source? Is there any way to fine-tune the .classpath file programmatically? - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Jacoco:check - pom example?
Under build I have:
plugin
groupIdorg.jacoco/groupId
artifactIdjacoco-maven-plugin/artifactId
version${version.jacoco}/version
executions
execution
idprepare/id
goals
goalprepare-agent/goal
/goals
/execution
execution
idverify/id
configuration
rules
rule
elementBUNDLE/element
limits
limit
counterINSTRUCTION/counter
valueCOVEREDRATIO/value
minimum0.15/minimum
/limit
limit
counterCLASS/counter
valueMISSEDCOUNT/value
maximum0/maximum
/limit
/limits
/rule
/rules
/configuration
/execution
execution
idreport/id
phaseprepare-package/phase
goals
goalreport/goal
/goals
/execution
/executions
/plugin
The execution verify is the bit I've just added but my build blows up:
Caused by: java.lang.IllegalStateException: Class
org/powermock/modules/junit4/common/internal/impl/JUnit4TestSuiteChunkerImpl
is already instrumented.
at
org.jacoco.agent.rt.internal_9dd1198.core.internal.instr.InstrSupport.assertNotInstrumented(InstrSupport.java:81)
at
org.jacoco.agent.rt.internal_9dd1198.core.internal.instr.ClassInstrumenter.visitField(ClassInstrumenter.java:79)
at org.jacoco.agent.rt.internal_9dd1198.asm.ClassVisitor.visitField(Unknown
Source)
at org.jacoco.agent.rt.internal_9dd1198.asm.ClassReader.a(Unknown Source)
at org.jacoco.agent.rt.internal_9dd1198.asm.ClassReader.accept(Unknown
Source)
at org.jacoco.agent.rt.internal_9dd1198.asm.ClassReader.accept(Unknown
Source)
at
org.jacoco.agent.rt.internal_9dd1198.core.instr.Instrumenter.instrument(Instrumenter.java:78)
at
org.jacoco.agent.rt.internal_9dd1198.core.instr.Instrumenter.instrument(Instrumenter.java:96)
... 39 more
java.lang.instrument.IllegalClassFormatException: Error while instrumenting
class org/powermock/tests/utils/impl/AbstractTestSuiteChunkerImpl.
( etc )
I'm guessing that I've added the instruction the the pom incorrectly but
the documentation lacks an in-context example. Can anyone shed light on
this?
Thanks,
James
Re: Jacoco:check - pom example?
Hi,
Under build I have:
plugin
groupIdorg.jacoco/groupId
artifactIdjacoco-maven-plugin/artifactId
version${version.jacoco}/version
executions
execution
idprepare/id
goals
goalprepare-agent/goal
/goals
/execution
execution
idverify/id
configuration
rules
rule
elementBUNDLE/element
limits
limit
counterINSTRUCTION/counter
valueCOVEREDRATIO/value
minimum0.15/minimum
/limit
limit
counterCLASS/counter
valueMISSEDCOUNT/value
maximum0/maximum
/limit
/limits
/rule
/rules
/configuration
/execution
execution
idreport/id
phaseprepare-package/phase
goals
goalreport/goal
/goals
/execution
/executions
/plugin
*snip*
I'm guessing that I've added the instruction the the pom incorrectly but
the documentation lacks an in-context example. Can anyone shed light on
this?
Just a guess:
You didn't specify a phase for the executions with id prepare and
verify...?
Regards
Thorsten
Re: Jacoco:check - pom example?
According to the documentation they both/all bind to default phases and I'm
in no position to disagree.
On 7 October 2013 14:00, thorsten.h...@vkb.de wrote:
Hi,
Under build I have:
plugin
groupIdorg.jacoco/groupId
artifactIdjacoco-maven-plugin/artifactId
version${version.jacoco}/version
executions
execution
idprepare/id
goals
goalprepare-agent/goal
/goals
/execution
execution
idverify/id
configuration
rules
rule
elementBUNDLE/element
limits
limit
counterINSTRUCTION/counter
valueCOVEREDRATIO/value
minimum0.15/minimum
/limit
limit
counterCLASS/counter
valueMISSEDCOUNT/value
maximum0/maximum
/limit
/limits
/rule
/rules
/configuration
/execution
execution
idreport/id
phaseprepare-package/phase
goals
goalreport/goal
/goals
/execution
/executions
/plugin
*snip*
I'm guessing that I've added the instruction the the pom incorrectly but
the documentation lacks an in-context example. Can anyone shed light on
this?
Just a guess:
You didn't specify a phase for the executions with id prepare and
verify...?
Regards
Thorsten
Re: Jacoco:check - pom example?
This works:
plugin
groupIdorg.jacoco/groupId
artifactIdjacoco-maven-plugin/artifactId
version${version.jacoco}/version
executions
execution
goals
goalprepare-agent/goal
/goals
/execution
execution
idcheck/id
goals
goalcheck/goal
/goals
configuration
rules
rule
elementBUNDLE/element
limits
limit
counterINSTRUCTION/counter
valueCOVEREDRATIO/value
minimum0.15/minimum
/limit
limit
counterCLASS/counter
valueMISSEDCOUNT/value
maximum125/maximum
/limit
/limits
/rule
/rules
/configuration
/execution
execution
idreport/id
phaseprepare-package/phase
goals
goalreport/goal
/goals
/execution
/executions
/plugin
On 7 October 2013 14:11, James Green james.mk.gr...@gmail.com wrote:
According to the documentation they both/all bind to default phases and
I'm in no position to disagree.
On 7 October 2013 14:00, thorsten.h...@vkb.de wrote:
Hi,
Under build I have:
plugin
groupIdorg.jacoco/groupId
artifactIdjacoco-maven-plugin/artifactId
version${version.jacoco}/version
executions
execution
idprepare/id
goals
goalprepare-agent/goal
/goals
/execution
execution
idverify/id
configuration
rules
rule
elementBUNDLE/element
limits
limit
counterINSTRUCTION/counter
valueCOVEREDRATIO/value
minimum0.15/minimum
/limit
limit
counterCLASS/counter
valueMISSEDCOUNT/value
maximum0/maximum
/limit
/limits
/rule
/rules
/configuration
/execution
execution
idreport/id
phaseprepare-package/phase
goals
goalreport/goal
/goals
/execution
/executions
/plugin
*snip*
I'm guessing that I've added the instruction the the pom incorrectly but
the documentation lacks an in-context example. Can anyone shed light on
this?
Just a guess:
You didn't specify a phase for the executions with id prepare and
verify...?
Regards
Thorsten
Re: maven-eclipse-plugin - configure source and output-folders
On Oct 4, 2013, at 5:18 PM, Andreas Dolk andreas.dolk.mo...@googlemail.com wrote: Hi all, we have a rather complex project structure with a lot of projects and a couple of code generators that produce java classes for production and test. The challenge now is to configure the build files so that a mvn eclipse:eclipse run will create all required source folders and set the correct output folders, for example: What happens if you run: mvn test-compile eclipse:eclipse instead of just mvn eclipse:eclipse By default, eclipse:eclipse just runs far enough to get the source directories, not all the test directories. If you force maven to run to the test-compile phase, then it should be able to pick everything up. Dan src folder: src/main/code-gen out folder: (default) - target/classes src folder: src/test/code-gen out folder: target/test-classes Currently we use the maven build helper to set the source folders but I still don't know how to set the out dirs - now it creates a project config that compiles production and test classes into the same out folder which actually causes conflicts. Is there any way to fine-tune the .classpath file programmatically? Cheers, Andreas -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help configuring checkstyle Maven plugin
This one: https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/custom-checker-config.html On Fri, Oct 4, 2013 at 9:48 AM, Dennis Lundberg denn...@apache.org wrote: Hi Andrew, Which tutorial is out of date? If you give me your working config, I can update the tutorials if needed. On Thu, Sep 26, 2013 at 4:33 PM, Andrew Pennebaker apenneba...@42six.com wrote: Ah, the tutorials for this are out of date. For version 2.10 of this plugin, the stuff should go inside `build`, not `reporting`. On Tue, Sep 24, 2013 at 3:00 PM, Andrew Pennebaker apenneba...@42six.comwrote: Could someone help me tweak my checkstyle plugin in my pom? I would like `mvn checkstyle:check` to output the checkstyle results directly to the console, but setting consoleOutputtrue/consoleOutput has no effect; it all goes to target/checkstyle-results.xml. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Xlint warnings hidden on `mvn compile -q`
I'm using maven-compiler-plugin to show Xlint warnings on `mvn compile`. I would like to hide the INFO output before and after these warnings, so I tried `mvn clean mvn compile -q`. However, this also hides the Xlint warnings. How can I tweak my pom so that `mvn compile` or `mvn compile -q` hides INFO messages, but shows WARNING messages? Is there another log level above quiet that shows more messages, but not INFO messages?
Re: m2e workspace resolution doesn't include test-classes
Hi all Stackoverflow provided the answer...http://stackoverflow.com/questions/19147684/work-around-for-m2e-workspace-resolution-lacking-test-classes-in-launcher-classp/19186830?noredirect=1#19186830 Maven favors test-jar type over test classifier and m2e follows suite. type does that right thing adding the test jar to the classpath on launcher classpath resolution. Classifier doesn't add the test jar to classpath. Thanks Peter On Wed, Oct 2, 2013 at 6:15 PM, Peter Kahn citizenk...@gmail.com wrote: Hi all, Does anyone have a workaround for m2e no longer adding target/test-classes to launcher when workspace resolution is used? This used to work but doesn't anymore which forces us to add folders and projects to launchers manually. After closing dependent projects in workspace I see the test jars on my classpath. It is only when they are opened that resolution fails. I saw a discussion back in may on this topic ( http://dev.eclipse.org/mhonarc/lists/m2e-dev/msg01343.html) and was hoping someone had a workaround. Thanks Peter Apologies is m2e is too off topic for this list. -- Peter Kahn citizenk...@gmail.com http://www.google.com/profiles/citizenkahn Awareness - Intention - Action -- Peter Kahn citizenk...@gmail.com http://www.google.com/profiles/citizenkahn Awareness - Intention - Action
RE: .cvspass file not found on windows.
Hi David, I have installed CVSNT on windows. And I didn't find .cvspass file. So as per your notes It will be stored in registery. PLease send me utility to which extracts and creates the .cvspass file. -- View this message in context: http://maven.40175.n5.nabble.com/cvspass-file-not-found-on-windows-tp45726p5772646.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
