struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Chen" <>
Subject RE: Maven test run
Date Fri, 28 Nov 2003 18:52:34 GMT
I submitted a patch recently for the maven build.
Sorry I didn't get a chance to (aka.. Just been lazy) attach it to a
formal bugzilla report as Rob had suggested that I do.
The maven test currently fail because the resources are not provided
(look at my past post for reference). Unfortunately, even after
including the source there are still test failures. I posted a sniplet
of one of the errors before.
I never bothered to find out if those test failures were due to the
maven build or because of incorrectly written tests.
Either way, I'll try to find some time to fix the maven build if anyone
is interested.

Tim Chen

-----Original Message-----
From: Ted Husted [] 
Sent: Friday, November 28, 2003 8:50 AM
To: Struts Developers List
Subject: Re: Maven test run

Steve Raeburn wrote:
> There were no tests found because the test section was commented out! 
> (and the example include pattern doesn't match our naming convention).

> I've enabled the JUnit tests. Using Cactus with Maven is beyond me, 
> for now :-)

Mea culpa on the comment block. I did that to see if I could get the 
rest of it to run, and then committed it accidentally. <head-slap/>

> When Maven runs the tests, TestModuleConfig is throwing a 
> NullPointerException that doesn't show up when running from Ant. I'm 
> inclined to believe that the Maven configuration requires more work 
> rather that it actually being a problem with ModuleConfig.
> The Maven build remains HIGHLY experimental!!

I wonder if we could try a compromise? Could we have a Maven build that 
just downloaded the dependencies into the central repository, and a that got everything from there. This would save us from

going back to a "struts-library" distribution.

I also wonder if it be possible to wrap our existing Ant build as Maven 
goals? The user guide says that any Ant task can be used in the

Another stepping-stone might be to provide Maven projects for the 
examples applications, especially the blank application. I'm thinking 
the cannonical approach here would be to have a master 
webapp-project.xml that we then extended for each application

I'm working on a changelog system now but will come back to this later, 
if no one beats me to it. [Please do, if you can :)]


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message