RE: [p4] P4WSAD question

Yes, we experience the same.  It is a real pain; especially so when
refactoring more than just a few things.  Sometimes you may just let it go,
sometimes you meticulously save the needed files aside, revert them, then to
the manual integrate to preserve the rename history.  Not fun.  

I have meant to explore this further - whether it is an Eclipse/WSAD API
issue or the Perforce plugin - as the same behavior exists with other
Eclipse/WSAD SCM plugins.

I have submitted other change requests to Perforce support on the plugin,
but not this one yet.  If you do, please let me know so I can ask for
inclusion on that request.  

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Smith, Jeff
Sent: Thursday, September 01, 2005 8:26 AM
To: perforce-user <at> perforce.com
Subject: [p4] P4WSAD question

We have some development groups that are using the latest version of P4WSAD
and claim that when they perform Perforce code restructuring, Eclipse is
doing a delete/add rather than an integrate/delete and thereby not leaving
any integration records of the change.

I have verified that there are no integration records for these changes and
was wondering if this is a known problem or if I need to investigate their
usage and configuration of P4WSAD.

Jeff