[jsword-devel] Build is broken

[DM Smith]

Joe Walker wrote:
> 
> I'm working on it, but it is a little complex.

I started, and found that out. I made such a mess, I reverted back to CVS.

> 
> I didn't rename jsword/java/* because I wanted to keep the CVS history 
> of the files. If we rename them all then it would be much harder to go 
> back in time on a file.

That's what I thought. I have found the history to be useful. I have 
used RCS before and have been able to move stuff around w/o losing 
history. It was a manual effort though. (i.e. directly in the file 
system). Since CVS is built on top of RCS, I agree with Paul and would 
think it would be possible.

> 
> Joe.
> 
> 
> DM Smith wrote:
> 
>> With the refactoring of the projects, the build is broken.
>>
>> I found this out the hard way by deleting the generated osis stuff.
>>
>> Anyway, I think this is probably important to fix, but I don't know 
>> that much about ant to be effective.
>>
>> Some thoughts:
>> The build for common, jsword, and bibledesktop should only build and 
>> test themselves.
>>
>> The build for jsword should build common, if needed.
>> Likewise, bibledesktop should build jsword, if needed.
>>   (Which would make sure common was built.)
>>
>> The build for jsword-web should gather and prepare for deployment.
>>   (It appears that this is what Joe intended)
>> It should build bibledesktop, if needed.
>>
>> Another thought on refactoring:
>> In common, bibledesktop and jsword-web there is a new layout of source 
>> folders, with java/main and java/test.
>> The project jsword still has the old layout, with java/jsword and 
>> java/jswordtest.
>> Perhaps these should be renamed.
>>
>> But wait until I send a patch. It would be too hard to merge after 
>> refactoring.