Re: [m2] handling of optional 3rd-party-dependencies in tests

2007-02-14 Thread franz see
Good day to you, martin, I'm guessing that happened while maven was building module B. AFAIK, that's just a reminder that that jar is using the scope test only. I don't think it's anything to worry about ( not unless you did not specify that jar to be of scope test ). Cheers, Franz matinh

Re: [m2] handling of optional 3rd-party-dependencies in tests

2007-02-14 Thread Martin Hoeller
Hello Franz! Thanks for your quick reply. On 14. February 2007 13:08 franz see wrote: I'm guessing that happened while maven was building module B. Yes, forgot to mention this. AFAIK, that's just a reminder that that jar is using the scope test only. I don't think it's anything to worry

Re: [m2] handling of optional 3rd-party-dependencies in tests

2007-02-14 Thread Tim Kettler
Hi, Am Mittwoch, den 14.02.2007, 13:38 +0100 schrieb Martin Hoeller: [...] However, as this is nothing I need to worry about (that's what I expected), I would like this warning to go away. I don't want warnings if everything is fine. What am I missing? There is a recent thread [1] about