Re: [Jsynthlib-devel] So, what's the next big feature?

[Joe E. <jo...@em...>]

Hiroo Hayashi wrote:

>2. package structure change (move to org.jsynthlib)
>
>2.1 making consensus
>We had discussion and I made summary a few times.  But I could not
>continue the job for my laziness.
>
>2.2 making change
>It is too much work for a person to make the all of changes.  How can we
>share the work?
>
>I think the refactoring feature in Eclipse may reduce the work a lot,
>but I'm not sure.
>  
>
Yes, it would. Also, IDEA has the same refactoring features and it 
really does work very easily. I could probably do all of this in an evening.

Although I was a big proponent of this idea back when I proposed it a 
couple of years ago (and I still would like to see it happen) one big 
downside to this has occured to me (which has probably been mentioned 
already). This will probably have *dramatic* effects on 
version-comparison in the CVS tree. Right now, on SourceForge, you can 
go into the CVS tree and compare any verison of a file to any other 
version of it. If we move the files in the CVS tree, I fear that CVS 
will think that we deleted a file and added another (instead of figuring 
out that we just moved one). I don't know how smart CVS is about things 
like that.

The alternative would be to merely change the *package* directives in 
the source so that they *compiled* to a different directory structure, 
while leaving the *source* files in their *old* structure. This would be 
the worst possible solution, in my opinion. In fact, I feel that it 
would be worse than how it is *now*.

Has this consideration already been addressed?

- Joe