Search:

Everywhere you want, outside the jar. Obviously in a location that is appropriate/reasonable.
You can use a "known" location, for example under the "home" directory of the user. It's easily...

"Resources" (in the sense intended by getResource/getResourceAsStream) are read-only. There's no equivalent to write a resource!

And, in general, you should not try to update the content of a jar....

This is a pathname on the local file-system (and it has nothing to do with "resources" into the jar). And it's an absolute path. On Windows it is resolved to e.g. C:\data\adminData.txt (or what is...

This is technically correct, for what I see here.


If you mean the creation/write of a file on the local file-system .... it's another thing. It has no (direct) relation to "resources".


...

First, you must use '/' as separator. That is not a "pathname" on file-system .... it's a resource specification! It's a different, more specific, thing. Javadoc documentation precisely states this....

For what I see here, a resource specification "/images/indaSupport.png" should work.
Does it work? Or not?

Yes, conceptually it would be correct!

Now .... I have a doubt: that Eclipse doesn't know how to handle those LoginSystemSource folder. May be that Eclipse doesn't copy all non-java files to the...

Sorry, it's not clear. If you have used Eclipse, your project should have an "src" folder. Is your LoginSystemSource the Eclipse source folder? (it would be strange).

If you had for example:

...

Did you understand the concept? I guess of no.
Where are those images? In which package?

Here you have used the concept of "resource". But a resource specification that starts with '/' means that the name is "absolute" starting from the classpath "root". So, do you have a top level...

I guess/imagine you have done a thing like:

.... ImageIO.read(new File("someimage.png"))

or similar concept.

Well, "someimage.png" is a specification on the local file-system and, more...