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.
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?
Otherwise I can prepare a allwaysTrue test to add to each project...
Matteo
----------------------------------------------------------------
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>
----------------------------------------------------------------
