You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/05/01 13:49:06 UTC
[jira] [Comment Edited] (JENA-192) Jena java package renaming.
[ https://issues.apache.org/jira/browse/JENA-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523098#comment-14523098 ]
Andy Seaborne edited comment on JENA-192 at 5/1/15 11:48 AM:
-------------------------------------------------------------
master is main jena3 code development now so i think it's time to close this. The "jena3" working branch has already gone.
was (Author: andy.seaborne):
master is main jena3 code development now so i think it's time to close this, and also to delete the "jena3" working branch.
> 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
> Fix For: Jena 3.0.0
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)