ARGHHHHHHHHHHHHHHHHH…
I got a new PC at work and I’m reinstalling everything. When it came time to install Eclipse - I decided to go back to 3.1 so I could run CFEclipse and FlexBuilder… Fine. Great.
BUT…
On my old machine I updated to Subversion 1.4 and at the time Subclipse didn’t work with 1.4. Today I noticed a new Subclipse release is out - Subclipse 1.1.8! Whoo hoo!
BUT…
As with previous 1.1.x releases, this release is only available for
Eclipse 3.2/Callisto users.
DOH!
Someday I hope all these wonderful tools can live in harmony on my desktop!
You May Also Enjoy Reading:
6 Comments
You may have already seen this, but in case you didn’t …
http://www.cfreport.org/index......lexBuilder
Yep - that’s why I had rolled back to 3.1 when I reinstalled - but now to get Subclipse working - I need Eclipse 3.2!
Think I’m just going to install both and use 3.1 just for messing with FlexBuilder and 3.2 for my regular IDE.
Subclipse 1.0.4 will be out in a couple of weeks, it will include SVN 1.4.
Also, Subclipse 1.0.3 works fine with 1.4 servers, it just does not interoperate with other 1.4 clients, like TortoiseSVN 1.4. One option is to use a 1.3 version of those clients. The other option is to just manually update Subclipse 1.0.3 to use the SVN 1.4 binaries. See this page for instructions:
http://subclipse.tigris.org/se.....msgNo=7969
With 1.0.3, the only other step you have to do is to copy libdb44.dll to somewhere in the PATH until you get the next version of Subclipse.
Jim,
That’s similar to what I do. I have different Eclipse installs for different purposes. At the moment I’m working on some back-end Java-fu, so I’m using my barebones Java Eclipse which only has one plug-in, Subversion.
When I work in CF, I use a different install. I used to do Python in Eclipse as well but moved to using Stani’s Python Editor.
I end-up (at least at work) with an install dir that looks like this:
c:\eclipse (this is where all eclipse releated foo goes)
c:\eclipse\3.2-cfeclipse
c:\eclipse\3.2-java
c:\eclipse\3.2-j2ee
Then I do this with the workspaces:
c:\eclipse\workspace\cf
c:\eclipse\workspace\java
c:\eclipse\workspace\j2ee
… etc.
I keep track of the version of Eclipse as well as what it’s purpose is. I’m sure this would annoy a lot of people, but it’s what keeps eclipse fast and stable for me.
I use subeclipse 1.0.3 with eclipse3.1 and it works nicely
Jim,
The only product that will give you problems will be Flex Builder 2. Because it is a closed product, it will always lag behind the others. I really think Adobe should bite the bullet and open source it. I really don’t think its making Adobe that much money. Plus I think in the long run, an open source version of Flex Builder 2 would go a long ways to making Flex a more viable language.
In fact, Flex Builder 2 has already bitten me. I downloaded the trial about 2 months ago. But after the initial look at it, I didn’t play with it. Last week, I tried to give it another look, but the trial has expired and I have no interest or time to get Adobe to give me another chance with it.