You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Holster (JIRA)" <ji...@codehaus.org> on 2007/02/23 10:21:27 UTC
[jira] Created: (SUREFIRE-290) [PATCH] Forking to java 1.3 not
working when using relative paths in modules.
[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
Attachments: 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
[jira] Commented: (SUREFIRE-290) [PATCH] Forking to java 1.3 not
working when using relative paths in modules.
Posted by "Mark Holster (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115006 ]
Mark Holster commented on SUREFIRE-290:
---------------------------------------
Confirmed, after downloading maven 2.0.7 the problem disappeared.
> [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
> 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
[jira] Updated: (SUREFIRE-290) [PATCH] Forking to java 1.3 not
working when using relative paths in modules.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-290:
----------------------------------
Patch Submitted: [Yes]
> [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
[jira] Closed: (SUREFIRE-290) [PATCH] Forking to java 1.3 not
working when using relative paths in modules.
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-290.
---------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.4)
Apparently we're not using absolute URLs any more, so this is no longer an issue. Checked in integration test in revision 597803.
> [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
> 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
[jira] Updated: (SUREFIRE-290) [PATCH] Forking to java 1.3 not
working when using relative paths in modules.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-290:
----------------------------------
Fix Version/s: 2.4
> [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.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
[jira] Updated: (SUREFIRE-290) [PATCH] Forking to java 1.3 not
working when using relative paths in modules.
Posted by "Mark Holster (JIRA)" <ji...@codehaus.org>.
[ 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