IC45411: WHEN COPYING .JAVA FILES IN ECLIPSE, THE COPY SOURCE GETS CHECKED OUT

APAR status

• Closed as suggestion for future release.

Error description

• Operating system:  Windows
  ClearCase versions affected: 2003.06.14, Eclipse 2.1, ClearCase
  plugin 2.2.62
  References:
  Could repro:   YES
  
  Problem Description:
  
  
  When you copy a .java file from one folder to another, using
  copy/paste, the source file is checked out. This is only the
  case with .java files. Textfiles for example show normal
  behaviour.
  
  Steps to repro:
  1. Inside an Eclipse-workspace, create 2 folders.
  2. In folder1, create a file test.java
  3. Check out test.java, make changes and check in.
  4. Rightclick on test.java and select copy.
  5. Navigate to folder2, rightclick and select paste.
  6. See test.java checked out in folder1.
  

Local fix

• undo checkout manually
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This issue is caused by Eclipse issuing an incorrect
  "validateEdit" command on issuance of the "paste" command.  The
  item in the Team->ClearCase SCM Adapter preference page is:
  "When checked in files are edited by an internal,
  non-interactive editor".  It's default setting is "automatically
  check out".  If you set this to "do nothing" the validateEdit
  fails and the new resource will not get created.  This is an
  Eclipse bug, and was evidently fixed for Eclipse 3.0.x.  If the
  customer needs to have it back-ported, they'll need to file a
  defect against Eclipse 2.1 with bugzilla, stating something
  like: "Eclipse causes an internal validateEdit when you paste a
  resource that has been copied -- causes uneeded checkouts with
  scm providers".  Note that you do not have to paste the java
  file into a different folder, either.  But this is an Eclipse
  problem in actuality.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels