Re: [tasklist] I made a booboo...it broke
Tor Norbye <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.modules.tasklist.devel |
|---|---|
| Organization | Sun Microsystems, Inc |
| Message-ID | <1049252649.879.32.camel@proto> |
On Tue, 2003-04-01 at 14:08, Andrew Serff wrote: > Ok, I did break the code. I just tried to d/l a clean copy and it > doesn't build. So I just copied my bugs dir from the working 3.5 > baseline and plopped that in the 3.4 working dir. Then I built, there > is a line in the build script looking for ../../core/external (in > netbeans code) for some api jars that I don't know what they are, so I > commented that out. The other thing it is complaining about is > Utilities.createWaitCursor. Is there something similar in 3.4? or > should I just comment it out. Sorry about breaking it. Let me know if > you can help. Hi there, no problem, don't worry about it - I don't think anyone is building the release34 branch regularly, so I'm sure breakage doesn't cause any pain for anybody. Yup, the manifest file is quite different since a fair bit of architecture cleanup went into 3.5. I don't think there is a wait cursor API you can use (beyond the regular setCursor call on Components - but I believe there's an API around that for a reason to avoid various problems.) Because of all these changes, keeping the release34 branch up to date is pretty painful - so painful I haven't done it in quite a while. My rationality behind it is that NetBeans 3.5 is pretty much beta quality. If you're willing to use beta quality tasklist you're probably willing to use beta quality NetBeans as well. So I haven't wanted to put all the effort into backporting all the changes to release34. If I were you I'd backrev the manifest file to what it was (except bump the spec version) and ditto for the build.xml file, unless you need new changes made in the trunk. -- Tor