+1, should probably be moved.
What these file names have in common is they all start with a dot:
In Ye Aulden Days using a dot was one way to "hide files in plain sight" as for most users it would not be common to have an 'ls' alias that included the "-a" switch (mine is by default aliased to '/bin/ls -al --time-style=long-iso --quoting-style=c' and I export "LS_COLORS=no"). These days there's easier ways to hide files and better ways to spot changes (running a system file integrity checker like Samhain, AIDE, hell even tripwire would be suggested).
How to find out what these files are about? For starters 0) using your distributions package manager to find out what package the file is part of ('dpkg -S /usr/lib/jvm/.java-7-oracle.jinfo'), verifying package contents integrity with say 'debsums -c name-of-package' (though debsums needs to be installed beforehand unfortunately to trigger post-apt-get hash generation), 1) examination of MAC times ('stat /usr/lib/jvm/*') to see if they are similar or not, 2) running 'file' on the file to find out what it contains and 3) visual inspection using a pager, 'strings', readelf, EXIF tools or whatever else simple, non-modifying(!) tool you use.
*Please note "security" isn't about running Chkrootkit, Rootkit Hunter, OSSEC HIDS or any other single tool but hardening the machine right after OS installation, regularly auditing and adjusting access controls and remaining vigilant ever: in short a continuous process based upon a sound foundation.