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

Re: [Subclipse-users] [RE:]RIM eclipse JDE plugin commit problem

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 5 May 2008 15:02:27 -0400

2008/5/5 Mustafa Kemal UGURLU <kemal.ugurlu_at_srsteknoloji.com>:
> >> I develop Blackberry applications. RIM (www.rim.com) relase
> eclipse(Eclipse
> >> Platform Version: 3.3.1.1 Build id: M20071023-1652) based new JDE and i
> use
> >> this.
> >> Subclipse initial import fine but new versions of project files not
> >> commited corretly. Only root dir in (alx,cod and debug) files commited.
> >
> >What does it mean that they were not committed correctly? Does that
> >mean they were not committed at all or something about them was wrong?
>
> Sorry,
> I think this explanation is more clear.
>
> In EclipseJDE ide first commit is no problem. All files fine in subversion
> repository.
> In later commits, only files (alx,cod and debug) in root dir are commited.
> But changed source and resource files aren't committed.
>
> "src" source directory Type changed to "Linked Folder" after first commit.
>
> when i look at src properties :
> Path : /MyProject/src
> Type: Linked Folder
> Location : jde:/MyProject/D$/bb/MyProject/src
> Resolved Location : jde:/MyProject/D$/bb/MyProject/src

Thanks, that is a very relevant piece of information to provide.
Subclipse follows the recommendations for team providers in handling
linked resources ... namely we tolerate that they exist but do not
attempt to version control them.

See:

http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm

Specifically:

In order to be "link friendly", a provider should allow projects with
linked resources to be version controlled, but can disallow the
version controlling of linked resources themselves.

A considerably more complex solution would be to allow the versioning
of the actual linked resources, but this should be discouraged since
it brings with it complex scenarios (e.g. the file may already be
version controlled under a different project tree by another
provider). Our recommendation therefore is to support version
controlled projects which contain non-version controlled linked
resources.

So this obviously does not preclude us from supporting linked
resources. The main reason that we do not is that we use Subversion
API to do all work and that API has no knowledge of Eclipse-based
idioms such as linked resources.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-05-05 21:02:47 CEST

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