Another option comes from David Williams in a thread a few months ago:
David M Williams wrote:
Just a tip ... I've sometimes used ...
if it would help avoid confusion.
You can "version off" the
old project, with a tag such as "vyyyymmdd_finalVersion" then,
delelete everthing in your local copy, except the .project file
(perhaps
simplified to be "simple project")
and one file, named something like
archive.txt,
and in that txt file put a description of the current status ... such as
"moved to <abcd> but
left here to keep the history of the files before the move. You can
load
the
vyyyymmdd_finalVersion to see
the final state and/or get history from there".
They you can commit this "nearly
deleted" version in head.
That way, if someone absent-mindedly
loads the old version, it'd be more obvious that was no longer the
correct version to be actively working
with.
(just don't use "obsolele.txt"
as the remaining file name, as that is, by convention, a marker meaning
its ok
to remove that project from cvs).
Just a suggestion.
Paul Fullbright wrote:
OK, rename done. New plugins in the same place as the old. Have fun
resynching; I know I did.
What's left to be done:
- Features and build need to incorporate renames (Tran?)
- Cleanup of old plugins. Exactly how extensive do we want to be?
There are old plugins and old old plugins in old modules in our
repository space. We need complete (but not *too* complete, if you
know what I mean) list of what needs to be removed.
- P
Brian Vosburgh wrote:
Yeah - it makes it a lot
easier for me to see what I've changed if there's something to compare
it to. :-) Otherwise, I'm OK with the plug-in rename.
Brian
Sent Tue
3/6/2007
2:56 PM
Subject Re:
[dali-dev] Dali 1.0 Package and Plugin Name Change Notice
- P
Karen Moore wrote:
I'm
fine with you continuing on and renaming the plugins now. Any chance
you want to clean out all the old plugins from cvs when you're done?
Karen
Paul Fullbright wrote:
1.
Correct
2. My thought was that we determined that there need not be a
distinction between testing internal and non-internal code in the test
package names. At any rate, the point is 'moo' (nod to Joey), since we
have no non-internal plugin code at the moment. This can always be
changed back, of course.
At any rate, the rename is complete now except for plugin renames.
Should I wait for people to synch before doing that?
- Paul
Brian Vosburgh wrote:
Two things:
1. I don't see ...jpa.core.facet; but I assume that it will be renamed ...jpa.core.internal.facet.
2. I thought we decided that the "internal" node did not need to be used in the test packages; but maybe I missed the final decision?
Thanks.
Brian
-----Original Message-----
>From Paul Fullbright <paul.fullbright@xxxxxxxxxx>
Sent Mon 3/5/2007 3:32 PM
To General Dali EJB ORM developer discussion. <dali-dev@xxxxxxxxxxx>
Subject Re: [dali-dev] Dali 1.0 Package and Plugin Name Change Notice
Hello all,
Here is my proposal for package renaming:
Current Name Proposed Name
jpa.core plugin
...jpa.core ...jpa.core.internal
...jpa.core.util ...jpa.core.internal.util
(Note, this will entail merging of two ePackages into one)
...jpa.core.java ...jpa.core.internal.content.java
...jpa.core.java.internal ...jpa.core.internal.content.java
(Note, just as above, these two ePackages will be merged)
...jpa.core.java.util ...jpa.core.internal.content.java.util
...jpa.core.java.internal.util ...jpa.core.internal.content.java.util
(Note, same merge)
...jpa.core.java.mappings ...jpa.core.internal.content.java.mappings
...jpa.core.java.mapping.util ...jpa.core.internal.content.java.mappings.util
...jpa.core.jdtutility ...jpa.core.internal.jdtutility
...jpa.core.mappings ...jpa.core.internal.mappings
...jpa.core.mappings.util ...jpa.core.internal.mappings.util
...jpa.core.platform ...jpa.core.internal.platform
...jpa.core.platform.generic ...jpa.core.internal.platform.generic
...jpa.core.prefs ...jpa.core.internal.prefs
jpa.core.tests plugin
...jpa.core.tests.* ...jpa.core.tests.internal.*
jpa.db plugin
...jpa.db.* ...jpa.db.internal.*
jpa.db.tests plugin
...jpa.db.tests.* ...jpa.db.tests.internal.*
jpa.db.ui plugin
...jpa.db.ui.* ...jpa.db.ui.internal.*
jpa.gen plugin
...jpa.gen.* ...jpa.gen.internal.*
jpa.ui plugin
...jpa.ui.* ...jpa.ui.internal.*
(various small renames to fall in line with core names)
jpa.utility plugin
...jpa.internal.utility.* ...jpa.utility.internal.*
jpa.utility.tests plugin
...jpa.utility.tests.* ...jpa.utility.tests.internal.*
Most everything "non-core" is straightforward.
Discussion appreciated.
- Paul
Brian Vosburgh wrote:
While renaming our plugins, we should also rename some of our packages:
Current Name Proposed Name
jpa.core plugin
...jpa.core.java.internal ...jpa.core.internal.java
...jpa.core.java.internal.util ...jpa.core.internal.java.util
jpa.utility plugin
...jpa.internal.utility ...jpa.utility.internal
...jpa.internal.utility.iterators ...jpa.utility.internal.iterators
jpa.utility.tests plugin
...jpa.utility.tests ...jpa.utility.tests.internal
...jpa.utility.tests.iterators ...jpa.utility.tests.internal.iterators
The proposed names simply move the "internal" package name node to immediately
following the plugin name portion of the package name.
Does this make sense?
Brian
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
--
Paul Fullbright
Oracle Corp.
Eclipse Dali/Java Persistence Tools Development
paul.fullbright@xxxxxxxxxx
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
--
Paul Fullbright
Oracle Corp.
Eclipse Dali/Java Persistence Tools Development
paul.fullbright@xxxxxxxxxx
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
--
Paul Fullbright
Oracle Corp.
Eclipse Dali/Java Persistence Tools Development
paul.fullbright@xxxxxxxxxx
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
|
