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/21 12:47:09 UTC

[Falcon][FlexJS] Thoughts about JS / SWC / JS+SWC libs

Hi,


I am currently thinking how I can simplify the handling of the JS and SWC dependencies. Now I thought that there are some libs that only have a SWC part, some only have a JS part and some have both.


Now what about me creating 3 different packaging types for maven:


js, swc and jswc


This would atomatically kick in the needed plugins at the right time. Currently I solve the only js or only swc library problem by manually forcing some parts to be skipped ... this is really ugly.


Being able to select a packaging type of "js" or "swc" for only-one-type libs and "jswc" for libs containing both would simplify things.


When referencing these types of libraries you would only use the old "swc" only for the pure-swc libs and start using the "js" and "jswc" for the other types. This way it should be transparent to the user what type of library he's referencing.


What do you think?


Chris

Re: [Falcon][FlexJS] Thoughts about JS / SWC / JS+SWC libs

Posted by Alex Harui <ah...@adobe.com>.
On 6/21/16, 5:47 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Hi,
>Being able to select a packaging type of "js" or "swc" for only-one-type
>libs and "jswc" for libs containing both would simplify things.
>
>
>When referencing these types of libraries you would only use the old
>"swc" only for the pure-swc libs and start using the "js" and "jswc" for
>the other types. This way it should be transparent to the user what type
>of library he's referencing.
>
>
>What do you think?

Seems reasonable to me.  Would this affect the Ant build?

-Alex