Yes, I think this would be very helpfull. Otherwise I see a lot of
people complaining about Maven and that is not able to do its work.
The best solution IMHO would be to print out a warning with a detailed
hint that no one could ignore.
Am 20.06.16 um 21:56 schrieb Paul Benedict:
Do you mean make it a warning in 3.4 and fix behavior in 3.5?
Cheers,
Paul
On Mon, Jun 20, 2016 at 2:42 PM, Oliver B. Fischer <o.b.fisc...@swe-blog.net
wrote:
Ok, I will fix it. But wouldn't it be an usefull option to print some
warning about this problem before changing the current behaviour?
WDYT?
Am 12.06.16 um 23:08 schrieb Christian Schulte:
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
