Fix parameters in Java comments (#2394)

Updates the parameters to match the form used for the other tracks.

Fixes exercism/exercism#6776.

Author: kahgoh

analyzer-comments/java/general/constructor_too_long.md

@@ -1,6 +1,6 @@
 # constructor too long
 
-Consider breaking down the following constructor(s) into calls to other semantically meaningful methods: `%<constructorNames>s`
+Consider breaking down the following constructor(s) into calls to other semantically meaningful methods: `%{constructorNames}`
 
 The constructor has more lines of code than this exercise generally requires.
 This might be acceptable, but it could be an indication that the constructor is doing too much work directly and should be delegating some of that work to other methods.

analyzer-comments/java/general/exemplar.md

@@ -1,5 +1,5 @@
 # Exemplar
 
-🎉 Your solution to %<exerciseName>s is exemplar, congratulations!
+🎉 Your solution to %{exerciseName} is exemplar, congratulations!
 It is exactly what we think is the most idiomatic implementation of the tasks at hand.
 Rejoice!

analyzer-comments/java/general/file_not_found.md

@@ -2,8 +2,8 @@
 
 The expected solution file was not found.
 
-Upload the solution file `./src/main/java/%<solutionFile>s`:
+Upload the solution file `./src/main/java/%{solutionFile}`:
 
 ```
-$ exercism submit ./src/main/java/%<solutionFile>s
+$ exercism submit ./src/main/java/%{solutionFile}
 ```

analyzer-comments/java/general/method_too_long.md

@@ -1,8 +1,8 @@
 # method too long
 
-Consider breaking down the following method(s) into calls to other semantically meaningful methods: `%<methodNames>s`
+Consider breaking down the following method(s) into calls to other semantically meaningful methods: `%{methodNames}`
 
 The method has more lines of code than this exercise generally requires.
 This might be acceptable, but it could be an indication that the method is doing too much work directly and should be delegating some of that work to other methods.
 Try to keep everything inside a method at one level of abstraction.
-For example, iterating through the elements of a loop could be in one method while manipulating each individual element could be in another.
+For example, iterating through the elements of a loop could be in one method while manipulating each individual element could be in another.

analyzer-comments/java/general/reuse_code.md

@@ -1,4 +1,4 @@
 # Reuse code
 
-The `%<callingMethod>s` method should reuse the logic implemented in `%<methodToCall>s`.
+The `%{callingMethod}` method should reuse the logic implemented in `%{methodToCall}`.
 Reusing existing methods can help make code easier to maintain.

analyzer-comments/java/general/use_proper_class_name.md

@@ -2,4 +2,4 @@
 
 The class name should match the file name.
 
-Rename the class to `%<className>s`.
+Rename the class to `%{className}`.

analyzer-comments/java/general/use_proper_method_name.md

@@ -2,7 +2,7 @@
 
 The method name should match exactly what was used in the tests.
 
-Rename the method to `%<methodName>s`.
+Rename the method to `%{methodName}`.
 
 **NOTE**: Don't modify the tests to match a different method name.
 In general, try to only add additional tests (if desired).

analyzer-comments/java/log-levels/use_substring_method_v2.md

@@ -1,5 +1,5 @@
 # use substring method
 
-Consider using the [substring][substring-method] method in `%<inMethod>s` to solve this exercise.
+Consider using the [substring][substring-method] method in `%{inMethod}` to solve this exercise.
 
 [substring-method]: https://docs.oracle.com/javase/8/docs/api/java/lang/String.html#substring-int-int-

analyzer-comments/java/salary-calculator/use_ternary_operators.md

@@ -1,3 +1,3 @@
 # use ternary operators
 
-As the goal of this exercise is to learn about ternary operators consider using them in `%<inMethod>s` to solve this exercise.
+As the goal of this exercise is to learn about ternary operators consider using them in `%{inMethod}` to solve this exercise.

analyzer-comments/java/secrets/use_bitwise_operator.md

@@ -1,4 +1,4 @@
 # use bitwise operator
 
-The `%<calledMethod>s` method should use the operator `%<operatorToUse>s`.
+The `%{calledMethod}` method should use the operator `%{operatorToUse}`.
 As this concept exercise intends to teach how Bitwise operators work