The uses unsafe or unchecked operations warning is displayed when you execute code which the Java compiler considers to be lacking in error-checking, or potentially unsafe in some way. However, it’s a warning, not an error, and will not stop your code from compiling — large projects will often churn out warning after warning, and you’re free to determine whether they’re worth taking action on or not. If you want to dig deeper into what’s causing the warning to trigger, you can recompile your .java file with the syntax javac -Xlint:unchecked yourfilename.java, and the compiler will give you more verbose information as to what exactly is causing the error.
In my experience, this warning can often be caused by using something like an ArrayList without specifying the type which it should expect to hold (i.e. using ArrayList a = new ArrayList() rather than ArrayList<String> a = new ArrayList<String>()). The compiler is, in my example case, warning you that your code isn’t going to do any checking for you that the values you add to it are any particular type. In a production application, it would likely be good to specify types, but in a test app, you’re free to ignore the warnings if you’re not concerned about them.