On 6/10/18 6:33 PM, Bryan Pendleton wrote:
Well, I can't say I'm wildly enthusiastic about the new longer
directory names,
I still don't understand the motivation for this requirement. Maybe it
makes sense as a best practice for greenfield applications. But it
struck me as an unnecessary hurdle for large, legacy codelines like
ours. I must be missing something tricky but crucial.
but I successfully sync'd my sandbox and built the
latest code on Windows 10.
I also had a few directories left around. In my case, they contained
things like '.rej' files, leftovers from svn merges in the past.
Thanks for continuing to push this ahead, Rick!
I'm grinding my teeth over javadoc warnings now.
Thanks,
-Rick
bryan
On Sat, Jun 9, 2018 at 6:29 AM, Rick Hillegas <[email protected]> wrote:
I have checked in derby-6945-37-aa-renameSourceRootsToModuleNames.diff. That
patch renames the source roots as follows:
java/client -> java/org.apache.derby.client
java/shared -> java/org.apache.derby.commons
java/engine -> java/org.apache.derby.engine
java/optional -> java/org.apache.derby.optionaltools
java/run -> java/org.apache.derby.runner
java/drda -> java/org.apache.derby.server
java/testing -> java/org.apache.derby.tests
java/tools -> java/org.apache.derby.tools
After checking in this patch, I updated another workspace on my machine. For
reasons which I don't understand, svn reported that the following
directories were still hanging around, even though they were no longer under
source control:
? java/client
? java/drda
? java/shared
? java/testing
? java/tools
I deleted those directories by hand. You may need to perform similar cleanup
after syncing to the head of the development trunk.
Thanks for your patience,
-Rick
