#33 Fix some trivial deprecation warnings
Closed: fixed by cipherboy. Opened by emaldonado.

In https://docs.oracle.com/javase/10/docs/api/index.html?deprecated-list.html
if you scroll down to the Constructors section you'll see ones like this:

java.lang.Boolean​(boolean)
It is rarely appropriate to use this constructor. The static factory Boolean.valueOf(boolean) is generally a better choice, as it is likely to yield significantly better space and time performance. Also consider using the final fields Boolean.TRUE and Boolean.FALSE if possible.
and
java.lang.Byte​(byte)
It is rarely appropriate to use this constructor. The static factory Byte.valueOf(byte) is generally a better choice, as it is likely to yield significantly better space and time performance.


Likewise for: java.lang.Character​(char), java.lang.Double​(double) , java.lang.Float​(float), java.lang.Integer​(int) , and java.lang.Long​(long)

These have trivial fixes that don't involve any risk, unlike the ones in
https://pagure.io/jss/issue/17 which we intend to defer until absolutely needed.

Will open a PR with a patch for these easy ones.


Fixed by pr-#195.

Metadata Update from @cipherboy:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata