Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Windows XP, Sun JDK 1.4.2_03
    • Number of attachments :
      0

      Description

      I'm working on a project that uses AspectWerkz AOP functionality. For obvious reasons, AspectWerkz needs to be bootstrapped during my unit tests. It's quite easy to do by simply telling the junit task to fork and using the aspectwerkz script as the jvm attribute. In fact, there is already a maven.junit.jvm property in the plugin.properties for the test plugin. It's just not used by the junit tasks.

      My request is to simply add the jvm attribute to all of the junit tasks. This would allow me to keep my maven installation up-to-date and not worry about breaking all of my unit tests.

      Thanks!

      John

        Issue Links

          Activity

          Hide
          Brett Porter added a comment -

          I can't see that property already in the properties. There is a functional jvmargs property - is that what was needed?

          Show
          Brett Porter added a comment - I can't see that property already in the properties. There is a functional jvmargs property - is that what was needed?
          Hide
          John M. Shields added a comment -

          I thought that the "maven.test.jvm" property already existed, but maybe it was added by someone here in our local repository.

          Regardless, all you need to do is add a default "maven.test.jvm=java" property to plugin.properties and then add 'jvm="$

          {maven.test.jvm}

          "' to all of the "ant:junit" invocations in plugin.jelly.

          The ant junit documentation states that the default JVM is "java", so this should be backwards compatible.

          Thanks!

          John

          Show
          John M. Shields added a comment - I thought that the "maven.test.jvm" property already existed, but maybe it was added by someone here in our local repository. Regardless, all you need to do is add a default "maven.test.jvm=java" property to plugin.properties and then add 'jvm="$ {maven.test.jvm} "' to all of the "ant:junit" invocations in plugin.jelly. The ant junit documentation states that the default JVM is "java", so this should be backwards compatible. Thanks! John
          Hide
          John M. Shields added a comment -

          I meant "maven.junit.jvm", not "maven.test.jvm"...

          Show
          John M. Shields added a comment - I meant "maven.junit.jvm", not "maven.test.jvm"...
          Hide
          Brett Porter added a comment -

          done

          Show
          Brett Porter added a comment - done

            People

            • Assignee:
              Brett Porter
              Reporter:
              John M. Shields
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 10 minutes
                10m
                Remaining:
                Remaining Estimate - 10 minutes
                10m
                Logged:
                Time Spent - Not Specified
                Not Specified