the svnmerge property is ignored when multiple projects are selected) > > This process of finding all the revisions takes about 5-10 minutes just for 2 eclipse projects, and I'm guessing It'd be worth trying that folder in the command. >> > I've tried it with the svn:mergeinfo only on /branch1, and on /branch1/eclipseprojecta and >> > /branch1/eclipseprojectb. Get release notes for CollabNet 5.3.0? we have made some fixes here that should speed this up for you. his comment is here
Mark Phippard-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: Re: Re: Branch merge issues On Tue, May 26, That seems to work fine so long as there are no new folders. It will go to the repository and find the parent mergeinfo. > Same for the branches/tags configuration. Just guessing. > My fifth issue is with attempting to use the alternative Compare With option to bring files from TRUNK to the Branch. read review
Stephen Colebourne-2 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ RE: Re: Re: Branch merge issues > There is a I find it very good that SVNKit can now easily be updated and is no longer coupled with Subclipse, thanks! Started by peerke, Jan 28 2013 09:10 AM Please log in to reply 1 reply to this topic #1 peerke peerke Newbie Members 1 posts Posted 28 January 2013 - 09:10 In my experience, the people that have the "classic" setup, the one's that would be the easiest to support, need this feature the least.
Atlassian Documentation Log in Bamboo Knowledge Base Select another version Bamboo knowledge base Browse all documentation Atlassian strives to provide high quality and evolving products to our customers. That will show logged errors –Mark Phippard Jul 29 '13 at 14:48 thanks for "Error log". My fourth issue is that I have NPE from the completed merge when I attempt to synchronize and then double click to compare the changes. Google Plugin for Eclipse 4.2 3.1.3.v201212122042-rel-r42 com.google.gdt.eclipse.suite.e42.feature.feature.group Google, Inc.
The details say, that there is a java.lang.NullPointerException. The Console view is an Eclipse view called "Console" beneath the "Basic" grouping in the View list. The proper solution for me is either > switching to JavaHL (but I hate depending on many external > libraries, I > want to distribute my configuration) or to switch https://confluence.atlassian.com/bamkb/svn-update-fails-with-nullpointerexception-179442614.html Also I don't see why you wouldn't issue the svn mergeinfo at the level of each of the projects, and union the set of returned revision numbers, as doing it at
Home | Browse | FAQ | Advertising | Blog | Feedback | MarkMail™ Legalese | About MarkLogic Server current community chat Stack Overflow Meta Stack Overflow your communities Sign up or This could occur if the message has been deleted or the URL has been edited. So, what I don't understand is why you believe that merge across projects is working great. Perhaps it would take the form of storing in each Eclipse project what the defined trunk URL is and the root for branches.
However, svn is now a mainstream corporate tool used by point and click developers in very standard patterns. Mark Phippard-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: Re: Re: Re: Re: Re: Branch merge issues In Sometimes the windows explorer restarts as well and I get strange graphic issues. However, I've mostly worked with branches that I created post merge tracking.
And i merge on the folder above the > projects > and i commit there the i do also commit the svn properties to that dir. this content The people that need this stuff the most are the hardest to support. First book of a series: boy disappears from his life, becomes time travelling agent Yes, of course I'm an adult! Finally, Subclipse does have a feature like you asked.
Then users could pick from the names in every location where a URL is currently used. Yes, those were basically the commands I ran (where MAXREV was the revision just after cvs migration). Atlassian recommends upgrading to the latest release for a proper fix. weblink Get over it or go back to CVS.
I didn't know. My recollection was that the UI comes entirely from the Eclipse compare plugin and we just provide the data model. You could really only use --record-only if you typically fully-synch the trunk revisions to the branch and you knew it had all of the trunk changes up to some revision.
Mark Phippard-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: Re: Re: Re: Re: Branch merge issues On Wed, According to the svn 1.5 online manual, all this does is block these revisions from being considered. (ie. That seems to work fine so long as there are no new folders. On Wednesday 08 February 2006 18:55, Mark Phippard wrote: Martin Stechert
Again, this makes merge pretty unusable. svn rv ~50,000. > > I have used the svn merge --record-only option to block the old changes prior to the cvs to svn migration. > > That has helped, as java.lang.NullPointerException And then my changes are in a new file *.tmp and the real file contains the server version. check over here Why are some programming languages Turing complete but lack some abilities of other languages?
Unfortunately, Collabnet/Subclipse doesn't log the svn mergeinfo command, so I can't prove that the command being sent from Subclipse is wrong. I give it up to find a solution by myself and hope, that anybody have an idea, what may cause the errors here.