Nope, creating a 'jar' (with a proper manifest and all) didn't do any good.
The problem seems to be the dependencies on the 'compiler' project. If I run MXMLJSC.class on the command line and feed it the following three class paths (pseudo paths): "falcon-compiler/generated/classes", "closure-compiler/compiler.jar" and "falcon-compiler/lib/commons-io.jar", I get what looks to be a 'working' compiler. If I feed that the arguments I noted earlier and point it to a valid AS project, I get: <error> Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/flex/compiler/internal/parsing/as/ASParser at org.apache.flex.compiler.internal.projects.ConfigManager$ProjectVariables.loadConfigData(ConfigManager.java:126) at org.apache.flex.compiler.internal.projects.ConfigManager$ProjectVariables.getProblems(ConfigManager.java:183) at org.apache.flex.compiler.internal.projects.ConfigManager.getProjectConfig(ConfigManager.java:308) at org.apache.flex.compiler.internal.projects.CompilerProject.collectConfigProblems(CompilerProject.java:652) at org.apache.flex.compiler.internal.projects.ASProject.collectProblems(ASProject.java:310) at org.apache.flex.compiler.internal.targets.Target.buildCompilationUnits(Target.java:216) at org.apache.flex.compiler.internal.targets.Target.buildAllCompilationUnits(Target.java:298) at org.apache.flex.compiler.internal.targets.Target.getBuiltCompilationUnitSet(Target.java:306) at org.apache.flex.compiler.internal.targets.JSTarget.buildAndCollectProblems(JSTarget.java:188) at org.apache.flex.compiler.internal.targets.JSTarget.build(JSTarget.java:116) at org.apache.flex.compiler.internal.targets.JSTarget.build(JSTarget.java:228) at org.apache.flex.compiler.clients.MXMLJSC.buildApplication(MXMLJSC.java:375) at org.apache.flex.compiler.clients.MXMLJSC.buildJSTarget(MXMLJSC.java:337) at org.apache.flex.compiler.clients.MXMLJSC.buildArtifact(MXMLJSC.java:329) at org.apache.flex.compiler.clients.MXMLJSC.compile(MXMLJSC.java:252) at org.apache.flex.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:191) at org.apache.flex.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:149) at org.apache.flex.compiler.clients.MXMLJSC.main(MXMLJSC.java:112) </error> Does that shed some light on my problem? Again, when I run in Eclipse, with the same arguments, I get a nicely compiled JS project as output. EdB On Wed, Jan 16, 2013 at 4:10 PM, Erik de Bruin <e...@ixsoftware.nl> wrote: > There you go... create a 'jar'. Google, here I come! > > EdB > > > > On Wed, Jan 16, 2013 at 4:05 PM, Michael Schmalle > <apa...@teotigraphix.com> wrote: >> Erik, >> >> I glanced at you update to the compiler class. My question is, what is "not" >> working when you try and run it on the command line? >> >> Basically, you need a jar to execute and call it with the same arguments you >> use in the Eclipse run config. >> >> Have you created a jar for the compiler? >> >> Mike >> >> >> Quoting Erik de Bruin <e...@ixsoftware.nl>: >> >>> Hi, >>> >>> I've been playing with FalconJx a bit and I have convinced it to >>> compile an entire AS project into JS for me... but only when I run it >>> in Eclipse (run configuration with arguments, for details see my last >>> commit). What do I need to do to get this to work from the command >>> line (Terminal, actually, as I'm on a Mac)? >>> >>> I'm working on an AIR app or ant build file to automate the JS >>> publishing workflow, so compiling an entire workflow from the command >>> line is (to say the least) "nice to have" :-) >>> >>> Thanks, >>> >>> EdB >>> >>> >>> >>> -- >>> Ix Multimedia Software >>> >>> Jan Luykenstraat 27 >>> 3521 VB Utrecht >>> >>> T. 06-51952295 >>> I. www.ixsoftware.nl >>> >> >> -- >> Michael Schmalle - Teoti Graphix, LLC >> http://www.teotigraphix.com >> http://blog.teotigraphix.com >> > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
