Re: Running Struts Cactus tests with Ant
> -Original Message-
> From: tomcatlist user [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 6, 2004 04:20 PM
> To: 'Struts Developers List'
> Subject: Re: Running Struts Cactus tests with Ant
>
> When I invoke maven, it complains about not finding commons-validator
> version 1.1.1-dev, so I tried modifying that to use the last version
> instead (1.0.2). It's a good thing I remembered someone mentioning
> commons-validator and the maven build. Looking through my messages I
> found this:
1.0.2 will work with the nightly build, only if you use the
validator-rules.xml from struts 1.1. There are been a number of improvements
in the javascript validation. The 1.1.1 download is still available under
my home directory. Let me know if there are any problems.
-Rob
>
> > 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.
>
> If this is going to persist, maybe it might be worth a common in the
> project.xml? If I wasn't paying attention to the list, I wouldn't
> necessarily know where to get the updated version. :)
>
> I got a lot of deprecation errors, but otherwise, both the default
> jar:jar and dist goals finished! So with minor caveats, even a maven
> novice can build struts. That's great considering.
>
> Paul Sundling
>
>
> Tim Chen wrote:
>
> >Sorry.. The default target is currently set up as jar:jar
> >That will do everything that you need it to.
> >So all you have to do is:
> >
> >//step-by-step-build-struts-with-maven.readme
> >1) Download maven 1.0 rc1 from http://maven.apache.org
> >2) Add a maven_home env variable that points to where you installed
> >maven to
> >3) Add ${maven_home}/bin or %MAVEN_HOME%\bin to your path
> >4) Optional: set
> >MAVEN_OPTS=-Djavax.xml.transform.TransformerFactory=org.apache.xalan.pro
> >cessor.TransformerFactoryImpl
> > This is not really necessary as I set the path for the xalan
> >TransformerFactory in the maven scripts but could save you the hassle
> >with other projects that might require xalan.
> >5) checkout jakarta-struts.
> >NOTE: At this point you do not need to have anything in your classpath.
> >6) cd to jakarta-struts root
> >7) invoke either:
> > - > maven
> > by default runs jar:jar which will simply jar up
> >struts-1.2.0.jar into your maven build directory (currently set to
> >${jakarta-struts_home}/m-target)
> > - > maven dist
> > this task will create not just the jar but also create a
> >${jakarta-struts_home}/m-target/distributions
> >Directory that has zip and tar.gz versions of the bin and src
> >distributions
> >
> >I have been really busy the last few weeks and haven't had a chance to
> >help Joe or to complete the distributions. So it will not include all
> >the items from the current ant build but at least you don't have to
> >manually set anything in jakarta-struts anymore :)
> >
> >Tim Chen
> >[EMAIL PROTECTED]
> >
> >
> >-Original Message-
> >From: David Graham [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, December 16, 2003 6:52 PM
> >To: Struts Developers List
> >Subject: Re: Running Struts Cactus tests with Ant
> >
> >
> >
> >--- James Mitchell <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Any chance someone wants to throw together a
> >>step-by-step-build-struts-with-maven.readme?
> >>
> >>
> >
> >cd your-struts-dir
> >maven build
> >
> >Anything much more complicated than that defeats the purpose of using
> >Maven.
> >
> >David
> >
>
>
>
> -
> 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]
Re: Running Struts Cactus tests with Ant
At 8:20 AM -0800 1/6/04, tomcatlist user wrote: I already submitted a patch for the obvious URL errors in the project.xml (I hope I did it correctly, as it's only my second patch submission). You did it exactly right; as may be seen from the Bugzilla notification, I applied the patch and added some commentary about the Validator dependency. Worth noting for anyone following this, I also bumped the Validator dependency to 1.1.1 (not -dev) since Rob doesn't serve the dev version any more (and because there was an actual 1.1.1 release). Here's what I put in project.xml, in case anyone needs to deal with the dependency and doesn't want to go looking there: -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "We want beef in dessert if we can get it there." -- Betty Hogan, Director of New Product Development, National Cattlemen's Beef Association - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running Struts Cactus tests with Ant
I'm a maven novice, so I thought I'd share my experience building with
maven:
I already submitted a patch for the obvious URL errors in the
project.xml (I hope I did it correctly, as it's only my second patch
submission).
When I invoke maven, it complains about not finding commons-validator
version 1.1.1-dev, so I tried modifying that to use the last version
instead (1.0.2). It's a good thing I remembered someone mentioning
commons-validator and the maven build. Looking through my messages I
found this:
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.
If this is going to persist, maybe it might be worth a common in the
project.xml? If I wasn't paying attention to the list, I wouldn't
necessarily know where to get the updated version. :)
I got a lot of deprecation errors, but otherwise, both the default
jar:jar and dist goals finished! So with minor caveats, even a maven
novice can build struts. That's great considering.
Paul Sundling
Tim Chen wrote:
Sorry.. The default target is currently set up as jar:jar
That will do everything that you need it to.
So all you have to do is:
//step-by-step-build-struts-with-maven.readme
1) Download maven 1.0 rc1 from http://maven.apache.org
2) Add a maven_home env variable that points to where you installed
maven to
3) Add ${maven_home}/bin or %MAVEN_HOME%\bin to your path
4) Optional: set
MAVEN_OPTS=-Djavax.xml.transform.TransformerFactory=org.apache.xalan.pro
cessor.TransformerFactoryImpl
This is not really necessary as I set the path for the xalan
TransformerFactory in the maven scripts but could save you the hassle
with other projects that might require xalan.
5) checkout jakarta-struts.
NOTE: At this point you do not need to have anything in your classpath.
6) cd to jakarta-struts root
7) invoke either:
- > maven
by default runs jar:jar which will simply jar up
struts-1.2.0.jar into your maven build directory (currently set to
${jakarta-struts_home}/m-target)
- > maven dist
this task will create not just the jar but also create a
${jakarta-struts_home}/m-target/distributions
Directory that has zip and tar.gz versions of the bin and src
distributions
I have been really busy the last few weeks and haven't had a chance to
help Joe or to complete the distributions. So it will not include all
the items from the current ant build but at least you don't have to
manually set anything in jakarta-struts anymore :)
Tim Chen
[EMAIL PROTECTED]
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 6:52 PM
To: Struts Developers List
Subject: Re: Running Struts Cactus tests with Ant
--- James Mitchell <[EMAIL PROTECTED]> wrote:
Any chance someone wants to throw together a
step-by-step-build-struts-with-maven.readme?
cd your-struts-dir
maven build
Anything much more complicated than that defeats the purpose of using
Maven.
David
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running Struts Cactus tests with Ant
> As noted in a previous thread, I am hitting a wall trying to run the cactus tests in Ant. I want to commit the changes I've made to help Maven run cactus tests, and I've already had to reconcile a bunch of conflicts once... The error seems to come with the first Cactus test case (org.apache.struts.action.TestActionServlet) and is "Error instantiating class" -- so I'm guessing maybe I haven't gotten all of the necessary jars defined correctly (the build.properties.sample is pretty confusing the way it repeats blocks of properties over and over). For those hanging on the edge of your seats... I had compiled a local copy of the Cactus/Ant integration jar which has patches to work with Mac OS X, and I neglected to also compile a copy of the core Cactus framework; apparently (and unsurprisingly, really), there was some compiled incompatibility between the versions. So compiling a CVS copy of Cactus got me past that problem... and a lot farther once I turned off the halt on failure/error values. How much farther? well, I'm passing 83 out of 103 test classes cleanly; however, I've run the tests against a fresh repository checkout and I get the same results as I do against my modifications (barring a few line number differences in stack traces). It's a bit of a puzzle that configuration problems could lead to a distribution like that, with so many tests passing, and yet a substantial number failing. If anyone has all the cactus tests passing under Ant and would like to give my "maven changes" a shot, let me know. Otherwise, stay tuned for the next exciting installment... Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "We want beef in dessert if we can get it there." -- Betty Hogan, Director of New Product Development, National Cattlemen's Beef Association - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Running Struts Cactus tests with Ant
Sorry.. The default target is currently set up as jar:jar
That will do everything that you need it to.
So all you have to do is:
//step-by-step-build-struts-with-maven.readme
1) Download maven 1.0 rc1 from http://maven.apache.org
2) Add a maven_home env variable that points to where you installed
maven to
3) Add ${maven_home}/bin or %MAVEN_HOME%\bin to your path
4) Optional: set
MAVEN_OPTS=-Djavax.xml.transform.TransformerFactory=org.apache.xalan.pro
cessor.TransformerFactoryImpl
This is not really necessary as I set the path for the xalan
TransformerFactory in the maven scripts but could save you the hassle
with other projects that might require xalan.
5) checkout jakarta-struts.
NOTE: At this point you do not need to have anything in your classpath.
6) cd to jakarta-struts root
7) invoke either:
- > maven
by default runs jar:jar which will simply jar up
struts-1.2.0.jar into your maven build directory (currently set to
${jakarta-struts_home}/m-target)
- > maven dist
this task will create not just the jar but also create a
${jakarta-struts_home}/m-target/distributions
Directory that has zip and tar.gz versions of the bin and src
distributions
I have been really busy the last few weeks and haven't had a chance to
help Joe or to complete the distributions. So it will not include all
the items from the current ant build but at least you don't have to
manually set anything in jakarta-struts anymore :)
Tim Chen
[EMAIL PROTECTED]
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 6:52 PM
To: Struts Developers List
Subject: Re: Running Struts Cactus tests with Ant
--- James Mitchell <[EMAIL PROTECTED]> wrote:
> Any chance someone wants to throw together a
> step-by-step-build-struts-with-maven.readme?
cd your-struts-dir
maven build
Anything much more complicated than that defeats the purpose of using
Maven.
David
>
>
>
> > Anyway, maybe I just need an Ant trick to give me better feedback
> > about why it's failing -- it's probably something very routine.
> >
> > I do know that the same test case passes when I run it in Maven.
> >
> > Thanks in advance for any tips...
> >
> > Joe
> >
> > start.tomcat.41:
> > [java] Dec 16, 2003 3:38:21 PM
> > org.apache.coyote.http11.Http11Protocol init
> > [java] INFO: Initializing Coyote HTTP/1.1 on port 8080
> > [java] Starting service Tomcat-Standalone
> > [java] Apache Tomcat/4.1.29
> > [java] log4j:WARN No appenders could be found for logger
> > (org.apache.struts.util.PropertyMessageResources).
> > [java] log4j:WARN Please initialize the log4j system properly.
> > [java] Dec 16, 2003 3:38:31 PM
> > org.apache.coyote.http11.Http11Protocol start
> > [java] INFO: Starting Coyote HTTP/1.1 on port 8080
> >
> > run.test:
> > [junit] Running org.apache.struts.action.TestActionMessage
> > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed:
> > 0.075
> sec
> > [junit] Testsuite: org.apache.struts.action.TestActionMessage
> > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed:
> > 0.075
> sec
> >
> > [junit] Testcase: testActionMessageWithNoValue took 0.039 sec
> > [junit] Testcase: testActionMessageWithAStringValue took 0.001
> sec
> > [junit] Running org.apache.struts.action.TestActionMessages
> > [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed:
> > 0.06
> sec
> > [junit] Testsuite: org.apache.struts.action.TestActionMessages
> > [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed:
> > 0.06
> sec
> >
> > [junit] Testcase: testEmpty took 0.025 sec
> > [junit] Testcase: testNotEmpty took 0.005 sec
> > [junit] Testcase: testSizeWithOneProperty took 0.001 sec
> > [junit] Testcase: testSizeWithManyProperties took 0.001 sec
> > [junit] Testcase: testSizeAndEmptyAfterClear took 0 sec
> > [junit] Testcase: testGetWithNoProperty took 0.013 sec
> > [junit] Testcase: testGetForAProperty took 0 sec
> > [junit] Testcase: testAddMessages took 0.001 sec
> > [junit] Running org.apache.struts.action.TestActionServlet
> > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed:
> > 1.782
> sec
> > [junit] Testsuite: org.apache.struts.action.TestActionServlet
> > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed:
> > 1.782
> sec
> >
> > [junit] Testcase: testInitDestroyInternal took 1.771 sec
> > [junit] Caused an ERROR
> > [junit] Error instantiating
Re: Running Struts Cactus tests with Ant
--- James Mitchell <[EMAIL PROTECTED]> wrote: > Any chance someone wants to throw together a > step-by-step-build-struts-with-maven.readme? cd your-struts-dir maven build Anything much more complicated than that defeats the purpose of using Maven. David > > > > > Anyway, maybe I just need an Ant trick to give me better > > feedback about why it's failing -- it's probably something very > > routine. > > > > I do know that the same test case passes when I run it in Maven. > > > > Thanks in advance for any tips... > > > > Joe > > > > start.tomcat.41: > > [java] Dec 16, 2003 3:38:21 PM > > org.apache.coyote.http11.Http11Protocol init > > [java] INFO: Initializing Coyote HTTP/1.1 on port 8080 > > [java] Starting service Tomcat-Standalone > > [java] Apache Tomcat/4.1.29 > > [java] log4j:WARN No appenders could be found for logger > > (org.apache.struts.util.PropertyMessageResources). > > [java] log4j:WARN Please initialize the log4j system properly. > > [java] Dec 16, 2003 3:38:31 PM > > org.apache.coyote.http11.Http11Protocol start > > [java] INFO: Starting Coyote HTTP/1.1 on port 8080 > > > > run.test: > > [junit] Running org.apache.struts.action.TestActionMessage > > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.075 > sec > > [junit] Testsuite: org.apache.struts.action.TestActionMessage > > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.075 > sec > > > > [junit] Testcase: testActionMessageWithNoValue took 0.039 sec > > [junit] Testcase: testActionMessageWithAStringValue took 0.001 > sec > > [junit] Running org.apache.struts.action.TestActionMessages > > [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.06 > sec > > [junit] Testsuite: org.apache.struts.action.TestActionMessages > > [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.06 > sec > > > > [junit] Testcase: testEmpty took 0.025 sec > > [junit] Testcase: testNotEmpty took 0.005 sec > > [junit] Testcase: testSizeWithOneProperty took 0.001 sec > > [junit] Testcase: testSizeWithManyProperties took 0.001 sec > > [junit] Testcase: testSizeAndEmptyAfterClear took 0 sec > > [junit] Testcase: testGetWithNoProperty took 0.013 sec > > [junit] Testcase: testGetForAProperty took 0 sec > > [junit] Testcase: testAddMessages took 0.001 sec > > [junit] Running org.apache.struts.action.TestActionServlet > > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.782 > sec > > [junit] Testsuite: org.apache.struts.action.TestActionServlet > > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.782 > sec > > > > [junit] Testcase: testInitDestroyInternal took 1.771 sec > > [junit] Caused an ERROR > > [junit] Error instantiating class > > [org.apache.struts.action.TestActionServlet([testInitDestroyInternal], > > [null])] > > [junit] javax.servlet.ServletException: Error instantiating class > > [org.apache.struts.action.TestActionServlet([testInitDestroyInternal], > > [null])] > > [junit] at > > > org.apache.cactus.server.AbstractWebTestCaller.getTestClassInstance(AbstractWebTestCaller.java:459) > > [junit] at > > > org.apache.cactus.server.AbstractWebTestCaller.doTest(AbstractWebTestCaller.java:148) > > [junit] at > > > org.apache.cactus.server.AbstractWebTestController.handleRequest_aroundBody0(AbstractWebTestController.java:130) > > [---% snip stack trace %] > > [junit] Testcase: testInitDestroyInternal > > > > stop.tomcat.41: > > [java] Stopping service Tomcat-Standalone > > [java] Dec 16, 2003 3:38:47 PM > > org.apache.coyote.http11.Http11Protocol destroy > > [java] INFO: Stoping http11 protocol on 8080 > > Catalina:type=ThreadPool,name=http8080 > > > > BUILD FAILED > > > /Users/germuska/Development/jakarta/jakarta-struts/build-tests.xml:236: > > Test org.apache.struts.action.TestActionServlet failed > > > > Total time: 50 seconds > > > > This same test > > > > -- > James Mitchell > Software Developer / Struts Evangelist > http://www.struts-atlanta.org > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running Struts Cactus tests with Ant
On Tue, 16 Dec 2003, Joe Germuska wrote: > As noted in a previous thread, I am hitting a wall trying to run the > cactus tests in Ant. I want to commit the changes I've made to help > Maven run cactus tests, and I've already had to reconcile a bunch of > conflicts once... > > The error seems to come with the first Cactus test case > (org.apache.struts.action.TestActionServlet) and is "Error > instantiating class" -- so I'm guessing maybe I haven't gotten all of > the necessary jars defined correctly (the build.properties.sample is > pretty confusing the way it repeats blocks of properties over and > over). Yes, I made that change becuase setting the paths correctly for each of those properties was becoming a pain and prone to error, so I figured that would at least make it easier. You just uncomment the section for your choice of Cactus version. Only problem with that is ... not every version is supported. Funny, I can't seem to get Maven to do anything for me (build, tests, etc), but Ant still works fine (compile, ripping the docs/tlds/etc, tests). And the problem for you is vica versa. Ok Ok...it's not "actually" funny, but still, I would like to see us move over to Maven as well. Any chance someone wants to throw together a step-by-step-build-struts-with-maven.readme? > Anyway, maybe I just need an Ant trick to give me better > feedback about why it's failing -- it's probably something very > routine. > > I do know that the same test case passes when I run it in Maven. > > Thanks in advance for any tips... > > Joe > > start.tomcat.41: > [java] Dec 16, 2003 3:38:21 PM > org.apache.coyote.http11.Http11Protocol init > [java] INFO: Initializing Coyote HTTP/1.1 on port 8080 > [java] Starting service Tomcat-Standalone > [java] Apache Tomcat/4.1.29 > [java] log4j:WARN No appenders could be found for logger > (org.apache.struts.util.PropertyMessageResources). > [java] log4j:WARN Please initialize the log4j system properly. > [java] Dec 16, 2003 3:38:31 PM > org.apache.coyote.http11.Http11Protocol start > [java] INFO: Starting Coyote HTTP/1.1 on port 8080 > > run.test: > [junit] Running org.apache.struts.action.TestActionMessage > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.075 sec > [junit] Testsuite: org.apache.struts.action.TestActionMessage > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.075 sec > > [junit] Testcase: testActionMessageWithNoValue took 0.039 sec > [junit] Testcase: testActionMessageWithAStringValue took 0.001 sec > [junit] Running org.apache.struts.action.TestActionMessages > [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.06 sec > [junit] Testsuite: org.apache.struts.action.TestActionMessages > [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.06 sec > > [junit] Testcase: testEmpty took 0.025 sec > [junit] Testcase: testNotEmpty took 0.005 sec > [junit] Testcase: testSizeWithOneProperty took 0.001 sec > [junit] Testcase: testSizeWithManyProperties took 0.001 sec > [junit] Testcase: testSizeAndEmptyAfterClear took 0 sec > [junit] Testcase: testGetWithNoProperty took 0.013 sec > [junit] Testcase: testGetForAProperty took 0 sec > [junit] Testcase: testAddMessages took 0.001 sec > [junit] Running org.apache.struts.action.TestActionServlet > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.782 sec > [junit] Testsuite: org.apache.struts.action.TestActionServlet > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.782 sec > > [junit] Testcase: testInitDestroyInternal took 1.771 sec > [junit] Caused an ERROR > [junit] Error instantiating class > [org.apache.struts.action.TestActionServlet([testInitDestroyInternal], > [null])] > [junit] javax.servlet.ServletException: Error instantiating class > [org.apache.struts.action.TestActionServlet([testInitDestroyInternal], > [null])] > [junit] at > org.apache.cactus.server.AbstractWebTestCaller.getTestClassInstance(AbstractWebTestCaller.java:459) > [junit] at > org.apache.cactus.server.AbstractWebTestCaller.doTest(AbstractWebTestCaller.java:148) > [junit] at > org.apache.cactus.server.AbstractWebTestController.handleRequest_aroundBody0(AbstractWebTestController.java:130) > [---% snip stack trace %] > [junit] Testcase: testInitDestroyInternal > > stop.tomcat.41: > [java] Stopping service Tomcat-Standalone > [java] Dec 16, 2003 3:38:47 PM > org.apache.coyote.http11.Http11Protocol destroy > [java] INFO: Stoping http11 protocol on 8080 > Catalina:type=ThreadPool,name=http8080 > > BUILD FAILED > /Users/germuska/Development/jakarta/jakarta-struts/build-tests.xml:236: > Test org.apache.struts.action.TestActionServlet failed > > Total time: 50 seconds > > This same test > -- James Mitchell Software Developer / Struts Evangelist htt
