Hi everybody,
let me briefly introduce myself, my name is Patricio Keilty, work for a
company which is planning to migrate from CVS to SVN, we mostly develop
with Eclipse so we decided to probe Subclipse, i´m new to SVN & Subclipse.
This mail encouraged me to post my first message......
Agree with Charles, it would be nice that Subversion takes care of
repository layout based on recommended practices, in my opinion this
would cover 90% of the import new project use cases. Within CVS sharing
a project consists basically of a 2 steps process ( create module +
commit new files ), doing so with Subclipse involves further steps as
described in previous post (
http://subclipse.tigris.org/servlets/ReadMsg?list=users&msgNo=1884 ) :
create module + create "trunk" , "branches", "tags" subfolders in repos
+ switch project to "trunk" + commit new files. Is this feasible?
Regards,
Patricio.
Charles Nutter wrote:
> It seems that at least part of the problem was that I was trying to
> create a module named “<project>/trunk”. When I just allowed Subclipse
> to choose the name, it seemed to succeed.
>
> Is this correct behavior? I would like to follow the standard
> recommendations for Subversion repository layout (project/trunk,
> project/branch, etc) but it seems when adding to the repository it
> does not like me specifying this sort of layout.
>
> It also brings another question to mind: Could not Subclipse provide
> the very friendly and useful Versions/Branches style tree layout from
> the CVS repository view, but behind the scenes be enforcing or
> supporting the standard Subversion repository layout?
>
> One of the biggest problems I’ve had with Subversion is that it’s
> almost too permissive in how projects/versions/branches are laid out
> in the repository…permissive to the point of confusion, since I have
> seen multiple conflicting recommendations at various times. It would
> be great if Subclipse could have a “strict” mode of operation that
> takes care of generating and maintaining this layout for me.
>
> - Charlie
>
> ------------------------------------------------------------------------
>
> *From:* Charles Nutter [mailto:cnutter@ventera.com]
> *Sent:* Wednesday, May 04, 2005 1:29 AM
> *To:* users@subclipse.tigris.org
> *Subject:* More on importing large project
>
> I tried again today to import a large project. I added it to source
> control, went to the sync view, chose Commit at the root of the sync
> tree, entered my comment, hit Select All to add all listed files to
> version control, and proceeded from there. I got this message:
>
> The SVN synchronization information for {0} has become corrupt or does
> not exist.
>
> I'm running current Subclipse and JavaSVN. The server should be
> running Subversion 1.1-ish.
>
> I thought I saw this mentioned somewhere before, but could not find
> the reference...
>
> **--**
>
> **Charles Oliver Nutter** | Senior Specialist, Architect
>
> **Ventera Corporation** | Minneapolis, Minnesota
>
> **Office:** 612-370-3061 | **Mobile:** 612-710-1274
>
Received on Fri May 6 00:57:06 2005