Re: AW: FlexJS 0.7.0 - NPM installation issues
I don't know what fix is needed for NPM, but based on the questions Om is asking, I doubt the NPM fix will affect the Maven jars. It will, however, mean that if you publish artifacts before Om fixes NPM, I won't be able to use whatever tag you give me since I will use the later commit from Om when building the source package. So, IMO, up to you if you want get started now, although I did see that Josh checked in something to the develop branch which is not in the release branch. -Alex On 8/22/16, 1:22 PM, "Christofer Dutz" wrote: >Aaaahh ... I think I just misunderstood you. I thought you added some >changes to the compiler defaults. Yes, we did clean up quite a bit there. >But the changes I did should probably only have an effect on Maven >builds. So I guess we're on the safe side from the Maven point of view. > > >Chris > > >Von: Josh Tynjala >Gesendet: Montag, 22. August 2016 22:15:35 >An: dev@flex.apache.org >Betreff: Re: FlexJS 0.7.0 - NPM installation issues > >Chris, I'm guessing you don't need to do anything because I think you and >Alex were working together on the various changes. However, I don't follow >the Maven stuff closely enough to know for sure. > >Basically, instead of hard-coding certain compiler options in the >executable scripts in js/bin, they now specify a +configname option to >tell >the compiler to load the default options from one of the *-config.xml >files >in the frameworks directory. > >Here is the relevant line of js/bin/asjsc in Apache FlexJS 0.6: > >java $VMARGS $D32 $SETUP_SH_VMARGS -Dflexcompiler="$FALCON_HOME" >-Dflexlib="$FLEX_HOME/frameworks" -jar "$SCRIPT_HOME/../lib/mxmlc.jar" >+flexlib="$FLEX_HOME/frameworks" -js-output-type=jsc >-external-library-path="$SCRIPT_HOME/../libs/js.swc" "$@" > >And js/bin/asjsc from the 0.7 nightly: > >java $VMARGS $D32 $SETUP_SH_VMARGS -Dflexcompiler="$FALCON_HOME" >-Dflexlib="$FLEX_HOME/frameworks" -jar "$SCRIPT_HOME/../lib/mxmlc.jar" >+flexlib="$FLEX_HOME/frameworks" -js-output-type=jsc +configname=js "$@" > >+configname=js tells the compiler to load frameworks/js-config.xml. The >external-library-path option that was hard-coded in js/bin/asjsc in 0.6 is >now specified in js-config.xml. I think there are some other options that >are different from the default flex-config.xml too. > >asnodec, as another example, used to add both js.swc and node.swc to the >external-library-path in the executable script, but now it specifies >+configname=node, which loads frameworks/node-config.xml. > >Ultimately, this will make maintenance of the NPM version easier because >any new compiler options will be picked up automatically in the >*-config.xml files. It also means that compiler options used by the Shell >scripts (Unix) or Batch files (Windows) won't get out of sync because >they're now specified in one place only. > >- Josh > >On Mon, Aug 22, 2016 at 12:47 PM, Christofer Dutz >> wrote: > >> Will this have an effect on the Maven Plugin? >> >> >> Chris >> >> >> Von: Josh Tynjala >> Gesendet: Montag, 22. August 2016 17:09:03 >> An: dev@flex.apache.org >> Betreff: Re: FlexJS 0.7.0 - NPM installation issues >> >> One more thing that will be easy to miss: >> >> The executable files like asjsc in js/bin have been tweaked a bit to >> include different default compiler arguments. The NPM exectuables like >> asjscnpm will need those same tweaks. >> >> - Josh >> >> On Fri, Aug 19, 2016 at 3:44 PM, OmPrakash Muppirala >>> > >> wrote: >> >> > I just tried the rc release with the current npm installation setup. >> > >> > First issue I see is this: >> > >> > >> > Error: ENOENT: no such file or directory, scandir >> > 'C:\Users\omuppirala\AppData\Roaming\npm\node_modules\ >> > flexjs\downloads\falcon\compiler\generated\dist\sdk\bin' >> > >> > In 0.6.0, we were copying files from the >> > '...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did >> > that >> > get moved? >> > >> > Thanks, >> > Om >> > >>
AW: FlexJS 0.7.0 - NPM installation issues
Aaaahh ... I think I just misunderstood you. I thought you added some changes to the compiler defaults. Yes, we did clean up quite a bit there. But the changes I did should probably only have an effect on Maven builds. So I guess we're on the safe side from the Maven point of view. Chris Von: Josh Tynjala Gesendet: Montag, 22. August 2016 22:15:35 An: dev@flex.apache.org Betreff: Re: FlexJS 0.7.0 - NPM installation issues Chris, I'm guessing you don't need to do anything because I think you and Alex were working together on the various changes. However, I don't follow the Maven stuff closely enough to know for sure. Basically, instead of hard-coding certain compiler options in the executable scripts in js/bin, they now specify a +configname option to tell the compiler to load the default options from one of the *-config.xml files in the frameworks directory. Here is the relevant line of js/bin/asjsc in Apache FlexJS 0.6: java $VMARGS $D32 $SETUP_SH_VMARGS -Dflexcompiler="$FALCON_HOME" -Dflexlib="$FLEX_HOME/frameworks" -jar "$SCRIPT_HOME/../lib/mxmlc.jar" +flexlib="$FLEX_HOME/frameworks" -js-output-type=jsc -external-library-path="$SCRIPT_HOME/../libs/js.swc" "$@" And js/bin/asjsc from the 0.7 nightly: java $VMARGS $D32 $SETUP_SH_VMARGS -Dflexcompiler="$FALCON_HOME" -Dflexlib="$FLEX_HOME/frameworks" -jar "$SCRIPT_HOME/../lib/mxmlc.jar" +flexlib="$FLEX_HOME/frameworks" -js-output-type=jsc +configname=js "$@" +configname=js tells the compiler to load frameworks/js-config.xml. The external-library-path option that was hard-coded in js/bin/asjsc in 0.6 is now specified in js-config.xml. I think there are some other options that are different from the default flex-config.xml too. asnodec, as another example, used to add both js.swc and node.swc to the external-library-path in the executable script, but now it specifies +configname=node, which loads frameworks/node-config.xml. Ultimately, this will make maintenance of the NPM version easier because any new compiler options will be picked up automatically in the *-config.xml files. It also means that compiler options used by the Shell scripts (Unix) or Batch files (Windows) won't get out of sync because they're now specified in one place only. - Josh On Mon, Aug 22, 2016 at 12:47 PM, Christofer Dutz wrote: > Will this have an effect on the Maven Plugin? > > > Chris > > ____ > Von: Josh Tynjala > Gesendet: Montag, 22. August 2016 17:09:03 > An: dev@flex.apache.org > Betreff: Re: FlexJS 0.7.0 - NPM installation issues > > One more thing that will be easy to miss: > > The executable files like asjsc in js/bin have been tweaked a bit to > include different default compiler arguments. The NPM exectuables like > asjscnpm will need those same tweaks. > > - Josh > > On Fri, Aug 19, 2016 at 3:44 PM, OmPrakash Muppirala > > wrote: > > > I just tried the rc release with the current npm installation setup. > > > > First issue I see is this: > > > > > > Error: ENOENT: no such file or directory, scandir > > 'C:\Users\omuppirala\AppData\Roaming\npm\node_modules\ > > flexjs\downloads\falcon\compiler\generated\dist\sdk\bin' > > > > In 0.6.0, we were copying files from the > > '...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did > > that > > get moved? > > > > Thanks, > > Om > > >
Re: FlexJS 0.7.0 - NPM installation issues
Chris, I'm guessing you don't need to do anything because I think you and Alex were working together on the various changes. However, I don't follow the Maven stuff closely enough to know for sure. Basically, instead of hard-coding certain compiler options in the executable scripts in js/bin, they now specify a +configname option to tell the compiler to load the default options from one of the *-config.xml files in the frameworks directory. Here is the relevant line of js/bin/asjsc in Apache FlexJS 0.6: java $VMARGS $D32 $SETUP_SH_VMARGS -Dflexcompiler="$FALCON_HOME" -Dflexlib="$FLEX_HOME/frameworks" -jar "$SCRIPT_HOME/../lib/mxmlc.jar" +flexlib="$FLEX_HOME/frameworks" -js-output-type=jsc -external-library-path="$SCRIPT_HOME/../libs/js.swc" "$@" And js/bin/asjsc from the 0.7 nightly: java $VMARGS $D32 $SETUP_SH_VMARGS -Dflexcompiler="$FALCON_HOME" -Dflexlib="$FLEX_HOME/frameworks" -jar "$SCRIPT_HOME/../lib/mxmlc.jar" +flexlib="$FLEX_HOME/frameworks" -js-output-type=jsc +configname=js "$@" +configname=js tells the compiler to load frameworks/js-config.xml. The external-library-path option that was hard-coded in js/bin/asjsc in 0.6 is now specified in js-config.xml. I think there are some other options that are different from the default flex-config.xml too. asnodec, as another example, used to add both js.swc and node.swc to the external-library-path in the executable script, but now it specifies +configname=node, which loads frameworks/node-config.xml. Ultimately, this will make maintenance of the NPM version easier because any new compiler options will be picked up automatically in the *-config.xml files. It also means that compiler options used by the Shell scripts (Unix) or Batch files (Windows) won't get out of sync because they're now specified in one place only. - Josh On Mon, Aug 22, 2016 at 12:47 PM, Christofer Dutz wrote: > Will this have an effect on the Maven Plugin? > > > Chris > > ____________ > Von: Josh Tynjala > Gesendet: Montag, 22. August 2016 17:09:03 > An: dev@flex.apache.org > Betreff: Re: FlexJS 0.7.0 - NPM installation issues > > One more thing that will be easy to miss: > > The executable files like asjsc in js/bin have been tweaked a bit to > include different default compiler arguments. The NPM exectuables like > asjscnpm will need those same tweaks. > > - Josh > > On Fri, Aug 19, 2016 at 3:44 PM, OmPrakash Muppirala > > wrote: > > > I just tried the rc release with the current npm installation setup. > > > > First issue I see is this: > > > > > > Error: ENOENT: no such file or directory, scandir > > 'C:\Users\omuppirala\AppData\Roaming\npm\node_modules\ > > flexjs\downloads\falcon\compiler\generated\dist\sdk\bin' > > > > In 0.6.0, we were copying files from the > > '...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did > > that > > get moved? > > > > Thanks, > > Om > > >
AW: FlexJS 0.7.0 - NPM installation issues
Will this have an effect on the Maven Plugin? Chris Von: Josh Tynjala Gesendet: Montag, 22. August 2016 17:09:03 An: dev@flex.apache.org Betreff: Re: FlexJS 0.7.0 - NPM installation issues One more thing that will be easy to miss: The executable files like asjsc in js/bin have been tweaked a bit to include different default compiler arguments. The NPM exectuables like asjscnpm will need those same tweaks. - Josh On Fri, Aug 19, 2016 at 3:44 PM, OmPrakash Muppirala wrote: > I just tried the rc release with the current npm installation setup. > > First issue I see is this: > > > Error: ENOENT: no such file or directory, scandir > 'C:\Users\omuppirala\AppData\Roaming\npm\node_modules\ > flexjs\downloads\falcon\compiler\generated\dist\sdk\bin' > > In 0.6.0, we were copying files from the > '...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did > that > get moved? > > Thanks, > Om >
Re: FlexJS 0.7.0 - NPM installation issues
One more thing that will be easy to miss: The executable files like asjsc in js/bin have been tweaked a bit to include different default compiler arguments. The NPM exectuables like asjscnpm will need those same tweaks. - Josh On Fri, Aug 19, 2016 at 3:44 PM, OmPrakash Muppirala wrote: > I just tried the rc release with the current npm installation setup. > > First issue I see is this: > > > Error: ENOENT: no such file or directory, scandir > 'C:\Users\omuppirala\AppData\Roaming\npm\node_modules\ > flexjs\downloads\falcon\compiler\generated\dist\sdk\bin' > > In 0.6.0, we were copying files from the > '...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did > that > get moved? > > Thanks, > Om >
Re: FlexJS 0.7.0 - NPM installation issues
On 8/20/16, 11:08 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Aug 20, 2016 10:33 PM, "Alex Harui" wrote: >> >> >> >> On 8/20/16, 5:50 PM, "omup...@gmail.com on behalf of OmPrakash >>Muppirala" >> wrote: >> >> >Okay, looks like the falcon distribution has changed a lot. Can you >> >please >> >point me to the new way of doing these: >> > >> >Right now, we copy: >> > >> >falcon/js/lib to flexjs/js/lib >> >falcon/js/lib to flexjs/js/libs >> >falcon/externs to flexjs/externs >> >falcon/compiler/generated/dist/sdk/lib to flexjs/lib >> >falcon/compiler/lib to flexjs/lib/external >> > >> >How would this change with the new maven related changes? >> >> I'm not quite sure what you are looking for. Are you copying files from >> the repos or a binary package? > >Binary package. I am trying to reconcile the way we were packaging >0.6.0 >vs the way we are doing it with 0.7.0. If you are starting with apache-flex-falconjx-0.7.0-bin, then the answers are slightly different because the binary packages bundles flex-typedefs (sort of like how flex-sdk bundles flex-tlf): I think what was in falcon/js/lib is now in falcon/compiler-jx/lib falcon/js/libs should still be there What was in falcon/externs is now in falcon/flex-typedefs falcon/compiler/generated/dist/sdk/lib is probably in falcon/compiler/lib and already has the external folder set up correctly. -Alex
Re: FlexJS 0.7.0 - NPM installation issues
On Aug 20, 2016 10:33 PM, "Alex Harui" wrote: > > > > On 8/20/16, 5:50 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > wrote: > > >Okay, looks like the falcon distribution has changed a lot. Can you > >please > >point me to the new way of doing these: > > > >Right now, we copy: > > > >falcon/js/lib to flexjs/js/lib > >falcon/js/lib to flexjs/js/libs > >falcon/externs to flexjs/externs > >falcon/compiler/generated/dist/sdk/lib to flexjs/lib > >falcon/compiler/lib to flexjs/lib/external > > > >How would this change with the new maven related changes? > > I'm not quite sure what you are looking for. Are you copying files from > the repos or a binary package? Binary package. I am trying to reconcile the way we were packaging 0.6.0 vs the way we are doing it with 0.7.0. Assuming the repos: > > I think what was in falcon/js/lib is now in compiler-jx/lib > falcon/js/libs is now in individual folders in the flex-typedefs repo and > aggregated into flex-asjs/js/libs > Falcon/externs is moved to the flex-typedefs repo > Falcon/compiler/generated/dist/sdk/lib is probably in compiler/lib and > already has the external folder set up correctly. This is good info. Let me try these changes. Is this different from the binaries? Thanks, Om > > HTH, > -Alex >
Re: FlexJS 0.7.0 - NPM installation issues
On 8/20/16, 5:50 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >Okay, looks like the falcon distribution has changed a lot. Can you >please >point me to the new way of doing these: > >Right now, we copy: > >falcon/js/lib to flexjs/js/lib >falcon/js/lib to flexjs/js/libs >falcon/externs to flexjs/externs >falcon/compiler/generated/dist/sdk/lib to flexjs/lib >falcon/compiler/lib to flexjs/lib/external > >How would this change with the new maven related changes? I'm not quite sure what you are looking for. Are you copying files from the repos or a binary package? Assuming the repos: I think what was in falcon/js/lib is now in compiler-jx/lib falcon/js/libs is now in individual folders in the flex-typedefs repo and aggregated into flex-asjs/js/libs Falcon/externs is moved to the flex-typedefs repo Falcon/compiler/generated/dist/sdk/lib is probably in compiler/lib and already has the external folder set up correctly. HTH, -Alex
Re: FlexJS 0.7.0 - NPM installation issues
Okay, looks like the falcon distribution has changed a lot. Can you please point me to the new way of doing these: Right now, we copy: falcon/js/lib to flexjs/js/lib falcon/js/lib to flexjs/js/libs falcon/externs to flexjs/externs falcon/compiler/generated/dist/sdk/lib to flexjs/lib falcon/compiler/lib to flexjs/lib/external How would this change with the new maven related changes? Thanks, Om On Fri, Aug 19, 2016 at 10:04 PM, Alex Harui wrote: > On 8/19/16, 3:44 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > wrote: > > > >In 0.6.0, we were copying files from the > >'...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did > >that > >get moved? > > Yes. The Maven refactor moved things around. > > > I think what was in that folder is now in compiler/src/assembly/scripts > > HTH, > -Alex > >
Re: FlexJS 0.7.0 - NPM installation issues
On 8/19/16, 3:44 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: > >In 0.6.0, we were copying files from the >'...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did >that >get moved? Yes. The Maven refactor moved things around. I think what was in that folder is now in compiler/src/assembly/scripts HTH, -Alex
FlexJS 0.7.0 - NPM installation issues
I just tried the rc release with the current npm installation setup. First issue I see is this: Error: ENOENT: no such file or directory, scandir 'C:\Users\omuppirala\AppData\Roaming\npm\node_modules\flexjs\downloads\falcon\compiler\generated\dist\sdk\bin' In 0.6.0, we were copying files from the '...\downloads\falcon\compiler\generated\dist\sdk\bin' directory. Did that get moved? Thanks, Om