On Tuesday 17 March 2009 17:58:58 Randy Burgess wrote:
> Hello,
> I originally sent this from an address that isn't subscribed to this list
> so I hope it doesn't show up twice, if it does I apologize. I haven't
> gotten a bounce message or seen it so I'm assuming the original won't show
> up.
>
> RB
> ===========
>
> I was just looking over the dependencies of a test S2 2.1.6 Mavenized app
> I'm using and noticed that JUnit is required in my WAR, which shouldn't be
> the case. Then I did a little digging and noticed that struts2-core-2.1.6
> depends on XWork which has a compile dependency on spring-test 2.5.6 which
> in turn has a compile dependency on JUnit. Is there a reason that the scope
> isn't set to "test" on spring-test? Same JUnit compile dependency with
> struts2-sitemesh and struts2-config-browser and probably other plugins.
>
> This is what I'm seeing with m2eclipse so if I'm off base let me know, but
> it has always reliably shown dependency trees for me. I don't recall seeing
> this with 2.0.x.
>
> If there is any way I can help fix this for 2.1.7 I'll be glad to pitch in

Randy, IIRC, this came up a while ago. We were trying to move test 
dependencies out of Xwork, but there was a reason that we couldn't (in maven). 
There are a few ways to deal with it, though. If you explicitly add JUnit as a 
dependency (in test scope), I think it will move it out and you shouldn't have 
any problems. Another choice, if you aren't writing unit tests would be to use 
an exclusion to get JUnit out of there. I think it is a compile-time 
dependency, so excluding it shouldn't cause problems for your app at run-time.

Of course, my memory is hazy on this, so I could be completely wrong. Check it 
out and let us know.

-Wes

-- 

Wes Wannemacher
Author - Struts 2 In Practice 
Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more
http://www.manning.com/wannemacher


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to