Ulrich Köster wrote:
> Am 02.08.2004 um 18:08 schrieb Anjo Krank:
>> Am 02.08.2004 um 18:08 schrieb Ulrich Köster:
>>> Am 02.08.2004 um 17:59 schrieb Anjo Krank:
>>>> can someone else verify that changing a ant/*.patternset file will
>>>> throw Eclipse in a state where it is always building, then updating
>>>> resources, then updating the java files and start at the beginning
>>>> again? My uneducated guess is that the build/ folder resources will
>>>> trigger an update again.
>>>>
>>>> I seemingly fixed this in CVS by excluding the .svn/, CVS/, dist/,
>>>> *~/ and build/ folders automatically from the build with no need to
>>>> set it explicitely. There's just no use case where it would make
>>>> sense to include a resource from there for incremental builds.
>>>> IsPrivateTeamMember just doesn't cut it if one is not using
>>>> Eclipse's built-in version control.
>>>
>>> In which class?
>>
>>
>> ./projects/wolips/plugins/org.objectstyle.wolips.datasets/java/org/
>> objectstyle/wolips/datasets/adaptable/ProjectPatternsets.java
>>
>> But that's still not it. I still get the ping-pong effect when I
>> change a whatever.include.patternset.
>
>
> Is svn the problem?
>
> I've changed the JavaElementListener to a ResourceListener.
I think the reason this happens is that both the incremental builder and
the resource listener always change certain files. The incremental
builder touches at least the Info.plist, the PB.project updater always
writes the PB.project .
As I mentioned before, I think converting the different
ResourceChangeListenerS into builders should fix the problem.
Harald
This archive was generated by hypermail 2.0.0 : Mon Aug 02 2004 - 13:21:53 EDT