[jdom-interest] JDOM-like package names

[Joseph Bowbeer]

I for one would like to avoid confusion over package names.  If someone
wants to add something to the org.jdom package in their own project as a
temp. workaround, that's one thing, but I don't want two different
org.jdom.Element's running around on the internet.

I would suggest a separate project, separate package name, and only
JDOM-like compatibility.


----- original message -----

Patrick Dowler wrote:

On the subject of forking code and interfaces, there is one
catch here that seems relevant. James' goal is for his fork
to remain API compatible with JDOM, which means that he
needs to have classes named org.jdom.Element (etc).

Is that an acceptable use of the word "jdom"?