Also comitted to the 2.0 branch, rev 1427.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=72225&messageID=137835#137835
-
To unsubs
James.
I'll fix it shortly. Just remove the sourcepath tag from the pom.
I didn't want to mess to much with the pom file since I am rather new to maven
and how you guys have setup the maven build for xwork. When I was active we
used Ant.
And why is the javadoc set to show private also? Shouldn
I've had that funky package name problem as well.
On 3/31/07, James Mitchell <[EMAIL PROTECTED]> wrote:
Great! I can almost build again with Maven.
The problem (for me) now is with this ...
...
...
org.apache.maven.plugins
maven-javadoc-plugin
Great! I can almost build again with Maven.
The problem (for me) now is with this ...
...
...
org.apache.maven.plugins
maven-javadoc-plugin
attach-source
Okay fixed the last broken test. All now passes in trunk and 2.0 branch.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=72225&messageID=137590#137590
-
Fixed 3 out of 4 failed tests.
Comitted to trunk and the 2.0 branch.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=72225&messageID=137587#137587
-
I'll be out of town for a few days but will commit the fixes for xwork in trunk
and the 2.0x branch.
(the one with OgnlValueStackTest)
However the last failed test with the alias interceptor is still open at the
moment. If anyone knows how to fix? Details posted in prev post.
---
Only one failing test left.
Failed tests:
testUsingDefaultInterceptorThatAliasPropertiesAreCopied(com.opensymphony.xwork2.interceptor.AliasInterceptorTest)
Tests run: 518, Failures: 1, Errors: 0, Skipped: 0
---
Test
James did you specify version 2.3 in the pom.xml to use the one that works?
The pom.xml in the svn does not specify this.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=72225&messageID=135764#135764
Yes, that's exactly what I've been seeing.
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 25, 2007, at 7:57 AM, Claus Ibsen wrote:
Great news.
I was using Maven 2.05 vanilla. The surefire plugin in this dist is
buggy.
(*) Would be nice if maven could report if there
Got 3 out of 4 failed tested fixed now.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=72225&messageID=135717#135717
-
To unsubscri
Great news.
I was using Maven 2.05 vanilla. The surefire plugin in this dist is buggy.
(*) Would be nice if maven could report if there are never plugins released
that you could use.
Well I upgraded to v2.3 of the surefire plugin and it now executes all the
tests.
Before:
Tests run: 168, Failu
James can you look in the corresponding TEST- XML fille. It's this file that
has additional tests in the bag.
The plain .txt file is correct. Also on my system.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?
When I run it, here's what's in my ActionContextTest.txt
---
Test set: com.opensymphony.xwork2.ActionContextTest
---
Tests run: 8, Failures
Damm surefire seems to be a bit buggy. Just browsed it's JIRA.
Created a minor bug: http://jira.codehaus.org/browse/SUREFIRE-312
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=72225&messageID=135529#1
Is it just me or is surefire not a bit strange on the xwork project?
Could you try this:
mvn clean
mvn surefire-report:report
And then look in target/site/surefire-report.html. Then click on the first test
- ActionContextTest.
It should have only 8 tests. but the list is much bigger on my repor
I'm on a MacBook Pro.
You can also look under target/surefire-reports/(test class).txt
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 23, 2007, at 11:29 AM, Ted Husted wrote:
On 3/23/07, Piero Sartini <[EMAIL PROTECTED]> wrote:
Am Donnerstag, 22. März 2007 schrieb Cl
Am Freitag, 23. März 2007 schrieb Ted Husted:
> On 3/23/07, Piero Sartini <[EMAIL PROTECTED]> wrote:
> > Am Donnerstag, 22. März 2007 schrieb Claus Ibsen:
> > > Isn't it a unit test executed by surefire? that tests what happens if
> > > you do a XSLTransformation with an invalid filename, and thus
On 3/23/07, Piero Sartini <[EMAIL PROTECTED]> wrote:
Am Donnerstag, 22. März 2007 schrieb Claus Ibsen:
> Isn't it a unit test executed by surefire? that tests what happens if you
> do a XSLTransformation with an invalid filename, and thus it log it at
> ERROR level but the test is fine.
But the
Ok, I checked it again and you are right. I assumed it is the XSLTResult
because it is the last error I see when the tests are finnished.
Actually, the errors are:
[surefire] Running org.apache.struts2.views.jsp.PortletUrlTagTest
[surefire] Tests run: 8, Failures: 1, Errors: 0, Time elapsed: 1,3
Piero
Are you sure surefire tests really fails. It reports something like <<<
FAILURE in the output if it fails.
The test can output logging at ERROR level and still not fail the test. Could
you double check it and report back.
---
Am Donnerstag, 22. März 2007 schrieb Claus Ibsen:
> Isn't it a unit test executed by surefire? that tests what happens if you
> do a XSLTransformation with an invalid filename, and thus it log it at
> ERROR level but the test is fine.
But the test fails, and this should not happen I assume?
[INF
Strange.
On my XP it seems to work.
D:\project\xwork>svn info
Path: .
URL: https://svn.opensymphony.com/svn/xwork/trunk
Repository Root: https://svn.opensymphony.com/svn/xwork
Repository UUID: e221344d-f017-0410-9bd5-d282ab1896d7
Revision: 1388
Node Kind: directory
Schedule: normal
Last Changed A
From XW trunk...
...
...
Mar 22, 2007 9:11:40 AM
org.springframework.beans.factory.support.DefaultListableBeanFactory
preInstantiateSingletons
INFO: Pre-instantiating singletons in factory
[org.springframework.beans.factory.support.DefaultListableBeanFactory
defining beans [spring-object
Isn't it a unit test executed by surefire? that tests what happens if you do a
XSLTransformation with an invalid filename, and thus it log it at ERROR level
but the test is fine.
Try compiling without executing the tests with -Dskip.test=true or whatever the
syntax is.
-
Dont know if this is related.
But I am unable to build s2 trunk (as well as 2_0_7) because of the following
error:
2007-03-22 12:57:16,391 ERROR [XSLTResult.java:365] : Unable to render XSLT
Template, 'nofile.xsl'
javax.xml.transform.TransformerException: Stylesheet nofile.xsl not found in
reso
The XW2 head is building under Maven here.
On 3/22/07, James Mitchell <[EMAIL PROTECTED]> wrote:
Does XW trunk build for anyone else? When I try to build with Maven,
it fails on a few tests, but if I run those same tests within
Eclipse, they pass fine.
--
James Mitchell
The Ruby Roundup
http:
What exceptions and what XW version ? There are some confusing
problems with XW1_2 [1], but the others seem to run fine [2].
Cheers,
Phil
[1] http://forums.opensymphony.com/thread.jspa?threadID=70501&tstart=0
[2] http://opensource.bamboo.atlassian.com/browse/XWORK
On 3/22/07, James Mitchell <
28 matches
Mail list logo