Closed GoogleCodeExporter closed 9 years ago
Run with -e parameter so I can see the stack trace.
Are you sure your FDK is not corrupted some how?
VELO
Original comment by velo...@gmail.com
on 12 Jan 2009 at 11:57
Hmm. Maybe I add Russian locals? With M8 all works fine.
Here is trace:
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to create
fdk-bundle
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(Defaul
tLifecycleExecutor.java:512
)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.j
ava:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:227)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to create
fdk-bundle
at info.flexmojos.install.AbstractInstallMojo.installBundle(AbstractInstallMojo.java:426)
at info.flexmojos.install.AbstractInstallMojo.execute(AbstractInstallMojo.java:411)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Original comment by sokolov....@gmail.com
on 12 Jan 2009 at 12:07
Good news and bad news....
The good news is: what this occur on the end of the process. And it isn't
harmful in
99% of cases (truly this fdk-bundle is used only by me currently).
The bad news is: I forget to propagate cause exception, so you log won't help
much =/
I changed flex-mojos on TRUNK to propagate the real cause exception. So far
what I
can tell is install-mojo tried to create a FDK.zip and fail.
VELO
Original comment by velo...@gmail.com
on 12 Jan 2009 at 12:38
Hi,
I just released 2.0.1.
This version should show more details on this error. Can you give it a shoot?
VELO
Original comment by velo...@gmail.com
on 15 Jan 2009 at 11:17
Hi,
2.0M10 work like as charm ) all installed perfectly
mvn -s settings.xml info.flex-mojos:install-mojo:2.0M10:install-sdk
-Dflex.sdk.folder=flex_sdk_3_fast -
Dversion=3.1.0-fast
[INFO] Installing /tmp/air-framework14792.pom to
/Users/stanislav/.m2/repository/com/adobe/flex/framework/air-framework/3.1.0-fas
t/air-framework-
3.1.0-fast.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
Original comment by sokolov....@gmail.com
on 15 Jan 2009 at 12:29
Then, lemme close it.
Original comment by velo...@gmail.com
on 15 Jan 2009 at 12:34
Original issue reported on code.google.com by
sokolov....@gmail.com
on 12 Jan 2009 at 11:55