Details

    • Type: Sub-task Sub-task
    • Status: Closed Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 1.0.4
    • Fix Version/s: 1.0.5
    • Component/s: XML tests
    • Labels:
      None
    • Number of attachments :
      1

      Issue Links

        Activity

        Hide
        Edward Kuns added a comment -

        How to handle Java 5 code in CTF tests .... add a flag to the TestDescriptor.xml to indicate that this entire test case is Java-5 only. It has to be all-or-nothing. You cannot have a TestDescriptor.xml with one unit test that is Java 1.3 and another that is Java 5, because all of the code for a CTF test is either compiled or not. Buf if a full TestDescriptor.xml is Java 5 and all of the tests in that directory are Java 5, then that whole test can be disabled for those running under Java 1.4 and earlier.

        That will avoid trying to compile Java 5 source under an earlier compiler.

        I cannot see an easy (or reasonable) way to have one TestDescriptor.xml with two different unit tests where one unit test is Java 5 and the other is Java 1.4.

        Show
        Edward Kuns added a comment - How to handle Java 5 code in CTF tests .... add a flag to the TestDescriptor.xml to indicate that this entire test case is Java-5 only. It has to be all-or-nothing. You cannot have a TestDescriptor.xml with one unit test that is Java 1.3 and another that is Java 5, because all of the code for a CTF test is either compiled or not. Buf if a full TestDescriptor.xml is Java 5 and all of the tests in that directory are Java 5, then that whole test can be disabled for those running under Java 1.4 and earlier. That will avoid trying to compile Java 5 source under an earlier compiler. I cannot see an easy (or reasonable) way to have one TestDescriptor.xml with two different unit tests where one unit test is Java 5 and the other is Java 1.4.
        Hide
        Werner Guttmann added a comment -

        Hmm, given Edward's description, it looks doable to me (as long as this test directory with Java 5 specific sources never ends up on the build path. Edward, feel like showing us that it is doable indeed .. ?

        Show
        Werner Guttmann added a comment - Hmm, given Edward's description, it looks doable to me (as long as this test directory with Java 5 specific sources never ends up on the build path. Edward, feel like showing us that it is doable indeed .. ?
        Hide
        Edward Kuns added a comment -

        Absolutely. Now that I've delivered a big chunk of work on the CTF, I an ready to start something new.
        See CASTOR-1672

        Show
        Edward Kuns added a comment - Absolutely. Now that I've delivered a big chunk of work on the CTF, I an ready to start something new. See CASTOR-1672
        Hide
        Edward Kuns added a comment -

        Adding a link (depends on) to the CTF Jira issue which will add the ability to specify a minimum JVM for a test.

        Show
        Edward Kuns added a comment - Adding a link (depends on) to the CTF Jira issue which will add the ability to specify a minimum JVM for a test.
        Hide
        Werner Guttmann added a comment -

        Bulk-closing all issues assigned to 1.0.5. Please feel free to re-open any of those when required.

        Show
        Werner Guttmann added a comment - Bulk-closing all issues assigned to 1.0.5. Please feel free to re-open any of those when required.

          People

          • Assignee:
            Werner Guttmann
            Reporter:
            Ralf Joachim
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

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