You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bu...@apache.org on 2023/02/02 19:03:17 UTC

[Bug 66464] New: JUnitLauncher missing jvm option

https://bz.apache.org/bugzilla/show_bug.cgi?id=66464

            Bug ID: 66464
           Summary: JUnitLauncher missing jvm option
           Product: Ant
           Version: 1.10.12
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks
          Assignee: notifications@ant.apache.org
          Reporter: filipe.silva@oracle.com
  Target Milestone: ---

JUnit task supports specifying the JVM to use when running the tests in forked
mode. This feature does not exist in the task JUnitLaucher.

Unless there's is an alternative I'm missing, I'd say the nested element `fork`
should allow specifying a different JVM for running the tests. This would be
very useful, for example, for running the same testsuite against different JVMs
in a single run.

Thank you.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66464] JUnitLauncher missing jvm option

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66464

Jaikiran Pai <ja...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Jaikiran Pai <ja...@apache.org> ---
I've now pushed a commit to upstream which introduces a new optional "java"
attribute to the <fork> element of the junitlauncher task. This attribute can
be set to point to any "java" command of choice to launch the forked tests.

This will be available in Ant release 1.10.14 (no specific date).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66464] JUnitLauncher missing jvm option

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66464

Jaikiran Pai <ja...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |1.10.14

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66464] JUnitLauncher missing jvm option

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=66464

--- Comment #1 from Jaikiran Pai <ja...@apache.org> ---
Hello Filipe,

> Unless there's is an alternative I'm missing, I'd say the nested element `fork` should allow specifying a different JVM for running the tests.

What you note is correct and you didn't miss anything. The fork element
currently doesn't have a way to specify an alternate "java" command/location. 

> This would be very useful, for example, for running the same testsuite against different JVMs in a single run.

I think that's a valid point. I'll enhance the fork element in the coming days
to help support this.

-- 
You are receiving this mail because:
You are the assignee for the bug.