Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 72349

Summary:	[Operations] Problem with commiting project 'bin' folder
Product:	[Eclipse Project] Platform	Reporter:	Paweł Dembski <paweld>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	kubak
Version:	3.0	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Paweł Dembski

2004-08-20 10:21:39 EDT

For certain reasons we need to store in repository not only source files, but
also project output files. We used to store output in separate folder bin. It
seems that the only way to achieve this is to explicitly add every output file
to version control, which is very cumbersome. It would be pleasant to have it
done with clicking one check box.

Comment 1 Kuba Królikowski

2004-09-07 06:37:31 EDT

In my opinion this is a bug. There is "*.class" in "Ignored Resources"
(Preferences -> Team), but when I'm using "Synchronize with repository" on "bin"
folder (which is my output folder of course) classes are ignored. I have to add
to verstion control each class by hand, and only then synchronizing is taking
this files into account. I think there should be a way to work with ".class"
files (and other binary) as like with ".java" files.

Comment 2 Michael Valenta

2004-10-13 12:27:32 EDT

Could be done in conjunction with bug 76037.

Comment 3 Krzysztof Daniel

2007-05-14 07:35:57 EDT

In 3.3m7 *.class are not in ignored resources anymore.

However, the behaviour still exists. Any hints, Michael?

Comment 4 Michael Valenta

2007-05-14 15:44:57 EDT

The *.class files are marked as "derived" by the Java builder. Repository Providers like CVS will ignore derived resources.

Comment 5 Krzysztof Daniel

2007-06-22 05:42:59 EDT

Kuba,

As Michael said, derived resources are ignored by Repository Providers. And it seems, that we can do nothing about this.

Could you provide more details about your use case? Maybe we can work together out some solution...

Comment 6 Krzysztof Daniel

2007-06-22 05:44:07 EDT

Sorry, my previous comment is addressed to Pawel.

Comment 7 Krzysztof Daniel

2007-06-27 07:14:24 EDT

It seems to me that this bug is tightly connected to the bug 150578. If we will have project specific derived setting, I think it would be possible to manually *unmark* derived resources.

Comment 8 Eclipse Webmaster

2019-09-06 16:03:55 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.

Comment 9 Eclipse Genie

2021-11-26 07:46:25 EST

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.