Ask first yourself: Is your file an internal component of your application?
(That usually implies that it’s packed inside your JAR, or WAR if it is a web-app; typically, it’s some configuration file or static resource, read-only).
If the answer is yes, you don’t want to specify an absolute path for the file. But you neither want to access it with a relative path (as your example), because Java assumes that path is relative to the “current directory“. Usually the preferred way for this scenario is to load it relatively from the classpath.
Java provides you the classLoader.getResource() method for doing this. And Eclipse (in the normal setup) assumes src/ is to be in the root of your classpath, so that, after compiling, it copies everything to your output directory ( bin/ ), the java files in compiled form ( .class ), the rest as is.
So, for example, if you place your file in src/Files/myfile.txt, it will be copied at compile time to bin/Files/myfile.txt ; and, at runtime, bin/ will be in (the root of) your classpath. So, by calling getResource("/Files/myfile.txt") (in some of its variants) you will be able to read it.
Edited: Further, if your file is conceptually tied to a java class (eg, some com.example.MyClass has a MyClass.cfg associated configuration file), you can use the getResource() method from the class and use a (resource) relative path: MyClass.getResource("MyClass.cfg"). The file then will be searched in the classpath, but with the class package pre-appended. So that, in this scenario, you’ll typically place your MyClass.cfg and MyClass.java files in the same directory.