Comments on: Flex Builder 3 works with Eclipse 3.3 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/ Mike Morearty's blog Thu, 29 Jul 2010 09:15:11 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Evans http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-52883 Evans Thu, 13 Nov 2008 14:15:39 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-52883 I know this entry is almost a year old, but I must say how nice and informative I've found the discussions going on in here. Well, I now use Flex 3 - but looking to get a plug in for Eclipse, I believe that was what led me to this blog# Nice site, I will try and bookmark your site :) I know this entry is almost a year old, but I must say how nice and informative I’ve found the discussions going on in here.

Well, I now use Flex 3 – but looking to get a plug in for Eclipse, I believe that was what led me to this blog#

Nice site, I will try and bookmark your site :)

]]> By: Luxspes http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-32565 Luxspes Wed, 12 Dec 2007 02:20:03 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-32565 Finally I found out how to run Flex 2 in Eclipse 3.3, and i was going to blog about it... but it turns out that others have found the same solution i found: http://www.eclipsezone.com/articles/howto-flexbuilder2/ Finally I found out how to run Flex 2 in Eclipse 3.3, and i was going to blog about it… but it turns out that others have found the same solution i found:

http://www.eclipsezone.com/articles/howto-flexbuilder2/

]]> By: nl-x http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-32477 nl-x Mon, 10 Dec 2007 11:33:32 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-32477 I wanted to reply to Jason. Jason, your comparison from MS-DOS to Vista doesn't stand. In your comparison, you leave out the fact that FB2 is the current latest stable and sold release and that Eclipse 3 is the current stable release. Using your comparisation, the correct comparisation would be that let's say Microsoft would sell Microsoft Office 2003, but have it not be compatible with Windows Vista. That is just as not-done. Months have passed and on the Adobe site I still haven't had the answer to the simple question: Will Adobe be doing something about it? Or should we stop holding our breath. (And as an answer to your question why not use the Beta: - It is a beta. There's a reason for calling software beta. - Once it comes out of beta I MUST do a PAID upgrade. The beta project files do not work on FB2. - Are you telling me I bought FB2 just to throw away my money? I bought it just a month before my previous post. ) Maybe as insiders you guys can give the answer to my question above, whether or not Adobe will pick this up. I wanted to reply to Jason.

Jason, your comparison from MS-DOS to Vista doesn’t stand. In your comparison, you leave out the fact that FB2 is the current latest stable and sold release and that Eclipse 3 is the current stable release. Using your comparisation, the correct comparisation would be that let’s say Microsoft would sell Microsoft Office 2003, but have it not be compatible with Windows Vista. That is just as not-done.

Months have passed and on the Adobe site I still haven’t had the answer to the simple question:
Will Adobe be doing something about it? Or should we stop holding our breath.

(And as an answer to your question why not use the Beta:
- It is a beta. There’s a reason for calling software beta.
- Once it comes out of beta I MUST do a PAID upgrade. The beta project files do not work on FB2.
- Are you telling me I bought FB2 just to throw away my money? I bought it just a month before my previous post.
)

Maybe as insiders you guys can give the answer to my question above, whether or not Adobe will pick this up.

]]> By: mike http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-31940 mike Thu, 29 Nov 2007 06:32:35 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-31940 Alan, I don't know of any reason why an Eclipse extension wouldn't load into standalone Flex Builder. We aren't doing anything special there -- standalone Flex Builder is pretty much just Eclipse plus some plugins, no special magic. As far as I know, it should just work. Naturally we love it when people add value to Flex Builder; when that happens, everybody wins. As far as debugging the particular issue you are having, I'm the wrong person to help with that -- you could post a message on adobe.com's support forums, or post a message on the "flexcoders" list on Yahoo groups, which has a very active and helpful user community. If those don't do the trick, perhaps contact Adobe tech support and explain that you are a vendor trying to integrate your product into an Adobe product. Alan, I don’t know of any reason why an Eclipse extension wouldn’t load into standalone Flex Builder. We aren’t doing anything special there — standalone Flex Builder is pretty much just Eclipse plus some plugins, no special magic. As far as I know, it should just work. Naturally we love it when people add value to Flex Builder; when that happens, everybody wins.

As far as debugging the particular issue you are having, I’m the wrong person to help with that — you could post a message on adobe.com’s support forums, or post a message on the "flexcoders" list on Yahoo groups, which has a very active and helpful user community. If those don’t do the trick, perhaps contact Adobe tech support and explain that you are a vendor trying to integrate your product into an Adobe product.

]]> By: Alan http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-31938 Alan Thu, 29 Nov 2007 05:45:50 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-31938 Hi Mike, As you are a developer on the Flex Builder team, I'm hoping you can answer something for me... We are building a plug-in that customizes a Flex development environment for a proprietary framework. This is moving along well for the plug-in version of FB that runs in standard Eclipse, but I've run into a brick wall with the stand-alone Flex Builder. Somehow Adobe has either intentionally or inadvertently disabled the ability to add plug-ins to the latter platform. This is a real headache as we would like to take advantage of the same motivations Adobe used for creating the stand-alone version... specifically, we want to simplify the installation process for those folks that are Eclipse neophytes. Can you comment on how to add plug-ins to the stand-alone version? I am not talking about anything fancy here--just a menu popup menu extension, which Adobe is clearly using within its framework. How does one enable the ability to add such a beast. Thanks, Alan Hi Mike,
As you are a developer on the Flex Builder team, I’m hoping you can answer something for me… We are building a plug-in that customizes a Flex development environment for a proprietary framework. This is moving along well for the plug-in version of FB that runs in standard Eclipse, but I’ve run into a brick wall with the stand-alone Flex Builder. Somehow Adobe has either intentionally or inadvertently disabled the ability to add plug-ins to the latter platform. This is a real headache as we would like to take advantage of the same motivations Adobe used for creating the stand-alone version… specifically, we want to simplify the installation process for those folks that are Eclipse neophytes.

Can you comment on how to add plug-ins to the stand-alone version? I am not talking about anything fancy here–just a menu popup menu extension, which Adobe is clearly using within its framework. How does one enable the ability to add such a beast.

Thanks,
Alan

]]> By: JosephS http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-30914 JosephS Thu, 08 Nov 2007 17:15:52 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-30914 Adobe likely will get around to providing an update to Flex Builder 2 to allow it to work with Eclipse 3.3. They say they are commited to CFEclipse which works on 3.3 and do not want to anger those who use both. But lets let them get Flex Builder 3 out the door first as the bug fixes for 3.0 could well find their way into any 2.0 update. Adobe likely will get around to providing an update to Flex Builder 2 to allow it to work with Eclipse 3.3. They say they are commited to CFEclipse which works on 3.3 and do not want to anger those who use both. But lets let them get Flex Builder 3 out the door first as the bug fixes for 3.0 could well find their way into any 2.0 update.

]]> By: Jason The Saj http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-30747 Jason The Saj Mon, 05 Nov 2007 17:25:55 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-30747 Really, so you expect an old version of software to be designed to run on a new version of the platform that was unknown (unless you can foresee the future). Come on...that's just silliness. How many old DOS and Windows 3.x apps can you run in Vista? Not the simple ones but the hefty ones. Adobe has done something though. They've released the Flex Builder 3 Beta (which I've been using for nearly 6 months and found to be extremely stable. One of the advantages of FB3beta is it allows you to use different Flex SDKs. So why not install FB3beta, select to use Flex Builder 2 SDK. And go on your merry way. And if that doesn't work. Well guess what - welcome to the world of computing. Would you like to see the pile of hardware and software worth thousands of $$$ that I've had to toss out over the past 10 yrs because incompatibilities with new operating systems and software products? It stinks...but I think Adobe's handled this much better than many others have by allowing the new Flex Builder 3 beta to be able to use the older SDK. Really, so you expect an old version of software to be designed to run on a new version of the platform that was unknown (unless you can foresee the future).

Come on…that’s just silliness. How many old DOS and Windows 3.x apps can you run in Vista? Not the simple ones but the hefty ones.

Adobe has done something though. They’ve released the Flex Builder 3 Beta (which I’ve been using for nearly 6 months and found to be extremely stable. One of the advantages of FB3beta is it allows you to use different Flex SDKs.

So why not install FB3beta, select to use Flex Builder 2 SDK. And go on your merry way. And if that doesn’t work. Well guess what – welcome to the world of computing. Would you like to see the pile of hardware and software worth thousands of $$$ that I’ve had to toss out over the past 10 yrs because incompatibilities with new operating systems and software products?

It stinks…but I think Adobe’s handled this much better than many others have by allowing the new Flex Builder 3 beta to be able to use the older SDK.

]]> By: nl-x http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-28539 nl-x Wed, 03 Oct 2007 08:42:54 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-28539 I wish to emphesize the words in Sean Genung's first post, without retyping everything he said. IMHO Adobe must take its responsability and patch FB2 to be able to work with Eclipse 3.3. Adobe chose to use the Open Source community for its not-Open Source project. Off course that's no problem. As lons as Adobe uses, and not abuses. If Adobe sees the unnual upgrade to Eclipse 3.3, with loads of attractive functionalities that appeal to current users, as a way to have those users upgrade to the newest Flex Builder, I would call it abuse of the Open Source community. Because then Adobe isn't merely making profit out of it's own work, but out of the Open Source work. ...But you don't need to tell me that this does consent to the License Agreements of Eclipse, as I am aware that it most likely is. But nevertheless in my opinion it just aint right. I personally bought 2 licenses of Flex Builder one month ago and didnt realise that this was going to be the case. I have experimented in getting FB 2 to work with Eclipse 3.3 anyway and got to the unsupported solution of copying Startup.jar from an Eclipse 3.2 environment to the 3.3 environment. This would unlock the FB 2 installation to install to Eclipse 3.3. I have seen that this works for a very very big part. I get code-completion, building, compiling, debugging. Almost everything works... At the moment there is only 1 bug that still annoys me: when in project-settings in Additional Compiler Arguments I state ' -services "services-config.xml"' (this file exists and Eclipse doesn't say It can't find it, just like it would if I misspelled it.) then I simply get 1 error "Unknown problem" in the Problems View. Surely this isn't the only bug, there probably are a few more. What I am trying to say is it probably IS feasable (Matt: August 13th, 2007 at 3:44 pm) to patch FB2 to Eclipse 3.3. The question only is, is Adobe willing to do the right thing and patch the "older" FB2 while they actually want to sell people the "newer" FB3 as soon as it is released. I wish to emphesize the words in Sean Genung’s first post, without retyping everything he said. IMHO Adobe must take its responsability and patch FB2 to be able to work with Eclipse 3.3.

Adobe chose to use the Open Source community for its not-Open Source project. Off course that’s no problem. As lons as Adobe uses, and not abuses.

If Adobe sees the unnual upgrade to Eclipse 3.3, with loads of attractive functionalities that appeal to current users, as a way to have those users upgrade to the newest Flex Builder, I would call it abuse of the Open Source community. Because then Adobe isn’t merely making profit out of it’s own work, but out of the Open Source work. …But you don’t need to tell me that this does consent to the License Agreements of Eclipse, as I am aware that it most likely is. But nevertheless in my opinion it just aint right.

I personally bought 2 licenses of Flex Builder one month ago and didnt realise that this was going to be the case.

I have experimented in getting FB 2 to work with Eclipse 3.3 anyway and got to the unsupported solution of copying Startup.jar from an Eclipse 3.2 environment to the 3.3 environment. This would unlock the FB 2 installation to install to Eclipse 3.3.
I have seen that this works for a very very big part. I get code-completion, building, compiling, debugging. Almost everything works… At the moment there is only 1 bug that still annoys me: when in project-settings in Additional Compiler Arguments I state ‘ -services "services-config.xml"’ (this file exists and Eclipse doesn’t say It can’t find it, just like it would if I misspelled it.) then I simply get 1 error "Unknown problem" in the Problems View.
Surely this isn’t the only bug, there probably are a few more.

What I am trying to say is it probably IS feasable (Matt: August 13th, 2007 at 3:44 pm) to patch FB2 to Eclipse 3.3. The question only is, is Adobe willing to do the right thing and patch the "older" FB2 while they actually want to sell people the "newer" FB3 as soon as it is released.

]]> By: levani http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-27363 levani Fri, 07 Sep 2007 16:29:17 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-27363 Hi Sean, I have to say you are not completely going towards right direction putting all the blame on Adobe, I am not anyway affiliate with adobe and just expressing my opinion, hopely its not gonna be taken wrong way. When you say you have upgraded whole development team to eclipse 3.3 and then realized flex builder is not working, this is already a mistake on your side, eclipse minor version upgrades are (as you know) not really minor, 3.1 vs 3.2 vs 3.3 etc .. are significantly different including possible platform API modifications, as Mike stated its something that can not be "fully" predictable until release is out, and only then plugin developers have best shot to adjust plugin to new version api. first thing that you should have done before upgrade is to make sure that,all plugins currently in your existing eclipse version(s) are going to work with new Eclipse version. for flexBuilder specifically all it takes is three word search "flexbuilder eclipse 3.3" it is reasonable doubt to assume that plugin can not physically support versions of IDE that are not even out yet, how can you assume that flexubuilder plugin *should* support all eclipse 3.x versions including future 3.4, 3.5, 3.6, 3.7 etc .. 3.x series ..which are not even born as an idea yet, thats very unreasonable , and physically not possible to support non existing versions. when FB2 was out there was no Eclipse 3.3 .and thats something you should have put into consideration before upgrade, now other thing is, upgrade is done, there is nothing can be done, but again, instead of finding your way out, you attack adobe again, but why? I have seen many many developers using FB2 SDK with FB3 IDE successfully in production environment and waiting for a FB3 release, thats just a reality they face if they want cutting edge Eclipse and same time face the reality. Hi Sean,
I have to say you are not completely going towards right direction putting all the blame on Adobe, I am not anyway affiliate with adobe and just expressing my opinion, hopely its not gonna be taken wrong way.
When you say you have upgraded whole development team to eclipse 3.3
and then realized flex builder is not working, this is already a mistake on your side, eclipse minor version upgrades are (as you know) not really minor, 3.1 vs 3.2 vs 3.3 etc .. are significantly different including possible platform API modifications, as Mike stated its something that can not be "fully" predictable until release is out, and only then plugin developers have best shot to adjust plugin to new version api. first thing that you should have done before upgrade is to make sure that,all plugins currently in your existing eclipse version(s) are going to work with new Eclipse version. for flexBuilder specifically all it takes is three word search "flexbuilder eclipse 3.3"
it is reasonable doubt to assume that plugin can not physically support versions of IDE that are not even out yet,
how can you assume that flexubuilder plugin *should* support all eclipse 3.x versions including future 3.4, 3.5, 3.6, 3.7 etc .. 3.x series ..which are not even born as an idea yet, thats very unreasonable , and physically not possible to support non existing versions.

when FB2 was out there was no Eclipse 3.3 .and thats something you should have put into consideration before upgrade, now other thing is, upgrade is done, there is nothing can be done, but again, instead of finding your way out, you attack adobe again, but why?
I have seen many many developers using FB2 SDK with FB3 IDE successfully in production environment and waiting for a FB3 release, thats just a reality they face if they want cutting edge Eclipse and same time face the reality.

]]> By: mike http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/comment-page-1/#comment-26827 mike Tue, 28 Aug 2007 19:20:55 +0000 http://www.morearty.com/blog/2007/06/12/flex-builder-3-works-with-eclipse-33/#comment-26827 I'm glad you like it, Santiago. An official release date for Flex Builder 3 has not yet been announced. I’m glad you like it, Santiago. An official release date for Flex Builder 3 has not yet been announced.

]]>