maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Holster (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (SUREFIRE-290) [PATCH] Forking to java 1.3 not working when using relative paths in modules.
Date Thu, 01 Mar 2007 10:26:44 GMT

     [ http://jira.codehaus.org/browse/SUREFIRE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Holster updated SUREFIRE-290:
----------------------------------

    Attachment: no-relative-classpath-urls-without-typo.patch

I noticed a typo in the patch. This patch should do the trick

> [PATCH] Forking to java 1.3 not working when using relative paths in modules.
> -----------------------------------------------------------------------------
>
>                 Key: SUREFIRE-290
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-290
>             Project: Maven Surefire
>          Issue Type: Bug
>         Environment: WinXp + Java 1.3
>            Reporter: Mark Holster
>             Fix For: 2.4
>
>         Attachments: no-relative-classpath-urls-without-typo.patch, no-relative-classpath-urls.patch
>
>
> For a java 1.3 multi-module project we use a construction like
> {code:xml}
> <modules>
>   <module>..\mymodule1</module>
>   <module>..\..\mymodule2</module>
> </modules>
> {code}
> The testcases work fine if maven is started in the modules, but when running from the
aggegator pom a ClassNotFoundException on any testcase will occur.
> The attached patch add canonnical paths to the classpath if a given path is absolute.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message