flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject AW: AW: AW: AW: AW: AW: AW: AW: AW: AW: AW: [Falcon][FlexJS] Help with finishing the maven migration
Date Mon, 04 Jul 2016 14:26:49 GMT
No thought's ... just being totally confused now ;-)


Could you please run a Maven build (or check the on Jenkins) and have a look at the generated
config files, if everything is in the right place? I think I still haven's understood the
concept behind these externs (the ones from falcon and the ones from framework modules) ...
Think I'll just go to sports now or my brain will explode instantly :-)


Enjoy your holiday :-)


Chris

________________________________
Von: Alex Harui <aharui@adobe.com>
Gesendet: Montag, 4. Juli 2016 16:16:26
An: Christofer Dutz; dev@flex.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: AW: [Falcon][FlexJS] Help with finishing
the maven migration

OK, I will try again, but it might not be today (holiday in US).

IMO, there are at least two, maybe 3 categories of SWCs:


  1.  External stuff that doesn't use goog.require (playerglobal, airglobal, js.swc, jquery.swc,
cordova.swc, createjs.swc)
  2.  Stuff (some that we wrote, some from third parties)  that does use goog.require (gcl.swc,
Core,  Binding, HTML, and other frameworks projects)
  3.  A theoretical, but AFAIK, not-yet-existant library of code to be included in SWCs in
#2.

When building other SWCs that go in #2, up stream SWCs are configured as follows:
#1 always goes on external library path for both SWF and JS
#2 goes on external library path for SWF and library path for JS
#3 would go on library path for both SWF and JS

When building apps, and SWCs that share code for apps,
#1 goes on external library path
#2 goes on library path
There shouldn't be any #3s.

It might be that we should mark our SWCs somehow and make the compiler smarter so up-stream
#2 can always be on library path when building other #2 SWCs.

Thoughts?
-Alex

From: Christofer Dutz <christofer.dutz@c-ware.de<mailto:christofer.dutz@c-ware.de>>
Date: Monday, July 4, 2016 at 3:17 AM
To: Alex Harui <aharui@adobe.com<mailto:aharui@adobe.com>>, "dev@flex.apache.org<mailto:dev@flex.apache.org>"
<dev@flex.apache.org<mailto:dev@flex.apache.org>>
Subject: AW: AW: AW: AW: AW: AW: AW: AW: AW: AW: [Falcon][FlexJS] Help with finishing the
maven migration


Ok some progress [?]


So I added a new compiler option to the maven plugin:

forceSwcExternalLibraryPath

This is set to false per default, but if set to true, ALL libraries go to the external-library-path.
I think this is a lot easier than to sort of think of a way to manually configure stuff like
this. Eventually this will not work for all usecases, but it works for now and it only has
to work for as long as I need to implement some new functionality in Maven and have a new
Maven release with that functionality built in.


I also found that in Network and Binding I had added a JSLib to the external-library-path.
I removed this and now almost all Examples seem to be working. I even found out that the CreateJSExample
is actually animated ... wonder why the ball doesn't move in the Flash version.


Unfortunately I didn't find the external-lib-problem in Network before starting the next build,
so I'm currently doing another one and then I'll be going through the examples again, checking
the SWF and the JS version and update the TODO section with findings in the examples pom.xmls


Chris


________________________________
Von: Christofer Dutz <christofer.dutz@c-ware.de<mailto:christofer.dutz@c-ware.de>>
Gesendet: Montag, 4. Juli 2016 11:03:25
An: Alex Harui; dev@flex.apache.org<mailto:dev@flex.apache.org>
Betreff: AW: AW: AW: AW: AW: AW: AW: AW: AW: AW: [Falcon][FlexJS] Help with finishing the
maven migration

Hi Alex,


I could confirm your observation, so in order to test things, I changed the dependencies to
all the libraries to the library-path in all cases. With this the output had a lot less errors.
However I am still getting errors from the binding system.


I am having real trouble to make this setup work nicely in Maven. We seem to have 3 different
cases:

1. Library is on library-path for SWC and JS

2. Library is on external-library-path for SWC and JS

3. Library is on external-library-path for SWC and library-path for JS

the first two cases are trivial and I select which one by choosing "compile" (1) or "runtime"
(2).

Unfortunately I have no idea how I could tell maven to use option 3 in a way that is not a
complete hack.

Would it be ok to add a plugin config option to forcefully link all libraries using external-library-path?


Chris

________________________________
Von: Alex Harui <aharui@adobe.com<mailto:aharui@adobe.com>>
Gesendet: Montag, 4. Juli 2016 09:10:22
An: dev@flex.apache.org<mailto:dev@flex.apache.org>; Christofer Dutz
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: AW: AW: [Falcon][FlexJS] Help with finishing the
maven migration



On 7/3/16, 7:48 AM, "Alex Harui" <aharui@adobe.com<mailto:aharui@adobe.com>> wrote:

>Excellent!  I will investigate the runtime issues this evening.

I poked around.  I noted:

-RadioButton is broken.  Peter or I will look into it.
-For Binding (and probably other projects), Core.swc is on the
external-library-path for the AS compile, but needs to be on the
library-path for JS compiles.  Hopefully that's not too hard to pull off.
-I did not see the HTTPService errors.

I'll try to find time to look at a few more this week.

-Alex


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message