Eclipse IDE on Intel

Jump to First Reply
Posted:
in Mac Software edited January 2014
Has anybody succeeded in getting the Eclipse Java IDE working on MacIntel?



I googled for info on this and the results were pretty sparse.



Somebody on this forum mentioned that they simply had to substitute an SWT jar file to get it to work.



This is the deal-breaker for me. If I have to step(s) to get Eclipse on MacIntel, then I'll probably pull the trigger within the next few days and get an Intel iMac.

Comments

  • Reply 1 of 7
    mr. memr. me Posts: 3,221member
    Quote:

    Originally posted by JavaCowboy

    Has anybody succeeded in getting the Eclipse Java IDE working on MacIntel?



    I googled for info on this and the results were pretty sparse.



    Somebody on this forum mentioned that they simply had to substitute an SWT jar file to get it to work.



    This is the deal-breaker for me. If I have to step(s) to get Eclipse on MacIntel, then I'll probably pull the trigger within the next few days and get an Intel iMac.




    What do you have against Xcode?
     0Likes 0Dislikes 0Informatives
  • Reply 2 of 7
    Quote:

    Originally posted by Mr. Me

    What do you have against Xcode?



    Never used it, and it would take me a while to learn. I use Eclipse at work every single day.



    XCode might possibly be a better IDE than Eclipse, but for the moment, I want to stick with what I know.
     0Likes 0Dislikes 0Informatives
  • Reply 3 of 7
    kickahakickaha Posts: 8,760member
    I think you mean this thread:



    http://forums.appleinsider.com/showt...ipse+AND+Intel



    Or, more directly from this thread:



    From ciparis:



    It runs very well -- I'm pleased. It's been left running for over 24 hours now with a project (200+ files) open, and it still is snappy and responsive. To get it running required using a patch posted to bugzilla, which just replaced one of the files. The file link is here, and to use it you just delete the current swt carbon file (with a similar filename) in the plugins folder, and drop this one in instead. That's the only native item in Eclipse (SWT) -- the rest is Java, and Java on these new machines is already native x86. I'm using Java 5 (you still have to manually switch CurrentSDK from 1.4 to 1.5 to do that, though both JDKs are installed so it's just a symlink change). There is an eclipse-mac group at google, which is great for getting support and sharing tips.





    Search is your friend.
     0Likes 0Dislikes 0Informatives
  • Reply 4 of 7
    wgauvinwgauvin Posts: 100member
    Quote:

    Originally posted by Mr. Me

    What do you have against Xcode?



    I haven't used XCode 2.1 or 2.2, but for serious Java work, like J2EE, Eclipse and NetBeans are a better option. NetBeans should work natively with Intel, since it's pure Java, Eclipse needs the SWT to be compiled on Intel and I don't know the status on that. When I tried XCode 2.0, I didn't like the syntax highlighting for Java, and it couldn't handle Java 5.0 syntax. As for building Cocoa-Java Apps, then XCode would win. BTW, NetBeans 5.0 has a GUI builder similar to what is in XCode.
     0Likes 0Dislikes 0Informatives
  • Reply 5 of 7
    Quote:

    Originally posted by wgauvin

    I haven't used XCode 2.1 or 2.2, but for serious Java work, like J2EE, Eclipse and NetBeans are a better option. NetBeans should work natively with Intel, since it's pure Java, Eclipse needs the SWT to be compiled on Intel and I don't know the status on that. When I tried XCode 2.0, I didn't like the syntax highlighting for Java, and it couldn't handle Java 5.0 syntax. As for building Cocoa-Java Apps, then XCode would win. BTW, NetBeans 5.0 has a GUI builder similar to what is in XCode.



    Wow! You're right about NetBeans 5.0. I just downloaded RC 2 and it rocks! 4.1 didn't respect the Mac GUI convetions, but 5.0 is totally compliant. There's so much functionality out of the box (JSP/SQL/XML syntax highlighting, internal Tomcat instance) that Eclipse needs plugins for. What's more, 4.1 insisted I have a WEB-INF directory in my source folder. 5.0 respects whatever I have in build.xml. It's totally configurable, right down to the keyboard shortcuts. From what I heard, NetBeans supports J2EE right out of the box, whereas Eclipse does not (probably due to IBM politicking).



    I haven't tried to do much with it yet, but I think I'll probably switch.
     0Likes 0Dislikes 0Informatives
  • Reply 6 of 7
    wgauvinwgauvin Posts: 100member
    Quote:

    Originally posted by JavaCowboy

    From what I heard, NetBeans supports J2EE right out of the box, whereas Eclipse does not (probably due to IBM politicking).



    I haven't tried to do much with it yet, but I think I'll probably switch.




    Yeah, I think Sun has donated a lot more code for NB5.0 and they really want it to be the choice for Java EE development. NB5.1 should support Java EE 5 (there are daily builds for it, that support Glassfish, JBoss and Weblogic)



    At work I use WSAD, I can see where Eclipse has it's advantages, but NB is no longer crappy IDE, in the last 18 months it has really caught up.
     0Likes 0Dislikes 0Informatives
  • Reply 7 of 7
    Eclipse 3.2 RC4 with the native SWT-Carbon JAR on 20" Core Duo iMac is stunning. Even better, debugging applications running in JBoss is now really fast. On G4 (and even G5), this was simply not fast enough.



    As for Eclipse versus XCode: for purely Java development, Eclipse wins hands down. I use Eclipse all day, every day and it is an awesome IDE.



    Shame Apple aren't a little more forthcoming with technical help for Eclipse in general. The guys at Eclipse are posting away, telling us that the SWT-Carbon library is far from optimised (come on Apple - lend a hand) and they also note the SWT-Carbon Library was developed/compiled minus any OS X86 machine.



    Of note, MySQL have also just released native binaries for MySQL (v5.0.18) - but not yet for their MySQL Admininistrator and MySQL Query Browser (still v buggy).
     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.