I committed pom.xml with excluded URUtilTest, that solved all the
problems and also updated Surefire plugin to version 2.4.2
Regards
--
Lukasz
http://www.lenart.org.pl/
-
To unsubscribe, e-mail:
2009/3/13 Wes Wannemacher w...@wantii.com:
On Thursday 12 March 2009 19:35:37 Musachy Barroso wrote:
Yeah, I have to find a better way to test those dumb URLs with weird
protocols. Is there a problem running with pertest?
I don't see a problem with it, so long as we know why we're doing it.
2009/3/13 Musachy Barroso musa...@gmail.com:
Me forgetting something? pfft, what are we talking about again?
:D:D:D:D
Regards
--
Lukasz
http://www.lenart.org.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
2009/3/1 Lukasz Lenart lukasz.len...@googlemail.com:
I found solution, just set fork mode to pretest, like below
forkModepertest/forkMode
but I think it isn't a real solution.
The real problem is with URLUtilTest.setUp(), in such method
URL.setURLStreamHandlerFactory() is called to setup
Yeah, I have to find a better way to test those dumb URLs with weird
protocols. Is there a problem running with pertest?
musachy
On Thu, Mar 12, 2009 at 6:26 PM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
2009/3/1 Lukasz Lenart lukasz.len...@googlemail.com:
I found solution, just set
On Thursday 12 March 2009 19:35:37 Musachy Barroso wrote:
Yeah, I have to find a better way to test those dumb URLs with weird
protocols. Is there a problem running with pertest?
musachy
I don't see a problem with it, so long as we know why we're doing it. The key
seems to be in the
On Thu, Mar 12, 2009 at 8:06 PM, Wes Wannemacher w...@wantii.com wrote:
It'd probably be sufficient to file a JIRA against it, just so that we don't
forget in the future that we should fix it up.
Me forgetting something? pfft, what are we talking about again?
musachy
--
Hey you! Would you
2009/2/27 Wes Wannemacher w...@wantii.com:
http://hudson.zones.apache.org/hudson/view/Struts/job/xwork2/5/
There are some new tests failing :(
It appears related, I'll check into it, if I don't fall asleep first.
Could you remove the setting for forkMode? I think this can be related
to (from
Subject: Re: XWork test failures
To: Lukasz Lenart lukasz.len...@googlemail.com
That build ran without any forkmode setting... Here is how Hudson ran it -
[xwork] $ /home/hudson/tools/java/latest1.6/bin/java -Xms128m -Xmx768m
-XX:MaxPermSize=256m -XX:PermSize=128m [-cp classpath snipped
When I updated my local copy, such tests below are failing, before
that, there wasn't any problem
testGetSnippetNoPadding(com.opensymphony.xwork2.util.location.LocationImplTest)
testGetSnippet(com.opensymphony.xwork2.util.location.LocationImplTest)
On Friday 27 February 2009 02:37:39 Lukasz Lenart wrote:
ehhh... sorry but I don't understand, I have already account in JIRA
or you are talking about something else? Another thing, I sent my CLA
months ago to apache.org and didn't get any answer, what can I do
else?
Sorry Lukasz, I thought
It has something to do with forking in the surefire plugin, running
the tests without forking works(for me at least):
mvn test -DforkMode=none
musachy
On Thu, Feb 26, 2009 at 2:38 AM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
2009/2/25 Lukasz Lenart lukasz.len...@googlemail.com:
On Thu, Feb 26, 2009 at 11:05 AM, Musachy Barroso musa...@gmail.com wrote:
It has something to do with forking in the surefire plugin, running
the tests without forking works(for me at least):
mvn test -DforkMode=none
musachy
I added that to Hudson and it appears to be working better...
testJaredFiles could be related to the FileManager changes, that line:
FileManager.setReloadingConfigs(true);
is suspicious. It works for me on Windows XP (/cry).
On Thu, Feb 26, 2009 at 11:14 AM, Wes Wannemacher w...@wantii.com wrote:
On Thu, Feb 26, 2009 at 11:05 AM, Musachy Barroso
2009/2/26 Wes Wannemacher w...@wantii.com:
testJaredFiles is still failing... (Who is Jared? Maybe we should ask
him what is up with his files... j/k). It's the only test still
failing on Hudson.
Jared means xwork config files in JAR files ;-) I changed the name to
be more readable.
I think I
2009/2/26 Musachy Barroso musa...@gmail.com:
It has something to do with forking in the surefire plugin, running
the tests without forking works(for me at least):
mvn test -DforkMode=none
If my change don't solve the problem, I think we should switch back
the fork mode.
Regards
--
Lukasz
It is working for me after your last change. Thanks :)
musachy
On Thu, Feb 26, 2009 at 5:36 PM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
2009/2/26 Musachy Barroso musa...@gmail.com:
It has something to do with forking in the surefire plugin, running
the tests without forking
On Thursday 26 February 2009 17:27:09 Lukasz Lenart wrote:
2009/2/26 Wes Wannemacher w...@wantii.com:
testJaredFiles is still failing... (Who is Jared? Maybe we should ask
him what is up with his files... j/k). It's the only test still
failing on Hudson.
Jared means xwork config files in
On Thursday 26 February 2009 17:27:09 Lukasz Lenart wrote:
2009/2/26 Wes Wannemacher w...@wantii.com:
testJaredFiles is still failing... (Who is Jared? Maybe we should ask
him what is up with his files... j/k). It's the only test still
failing on Hudson.
Jared means xwork config files in
2009/2/27 Wes Wannemacher w...@wantii.com:
Jared means xwork config files in JAR files ;-) I changed the name to
be more readable.
I was just messing around... You know, being a spelling nazi, I assumed you
meant jarred files. :)
I understand and that's good, thanks for your point ;-)
2009/2/27 Wes Wannemacher w...@wantii.com:
http://hudson.zones.apache.org/hudson/view/Struts/job/xwork2/5/
There are some new tests failing :(
It appears related, I'll check into it, if I don't fall asleep first.
They base on additional jar files added to classpath with Surefire and
it looks
Now that we are depending on the xwork snapshot, I went ahead and
setup an XWork build in Hudson, just like the struts2 builds.
The test failures are showing up there, but I can't reproduce them...
Well, I can, they fail when you run the build with Maven, but if you
run the tests individually
snapshot, I went ahead and
setup an XWork build in Hudson, just like the struts2 builds.
The test failures are showing up there, but I can't reproduce them...
Well, I can, they fail when you run the build with Maven, but if you
run the tests individually, like in Eclipse, they pass. The test
Problems with testWildCardInclude and testFinder are related to new
Surefire plugin version, with 2.4 they fail, but passed with 2.3 (both
will pass under IDEA)
testJaredFiles - is strange for me, there wasn't problem, but I will
double-check
testOverflows - this can be related to conversion
On Wed, Feb 25, 2009 at 10:58 AM, Rene Gielen gie...@it-neering.net wrote:
Same here. Is the failing Hudson snapshot build also the reason why the
S2.1 Bamboo build is still failing? Bamboo build isn't able to get the
XWork update with Musachy's latest XW commit, needed for S2 build.
Am Mi,
On Wed, Feb 25, 2009 at 11:14 AM, Musachy Barroso musa...@gmail.com wrote:
Yeah, I overloaded a constructor and used it in Convention.
I don't think it's the change that killed it, just the fact that the
XWork snapshot isn't in Bamboo's repo because it's build is failing.
-Wes
--
Wes
2009/2/25 Lukasz Lenart lukasz.len...@googlemail.com:
Problems with testWildCardInclude and testFinder are related to new
Surefire plugin version, with 2.4 they fail, but passed with 2.3 (both
will pass under IDEA)
I've been playing with testFinder but no idea what is wrong, when I
launch it
Is Bamboo running a different set of tests than the ones that Maven runs, or
is it somehow running them differently? We've been seeing a flurry of
failures over the last few days, and I can't help thinking that we should be
finding the problems *before* checking in, rather than letting Bamboo
No, the tests should be the same. Most of the Bamboo messages are a result of
some checkins I made without noticing the test failures coming out of Maven. I
will pay closer attention to this going forward to cut down on the Bamboo
messages.
James
On Thu Jul 19 14:47 , 'Martin Cooper' [EMAIL
I'm seeing some test failures in Struts 2 head. It's difficult to tell what
exactly is failing with all the log output. Should we disable test log
output?
Bob
I believe Rene's last commit broke the select tag tests, some 23 in
all. Rene?
Don
Bob Lee wrote:
I'm seeing some test failures in Struts 2 head. It's difficult to tell
what
exactly is failing with all the log output. Should we disable test log
output?
Bob
FYI - I'm working on a maven2 repo for opensymphony that will resolve this
issue.
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37086messageID=73119#73119
]
[INFO] There are test failures.
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: There are test
failures
]
[ERROR] BUILD ERROR
[INFO]
[INFO] There are test failures.
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException
It looks like the changes for the validator broke the core-library unit
tests. Gary, can you take a look please?
[EMAIL PROTECTED] core-library]$ ant test
Buildfile: build.xml
init:
[echo] -- Shale Core Library 1.0.3-SNAPSHOT ---
[echo] jsf-api.jar =
It looks like the changes for the validator broke the core-library unit
tests. Gary, can you take a look please?
[EMAIL PROTECTED] core-library]$ ant test
Buildfile: build.xml
We are now locked into validator 1.3. I think you need to run the
download-dependencies. I changed the ant and maven
On 4/11/06, Gary VanMatre [EMAIL PROTECTED] wrote:
It looks like the changes for the validator broke the core-library unit
tests. Gary, can you take a look please?
[EMAIL PROTECTED] core-library]$ ant test
Buildfile: build.xml
We are now locked into validator 1.3. I think you need to
From: Craig McClanahan [EMAIL PROTECTED]
On 4/11/06, Gary VanMatre wrote:
It looks like the changes for the validator broke the core-library unit
tests. Gary, can you take a look please?
[EMAIL PROTECTED] core-library]$ ant test
Buildfile: build.xml
We are now locked
Great thanks for the info Wendy. I should have looked at the maven files -
but confess to still being a bit of a maven-phobe.
Niall
- Original Message -
From: Wendy Smoak [EMAIL PROTECTED]
Sent: Sunday, September 04, 2005 4:45 AM
From: Niall Pemberton [EMAIL PROTECTED]
Appears that
Apologies, I ran the tests in 1.2 (using ant), but not 1.3 (using maven).
Appears that maven expects a class named Test to be a JUint test. I've
renamed TestI18nFactorySet to CustomI18nFactorySet and it now works.
I didn't add the new tests to the sandbox/standalone tiles - it needs a
From: Niall Pemberton [EMAIL PROTECTED]
Appears that maven expects a class named Test to be a JUint test. I've
renamed TestI18nFactorySet to CustomI18nFactorySet and it now works.
Maven itself doesn't expect anything in particular. It's coming from
build/project.xml:
unitTest
41 matches
Mail list logo
