Have you compared the folder structures from npm install vs the installer? Should they be the same?
-Alex On 12/29/15, 1:04 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: >I got the FlexJS 0.5 installed via the Installer and the call to asjsc >from >that folder seems to work fine. > >So, I don't think it is a Java version conflict. > >Any other ideas? > >Thanks, >Om > >On Mon, Dec 28, 2015 at 3:03 AM, Michael Schmalle ><teotigraphix...@gmail.com >> wrote: > >> Just shooting in the dark but some type of Java version conflict? It >>seems >> familiar to me like that could be a possibility. >> >> Mike >> >> On Mon, Dec 28, 2015 at 4:34 AM, OmPrakash Muppirala >><bigosma...@gmail.com >> > >> wrote: >> >> > I have this working locally. If the user has npm and Java installed >>on >> > their machine, they can now simply do: >> > >> > *npm install flexjs -g* >> > (or should it be npm install apache-flexjs -g?) >> > >> > This will download all the dependencies (which has some bugs for now, >> will >> > get to that in a bit), register the asjsc and asjscompc files as >>global >> > binaries. >> > >> > One issue I am currently facing is, when I do this: >> > >> > >> > >> >>C:\Users\omuppirala\AppData\Roaming\npm\node_modules\flexjs\examples\nati >>ve\USStatesMap\src>asjsc >> > USStatesMap.as >> > >> > I am getting this error: >> > Error: Could not find or load main class >> > org.apache.flex.compiler.clients.MXMLJSC >> > >> > This looks familiar, but I am not sure what I am doing wrong. >> > >> > Any pointers? >> > >> > P.S. I will upload this flexjs npm module as a tarball on to my >>personal >> > site from where the rest of the folks can test. Once we iron out all >>the >> > kinks, I will set about publishing the module to the npm repository. >> > >> > Thanks, >> > Om >> > >>
