Compiler 'Warning' not understood for relevance.

Writing a small GUI programme, and coming across a Warning (which I have suppressed / got rid of but ) which I don't understand :

warning: [path] bad path element "C:\EE_Q_CODE\packg": no such file or directory

I'm not referencing anything requiring resources in that non-existent folder, neither are there any jars or classes that are missing. So where is the idea coming from that this folder is required? Never seen such a phenomenon before.

As I say, I have got rid of the warning, (presently by adding an empty dir "packg" into the directory structure), but I'd very much like to know where the requirement for this is coming from. Any ideas please?
LVL 17
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are there any jar files in the build path?
krakatoaAuthor Commented:
No, none.
It would be interesting to see what your command line was

There are various reports about that error, including mention of it as a bug.


Open in new window

should work to suppress the error as well

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Learn Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

krakatoaAuthor Commented:
Yes, thanks.

Well the command line was simply javac, and my .java file. There's  nothing like a jar or anything else other than straight API imports anywhere near the code.
krakatoaAuthor Commented:
One of the most unexpected oddities I've yet come across in Java. It's usually me.
How could we reproduce the error on our machines?
krakatoaAuthor Commented:
I don’t really know ...
krakatoaAuthor Commented:
(Schedule a live session? I thought I was alive . . . or, at least, the present interface. Better check-back later).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.