You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@any23.apache.org by "Andy Seaborne (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/01/12 10:19:39 UTC
[jira] [Issue Comment Edited] (ANY23-21) Migrate all packages and
classes to ORG.APACHE.ANY23
[ https://issues.apache.org/jira/browse/ANY23-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184837#comment-13184837 ]
Andy Seaborne edited comment on ANY23-21 at 1/12/12 9:17 AM:
-------------------------------------------------------------
Eclipse rename of a package tree works for the source tree. grepping for renaming occurrences of the old name points things to checked e.g. POM files.
I've just done this for Jena Fuseki this week. The biggest problem I encountered is Eclipse subversion (subclipse or subversive) checking it back into SVN. Using command line SVN is much more reliable for directory changes in my experience. It was not done by patch - the changes were made directly to trunk.
If anything does go wrong with the check-in, its with deleting the old directories. Sometimes, you have to update/overwrite to get the old tree (directories, not files) back and redelete. Breaking it up into all the file changes and then all the directory changes is less nerve racking. I have never lost anything.
By the way: in Jena, we are probably leaving any java repackaging until there is a major version change for some technical changes. Changes around RDF 1.1, while small, are externally visible changes so such a point is coming up and its a chance to do some tidying up as well. We did change the maven group id. for the first release.
Long ago, for Jena1->Jena2 we did a package rename using perl: it is quite easy. Moving files and fixing package/imports does nearly everything, then a few manual changes if there are any explicit full path names ro dynamic loading. We then shipped the perl script with the next release to help application writers migrate. The user base was a lot smaller then though.
Good luck - it's a large change but it's not a long job in my experience.
was (Author: andy.seaborne):
Eclipse rename of a package tree works for the source tree. grepping for renaming occurrences of the old name points things to checked e.g. POM files.
I've just done this for Jena Fuseki this week. The biggest problem I encountered is Eclipse subversion (subclipse or subversive) checking it back into SVN. Using command line SVN is much more reliable for directory changes in my experience.
If anything does go wrong with the check-in, its with deleting the old directories. Sometimes, you have to update/overwrite to get the old tree (directories, not files) back and redelete. Breaking it up into all the file changes and then all the directory changes is less nerve racking. I have never lost anything.
By the way: in Jena, we are probably leaving any java repackaging until there is a major version change for some technical changes. Changes around RDF 1.1, while small, are externally visible changes so such a point is coming up and its a chance to do some tidying up as well. We did change the maven group id. for the first release.
Long ago, for Jena1->Jena2 we did a package rename using perl: it is quite easy. Moving files and fixing package/imports does nearly everything, then a few manual changes if there are any explicit full path names ro dynamic loading. We then shipped the perl script with the next release to help application writers migrate. The user base was a lot smaller then though.
Good luck - it's a large change but it's not a long job in my experience.
> Migrate all packages and classes to ORG.APACHE.ANY23
> ----------------------------------------------------
>
> Key: ANY23-21
> URL: https://issues.apache.org/jira/browse/ANY23-21
> Project: Apache Any23
> Issue Type: Task
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Blocker
>
> This is standard operating procedures @ ASF so we should adhere to best practice.
--
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