You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jakub Pawlowicz <co...@jakubpawlowicz.com> on 2006/07/18 16:23:56 UTC

SOLVED Re: [M2] Difference between 'mvn test' and 'mvn install'

Hi Jörg,

I used the -X switch and I found that 'mvn test' uses module's  
"target/classes" directory where 'mvn install' uses module's jar.
And then I discovered, that Spring does not handle wildcard patterns  
(eg applicationContext*.xml) when looking for contexts packaged in  
other jars.
So I've changed wildcard pattern to the real names and now everything  
works perfectly well.

Thanks for your help!

Best regards,
Jakub Pawlowicz

On Jul 18, 2006, at 9:17 AM, Jörg Schaible wrote:

> Jakub Pawlowicz wrote on Monday, July 17, 2006 8:06 PM:
>
>> Hi Jörg,
>>
>> Unfortunately this does not work for me, probably, because all my
>> modules have the same version.
>> I've installed maven-project-plugin snapshot version and my tests
>> fail in the same place as before.
>
> Then start with -X and look if you find a difference in the  
> classpath used to start the tests ...
>
> - Jörg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: SOLVED Re: [M2] Difference between 'mvn test' and 'mvn install'

Posted by Jakub Pawlowicz <co...@jakubpawlowicz.com>.
Hi Daniel,

I've just started a new thread on the Spring forums.
http://forum.springframework.org/showthread.php?t=27048

Regards,
Jakub Pawlowicz

On Jul 18, 2006, at 4:33 PM, Daniel Serodio wrote:

> Jakub Pawlowicz wrote:
>> Hi Jörg,
>>
>> I used the -X switch and I found that 'mvn test' uses module's
>> "target/classes" directory where 'mvn install' uses module's jar.
>> And then I discovered, that Spring does not handle wildcard patterns
>> (eg applicationContext*.xml) when looking for contexts packaged in
>> other jars.
>> So I've changed wildcard pattern to the real names and now everything
>> works perfectly well.
> Thanks for sharing the information, but shouldn't Spring handle  
> wildcard
> patterns when looking for contexts packaged in other jars? Did you  
> post
> about this in the Spring forums?
>
> Thanks in advance,
> Daniel Serodio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: SOLVED Re: [M2] Difference between 'mvn test' and 'mvn install'

Posted by Daniel Serodio <da...@xxx.com.br>.
Jakub Pawlowicz wrote:
> Hi Jörg,
>
> I used the -X switch and I found that 'mvn test' uses module's
> "target/classes" directory where 'mvn install' uses module's jar.
> And then I discovered, that Spring does not handle wildcard patterns
> (eg applicationContext*.xml) when looking for contexts packaged in
> other jars.
> So I've changed wildcard pattern to the real names and now everything
> works perfectly well.
Thanks for sharing the information, but shouldn't Spring handle wildcard
patterns when looking for contexts packaged in other jars? Did you post
about this in the Spring forums?

Thanks in advance,
Daniel Serodio

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org