Bug 138278 - [Model Sync Share] Java hides bin folder during share
Summary: [Model Sync Share] Java hides bin folder during share
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 172027
  Show dependency tree
 
Reported: 2006-04-24 18:03 EDT by mike.andrews@sac.com CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mike.andrews@sac.com CLA 2006-04-24 18:03:39 EDT
in 3.2RC1a: 

when i initially share a project (initial import), i get two dialogs about which files and directories to share. first one leaves out "bin" directory where "*.class" files are, but then the second one, the "Commit files" dialog, doesn't. in that view i have to explicitly right-click and add "bin" dir to cvsignore. seems like a bug, and moreover is dangerous, since first dialog leads you to believe that bin won't be shares, whereas in fact it WOULD be shared if you click through second dialog too quickly without realizing the difference.

thanks,
mike
Comment 1 Michael Valenta CLA 2006-06-07 11:40:18 EDT
There's nothing wrong with the .cvsignore. The bin folder is not a derived folder (i.e. it is not generated by the build) so it must be manually ignored. The problem is that the Java content provider (which appears during the share) hides the bin folder. It would be good if we could come up with some way for the Java model to help the user ignore this file during a share.
Comment 2 Michael Valenta CLA 2007-04-18 21:22:13 EDT
We didn't have time to address this in 3.3.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:15:21 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.