I actually have two full CVS checkouts of Wicket on the go now. I have one that I keep up to date with the latest changes and which I use for bug fixing and small changes that can be made quickly and without much impact. I then have another that I am using for doing all of the localization work. I update this second one less frequently so that I get more stability for the changes that I am making and deal with merge issues when I have completed a particular piece of work. If I was working on other major areas of functionality then I would have separate CVS checkouts for these also. This completely eliminates the need doing any CVS branching or similar. The only downside is that the makes it more difficult to share ongoing changes with other developers in the team.
Regards,
Chris
>
>
> Johan,
>
> Yes I know that. But it is actually not was meant. Branches
> are, from my experience, most often used to developed
> something like 1.1, 2.0 etc. minor and major relases. This is
> due to how CVS works and how CVS defines branches. CVS does
> not support (like e.g. ClearCase) user-specific branches only
> visible to one developer (or maybe a small group); a
> developer working on a small piece (a single feature of
> 0.9.13-alpha). Like the problem I had. I was working on
> encrypting password, Eeclos actionlink problem etc. and code
> got mixed up between these changes. To my understanding, and
> please correct me if I'm wrong, does CVS not offer such kind
> of branching. Scanning (not thoroughly reading) CVS docs,
> they discourage users to use it that way.
>
>
> Regards
> Juergen
>
> -----Urspr�ngliche Nachricht-----
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] Im
> Auftrag von Johan Compagner
> Gesendet: Mittwoch, 20. Oktober 2004 09:29
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: [Wicket-develop] CVS HEAD breaks junit tests
>
> Eclispe does support branches/versions perfectly.
> Just import the project from a branch not head.
> Then with Team->merge you can merge them back into head<->branch
>
> johan
>
>
> Donnerstag, Juergen wrote:
>
> >Sorry, my fault. Unfortunately I access public access to the internet
> >only tonight. I'll fix it. Development (see my previous mails) and
> >checked in version are inconsistent.
> >
> >Which leads me to the question: Assuming I'm working on different
> >features/bugs etc. some of them ready to be checked in, others
> >experimental only. Does anybody know how to easily handle
> it. (Local or
> >personal; not on the server) branches I think are usually
> the way to do
> >it. CVS (or Eclipse) doesn't support anything like that,
> correct? Any other
> idea?
> >
> >Regards
> >Juergen
> >
> >-----Urspr�ngliche Nachricht-----
> >Von: [EMAIL PROTECTED]
> >[mailto:[EMAIL PROTECTED]] Im Auftrag von
> >Martijn Dashorst
> >Gesendet: Montag, 18. Oktober 2004 23:57
> >An: [EMAIL PROTECTED]
> >Betreff: [Wicket-develop] CVS HEAD breaks junit tests
> >
> >Hi,
> >
> >Current CVS head fails 2 junit tests.
> >
> >junit.framework.ComparisonFailure: expected:<null> but was:<>
> > at junit.framework.Assert.assertEquals(Assert.java:81)
> > at junit.framework.Assert.assertEquals(Assert.java:87)
> > at
> >com.voicetribe.wicket.markup.html.form.CookieTest.testSetCook
> ieOnPage(C
> >ookie
> >Test.java:125)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> > at java.lang.reflect.Method.invoke(Unknown Source)
> > at junit.framework.TestCase.runTest(TestCase.java:154)
> > at junit.framework.TestCase.runBare(TestCase.java:127)
> > at junit.framework.TestResult$1.protect(TestResult.java:106)
> > at junit.framework.TestResult.runProtected(TestResult.java:124)
> > at junit.framework.TestResult.run(TestResult.java:109)
> > at junit.framework.TestCase.run(TestCase.java:118)
> > at junit.framework.TestSuite.runTest(TestSuite.java:208)
> > at junit.framework.TestSuite.run(TestSuite.java:203)
> > at
> >org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTes
> ts(RemoteT
> >estRu
> >nner.java:421)
> > at
> >org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(Re
> moteTestRu
> >nner
> .
> >java:305)
> > at
> >org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(R
> emoteTestR
> >unner
> >.java:186)
> >
> >junit.framework.AssertionFailedError: expected:<0> but was:<2>
> > at junit.framework.Assert.fail(Assert.java:47)
> > at junit.framework.Assert.failNotEquals(Assert.java:282)
> > at junit.framework.Assert.assertEquals(Assert.java:64)
> > at junit.framework.Assert.assertEquals(Assert.java:201)
> > at junit.framework.Assert.assertEquals(Assert.java:207)
> > at
> >com.voicetribe.wicket.markup.html.form.CookieTest.testPersist
> Cookie(Coo
> >kieTe
> >st.java:180)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> > at java.lang.reflect.Method.invoke(Unknown Source)
> > at junit.framework.TestCase.runTest(TestCase.java:154)
> > at junit.framework.TestCase.runBare(TestCase.java:127)
> > at junit.framework.TestResult$1.protect(TestResult.java:106)
> > at junit.framework.TestResult.runProtected(TestResult.java:124)
> > at junit.framework.TestResult.run(TestResult.java:109)
> > at junit.framework.TestCase.run(TestCase.java:118)
> > at junit.framework.TestSuite.runTest(TestSuite.java:208)
> > at junit.framework.TestSuite.run(TestSuite.java:203)
> > at
> >org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTes
> ts(RemoteT
> >estRu
> >nner.java:421)
> > at
> >org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(Re
> moteTestRu
> >nner
> .
> >java:305)
> > at
> >org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(R
> emoteTestR
> >unner
> >.java:186)
> >
> >Apparently, there is a jinx on creating another alpha release :-)
> >
> >Martijn
> >
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: IT Product Guide on
> >ITManagersJournal Use IT products in your business? Tell us what you
> >think of them. Give us Your Opinions, Get Free ThinkGeek Gift
> >Certificates! Click to find out more
> >http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >_______________________________________________
> >Wicket-develop mailing list
> >[EMAIL PROTECTED]
> >https://lists.sourceforge.net/lists/listinfo/wicket-develop
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: IT Product Guide on
> >ITManagersJournal Use IT products in your business? Tell us what you
> >think of them. Give us Your Opinions, Get Free ThinkGeek Gift
> >Certificates! Click to find out more
> >http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >_______________________________________________
> >Wicket-develop mailing list
> >[EMAIL PROTECTED]
> >https://lists.sourceforge.net/lists/listinfo/wicket-develop
> >
> >
> >
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal Use IT products in your business? Tell us
> what you think of them. Give us Your Opinions, Get Free
> ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guid> epromo.tmpl
>
> _______________________________________________
>
> Wicket-develop mailing list [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal Use IT products in your business? Tell us
> what you think of them. Give us Your Opinions, Get Free
> ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guid> epromo.tmpl
>
> _______________________________________________
>
> Wicket-develop mailing list [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
