Infinitest issue marker in wrong place for multi-module Maven projects
Reported by benrady (at gmail) | October 13th, 2009 @ 04:44 AM
I have a multi-module Maven project in Eclipse. Eclipse shows the child modules both as folders in the parent module and as separate projects. When Infinitest detects a test failure, the error indicator appears in the parent project (not false, but of limited use), and not in the child project. So I don't see any errors in the child project (where I am working), or in the source code when I open it from within the child project. Displaying the errors in both places would be nice.
Comments and changes to this ticket
-
benrady (at gmail) October 13th, 2009 @ 05:18 PM
- no changes were found...
-
benrady (at gmail) December 11th, 2009 @ 04:52 AM
- Assigned user set to “benrady (at gmail)”
The projects in this screenshot were created using m2eclipse. Says one user...
"I get this all the time in m2eclipse (I don't do mvn eclipse:eclipse, I just import the Maven projects directly into Eclipse with m2eclipse). For me, it's been pretty systematic. I can get around it by closing the parent project and reopening Eclipse, but it's not very elegant."
screen-shot-2009-09-28-at-23120-pm.png
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Continuous Test Runner for Java
People watching this ticket
benrady (at gmail)
Attachments
-
screen-shot-2009-09-28-at-2...
200.3 KB