Serious bug in Flex Builder 3

I just lost a whole morning's work. Here's what I did:
I needed to base a new component on an existing one. So, in
the FB3 file list I right-click, copy file, paste file, rename to
new name. Open up the new file and do my work on it. I saved the
file several times as I normally do as I work, and ran and debugged
the program many times.
Then, at one point I did command-Z to undo something.
However, I guess the editor did not have focus. Instead of undoing
my typing, the tab I was working on closed. The undo/redo menu read
"Redo duplicate file". Worst of all, the newer file -- the one i
had been working on all day -- had reverted back to the way it was
when I first duplicated it, i.e. a clone of file 1. All the work I
had done to transform the file 1 clone into file 2 was lost. Even
the Finder modification date was the same as file 1. No trace of
the file versions saved today.
I have never seen a program overwriting a never file with an
old one with no dialog or warning. I realize nothing can be done, I
need to re-do my work, but to other be aware. I will never
duplicate a file or perform any file operation from within FB from
now on, I will use the OS.

It is also possible that there are 'backup' plugins for
eclipse that you can use with Flex Builder, say that archive your
work every 5 minutes or whatever. Not sure, but wouldn't be
surprised.
Something along these lines:
http://sourceforge.net/projects/savedirtyeditor/
I realize this may not be exactly it.

Similar Messages

Serious Bug Powerbuilder 12.5.2 build 5609 with Inheritance

Hi ,
I'm using Powerbuilder 12.5.2. build 5609. I think it is the latest release. I have three windows in my app.
The Grandfather , the father and the child. Child window (w_child) is inherited from the father (w_father) which inherits from the grandfather (w_grandfather).
I have some events in my windows , clicked events with code etc.
I made a change in the grandfather , regenerated the father and the child and my code in the child window was messed up!. And when I say messed up I mean that the code in my clicked event was disappeared or moved in other cases to other events.
With Full build and incremental build didn't fix the bug.
Using export and import FIXED the issue.
BUT.....
Why is this happening ? Of course this is a Powerbuilder BUG but do I need to export and import my objects when I make a change to ancestors objects ?
FYI using the edit source option I can see the code that it's there.
Will this issue been fixed because this is a very serious BUG. Every time I want to make a change to ancestors should I need to export all objects and import them again ???
thank you
zkar

Hi Andreas ,
I don't know.
But I tried the below scenario and found a different bug.
Same hierarchy. Grandfather, Father and Child.
Steps to reproduce.
1. Go to Fathers screen and Add a button. Leave the name as it is. cb_1
2. Go to Grandfather and add a button(didn't have any buttons yet). The name will be cb_1.
If you try to open the Father's screen you will be prompted from Powebuilder with a messagebox which suggest to make the changes for you because there was a name conflict. OK fair enough.
But.
If you press OK and let powerbuilder handles this then this doesn't work.
Anyway. This is a completely different thing from the original post . But I have just founded out trying to reproduce it to a new application.
FYI. The application was at first in Powerbuilder 10 but we have Migrated succesfully to powerbuilder 12.5 and It was working fine until we ;ve changed the intermediate level of inheritance.
The solution to my problem is export and import the intermediate level so don't search anymore. You will loose time trying to reproduce it.
thank you

Bug in the flex builder installer

I found a bug in the Flex builder installer, while someone
tried to install Flex on top of our EasyEclipse eclipse distro.
I am making a post here since I could not find a way to
report a bug anywhere on the Adobe web site :-\
So the bug is that the installer is looking for an eclipse
installation that is packaged exactly like the Eclipse platform,
but also specifically checks for the presence of features named
org.eclipse.rcp and org.eclipse.platform.
Yet the flex features themselves do not care about other
features only about the platform plugins to be present, as it
shoudl be.
It is considered a bad practice by the Eclipse platform team
to have a dependecy on features, and it is recommended to use
instead plugin depdencies.
See
http://wiki.eclipse.org/index.php/Version_Numbering#Versioning_features
As a result, Flex cannot be installed anywhere but on a vanilla
Eclipse.
EasyEclipse does not ship the base features of the Eclipse
platform, yet all the Flex plugins dependencies are statisfied.
See our forum for more details:
http://sourceforge.net/forum/message.php?msg_id=3982548

Getting back to the original message in this thread, I want
to post an update about what I learned on digging deeper. The Flex
Builder 2.0.1 Plug-in version does not require a vanilla eclipse to
install into, but it does impose some minimal constraints. Before
release, we installed FB 2.0.1 Plug-in successfully with several
customized Eclipse configurations, including RSA7 and BEA, each of
which uses a different folder configuration for its product
extension point.
I took a close look at the dependency list for our FB 2.0.1
features, and these have been plugin-based dependencies all along,
not feature dependencies. I understand why it might appear as if
they're feature-based though, because our installer requires that
the feature named org.eclipse.platform be present.
We have the installer look for that feature, because that's
the way Eclipse's update manager reports what's already installed
and available. Eclipse's commandline API for updates only provides
Feature info, not Plugin info:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/mis c/update_standalone.html
The FB Plug-in installer checks for the existence of
org.eclipse.platform so that we have some assurance that the
version of eclipse proposed is at least version 3.1.2 or higher. In
our next release, we'll explore alternate way of gleaning this same
information, with the intention of allowing plug-in installs into
products such as EasyEclipse that don't include any Eclipse
features in their products.
C. Agruss
quote:
Originally posted by:
pombreda
I found a bug in the Flex builder installer, while someone
tried to install Flex on top of our EasyEclipse eclipse distro.
I am making a post here since I could not find a way to
report a bug anywhere on the Adobe web site :-\
So the bug is that the installer is looking for an eclipse
installation that is packaged exactly like the Eclipse platform,
but also specifically checks for the presence of features named
org.eclipse.rcp and org.eclipse.platform.
Yet the flex features themselves do not care about other
features only about the platform plugins to be present, as it
shoudl be.
It is considered a bad practice by the Eclipse platform team
to have a dependecy on features, and it is recommended to use
instead plugin depdencies.
See
http://wiki.eclipse.org/index.php/Version_Numbering#Versioning_features
As a result, Flex cannot be installed anywhere but on a vanilla
Eclipse.
EasyEclipse does not ship the base features of the Eclipse
platform, yet all the Flex plugins dependencies are statisfied.
See our forum for more details:
http://sourceforge.net/forum/message.php?msg_id=3982548

Flex Builder 2 Bug

For some reason, the text labels in the toolbar of my Flex
Builder installation have a white background. In fact, the same is
true for every Macromedia application I have installed. I have the
apps installed on another computer without any display bugs at all.
Anybody have an idea as to why this happens? I have posted an
image
here
showing the glitch. I only get that behavior in Dreamweaver,
Fireworks and Flash after my mouse moves over the buttons for the
first time.
I also have an error in Flex when I try to open an html
document which contains a swf. For example, the SyleExplorer from
AdobeConsulting.
Thanks for your help!

For some reason, the text labels in the toolbar of my Flex
Builder installation have a white background. In fact, the same is
true for every Macromedia application I have installed. I have the
apps installed on another computer without any display bugs at all.
Anybody have an idea as to why this happens? I have posted an
image
here
showing the glitch. I only get that behavior in Dreamweaver,
Fireworks and Flash after my mouse moves over the buttons for the
first time.
I also have an error in Flex when I try to open an html
document which contains a swf. For example, the SyleExplorer from
AdobeConsulting.
Thanks for your help!

Flex Build Path: fiber.swc, playerfds.swc & dcradSwcs automatically added after I removed them

Hi,
I'm working on an application which uses old Flex 3.4 (used for Adobe LiveCycle). This SDK already contains fiber.swc and playerfds.swc so I removed them from Flex Build Path. But if I reopen the project, the removed lines are there again.
So whats wrong? Bug? This is a serious issue for me since some classes from newer fiber.swc is not backwards compatible to version 3.4.
I'm using Flash Builder Premium 4.7. It would be great if I could solve that because I have to remove these paths everytime I open the project.
cu Floh

Few things I've discovered that might be able to help you.
Make sure you download both the newest version of the playerglobal.swc (for flash player 10.1), and replace it either in your SDK files, or have it in a library (in Flex 3 you need to disable the older playerglobal, I'm not sure about FB 4)
Use the newest OSMF.swc available from the OSMF downloads page.
Make sure you have the compile settings for OSMF set up in your compile line (mangle for FB4 if needed):-define CONFIG::LOGGING false -define CONFIG::DEBUG false -define CONFIG::FLASH_10_1 true
I've been able to compile flex projects using OSMF doing these steps.
Hope this helps.
-Will

[svn] 4917: Fix FB-16914: Flex Builder swallows some ADL errors if you click Run instead of Debug.

Revision: 4917
Author: [email protected]
Date: 2009-02-10 13:55:43 -0800 (Tue, 10 Feb 2009)
Log Message:
Fix FB-16914: Flex Builder swallows some ADL errors if you click Run instead of Debug.
Also, some debugger code cleanup.
Ticket Links:
http://bugs.adobe.com/jira/browse/FB-16914
Modified Paths:
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/ILaunchNotification.java
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/SessionManager.java
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/concrete/PlayerSessionManag er.java
flex/sdk/trunk/modules/debugger/src/java/flash/tools/debugger/concrete/ProcessListener.ja va

it's a beta. it stunk. but they put it out for review which helps Adobe and others. But never treat those products as stuff to base your serious work around. Flex3 is stable. FB4 is 90% reliable. Things are still broken in it.
btw if it was a leading university why in the world would they base it around a Beta that was buggy or was that your decision ?
now, since I helped, please give me my 5 or 10 points.

Flex Builder 3 will not work on Mac

Flex Builder 3 & Mac OSX:
The hard disk on my mac failed, lost everything, including
Flex Builder 2. I installed a new hard disk, and downloaded the
"trial" of Flex Builder 3 (FB 3). The software seemed to install
fine(no errors in the install log).
However, when I run FB 3, the default front page does not
load, and tells me that the flash player as stopped because of a
un-safe operation. I think okay, that is fine, but I do like the
page with the links to the docs, and adobe resources. I try to
build an app, default just dragged a button on the stage, and
complied. However, the page does not compile. I only get the "grey"
page, with no button.
After this I re-installed the flash player (9.0.115), but
still no love. I have re-installed FB 3, but the same results.
I am using Mac OS X (power PC). Can anybody help me. I am a
student at the University of Hawaii, and I am teaching myself Flex.
I am thinking that the error might be with the flash player, and I
am trying to install flash CS3, thinking that if I can get the
stand alone flash player that way, maybe then this will work.
Please help,
John

Hi Michael,
Thanks so much for all your help!
I just installed FB 3 again, but still no love, yikes! I
don't get it FB 2 was painless,...
I have the same issues, and safari does not handle any flex
apps, just a blank(grey page). Can I ask a favor? Can you check
this link, a flex charting app. It can view it perfectly in Camino,
but just a blank page in safari. Could you check this link in
safari?
http://cfhawaii.com/Charts/DrillDownWithEffects.html
I also still get the can't find the debugger player.
Maybe I need to take a on-line course(bring that I am in
hawaii) to learn how to get everything set up.
I send a bug report to adobe, and I am hoping that somebody
gets back to me, and can help me fix the problems, as I couldn't
even registrar FB3, I want to start learning flex, not dealing with
this.
Thanks so much for all your help`-`
John

Error while running C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\samples\explorer\build.bat

Hello
I am a flex beginner, when i run the C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\samples\explorer\build.bat file the following error is displayed
Loading Configuration file C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\frameworks\flex-config.xml
C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\samples\explorer\loaderPanel.mxml
Error :-1
Please help me to run the bat file, as it will help me to learn flex independently.
error message is attached as bmp.
Thanks in advance.

Hi,
Take a look at this report: https://bugs.adobe.com/jira/browse/FB-11626 It might be of help.
With best regards,
Barna Biro
Blog: http://blog.wisebisoft.com

Problem Installing Adobe Flex Builder 3 (Standalone)

I have attempted a few times today to install the Flex Builder 3 standalone file, but I am having issues. I am currently using Adobe CS4 Design Premium on my computer.
I am new to this type of application development. Currently, I mainly used flash to create my interactive applications, but I need to branch out to create more complex applications. As I already know actionscript 3.0, I was interesting into getting into Flex. I do not know Javascript, C++, etc.
Once I download the standalone file to my desktop and run the installer, I do not choose to download Flash Player 9 because I already have nor do I choose do download the Coldfusion or JSEclipse Plug-in as I do not have Eclipse on my computer (it comes with the standalone as I have been led to believe). After running the installer, it almost gets to the end and then I get the following error message:
I click OK, it finishes the install and says
I go to the log file and get the following:
!SESSION 2010-02-24 16:22:40.424 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application org.eclipse.update.core.standaloneUpdate -command install -from file:\C:\Program Files\Adobe\Flex Builder 3\com.adobe.flexbuilder.update.site/ -featureId com.adobe.flexbuilder.feature.standalone -version 3.0.214193
Command-line arguments: -application org.eclipse.update.core.standaloneUpdate -command install -from file:\C:\Program Files\Adobe\Flex Builder 3\com.adobe.flexbuilder.update.site/ -featureId com.adobe.flexbuilder.feature.standalone -version 3.0.214193
!ENTRY org.eclipse.update.core 4 0 2010-02-24 16:22:44.799
!MESSAGE Cannot install featurecom.adobe.flexbuilder.feature.standalone 3.0.214193
Can anybody help me on this? Is there something I missing prior to download?

We're in the same boat here - the the behavour of xsd:all in
BETA 3 renders our Flex app virtually useless because of
communication issues with the backend webservice. We have studied
the proposed workaround suggested, unfortunately we only control
the FLEX app - we do not control the WS we have to integrate with.
As a result we've gone back to BETA 2 to do some critical
changes in the software but the "Beta expired." message we've been
receiving is really not well received. As we have been very
proactive in supporting development in the BETA phases including
reporitng bugs, we think that Adobe shoudl also have some
flexibility here and offer ways to extend the BETA 2. We're not
asking for any type of support during that phase - purely the
ability to compile our source until we can implement the full work
around which will allow the software to run on BETA 3. The
suggestion to change dates or go to previous restore points do not
work well here with our numerous developers.

Weird Positioning for Skinned Panel in Flex Builder 3

In the previous versions of the Flex Builder 3, even for the
Flex Builder 3 Beta Milestone 4, my custom skinned Panel component
worked fine. So I have an image skin and then I put into Flex
Builder, set the 9 slice settings, did some adjustments to the
headerHeight. And when I add a child component to the Panel
component, it will automatically be placed beneath the Panel's
title (like a VBox layout), position it inside the panel.
But now, compiling with the same files and css in the new
Flex Builder 3 final release, the Panel does not position the
children components correctly anymore. The children are still
positioned in a VBox layout but the first child started from the
point 0,0 of the Panel. So, the first child is overlapping the
Panel's title and all the children seems to go out of the Panel a
bit. This isn't what it used to be(that's to automatically position
them in the content are of the Panel component or at least within
the 9 slice middle area).
A Panel that isn't skinned at all works fine.
Is there anything I have to change or do to solve this?
Thanks.

Looks like what I am having is something close to that except
that my problem is related to the borderSkin and not the
borderStyle. But I have seen some of the comments talking about the
borderSkin problem too.
What I have done now is I use the Flex 3 public release but
copied the sdk from the previous beta version and compile with that
sdk.
It kind of resolves that panel bug problem(since I am just
using the old version) but I am sure I will be missing out any new
features that the new Flex 3 public release has.

"Unembolden" keywords in Flex Builder 3 Editor

Is there anyway to remove the bold attribute from keywords
& string literals in the Flex Builder 3 editor?
In v2, I was able to tweak an xml file in a jar - I can't
find it in the new version.
It is quite troublesome as I like to line up similar lines of
declarative code vertically in order to reduce visual clutter.
As they are wider than normal ones, the bold characters
disturb the mono-spaced layout and foil this effort.
Thanks,
JP

Hi,
It'd be great if you could provide these kind of bugs and
enhancement requests over at the new public bug system!
http://bugs.adobe.com/flex.
Matt
Adobe

Gumbo in Flex builder 3: cannot resolve FxApplication to component implimentation

Hello everyone,
I've been banging my head on the keyboard over this issue for a while. I've downloaded and successfully installed 2 seperate versions of the nightly Flex Gumbo SDK 4.0.0.6831 and 4.0.0.6898 (two versions because i had first assumed that the error was a nightly bug). I've set the Flex compiler to use the new 4.0.0.6898 build and changed the Require flash player version to 10.0.0. Everything set right?
so i put this:
<Application xmlns="http://ns.adobe.com/mxml/2009" layout="absolute">
<FxButton label="Hello World" />
</Application>
and get the error at compile time: Gumbo in Flex builder 3: cannot resolve <FxApplication> to component implimentation. I've tried everything: <Application>, changed the namespaces, and more. Any other ideas?
Thank you in advance -brandon

Try something like this:
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/halo">
    <s:Button label="Hello World" />
</s:Application>

Can't install Flex Builder 2 plugin in Eclipse 3.3/Europa

[I hope Adobe reads these forums. I tried to submit this as a
customer service request, but the customer service request form
kept telling my I had to enter my First Name, Last Name, and Email
address, even though I _had_ entered them!]
I can't seem to install the Flex Builder 2 plugin in Eclipse
3.3/Europa. I had it installed fine in 3.2/Callisto. I uninstalled
it from there, installed Europa, then tried to install the plugin.
After I selected the Eclipse folder, I got the error:
"Please choose an existing Eclipse folder (3.1 or greater) to
be updated. This folder must contain eclipse.exe and the standard
folder named "configuration"."
All three conditions (3.1 or greater, eclipse.exe and
configuration) hold in my case, so I don't know what the real
problem is.

Actually it's quite simple. But you have to be warned. This
doesn't guarantee a bug free Eclipse setup and it isn't supported
by Adobe in any way. It is how-ever your only shot at getting
Eclipse with Flex Builder 2 AND php-development support, as Zend
has stopped deploying the php-development-requirement for Eclipse
3.2 (or at least I haven't found it in their archives.)
Flex Builder 2 simply checks for some files to see if the
directory you want to install to exist, so it recognizes the
directory as an Eclipse 3.1+ directory. Eclipse 3.3 however misses
the file startup.jar. If you simply copy startup.jar from an
Eclipse 3.2 directory into the 3.3 directory, Flex Builder 2 will
install in the 3.3 directory.
Again. This is not supported in any way by Adobe.
For more info, Google on: eclipse-3.3 Flex-builder-2
startup.jar
http://www.google.com/search?hl=en&q=eclipse-3.3+Flex-builder-2+startup.jar
Kind regards.
PS. I would still like to have an Adobe Representative answer
the simple question: Is Adobe or is Adobe not working on getting
Flex Builder 2 to work on Eclipse 3.3? A simple yes or no will
suffice.

Flex Builder 3 under Eclipse - project .settings problem

I've been experiencing some odd problems with a project using FlexBuilder 3 plug-in with Eclipse.
The first problem I've noticed is that a file under the .settings dir has a red 'x' beside it. The offending
file is org.eclipse.jst.common.project.facet.core.prefs. I've left the file as is until I understand how it became corrupt.
The second problem is that .as and .mxml files are no longer being opened in the Flex Builder editor -
the are being opened in TextPad, which it the default editor outside of Flex Builder. I've tried all of the available
editors and none of them work under Flex Builder.
The third problem is that when I try to create a new Flex Builder project from New->Project-> there is no
option for a FlexBuilder project.
The Flex Development perspective is visible in the top right hand corner as usual. When I select Open Perspective
there is no Flex perspective.
Should I just reinstall the FlexBuilder plugin?
Thanks!

Hi Peter,
It has not been fully tested yet but a few of us are using
it. If you see any issues in Eclipse 3.3RC4 with FB3 Plugin, please
file a bug in our new public bug system:
http://bugs.adobe.com/flex.
thanks,
Sharon

Flex Builder 4 Export Release Build fails on OSX

Flex Builder 4, SDK 4.1.0.16076
When I choose Project->Export Release Build, or Export Release Build from the Export context menu, nothing happens on teh interface, but I see the following error in the log. Any thoughts on solution or workaround?
Thanks
D
!ENTRY org.eclipse.ui 4 0 2011-05-25 14:54:44.886
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.getDefaultOutputFolderPath(ExportReleaseVersionProjectAndLocationPage.java:312)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createLocationControls(ExportReleaseVersionProjectAndLocationPage.java:297)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createControl(ExportReleaseVersionProjectAndLocationPage.java:501)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.createPag eControls(ExportReleaseVersionWizard.java:310)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:734)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:606)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction$1.run(Export ReleaseVersionAction.java:93)
at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction.run(ExportRe leaseVersionAction.java:103)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1669)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1693)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1678)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1421)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3657)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3240)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

looks like this is same as http://bugs.adobe.com/jira/browse/FB-29046 -- export works if turn Application Server in Properties to None/Other rather than J2EE... that bug report was closed as unreproducible. Looks like its still out there in the wild...

Serious bug in Flex Builder 3

Similar Messages

Maybe you are looking for