Hi,
> I would prefer to not have Apache Flex releases use code with licenses
> that have “bad” words in it, which appears to be the case for the
> https://code.google.com/p/reflections/ library. I would not like the
> Installer to have to offer up those bad words for approval by the
> customer.
On 11/11/14, 3:44 PM, "Justin Mclean" wrote:
>Hi,
>
>The "do what the f*ck you want" license has been discussed before as has
>this exact library on legal. It's is unresolved if you can use it. [1]
>
>The main concern "With a wildly permissive license like WTFPL, provenance
>might possibly get
Hi,
The "do what the f*ck you want" license has been discussed before as has this
exact library on legal. It's is unresolved if you can use it. [1]
The main concern "With a wildly permissive license like WTFPL, provenance might
possibly get overlooked." but it's also probably considered public
s it doesn't support it.
>
> Chris
>
>
> Von: Alex Harui
> Gesendet: Montag, 10. November 2014 21:30
> An: dev@flex.apache.org
> Betreff: Re: [FLEX-JS] Streamlining the packaging
>
> On 11/10/14, 12:23 AM, "Christofer Dutz"
>
On 11/10/14, 12:34 PM, "OmPrakash Muppirala" wrote:
>>
>> >I think these changes would need to be done anyway if tool vendors like
>> >Jetbrains would start adding support for FlexJS natively as they would
>> >have to deal with the same problems.
>>
>> I’ve been told Jetbrains already has imple
>
> >I think these changes would need to be done anyway if tool vendors like
> >Jetbrains would start adding support for FlexJS natively as they would
> >have to deal with the same problems.
>
> I’ve been told Jetbrains already has implemented FlexJS support, although
> nobody has a complete answer
On 11/10/14, 12:23 AM, "Christofer Dutz" wrote:
>Would it be possible to package the JS parts in the same units as SWFs?
>
>I was thinking of one of these scenarios:
>
>- For each FlexJS swc, a matching directory for JS exists
>
>- For each FlexJS swc a zip containing the JS part exists
>
>- A F
>From WebJars and Jangaroo, I have some experience with Maven artifact
packaging of Web resources, and I'd recommend to follow Christofer's advice
and bundle everything into a single artifact.
Maven *does* allow a module to produce multiple artifacts (using different
"classifiers"), but this is rat
