Resolving name conflicts

Question

hi all, i have this package called "Exception", but whenever i try to access this package from elsewhere by calling Exception.Class1, the compiler thought i was going for java.lang.Exception.Class1 and gave me an error. is there a way to resolve this?

Answer 1

@OP. The reason you do not want to name a package the same as a core Java class is that
1. You will confuse anyone reading your code
2. You will likely confuse you own IDE when it attempts to refactor, organize imports, etc. for you
Take the following advice. Follow standard Java naming conventions. That means:
1. A package should be all lower case. Rename your package to 'exceptions', and there will be less ambiguity
2. A type (class, interface, enum, etc.) should be UpperCamelCase
3. A method or a field should be lowerCamelCase
4. Constants should be ALL_UNDERSCORE_DELIMITED_UPPER_CASE
5. Avoid using core Java classes as names (e.g. anything in java.lang)
When asking a question on these forums, follow the following guidelines:
1. Write a short, concise description of what you have done, the problem you are encountering and what you think is wrong
2. Post a short, concise and relevant portion of the code you believe is causing the issue (normally invoking caller and the receiving method code)
3. If you are getting an actual error, post the stack trace. No one can help you without understanding what the error you are encountering is.
Follow the above guidelines, and you will both post better questions and receive better answers to your issues. Your code will also follow Java (rather than what appears to be VB or C#) conventions and be easier to understand.
- Saish