On 2017-02-16T18:32:10 +0100
"Robert Scholte" wrote:
> If you have a project under maven-assembly-plugin/src/it/projects/bugs and
> want to debug it, try:
>
> mvn verify -Prun-its -Dinvoker.mavenExecutable=mvnDebug
> -Dinvoker.test=projects/bugs (point to
If you have a project under maven-assembly-plugin/src/it/projects/bugs and
want to debug it, try:
mvn verify -Prun-its -Dinvoker.mavenExecutable=mvnDebug
-Dinvoker.test=projects/bugs (point to test-directory)
You'll see that Maven will hang during the invoker, at which time you have
to
I use the takari testing with the Android Maven Plugin all the time and it
works great for me.
Manfred
PS: also associated with Takari efforts..
Igor Fedorenko wrote on 2017-02-16 03:52:
> I don't use intellij, but if you are willing to try eclipse/m2e then
> there are at least two viable
Hello!
I think I may have explained myself poorly.
I'm not really looking for a general way to take a project and make it
debuggable. I'm looking for a concrete way to work on a bug in the
Assembly plugin.
On 2017-02-16T13:39:33 +
John Patrick wrote:
> this might
this might work and is what I get into the company/project root pom so
all developers can use the approach. create a debug profile and get
the tests to use is so you can debug in your preferred IDE. it doesn't
give you the nice red/green process bars and fancy output but it might
help you debug
I don't use intellij, but if you are willing to try eclipse/m2e then
there are at least two viable ways to implement "debuggable" integration
tests. Personally I prefer takari plugin testing harness [1]
(disclosure: I wrote the thing, so I am definitely biased).
Alternatively, you can also use
On 2017-02-14T15:13:46 +
org.apache.maven.u...@io7m.com wrote:
>
> I can't work out how to run this integration
> test from an IDE (Intellij IDEA, in this case) so that I can try to
> step through the execution with a debugger and see what's going on.
So nobody knows how to run an integration
Hello.
I'm having a look at working on
https://issues.apache.org/jira/browse/MASSEMBLY-848 but I've never
worked on any of the "official" Maven plugins before. It seems like
the most obvious way to start working on the bug is to introduce the
files attached to that report as an integration test