maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J?rg Hohwiller (JIRA)" <>
Subject [jira] Commented: (MSUREFIRE-115) Classloading problem for getting a resource
Date Wed, 14 Jun 2006 09:09:42 GMT
    [ ] 

Jörg Hohwiller commented on MSUREFIRE-115:

I have the same problem. The suggested classloader workaround does NOT work for me.
I had "MyClass.class.getResourceAsStream("/foo/bar.xml")" what works within Eclipse but not
with maven2.
I changed to "MyClass.class.getClassloader().getResourceAsStream("/foo/bar.xml")" without
a change.
The suggested workaround "Thread.currentThread().getContextClassLoader().getResourceAsStream("/foo/bar.xml")"
only caused that the Testcase does NOT even work in Eclipse anymore, what seems obvious to
me cause "/foo/bar.xml" is
located in the JAR containing "MyClass".
Anyways, I think that a typical maven2 user wants "mvn test" to work as within the IDE and
NOT digg into the problem and find 
a workaround somewhere he has to adopt in order to keep going with maven2.

> Classloading problem for getting a resource
> -------------------------------------------
>          Key: MSUREFIRE-115
>          URL:
>      Project: Maven 2.x Surefire Plugin
>         Type: Bug

>     Versions: 2.1.3, 2.2
>  Environment: Maven 2.0.4
> Windows XP
>     Reporter: Wim Deblauwe
>     Priority: Blocker
>  Attachments:,
> We are using Betwixt and some of our unit tests fail when run using
> surefire, but run fine in IntelliJ or Maven 1. Betwixt looks for
> descriptors with the name of the class + .betwixt to control how
> something is written out in XML. It uses the construct:
> myClass.getResource() to find the .betwixt file.
> E.g. com.mycomp.MyClass -> com/mycomp/MyClass.betwixt
> We have a betwixt file for the java.util.Date class. However, betwixt
> seems to be unable to pick it up when using surefire. I have created a
> small test that shows the problem and have attached it.
> I tried with version 2.2 using different configurations (never, once, pertest) and with
version 2.1.3 (default configuration)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message