A builder will only help if this builder is installed and activated for
the project.
Ulrich
Am Mittwoch, 26.02.03 um 18:42 Uhr schrieb Harald Niesche:
> we could do that in the incremental build ...
> ----- Original Message -----
> From: "Ulrich Köster" <ulric..ssense.com>
> To: "Anders Peterson" <anders_peterso..ptimatika.se>
> Cc: "Dirk Olmes" <dirk.olme..mx.de>; <woproject-dev@objectstyle.org>
> Sent: Wednesday, February 26, 2003 4:06 PM
> Subject: Re: CVS and *.eomodeld~ files
>
>
>> Hi,
>>
>> Hmm I can`t reproduce this on our machines.
>> How about a resource listener that removes the cvs stuff from
>> *.emodeld~ for us?
>>
>> Any volunteers?
>>
>> Ulrich
>>
>> Am Mittwoch, 26.02.03 um 15:19 Uhr schrieb Anders Peterson:
>>
>>> Dirk Olmes wrote:
>>>>> I have seen odd things happening with eomodel files. I occasionally
>>>>> had the
>>>>> impression of having to make the same changes twice. Wonder if this
>>>>> is related to
>>>>> CVS getting confused?
>>>> Not CVS ... well not really. It's just that the backup eomodel also
>>>> has the CVS info in it which confuses Eclipse.
>>>>> Should nobody have a clean reliable fix, an option would be to add
>>>>> an ant task to
>>>>> the build process that removes all CVS directories from the
>>>>> *.eomodeld~ directories.
>>>> That's what I do now - although manually. If you remove the
>>>> .eomodeld~ before checkin no confusion happens .-)
>>>
>>> It's best to do this 'outside' eclipse. Otherwise eclipse may think
>>> you want to delete something from CVS (I've had that happen).
>>>
>>> Letting the (some) Ant script handle this may be a solution.
>>>
>>> /Anders
>>>
>>>
>>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed Feb 26 2003 - 12:49:38 EST