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

Bug 337340

Summary:	ID-A99SX
Product:	[Technology] Subversive	Reporter:	kenneth.v.george
Component:	Core	Assignee:	Igor Burilo <igor.burilo>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	a.gurov
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description kenneth.v.george

2011-02-16 12:44:47 EST

When building projects (compiling, JAR building, etc.) when a project has been checked-out using Subversive, the .svn directories in the source are copied to the /bin compile directories.  Additionally, the .svn directories are also included in any JAR that is exported.  However, when using plug-ins such as Subclipse, this behavior is not seen.

Comment 1 Alexander Gurov

2011-02-17 15:15:30 EST

Such a behaviour is not seen even when using Subversive. :) 
Jokes aside, every Subversive build were done with Subversive and there is no problem with the distributions (no .svn folders), right?
Actually I've checked this with Eclipse IDE versions 3.4-3.7, with Java-development related distributions and with PDT and never even once encountered such a problem for years. And there is no similar reports AFAIR for recent plug-in versions for at least 2 or 3 years.

So, could you please provide some additional information:
1) main plugin version?
2) connectors version and which connector is actually used?
3) is there any specific to checking out the project where problem happens (or to the project itself)?
4) which Eclipse IDE version it is (or perhaps it is FlexBuilder or something else)?
5) is there any stable steps to reproduce?
6) Did it happens even if you create a new workspace (is there a chance that workspace is damaged in some way)?
7) Do you have another SVN-support plug-ins installed into the same Eclipse IDE instance where Subversive is installed (if there is - could it be conflict between implementations of the both plug-ins)?
8) Somethings else that matters for the issue?

Comment 2 Alexander Gurov

2011-03-08 04:45:44 EST

There are no additional information, no way to reproduce. Probably the issue is related to the damaged workspace, or caused by some third-party plug-in. If there are steps to reproduce, then please reopen the issue and provide all required information.