t could be useful to track down problems.
Chris
Von: Alex Harui
Gesendet: Mittwoch, 18. Mai 2016 18:32:10
An: dev@flex.apache.org
Betreff: Re: AW: AW: [DISCUSS] Handling of namespaces and xml
On 5/18/16, 1:58 AM, "Christofer Dutz" wrote:
>Hi
On 5/18/16, 1:58 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>I just had a look at the content of the catalog.xml and I agree actually
>the information should be available automatically without packing
>anything in the SWC.
>How much work would it be to make the compiler use this? I am currently
>
On 5/18/16, 8:06 AM, "Christofer Dutz" wrote:
>Hi,
>
>so I implemented this functionality. There is now a plugin goal that goes
>through the dependencies of the current module and creates
>manifest/namespace files for each uri it finds and automatically adds
>this to the compiler configuration.
my fingers crossed,
that my customers will keep postponing project starts so I will have another
few days to work on this full-time :-)
Chris
Von: Christofer Dutz
Gesendet: Mittwoch, 18. Mai 2016 10:58:50
An: dev@flex.apache.org
Betreff: AW: AW: [DISCUSS]
rates manifests on the fly by inspecting the classpath. But
I'll make it super-easy to remove.
Chris
Von: Alex Harui
Gesendet: Dienstag, 17. Mai 2016 20:23:16
An: dev@flex.apache.org
Betreff: Re: AW: [DISCUSS] Handling of namespaces and xml
On 5/17
On 5/17/16, 11:09 AM, "Christofer Dutz" wrote:
>The Manifest files seem to allow making a set of mxml tags be available
>using one prefix. The classes referenced by the "js" prefix fire example
>contain classes from different packages. You should have to import all
>packages individually. And you
Alex Harui
Datum: 17.05.16 18:17 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Handling of namespaces and xml
I don't know this part of the compiler at all. I think, though, there are
a couple of issues in here:
1) Making SWCs self-contained. Sounds good to me. Honestly, I
I don't know this part of the compiler at all. I think, though, there are
a couple of issues in here:
1) Making SWCs self-contained. Sounds good to me. Honestly, I don't know
why the compiler needs a separate -manifest.xml file. When I look at the
catalog.xml, I think I see everything we need
Hi,
I am currently working on compiling the examples in asjs with maven. The reason
for not having any [ASJS][FALCON] whatsoever, is that this could apply/affect
all types of Flex SKDs.
Currently we have the flex-config.xml in the frameworks directory. This defines
a lot of namespace element
