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 2014/10/12 19:24:41 UTC
Some Falcon problems with multiple source-paths.
Hi,
As I posted two days ago, I have succeeded in getting Flexmojos to work with Falcon. Now while I'm still trying to get the Flexmojos Testsuite running again, I started some first tests with Flexmojos and Falcon where I simply let Falcon compile some of my applications that build fine with the old compiler and I just ran into a problem which I could need some input.
In Maven you can have several sources (main-sources, main-resources, test-sources, test-resources for example). Now I have a project in which I have the Flex sourcecode in "src/main/flex" and the resources in "src/main/resources" - which is the default Maven pattern for separating sources and resources. Now when embedding an image, I am getting the following errors:
Error: Could not find Embed source '/assets/images/checkboxmiddle.png'. Searched 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\flex\com\flexicious\controls\assets\images\checkboxmiddle.png', 'assets/images/checkboxmiddle.png' on the source path
Which is true, as the resources are not located in the source path but in the resource path. 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\checkboxmiddle.png' would have worked.
Having a look at the code to me it seems af if Falcon wouldn't support multiple source roots ... is that correct?
Chris
AW: Some Falcon problems with multiple source-paths.
Posted by Christofer Dutz <ch...@c-ware.de>.
Well I ran Flexmojos twice against the same project. Once with falcon and once with the old compiler. Even with the old compiler there was only one source-path, but each ressource was added using "include-file" declaration and it seemed that the old compiler was able to resolve resources from the include-file declarations, and falcon doesn't.
The two paths are the "source-path" entry itself and the relative path directly used in the Embed statement.
Chris
________________________________________
Von: Darrell Loverin <da...@gmail.com>
Gesendet: Montag, 13. Oktober 2014 01:47
An: dev@flex.apache.org
Betreff: Re: Some Falcon problems with multiple source-paths.
The compiler should support multiple source paths. Each "-source-path"
option defines another source path. The compiler error messages seems to
say it searched two source paths for the asset. I think you want to add
your resource path to the source path.
-Darrell
On Sun, Oct 12, 2014 at 1:24 PM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi,
>
> As I posted two days ago, I have succeeded in getting Flexmojos to work
> with Falcon. Now while I'm still trying to get the Flexmojos Testsuite
> running again, I started some first tests with Flexmojos and Falcon where I
> simply let Falcon compile some of my applications that build fine with the
> old compiler and I just ran into a problem which I could need some input.
>
> In Maven you can have several sources (main-sources, main-resources,
> test-sources, test-resources for example). Now I have a project in which I
> have the Flex sourcecode in "src/main/flex" and the resources in
> "src/main/resources" - which is the default Maven pattern for separating
> sources and resources. Now when embedding an image, I am getting the
> following errors:
>
> Error: Could not find Embed source '/assets/images/checkboxmiddle.png'.
> Searched
> 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\flex\com\flexicious\controls\assets\images\checkboxmiddle.png',
> 'assets/images/checkboxmiddle.png' on the source path
>
> Which is true, as the resources are not located in the source path but in
> the resource path.
> 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\checkboxmiddle.png'
> would have worked.
>
> Having a look at the code to me it seems af if Falcon wouldn't support
> multiple source roots ... is that correct?
>
> Chris
>
>
Re: Some Falcon problems with multiple source-paths.
Posted by Darrell Loverin <da...@gmail.com>.
The compiler should support multiple source paths. Each "-source-path"
option defines another source path. The compiler error messages seems to
say it searched two source paths for the asset. I think you want to add
your resource path to the source path.
-Darrell
On Sun, Oct 12, 2014 at 1:24 PM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi,
>
> As I posted two days ago, I have succeeded in getting Flexmojos to work
> with Falcon. Now while I'm still trying to get the Flexmojos Testsuite
> running again, I started some first tests with Flexmojos and Falcon where I
> simply let Falcon compile some of my applications that build fine with the
> old compiler and I just ran into a problem which I could need some input.
>
> In Maven you can have several sources (main-sources, main-resources,
> test-sources, test-resources for example). Now I have a project in which I
> have the Flex sourcecode in "src/main/flex" and the resources in
> "src/main/resources" - which is the default Maven pattern for separating
> sources and resources. Now when embedding an image, I am getting the
> following errors:
>
> Error: Could not find Embed source '/assets/images/checkboxmiddle.png'.
> Searched
> 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\flex\com\flexicious\controls\assets\images\checkboxmiddle.png',
> 'assets/images/checkboxmiddle.png' on the source path
>
> Which is true, as the resources are not located in the source path but in
> the resource path.
> 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\checkboxmiddle.png'
> would have worked.
>
> Having a look at the code to me it seems af if Falcon wouldn't support
> multiple source roots ... is that correct?
>
> Chris
>
>
AW: Some Falcon problems with multiple source-paths.
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Justin,
don't know where you got that Idea that Flexmojos was an Apache License. It has never been.
The current license is what's preventing me from making this plugin truely Apache. Velo never
let people sign any ICLAs when contributing. In order to make this plugin an Apache Licensed plugin
I would have to track down every single contributor and ask them for permission :-(
I guess it's easier to start from scratch and be inspired by Flexmojos.
Chris
-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com]
Gesendet: Sonntag, 12. Oktober 2014 22:07
An: dev@flex.apache.org
Betreff: Re: Some Falcon problems with multiple source-paths.
Hi,
> [INFO] Flexmojos 7.1.0-SNAPSHOT
> [INFO] GPL License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
As an aside I thought Flexmojos was under an Apache license. [1]
Justin
1. https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/License
AW: Some Falcon problems with multiple source-paths.
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... if I follow your link I can see that too ... that's strange. All I ever see is the sourcecode and that's GPL ... strange.
Chris
-----Ursprüngliche Nachricht-----
Von: Justin Mclean [mailto:justin@classsoftware.com]
Gesendet: Sonntag, 12. Oktober 2014 22:07
An: dev@flex.apache.org
Betreff: Re: Some Falcon problems with multiple source-paths.
Hi,
> [INFO] Flexmojos 7.1.0-SNAPSHOT
> [INFO] GPL License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
As an aside I thought Flexmojos was under an Apache license. [1]
Justin
1. https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/License
Re: Some Falcon problems with multiple source-paths.
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> [INFO] Flexmojos 7.1.0-SNAPSHOT
> [INFO] GPL License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
As an aside I thought Flexmojos was under an Apache license. [1]
Justin
1. https://flexmojos.atlassian.net/wiki/display/FLEXMOJOS/License
AW: Some Falcon problems with multiple source-paths.
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi,
well I did a little bit of investigation. It seems the default compiler also had only one source directory.
But I noticed that Flexmojos passed in the static resources as "include-file" argument. Could it be possible that Falcon doesn't look in this list when encoding resuources? Here is flexmojos output for the commandline:
[INFO] Flexmojos 7.1.0-SNAPSHOT
[INFO] GPL License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
[DEBUG] Compilation arguments:
-link-report=C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\target\classic-data-grid-3.2-link-report.xml
-size-report=C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\target\classic-data-grid-3.2-size-report.xml
-swf-version=14
-dump-config=C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\target\classic-data-grid-3.2-configs.xml
-output=C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\target\classic-data-grid-3.2.swc
-load-config=
-include-sources=C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\flex
-include-file assets/CheckBox.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\CheckBox.png
-include-file assets/images/checkboxmiddle.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\checkboxmiddle.png
-include-file assets/images/DownArrow.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\DownArrow.png
-include-file assets/images/paging_first.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\paging_first.png
-include-file assets/images/paging_last.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\paging_last.png
-include-file assets/images/paging_next.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\paging_next.png
-include-file assets/images/paging_previous.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\paging_previous.png
-include-file assets/images/search.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\search.png
-include-file assets/images/UpArrow.png C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\UpArrow.png
-include-file defaults.css C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\defaults.css
-include-file defaults3.css C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\defaults3.css
-tools-locale=en_US
-compiler.debug=true
-compiler.locale=
-compiler.include-libraries=C:\Maven-Repository\com\flexicious\flexicious-licensing\3.1\flexicious-licensing-3.1.swc
-compiler.library-path=
-compiler.external-library-path=C:\Maven-Repository\org\apache\flex\framework\advancedgrids\4.13.0.20140701\advancedgrids-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\apache\4.13.0.20140701\apache-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\authoringsupport\4.13.0.20140701\authoringsupport-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\charts\4.13.0.20140701\charts-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\core\4.13.0.20140701\core-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\experimental\4.13.0.20140701\experimental-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\flash-integration\4.13.0.20140701\flash-integration-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\framework\4.13.0.20140701\framework-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\osmf\4.13.0.20140701\osmf-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\rpc\4.13.0.20140701\rpc-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\spark\4.13.0.20140701\spark-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\sparkskins\4.13.0.20140701\sparkskins-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\spark_dmv\4.13.0.20140701\spark_dmv-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\textLayout\4.13.0.20140701\textLayout-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\org\apache\flex\framework\mx\4.13.0.20140701\mx-4.13.0.20140701.swc
-compiler.external-library-path+=C:\Maven-Repository\com\adobe\flash\framework\playerglobal\11.1\playerglobal.swc
-compiler.theme=C:\Maven-Repository\org\apache\flex\framework\themes\spark\4.13.0.20140701\spark-4.13.0.20140701.swc
-compiler.source-path=C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\flex
-compiler.fonts.local-fonts-snapshot=C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\target\classes\fonts.ser
-compiler.headless-server=false
-compiler.namespaces.namespace=http://ns.adobe.com/mxml/2009,C:\Maven-Repository\org\apache\flex\framework\framework\4.13.0.20140701\configs_zip\mxml-2009-manifest.xml
-compiler.namespaces.namespace=library://ns.adobe.com/flex/spark,C:\Maven-Repository\org\apache\flex\framework\framework\4.13.0.20140701\configs_zip\spark-manifest.xml
-compiler.namespaces.namespace=library://ns.adobe.com/flex/mx,C:\Maven-Repository\org\apache\flex\framework\framework\4.13.0.20140701\configs_zip\mx-manifest.xml
-compiler.namespaces.namespace=http://www.adobe.com/2006/mxml,C:\Maven-Repository\org\apache\flex\framework\framework\4.13.0.20140701\configs_zip\mxml-manifest.xml
-compiler.namespaces.namespace=http://flex.apache.org/ns,C:\Maven-Repository\org\apache\flex\framework\framework\4.13.0.20140701\configs_zip\apache-manifest.xml
-compiler.namespaces.namespace=http://flex.apache.org/experimental/ns,C:\Maven-Repository\org\apache\flex\framework\framework\4.13.0.20140701\configs_zip\experimental-manifest.xml
-target-player=11.1
-metadata.date=12.10.14 21:50
-metadata.title=classic-data-grid
Perhaps it would be good for me to create a duplicate testsuite in Flexmojos that uses Falcon to test all the features the old compiler had and to make sure the new one supports all the features our users could be depending on. But I have to get the tests working first, which doesn't seem to simple (The internal changes in Maven from 3.0 to 3.1 were pretty severe)
Chris
-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Gesendet: Sonntag, 12. Oktober 2014 19:25
An: 'dev@flex.apache.org'
Betreff: Some Falcon problems with multiple source-paths.
Hi,
As I posted two days ago, I have succeeded in getting Flexmojos to work with Falcon. Now while I'm still trying to get the Flexmojos Testsuite running again, I started some first tests with Flexmojos and Falcon where I simply let Falcon compile some of my applications that build fine with the old compiler and I just ran into a problem which I could need some input.
In Maven you can have several sources (main-sources, main-resources, test-sources, test-resources for example). Now I have a project in which I have the Flex sourcecode in "src/main/flex" and the resources in "src/main/resources" - which is the default Maven pattern for separating sources and resources. Now when embedding an image, I am getting the following errors:
Error: Could not find Embed source '/assets/images/checkboxmiddle.png'. Searched 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\flex\com\flexicious\controls\assets\images\checkboxmiddle.png', 'assets/images/checkboxmiddle.png' on the source path
Which is true, as the resources are not located in the source path but in the resource path. 'C:\Projects\3rdParty\Flexicious\flexicious-components\classic-data-grid\src\main\resources\assets\images\checkboxmiddle.png' would have worked.
Having a look at the code to me it seems af if Falcon wouldn't support multiple source roots ... is that correct?
Chris