you can manually bind btrace instrumentation to 'test-compile'
specified within exec-maven-plugin e.g.
org.codehaus.mojo
exec-maven-plugin
1.1.1
test-compile
This is what I'm using right now, but I've found that my instrumentation
mojo won't run if someone does "mvn test" or "mvn test-compile". The
user has to explicitly ask maven to run it. For example, "mvn
test-compile coroutines:test-instrument".
Is there a way to automatically get my mojo to r
this implementation of btrace instrumentation executes in process-resources
phase
org.codehaus.mojo
exec-maven-plugin
1.1.1
process-resources
Hi All,
I am trying to build a maven project from jenkins server.I am facing an
issue while creating jar in local maven repository .Even i set the path of
Maven repo locaiton in setting.xml as shown in below.
/var/lib/jenkins/maven-repositories
All the maven jars are creating under 0 and 1 fold
Hi
Process-classes sounds a good place in the lifecycle for this purpose
HTH
Olivier
On Thursday, 15 September 2016, offbynull-maven <
offbynull-ma...@offbynull.com> wrote:
> What should the defaultPhase be for a Maven plugin that instruments
> classes? Should it be PROCESS_CLASSES / PROCESS_TES
What should the defaultPhase be for a Maven plugin that instruments
classes? Should it be PROCESS_CLASSES / PROCESS_TEST_CLASSES, or should
it be COMPILE / TEST_COMPILE?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache