(copied back to the list)
On 6 Nov 2006, at 18:31, Reynolds, Gordon R wrote:
> Jeremy,
>
> Thanks for your response.
>
> Yes, one could do that, but it would require leaving the .svn
> folder absent for very long periods
> of time while development is underway, and the developer might
> forget to replace it when they've
> completed work. It's a workaround rather than a solution.
Yes. It is a work around and it's far from ideal, but it's all I had
at the time.
>
> One can look at this problem from either one of two perspectives:
>
> it is either a 'design flaw' with Subversion itself, or it is a
> 'bug' with Fuego. In similar situations,
> this often ends up with the two vendors each pointing fingers at
> the other. Still, I've
> asked our onsite BEA guy to post a ticket for this issue to BEA,
> hoping they'll view it as in
> their interest to prevent this incompatibility since SVN is gaining
> fairly wide use.
It's a difficult one, but I think it's a flaw in the application that
treats a file system directory as a single opaque object and expects
everything else on the system to do the same.
>
> In the design flaw camp you can point to a lot of early IDE's that
> did something similar by adding
> proprietary markings to the code they managed. That eventually fell
> by the wayside, replaced by
> a single 'project' file (for JBuilder, or Eclipse, or IDEA) that
> was usually housed in a different directory
> than the code it managed. Although the .svn folder is not nearly as
> invasive, it is very pervasive.
> The Subversion team might want to consider making a future
> transition similar to the one that these
> earlier IDE's made.
>
> Regards,
>
> Gordon Reynolds
>
> From: Jeremy Pereira [mailto:jeremyp@jeremyp.net]
> Sent: Monday, November 06, 2006 8:59 AM
> To: Reynolds, Gordon R
> Cc: users@subversion.tigris.org
> Subject: Re: .svn folder causing errors with Fuego 5.5 (BEA ALBPM)
>
>
> On 3 Nov 2006, at 21:14, Reynolds, Gordon R wrote:
>
>> Until now, I've not run into this problem with using Subversion.
>> And strictly speaking,
>> this is not really a problem with Subversion but with Fuego 5.5
>> itself.
>>
>> It appears that the .svn folder in two of the Fuego 5.5 project
>> folders causes it to
>> fail to start up. I doubt many of you are familiar with Fuego - it
>> is a Business Process
>> Modeling product recently acquired by BEA - but I'll just mention
>> that the two folders
>> that cause the problem are /[Fuego project name]/organization/ou
>> and any subfolders
>> thereof.
>>
>> Has anyone encountered similar problems with other software
>> product incompatibilies
>> when using SVN for source control and, if so, have you found a
>> solution?
> Early versions of Macintosh xcode/Interface Builder had a similar
> issue. I used to get around it by moving the .svn folder out of
> the directory to somewhere else and then moving it back again
> whenever I needed to do a subversion operation.
>
> There was a feature request to have a property that would mark a
> folder and its contents as "opaque" so that Subversion would treat
> it as a single object but there was never much interest from the
> developers in getting it implemented, and then Apple fixed xcode.
>
>
>>
>> Regards,
>>
>> Gordon Reynolds | Sr. Analyst/Programmer
>> ISTS Application Services, Customer Services, Internet Services
>> Phone: (415) 973-2373
>> Cell: (916) 613-2315
>>
>>
>>
>
Received on Tue Nov 7 11:45:34 2006