So, we have a product that we OEM. Recently, an OEM customer was upset that our programmers documentation (and javadocs) had our name throughout, and we were supposed to have gotten rid of all references to us as port of the OEM process (we are doing the OEM work for this customer - usually companies do it themselves).

So, the question. I thought the convention for package names was com.companyname.productname.something.something. The company name is there to ensure that even if we have the same file names (,, to name two) the package is guaranteed to be unique.

Any thoughts on this? Should we continue going the way we have? Should an OEM have "generic" package names, and run the risk of someone coming before us in a classpath with the same package/file and screwing us up?