[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] EclipseME and "verified" directory

From: Erem Írs <erem.ors_at_integral.com.tr>
Date: 2006-03-28 15:17:51 CEST


These days I try to discover about Subclipse, but I met a problem. I
will be very glad if someone lends me a hand.

My system:
Server: Linux Debian Sarge + Subversion 1.3.0 (FSFS repository and svn
Client: Windows XP + Eclipse 3.1.1 + EclipseME 1.2.3 + Subclipse 0.9.108

What I did:
- I imported all my projects into repository with "svn import". J2ME
projects using EclipseME and Tomcat projects.
- I tried to check out one of the J2ME projects. I clicked yes button
when I was asked to overwrite the existing project.

Problem is this:
There is "verified" directory created by EclipseME plugin where verified
class files and libraries reside.
After all the files are added in the checkout process, Eclipse builds
the workspace and meanwhile "delete --force" commands appear in the
console 'deleting' all the files and folders under "verified" folder.
After this, Subclipse Team menu acts as if "verified" directory is not
in version control and there is not any sign on folder icon. TortoiseSVN
and svn console command tell me that the folders and files are deleted.
There was a "bin" directory under version control for which later I
added a svn:ignore property, because it is generated automatically with
every build. I think this is a similiar problem. Maybe I can ignore
"verified/classes" path, but I cannot ignore "verified/lib" path because
there are preverified libraries on which the project depends.

I hope there is someone who developes EclipseME projects with Subclipse
without problems and shares it with me.

Erem Írs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Mar 28 15:19:07 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.