https://bugzilla.redhat.com/show_bug.cgi?id=1132225 Bug ID: 1132225 Summary: java-functions set_flags and set_options functions do the same thing Product: Fedora Version: 21 Component: javapackages-tools Severity: low Assignee: mizdebsk(a)redhat.com Reporter: ctubbsii-fedora(a)apache.org QA Contact: extras-qa(a)fedoraproject.org CC: java-sig-commits(a)lists.fedoraproject.org, mizdebsk(a)redhat.com, msimacek(a)redhat.com, msrb(a)redhat.com Description of problem: set_flags and set_options do the same thing. This also means that %jpackage_script's 2nd and 3rd argument do the same thing. Version-Release number of selected component (if applicable): javapackages-tools-4.1.0-2.fc21.noarch (likely affects other versions as well) Actual results: The only difference between set_flags options and set_options options are whether they are placed on the $JAVA_CMD command line before or after the classpath, which is an arbitrary order, as these all should fall in the same scope (arguments to java). It appears to be a bug, as there seems to be little utility for this. Expected results: It seems the original intention may have been to pass default arguments to the main method, which would add a lot of value? This is a guess. Additional info: I suppose this may not be considered a "bug", per se, but the strangeness of this seems to indicate that it was not what was intended. Unless I'm missing something and the ordering around the classpath does actually matter, though I was unable to find any documentation indicating that it did. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=iH2vZjfKIp&a=cc_unsubscribe