Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 7u10, 8
    • Fix Version/s: 7u10
    • Component/s: docs

      Description

      FULL PRODUCT VERSION :
      jdk 1.7u10

      ADDITIONAL OS VERSION INFORMATION :
      windows 7 64-bit

      A DESCRIPTION OF THE PROBLEM :
      The wildcard character " * " doesn't work as it should. For example passing a parameter in batch file:

      java -Xmx256M -Xss1M -jar dev_*.jar run

      does not run the dev_build_01.jar file found in the same directory.

      In a program, for example, using ProcessBuilder and passing a jar's that includes a wildcard, Java seems to take this literally and says " Unable to find jarfile. "

      REGRESSION. Last worked in version 7

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      Make batch file and use a wildcard, or use a wildcard within any string that's to be used as a parameter. Java will evaluate this literally.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      wildcards work like normal. java will use the first found result that matches a string and wildcard, e.g. example*.jar
      ACTUAL -
       " Unable to access jarfile dev*.jar "

      REPRODUCIBILITY :
      This bug can be reproduced always.

      CUSTOMER SUBMITTED WORKAROUND :
      None. I had to use a hard coded string to get things to work.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dgollapudi Devika Gollapudi (Inactive)
                Reporter:
                webbuggrp Webbug Group
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: