surefire vs java.protocol.handler.pkgs
I have some unit tests that depend on a soap server. To this end I have written my own stub server and use the java.protocol.handler.pkgs system property to override the http connection, redirecting connections to my stub server. But I can't get this to work with surefire. I've tried all of the forking options (a fork is obviously required). The tests see the system property set to the correct value, but they fail with a java.net.ConnectException: Connection refused exception -- my protocol handler is not being used. The sources for my protocol handler are with the other test sources. It all works as expected using maven 1.0.2 and from within eclipse. I have been able to get this to work by copying all the test classes, the project classes and a number of jar files (like junit and log4j) into my ~/Library/Java/Extensions directory (I'm using OSX, and anything in the Extensions directory is automatically added to the classpath). This is clearly not a solution, but it does suggest it's a classpath problem. What can I do to get this to work under surefire? --Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven Checkstyle Plugin 3.0 for Maven 1.x released
The revised 3.0.1 snapshot works for me.
--Andy
On Feb 20, 2006, at 2:09 PM, Lukas Theussl wrote:
This was a separate bug, it's fixed. Please re-download the
snapshot and test.
Thanks,
Lukas
Eric Rose wrote:
On Sunday 19 February 2006 08:11, Lukas Theussl wrote:
I have deployed a new snapshot which uses a jsl transform instead of
ant's style task. This should eliminate any jdk related issues,
please
test:
maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://
cvs.apache.org/repo
sitory/ -DgroupId=maven -DartifactId=maven-checkstyle-plugin
-Dversion=3.0.1-SNAPSHOT
The plugin failed for me with a message as follows:
BUILD FAILED
File.. /usr/local/mavenPluginRepository/cache/maven-checkstyle-
plugin-3.0.1-SNAPSHOT/plugin.jelly
Element... util:file
Line.. 99
Column 75
You must define an attribute called 'name must be specified' for
this tag.
Total time: 21 seconds
Finished at: Mon Feb 20 09:34:29 EST 2006
But I think this might be related to MPCHECKSTYLE-9
Once I set the ${maven.checkstyle.header.file} explicitly, the
checkstyle plugin worked fine.
Eric
-
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: checkstyle 3.0 with maven 1.0.2
It does work with JDK 1.4.2. I was originally misled a bit by this because while adding a JAVA_VERSION env variable will result in the maven script saying it's using java version 1.4.2, it still uses your JAVA_HOME variable if that's set too. --Andy On Feb 16, 2006, at 6:04 PM, Lukas Theussl wrote: No, it does work with Maven 1.0.2. I tested it, however, not with java 5 (only 1.4.2). If it's a jdk issue then the $JAVA_HOME/lib/ endorsed/ solution is probably the only one that's gonna work. -Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: checkstyle 3.0 with maven 1.0.2
The work around appears to already be part of 3.0.1-SNAPSHOT. Unless I'm misunderstanding, it doesn't help, at least with maven 1.0.2 and JDK 5. --Andy On Feb 17, 2006, at 12:54 AM, Arnaud HERITIER wrote: I just forwarded to the mailing list a workaround... Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven Checkstyle Plugin 3.0 for Maven 1.x released
From my experience, using JDK 5 and maven 1.0.2,
checkstyle 3.0 and 3.0.1-SNAPSHOT with or without
the setProperty fail in this manner.
--Andy
On Feb 17, 2006, at 9:16 AM, Lukas Theussl wrote:
Hi,
The systemScope.setProperty line was introduced to fix
http://jira.codehaus.org/browse/MPCHECKSTYLE-53
so you are saying that you have to remove it again? Can you attach
your comments to the issue above, or maybe open a new issue to
attack the problem more generally.
Thanks,
-Lukas
Arnaud HERITIER wrote:
Forward to the list ..
I didn't saw that I was the only one to receive it
Thanks for the tip JB
Arnaud
On 2/12/06, JB Defard [EMAIL PROTECTED] wrote:
Hi,
BUILD FAILED
File..
/usr/local/mavenPluginRepository/cache/maven-checkstyle-plugin
-3.0/plugin.jelly
Element... style
Line.. 238
Column 59
Provider for javax.xml.transform.TransformerFactory cannot be
found
Total time: 36 seconds
Finished at: Tue Feb 07 15:58:56 EST 2006
I have the same problem.
I fix it with comment this line (238):
!-- Make sure xalan is used for ant's style task --
!--
${systemScope.setProperty
('javax.xml.transform.TransformerFactory','org.apache.xalan.processo
r.TransformerFactoryImpl')}
--
My environment: Java 5 , maven 1.1b3-SNAPSHOT, plugin 3.0.1-
SNAPSHOT.
Regards.
-
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]
checkstyle 3.0 with maven 1.0.2
I've updated my project to specify version 3.0 of the checkstyle plugin. Maven remains at version 1.0.2. I have also tried using the 3.0.1-SNAPSHOT version, and have tried this on both OSX and Solaris (both use jvm 1.5.0). I consistently get the error: BUILD FAILED File.. /Users/andy/.maven/cache/maven-checkstyle-plugin-3.0.1- SNAPSHOT/plugin.jelly Element... style Line.. 241 Column 59 Provider org.apache.xalan.processor.TransformerFactoryImpl not found Total time: 39 seconds Finished at: Thu Feb 16 16:35:28 PST 2006 The error goes away if I revert to version 2.5 of the checkstyle plugin, but it can't handle the j2se 5.0 stuff. I've tried putting an explicit dependency for xalan into my project.xml, as described in the maven faq, but that doesn't help. I've tried adding xalan-2.4.1 to my class path, and in places like /Library/Java/Extensions; the only variant that appears to work is to put it in $JAVA_HOME/lib/endorsed/. Is there another solution for this? --Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
