For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 20 years, 8 months ago by
.
-
Posts
-
I have eclipse 3.0.2 and evaluating myeclipse 3.8.4, using Tomcat 5.5.9 as the application server.
I also use SVN for the repository. SVN use a directory structure with .SVN as a control directory.
When deploying the .SVN directories are also deployed as well. How can I filter directories and files in order to prevent them to be deployed. Deleting, or moving is out of the question.
My System profile Info:
– System Setup ——————————-
Operating System and version:
Eclipse version: 3.0.2
Eclipse build id: 200503110845
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.8.4
Eclipse JDK version: 1.5.0
Application Server JDK version: 1.5.0
Are there any exceptions in the Eclipse log file? NOIf this is a DB related question please answer the following:
RDBMS vendor and version:
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:– Message Body ——————————-
This is a known problem, basically there is a way to mark a resource in Eclipse as “derived” like the CVS plugin does, but currently the SVN plugin does not do that, so to MyEclipse the .SVN directories look valid and goes ahead and deploys them. You can manually mark each SVN directory as “derived” which will stop the deployment tool from deploying it by right clicking on each dir and going to Properties then checking “Derived.”
What you are saying is that we can not have a filter pattern, and we should “mark” the undesire directory with a derived property.
I am relative new to eclipse, in fact I am testing it along with myeclipse. It seems to me that the suggested approach has two serious flaws that prevent it to be somewhat practical.
1.This property (derived) can not be exported, imported, nor backup; in order to allow them to be shared among different developers, or moved to different locations.
2.In a 1-5 folders project this is fun, in a medium size to big project this is imposible.
Do you have any other suggestion or approach that can address those two issues?
We understand this is a pain and wish the plugin would honor this property as it should (like the CVS plugin), for the time being there is no other workaround (I understand it doesn’t scale to large projects and cannot be shared) but we hope to provide filter patterns and things of that nature in the 5.x series of MyEclipse later this year. There is no official ETA yet. Have you tried contacting the subclipse developers and asking about this?
