renaming java/spec/sdo Java API folder -- similar required for DAS/SCA?

[kelvin goodson <ke...@gmail.com>]

FYI, particularly for DAS and SCA release managers

I have a further issue with cutting a source distribution for sdo that I
think DAS and SCA will have seen or will see.
The issue arises because of these factors

- We keep spec and impl projects separate
- The "top level" SDO folder in spec is named "sdo",  which is the same as
the top level folder for the impl
- We share the java/spec folder between sub-projects
- The top level folder of any source distribution requires a BUILDING.txtfile
- It would be good when
    a) creating a branch for a release and
    b) when a user has downloaded the two source distributions and extracted
them
  to have these two top level folders as peers (<parent-folder>/sdo and
<parent-folder>/sdo !!!)

so that's not possible when cutting a distribution,  and if a user were to
extract two archives side by side that had the same top level folder then
the outputs of the extraction would be merged.  To date I have been creating
an asymmetric branch with spec/sdo and sdo folders to get round this,  but
that doesn't help me get the BUILDING.txt file into the top level folder of
the spec source distro, as this shared folder would require different
BUILDING.txt files for each sub-project.

So the long and the sort of it is that I'm renaming the spec/sdo folder to
spec/sdo-api  .  I thought I had better explain why,  as it may seem like
gratuitous churn.

Regards, Kelvin.