You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2016/06/20 08:39:54 UTC
[Falcon][FlexJS] Help with finishing the maven migration
Hi,
I have finished migrating Falcon to Maven and all except the XML framework module of ASJS seem to be migrated too. I do need some help with getting the examples up and running and finding out why the js version of XML isn't working. I know that it worked a few days/1-2 weeks ago, but I have no idea why it's no longer working. A lot seems to have been changed with the configuration of the JS builds, so I would like to ask the people working on this to have a look.
As you all have the Ant environment variables in place, you shouldn't need to do anything on that side, all you need to do is download Maven and make sure the bin directory is on the path.
Then the following commands should built the individual parts of FlexJS
In the falcon root directory:
mvn -s settings-template.xml -P utils clean install
mvn -s settings-template.xml -P compiler clean install
(Add "-DskipTests" to skip tests)
mvn -s settings-template.xml -P externs clean install
In the ASJS root directory:
mvn -s settings-template.xml clean install
If you want to see what the compiler is doing, the plugin generates the configs for all build steps in the "target" directory of each module. I am not adding any other commandline arguments besides the location of the configuration so you can be sure that the config.xml contains all important settings.
If you find something that's missing or wrong, I'll adjust the templates or add some more config options (I am planning on supporting all options, but till now I only implemented the ones that are actually needed for the build)
Chris
AW: AW: [Falcon][FlexJS] Help with finishing the maven migration
Posted by Christofer Dutz <ch...@c-ware.de>.
Here the complete list of problems I'm having:
ChartExample:
VerifyError: Error #1032: Cpool index 0 is out of range 1847.
at org.apache.flex.core::ContainerBase/addedToParent()
at org.apache.flex.core::Application/addElement()
at org.apache.flex.core::Application/initialize()
at org.apache.flex.core::Application/initHandler()
CordovaCameraExample:
VerifyError: Error #1079: Native methods are not allowed in loaded code.
(Airglobal is not in the library-path)
CreateJSExample:
- Seems to be working nicely
DataBindingExample:
TypeError: Error #1006: value is not a function.
at MyInitialView()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLObject()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLProperties()
at org.apache.flex.core::Application/generateMXMLAttributes()
at DataBindingExample()
DataBindingExample_as:
TypeError: Error #1009: Cannot access a property or method of a null object reference.
at org.apache.flex.html.beads::ContainerView/set strand()
at org.apache.flex.core::UIBase/addBead()
at org.apache.flex.core::UIBase/addedToParent()
at org.apache.flex.core::ContainerBase/addedToParent()
at org.apache.flex.core::UIBase/addElement()
at org.apache.flex.core::ContainerBase/addElement()
at MyInitialView/get MXMLDescriptor()
at org.apache.flex.core::ContainerBase/addedToParent()
at org.apache.flex.core::Application/addElement()
at org.apache.flex.core::Application/initialize()
at org.apache.flex.core::Application/initHandler()
DataBindingExample_Flat:
TypeError: Error #1006: value is not a function.
at MyInitialView()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLObject()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLProperties()
at org.apache.flex.core::Application/generateMXMLAttributes()
at DataBindingExample()
DataGridExample:
- Seems to be working but looking a little strange
DesktopMap:
VerifyError: Error #1079: Native methods are not allowed in loaded code.
(Airglobal is not in the library-path)
FlexJSStore:
Not building due to Ambiguous MouseEvent
FlexJSStore_jquery:
Not building due to Ambiguous MouseEvent
FlexWebsiteStatsViewer:
Not building due to Ambiguous MouseEvent
HelloWorld:
- Seems to be working nicely
MapSearch:
VerifyError: Error #1079: Native methods are not allowed in loaded code.
(Airglobal is not in the library-path)
MobileTrader:
Not building due to
Implicit coercion of a value with static type Event to a possibly unrelated type Event.
StorageExample:
Not building due to
Ambiguous reference to IDataInput
TodoListSampleApp:
- Seems to be working but looking a little strange as the labels are all "[object Object]"
TreeExample:
- Seems to be working nicely
So we're up to 5 Working examples ... this is 5 more than this morning :-)
Just as an example I created a screenshot from the dependency graph for the FlexJSStore project:
http://apaste.info/ReG
[http://www.apache.org/images/asf_logo.gif]<http://apaste.info/ReG>
Paste #ReG - Apache Paste Bucket<http://apaste.info/ReG>
apaste.info
Chris
________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Dienstag, 21. Juni 2016 12:50:55
An: dev@flex.apache.org
Betreff: AW: AW: [Falcon][FlexJS] Help with finishing the maven migration
Ok so I had to add some more dependencies but now I'm getting an error that's not related to missing classes I guess:
TypeError: Error #1006: value is not a function.
at MyInitialView()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLObject()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLProperties()
at org.apache.flex.core::Application/generateMXMLAttributes()
at DataBindingExample()
Any Idea on this one?
Chris
________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Dienstag, 21. Juni 2016 12:44:18
An: dev@flex.apache.org
Betreff: AW: AW: [Falcon][FlexJS] Help with finishing the maven migration
Thanks for that tip ... indeed it was the airglobal that was in the library-path.
I moved that to the external library path and that error was replaced by another, but that's on I can handle ... I'll try to fix this and see how far I come [?]
Chris
________________________________
Von: piotrz <pi...@gmail.com>
Gesendet: Dienstag, 21. Juni 2016 12:00:01
An: dev@flex.apache.org
Betreff: Re: AW: [Falcon][FlexJS] Help with finishing the maven migration
Hi Chris,
I think I got same error a while ago. Maybe comments will help from my jira
[1]
[1] https://issues.apache.org/jira/browse/FLEX-34892
Piotr
-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Falcon-FlexJS-Help-with-finishing-the-maven-migration-tp53482p53488.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
AW: AW: [Falcon][FlexJS] Help with finishing the maven migration
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok so I had to add some more dependencies but now I'm getting an error that's not related to missing classes I guess:
TypeError: Error #1006: value is not a function.
at MyInitialView()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLObject()
at org.apache.flex.utils::MXMLDataInterpreter$/generateMXMLProperties()
at org.apache.flex.core::Application/generateMXMLAttributes()
at DataBindingExample()
Any Idea on this one?
Chris
________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Dienstag, 21. Juni 2016 12:44:18
An: dev@flex.apache.org
Betreff: AW: AW: [Falcon][FlexJS] Help with finishing the maven migration
Thanks for that tip ... indeed it was the airglobal that was in the library-path.
I moved that to the external library path and that error was replaced by another, but that's on I can handle ... I'll try to fix this and see how far I come [?]
Chris
________________________________
Von: piotrz <pi...@gmail.com>
Gesendet: Dienstag, 21. Juni 2016 12:00:01
An: dev@flex.apache.org
Betreff: Re: AW: [Falcon][FlexJS] Help with finishing the maven migration
Hi Chris,
I think I got same error a while ago. Maybe comments will help from my jira
[1]
[1] https://issues.apache.org/jira/browse/FLEX-34892
Piotr
-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Falcon-FlexJS-Help-with-finishing-the-maven-migration-tp53482p53488.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
AW: AW: [Falcon][FlexJS] Help with finishing the maven migration
Posted by Christofer Dutz <ch...@c-ware.de>.
Thanks for that tip ... indeed it was the airglobal that was in the library-path.
I moved that to the external library path and that error was replaced by another, but that's on I can handle ... I'll try to fix this and see how far I come [?]
Chris
________________________________
Von: piotrz <pi...@gmail.com>
Gesendet: Dienstag, 21. Juni 2016 12:00:01
An: dev@flex.apache.org
Betreff: Re: AW: [Falcon][FlexJS] Help with finishing the maven migration
Hi Chris,
I think I got same error a while ago. Maybe comments will help from my jira
[1]
[1] https://issues.apache.org/jira/browse/FLEX-34892
Piotr
-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Falcon-FlexJS-Help-with-finishing-the-maven-migration-tp53482p53488.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: AW: [Falcon][FlexJS] Help with finishing the maven migration
Posted by piotrz <pi...@gmail.com>.
Hi Chris,
I think I got same error a while ago. Maybe comments will help from my jira
[1]
[1] https://issues.apache.org/jira/browse/FLEX-34892
Piotr
-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Falcon-FlexJS-Help-with-finishing-the-maven-migration-tp53482p53488.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
AW: [Falcon][FlexJS] Help with finishing the maven migration
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok so I made sure the js-extern is added to the external library path of all modules, but it seems that I still am getting the same error message:
VerifyError: Error #1079: Native methods are not allowed in loaded code.
Would be grateful for some help to what's causing this.
Chris
________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Dienstag, 21. Juni 2016 11:19:32
An: dev@flex.apache.org
Betreff: AW: [Falcon][FlexJS] Help with finishing the maven migration
Hi Alex,
If you used the "settings-template.xml" it should have used the sdk converter automatically (You should see an ASCII Art Flex logo in the the build in that case).
I didn't add the dependency to the FlexSDK it was the Ant build that needed some of the libraries there. I think I remember some of the Falcon unit tests, requiring the Flex SWCs for building. (See ASFeatureTestBase)
I don't quite understand what you mean with "-mavenDir". I only wanted to put in the settings-template what is needed. When using this in a jenkins job, it was counterproductive to set the maven local repo home, so I stick to the defaults.
I added "strict-xml=true" to all externs and it seemed to have worked nicely ... thanks for that. Even if I thought I had already added that. Oh well ... if it works, it's good [?] So now all the Framework libs seem to be ok.
Will look into the Examples and the js dependency later on ...
Thanks ...
Chris
________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Dienstag, 21. Juni 2016 08:10:05
An: dev@flex.apache.org
Betreff: Re: [Falcon][FlexJS] Help with finishing the maven migration
On 6/20/16, 1:39 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi,
>
>
>I have finished migrating Falcon to Maven and all except the XML
>framework module of ASJS seem to be migrated too. I do need some help
>with getting the examples up and running and finding out why the js
>version of XML isn't working. I know that it worked a few days/1-2 weeks
>ago, but I have no idea why it's no longer working. A lot seems to have
>been changed with the configuration of the JS builds, so I would like to
>ask the people working on this to have a look.
The compiler build failed with:
[ERROR] Failed to execute goal on project compiler: Could not resolve
dependencies for project
org.apache.flex.flexjs.compiler:compiler:jar:0.7.0-SNAPSHOT: The following
artifacts could not be resolved:
com.adobe.flash.framework:playerglobal:swc:20.0,
org.apache.flex.framework:framework:swc:4.15.0,
org.apache.flex.framework:rpc:swc:4.15.0,
org.apache.flex.framework:spark:swc:4.15.0,
org.apache.flex.framework:framework:zip:configs:4.15.0: Failure to find
com.adobe.flash.framework:playerglobal:swc:20.0 in
https://repository.apache.org/content/repositories/releases was cached in
the local repository, resolution will not be reattempted until the update
interval of apache-release has elapsed or updates are forced -> [Help 1]
I finally figured out how to get around it by using flex-sdk-converter to
convert a 4.15.0 SDK, but it made me wonder:
1) Why does the compiler build need Flex SDK?
2) Why does the converter not assume the -mavenDir is the Maven Local Repo?
After that, the falcon build finished as expected as did the asjs build,
so congratulations there!
The XML compile that uses compile-extern-config.xml doesn't seem to be
using the -compiler.strict-xml=true option.
The DataBindingExample-SNAPSHOT.swf failed with an error about "native"
code. I noticed that in the XML compile-extern-config.xml that the js
extern is in the library path instead of external library path, which
might not cause a problem until you try to run a SWF.
HTH,
-Alex
AW: [Falcon][FlexJS] Help with finishing the maven migration
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Alex,
If you used the "settings-template.xml" it should have used the sdk converter automatically (You should see an ASCII Art Flex logo in the the build in that case).
I didn't add the dependency to the FlexSDK it was the Ant build that needed some of the libraries there. I think I remember some of the Falcon unit tests, requiring the Flex SWCs for building. (See ASFeatureTestBase)
I don't quite understand what you mean with "-mavenDir". I only wanted to put in the settings-template what is needed. When using this in a jenkins job, it was counterproductive to set the maven local repo home, so I stick to the defaults.
I added "strict-xml=true" to all externs and it seemed to have worked nicely ... thanks for that. Even if I thought I had already added that. Oh well ... if it works, it's good [😊] So now all the Framework libs seem to be ok.
Will look into the Examples and the js dependency later on ...
Thanks ...
Chris
________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Dienstag, 21. Juni 2016 08:10:05
An: dev@flex.apache.org
Betreff: Re: [Falcon][FlexJS] Help with finishing the maven migration
On 6/20/16, 1:39 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi,
>
>
>I have finished migrating Falcon to Maven and all except the XML
>framework module of ASJS seem to be migrated too. I do need some help
>with getting the examples up and running and finding out why the js
>version of XML isn't working. I know that it worked a few days/1-2 weeks
>ago, but I have no idea why it's no longer working. A lot seems to have
>been changed with the configuration of the JS builds, so I would like to
>ask the people working on this to have a look.
The compiler build failed with:
[ERROR] Failed to execute goal on project compiler: Could not resolve
dependencies for project
org.apache.flex.flexjs.compiler:compiler:jar:0.7.0-SNAPSHOT: The following
artifacts could not be resolved:
com.adobe.flash.framework:playerglobal:swc:20.0,
org.apache.flex.framework:framework:swc:4.15.0,
org.apache.flex.framework:rpc:swc:4.15.0,
org.apache.flex.framework:spark:swc:4.15.0,
org.apache.flex.framework:framework:zip:configs:4.15.0: Failure to find
com.adobe.flash.framework:playerglobal:swc:20.0 in
https://repository.apache.org/content/repositories/releases was cached in
the local repository, resolution will not be reattempted until the update
interval of apache-release has elapsed or updates are forced -> [Help 1]
I finally figured out how to get around it by using flex-sdk-converter to
convert a 4.15.0 SDK, but it made me wonder:
1) Why does the compiler build need Flex SDK?
2) Why does the converter not assume the -mavenDir is the Maven Local Repo?
After that, the falcon build finished as expected as did the asjs build,
so congratulations there!
The XML compile that uses compile-extern-config.xml doesn't seem to be
using the -compiler.strict-xml=true option.
The DataBindingExample-SNAPSHOT.swf failed with an error about "native"
code. I noticed that in the XML compile-extern-config.xml that the js
extern is in the library path instead of external library path, which
might not cause a problem until you try to run a SWF.
HTH,
-Alex
Re: [Falcon][FlexJS] Help with finishing the maven migration
Posted by Alex Harui <ah...@adobe.com>.
On 6/20/16, 1:39 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi,
>
>
>I have finished migrating Falcon to Maven and all except the XML
>framework module of ASJS seem to be migrated too. I do need some help
>with getting the examples up and running and finding out why the js
>version of XML isn't working. I know that it worked a few days/1-2 weeks
>ago, but I have no idea why it's no longer working. A lot seems to have
>been changed with the configuration of the JS builds, so I would like to
>ask the people working on this to have a look.
The compiler build failed with:
[ERROR] Failed to execute goal on project compiler: Could not resolve
dependencies for project
org.apache.flex.flexjs.compiler:compiler:jar:0.7.0-SNAPSHOT: The following
artifacts could not be resolved:
com.adobe.flash.framework:playerglobal:swc:20.0,
org.apache.flex.framework:framework:swc:4.15.0,
org.apache.flex.framework:rpc:swc:4.15.0,
org.apache.flex.framework:spark:swc:4.15.0,
org.apache.flex.framework:framework:zip:configs:4.15.0: Failure to find
com.adobe.flash.framework:playerglobal:swc:20.0 in
https://repository.apache.org/content/repositories/releases was cached in
the local repository, resolution will not be reattempted until the update
interval of apache-release has elapsed or updates are forced -> [Help 1]
I finally figured out how to get around it by using flex-sdk-converter to
convert a 4.15.0 SDK, but it made me wonder:
1) Why does the compiler build need Flex SDK?
2) Why does the converter not assume the -mavenDir is the Maven Local Repo?
After that, the falcon build finished as expected as did the asjs build,
so congratulations there!
The XML compile that uses compile-extern-config.xml doesn't seem to be
using the -compiler.strict-xml=true option.
The DataBindingExample-SNAPSHOT.swf failed with an error about "native"
code. I noticed that in the XML compile-extern-config.xml that the js
extern is in the library path instead of external library path, which
might not cause a problem until you try to run a SWF.
HTH,
-Alex
Re: [Falcon][FlexJS] Help with finishing the maven migration
Posted by Alex Harui <ah...@adobe.com>.
Ok will look into it.
Sent from my LG G3, an AT&T 4G LTE smartphone
------ Original message------
From: Christofer Dutz
Date: Mon, Jun 20, 2016 1:40 AM
To: 'dev@flex.apache.org';
Subject:[Falcon][FlexJS] Help with finishing the maven migration
Hi,
I have finished migrating Falcon to Maven and all except the XML framework module of ASJS seem to be migrated too. I do need some help with getting the examples up and running and finding out why the js version of XML isn't working. I know that it worked a few days/1-2 weeks ago, but I have no idea why it's no longer working. A lot seems to have been changed with the configuration of the JS builds, so I would like to ask the people working on this to have a look.
As you all have the Ant environment variables in place, you shouldn't need to do anything on that side, all you need to do is download Maven and make sure the bin directory is on the path.
Then the following commands should built the individual parts of FlexJS
In the falcon root directory:
mvn -s settings-template.xml -P utils clean install
mvn -s settings-template.xml -P compiler clean install
(Add "-DskipTests" to skip tests)
mvn -s settings-template.xml -P externs clean install
In the ASJS root directory:
mvn -s settings-template.xml clean install
If you want to see what the compiler is doing, the plugin generates the configs for all build steps in the "target" directory of each module. I am not adding any other commandline arguments besides the location of the configuration so you can be sure that the config.xml contains all important settings.
If you find something that's missing or wrong, I'll adjust the templates or add some more config options (I am planning on supporting all options, but till now I only implemented the ones that are actually needed for the build)
Chris