On May 25, 2009, at 5:41 PM, Matteo Pelucco wrote:
Grégory Joseph ha scritto:
On my local maven repo, I see 2.4.3, can I force to use another
one? We have a parent POM inheriting from magnolia-project POM.
You shouldn't.
Ok, I can understand the reason, but how can I solve this trouble?
We have that project which can stay without any test, but the
"standard" maven build can not produce any jar.
Try to add a dependency to junit on your project; seems weird, but
I've had to do this once ... can't remember the exact reason right now.
You said "After a module refactoring, I'm encountering this problem."
--- you're not saying what you refactored, and how that'd have
anything to do with the issue at hand.
You also don't mention is this occurs only within Eclipse or also from
the command line (since you mention you use m2eclipse, suspicion is
permitted ;))
The only way I manage to solve this issue is to bypass the entire
surefire test plugin, which is maybe the worst thing I have ever
done with maven, I know...
What about <failIfNoTests>false</failIfNoTests> property?
Can it be a solution? And in this case, which is the best place to
add it?
You'd rather need to *remove* it rather than add it. It would be in
the configuration of the surefire plugin.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
