Quantcast
Channel: Adobe Community : Popular Discussions - Using Flash Builder
Viewing all articles
Browse latest Browse all 70427

FlashBuilder 4.7 command line fails due to "Exception in com.adobe.flexbuilder.codemodel.CMCoreActivator.start() of bundle"

$
0
0

Hi,

I'm facing this issue:

 

When I use FB 4.7 GUI, everything works OK.

When I use FB 4.7 command line, it fails as follows:

 

  • org.osgi.framework.BundleException: Exception in com.adobe.flexbuilder.codemodel.CMCoreActivator.start() of bundle com.adobe.flexbuilder.codemodel.


By the way, I’ve overlaid FB 4.7 with AIR SDK 14 (which works fine in GUI).

By the way2, I think the following thread reports exactly the same issue but is yet not answered:

https://forums.adobe.com/thread/1445134

 

here is the XML:

 

<?xml version="1.0"?>

<project default="main">

    <target name="main">

         <echo message="Info: Starting main target"/>

        <fb.exportReleaseBuild project="888PokerAndroid_3_2_0" destdir="c:\temp\erez_test" platform="android" verbose="true" android.password="poker" packagetype="platform" />

    </target>

</project>


it works fine in the GUI.

 

any ideas?


here is how I run it:

C:\FB\mobile_Android_3.2.0_WS1>"C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\FlashBuilderC.exe" --launcher.suppressErrors -noSplash -application org.eclipse.ant.core.antRunner -data "C:\FB\mobile_Android_3.2.0_WS1" -file "c:\FB\build_888PokerAndroid_3_2_0.xml" main

Buildfile: c:\FB\build_888PokerAndroid_3_2_0.xml

 

main:

     [echo] Info: Starting main target

[fb.exportReleaseBuild] Compiling 1 application to C:/GamingX/Develop/PokerClient/Flash/ProjectSources/888PokerAndroid/v3.2.99/bin-release-t emp...

[fb.exportReleaseBuild] An internal build error has occurred. See the error log for more information: C:\FB\mobile_Android_3.2.0_WS1\.metadata\.log

[fb.exportReleaseBuild] [compilation completed 3,816ms]

 

BUILD FAILED

c:\FB\build_888PokerAndroid_3_2_0.xml:5: Build failed.

 

Total time: 6 seconds

Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.microsoft.tfs.client.common.ui.helpers.WorkbenchHelper$WorkbenchStartupJob

Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.microsoft.tfs.client.common.ui.helpers.WorkbenchHelper$WorkbenchStartupJob

Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.microsoft.tfs.client.eclipse.TFSRepositoryProvider$1

Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.microsoft.tfs.client.eclipse.TFSEclipseClientPlugin$1

F l a s h B u i l d e r C :

A n   e r r o r   h a s   o c c u r r e d .   S e e   t h e   l o g   f i l e

C : \ F B \ m o b i l e _ A n d r o i d _ 3 . 2 . 0 _ W S 1 \ . m e t a d a t a \ . l o g .

 

any suggestions?

 

thanks,

Erez.


Viewing all articles
Browse latest Browse all 70427

Trending Articles