> .. Regards, Abhi > > On Thu, Mar 4, 2010 at 3:33 PM, Bob Archer <bob.arc...@amsi.com> wrote: > >> On Thu, Mar 4, 2010 at 3:21 PM, Bob Archer <bob.arc...@amsi.com> wrote: > >> >> I am an Oracle Developer and I use "Oracle SQL Developer" IDE a lot. > I > >> was > >> >> wondering if anyone would be kind enough to refer me the setup > process > >> of > >> >> integrating Subversion with Oracle SQL Developer. > >> >> Thank you, > >> >> Abhi > >> > > >> > Is that a Windows tool? If so, does it support the SCC providers? > >> > > >> > If yes to both of those you could try Ankha > >> > http://ankhsvn.open.collab.net/ > >> > >> AnkhSVN is not a Windows SCC provider. It is an integration > >> specifically for modern versions of Visual Studio. > >> > > > > That used to be true... but from the project web site: > > > > In February 2008 the decision was made to rewrite the AnkhSVN engine to > create a full Source Code Control Package (SCC) for Visual Studio 2005, > 2008 and later on top of the new SharpSvn library. The new engine will be > the base of the new 2.X releases which saw its initial release in June > 2008. This new version integrates deeply in Visual Studio to give better > performance, stability and usability. The new Pending Changes window gives > an up-to-date overview of all your project actions and provides easy > access to most subversion commands. > > > You are confusing this usage of (SCC) with the old Microsoft Source > Code Control Interface (MSSCCI) which was the API that a lot of older > IDE's used to implement so that Source Safe worked with them. > > From the FAQ: > http://ankhsvn.open.collab.net/wiki/Faq/#head- > c716115ea60f783551e22b1d6d505f0e3aa3a014 > > Can I use AnkhSVN 2.X as MSSCCI provider in applications other than > Visual Studio? > > No, AnkhSVN 2.x implements the newer SCC implementation for Visual > Studio 2005 and later. The older MSSCCI implementation forced all > implementations to use the check-out check-in idiom (including making > files read-only). > > The newer VAPI SCC implementation implemented by AnkhSVN 2.x doesn't > have these limitations and allows our implementation to integrate > deeper in Visual Studio. >
Hmm... I wasn't aware there was a new SCC provider spec. Interesting. BOb
