[
https://issues.apache.org/jira/browse/JENA-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260734#comment-13260734
]
Stephen Allen commented on JENA-192:
------------------------------------
Moving this from email list to JIRA:
Would it be possible to have the c.h.h.j.* classes living in a separate
optional compatibility jar? It would be nice to be able to remove it if you've
switched fully to the new API. Would this be harder than having them in the
same jar?
One thought is new user confusion when their Eclipse autocomplete brings up two
copies of every class.
> Jena java package renaming.
> ---------------------------
>
> Key: JENA-192
> URL: https://issues.apache.org/jira/browse/JENA-192
> Project: Apache Jena
> Issue Type: Brainstorming
> Components: Jena
> Reporter: Andy Seaborne
>
> This JIRA is for discussion of renaming the package structure.
> What are the pros and cons of renaming the java packaging:
> com.hp.hpl.jena => org.apache.jena?
> The maven artifacts are already "org.apache.jena:jena-ABC"
> See also JENA-190 (delivery) and JENA-191 (modules and build)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
