Re: [Wicket-develop] JUnit dependency in Wicket

[Guillermo Castro]

So, you need junit to compile the classes for the 'tester' package. However, does the junit package need to be carried over all the way to the webapp? I haven't checked the tester package so I don't really know what it does, but there are other scopes that let you compile wicket with junit, yet don't make junit be propagated. Using 'provided' comes to mind.

I guess since I don't know what 'tester' does, I can't really comment, but making the junit jar be carried all the way to the webapp seems to me like a little overkill.

Anyway, thanks for your response.

Guillermo

On 5/5/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:

Wicket tester depends on junit. Without compile scope, you won't be able to compile Wicket

Martijn

On 5/5/06, Guillermo Castro < [EMAIL PROTECTED]> wrote:

Hi,

I've been using the latest sources from the wicket subversion repository to be 'on the edge'. I basically use maven2 to install the snapshots to my local repository and use them from there.

However, I just noticed that wicket's POM has a junit dependency marked as 'compile'. Shouldn't this dependency be 'test'?

When I create a war packaging for my project, I keep getting the junit jar inside WEB-INF/lib/ and looking at the dependency hierarchy it's seems to be wicket the one who's putting the jar there.

Is there a special reason to include junit in the jars?

Regards.

--
Guillermo Castro             [EMAIL PROTECTED]
Monterrey NL, Mexico     http://www.javageek.org/

--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org