I've updated project.xml to reference the validator 1.1.1 jar. You need
to manually download it from http://www.apache.org/~rleland/ and place
it in your local repository.
.maven
plugins
repository
...
commons-validator <-- you may need to create directories below here
jars
commons-validator-1.1.1-dev.jar
maven jar then works (at least for me :-))
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 :-)
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!!
Steve
> -----Original Message-----
> From: Martin Cooper [mailto:[EMAIL PROTECTED]
> Sent: November 28, 2003 12:05 AM
> To: Struts Developers List
> Subject: Re: Maven test run
>
>
> After copying my local Validator build to Maven's repo, I get
> the same as
> you do - no tests to run.
>
> Doing the Ant test.junit thing, I get the
> TestActionConfigMatcher failure,
> but it looks like Steve has tracked that one down.
>
> --
> Martin Cooper
>
>
> On Thu, 27 Nov 2003, James Mitchell wrote:
>
> > On Thu, 27 Nov 2003, Ted Husted wrote:
> >
> > > When I run the maven jar target, the upload tests fail
> > > (MultipartTestSuite).
> >
> > On a fresh copy of....well....everything (maven 1.0-rc1,
> jakarta-struts,
> > etc, etc) I cannot do anything with maven.
> >
> > The attempt to download validator SNAPSHOT fails. When I change
> > project.xml to use 1.0.1 or 1.0.2, it downloads, but the
> compile fails
> > complaining about missing ValidatorUtils.
> >
> > I downloaded a nightly, moved it to
> > ~/.maven/repository/commons-validator/jars/.
> >
> > Then changed "SNAPSHOT" to "nightly" in project.xml.
> >
> > Then this:
> >
> > [EMAIL PROTECTED] jakarta-struts]$ maven jar
> > __ __
> > | \/ |__ _Apache__ ___
> > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> > |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT
> >
> > java:prepare-filesystem:
> >
> > java:compile:
> > [echo] Compiling to m-target/classes
> > [javac] Compiling 266 source files to
> > /home/jmitchell/cvs/jakarta-struts/m-target/classes
> >
> /home/jmitchell/cvs/jakarta-struts/src/share/org/apache/struts
> /tiles/actions/DefinitionDispatcherAction.java:78:
> > warning: org.apache.struts.tiles.DefinitionsUtil in
> > org.apache.struts.tiles has been deprecated
> > import org.apache.struts.tiles.DefinitionsUtil;
> > ^
> >
> > <huge-snip/>
> >
> >
> >
> /home/jmitchell/cvs/jakarta-struts/src/share/org/apache/struts
> /validator/ValidatorPlugIn.java:264:
> > warning:
> org.apache.commons.validator.ValidatorResourcesInitializer in
> > org.apache.commons.validator has been deprecated
> >
> ValidatorResourcesInitializer.initialize(resources,
> > bis, false);
> > ^
> > 41 warnings
> >
> > java:jar-resources:
> > Copying 15 files to
> /home/jmitchell/cvs/jakarta-struts/m-target/classes
> >
> > test:prepare-filesystem:
> > [mkdir] Created dir:
> > /home/jmitchell/cvs/jakarta-struts/m-target/test-classes
> > [mkdir] Created dir:
> > /home/jmitchell/cvs/jakarta-struts/m-target/test-reports
> >
> > test:test-resources:
> >
> > test:compile:
> > [echo] No test source files to compile.
> >
> > test:test:
> > [echo] No tests to run.
> >
> > jar:jar:
> > [jar] Building jar:
> > /home/jmitchell/cvs/jakarta-struts/m-target/struts-1.2.0.jar
> > BUILD SUCCESSFUL
> > Total time: 26 seconds
> > Finished at: Fri Nov 28 01:40:35 EST 2003
> >
> >
> >
> >
> >
> > "No tests to run"....Am I missing something here?
> >
> >
> >
> >
> > >
> > > But, when I run the ant test.junit test, only the
> > > TestActionConfigMatcher test fails.
> > >
> > > Is it me, or do others share this experience?
> > >
> > > If so, any ideas as to why this would be?
> > >
> > > -Ted.
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> [EMAIL PROTECTED]
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
