That approach makes sense. We could put it in a “legacy” folder and bring in 
pieces as they seem needed or folks have time to sanitize the code — possibly 
with a different package structure.

On Jul 6, 2016, at 3:44 PM, Christofer Dutz <christofer.d...@c-ware.de> wrote:

> Hi Harbs,
> 
> 
> I remember a lot of these projects being built by flexmojos. While this is 
> definitely a valid approach, I disliked it because of Flexmojos GPL license. 
> But as I saw how easy it was to build Flexunit with the new Maven plugin I 
> built for FlexJS, it might be a good idea to bring this in and build it with 
> that. This would also add a lot of test-cases that I could use to have the 
> plugin mature and grow its feature set.
> 
> 
> But I wouldn't vote for creating a parity release. Logging for example was 
> used by almost every other AS3Commons module, but that had dependencies to an 
> insane amount of logging frameworks. Most of them died and non of them with 
> releases in Maven-Central or anywhere I could find them.
> 
> 
> I would vote for adopting AS3Commons, stripping it down to the bare 
> necessities and adding stuff as soon as it it required or asked by our users. 
> In that case I would vote +1 ... if we should continue to maintain a huge 
> pile of legacy functionality, I would vote -1.
> 
> 
> Chris
> 
> ________________________________
> Von: Harbs <harbs.li...@gmail.com>
> Gesendet: Mittwoch, 6. Juli 2016 14:24:29
> An: dev@flex.apache.org
> Betreff: Re: [DISCUSS] Adopting AS3Commons
> 
> I’d like to resurrect this discussion. It kind of fizzled out without a 
> resolution.
> 
> What’s bringing this back up, is I need to implement compression and 
> decompression of BinaryData. I believe that FZip has the code necessary for 
> that. (I may be wrong about that, though.)
> 
> On Feb 11, 2016, at 1:08 PM, Christophe Herreman 
> <christophe.herre...@gmail.com> wrote:
> 
>> What I meant was that the logging integrations, not the logging library
>> itself, can be ignored IMO. Except for the Flex logger then.
>> 
>> - Christophe
>> 
>> 2016-02-11 11:29 GMT+01:00 Christofer Dutz <christofer.d...@c-ware.de>:
>> 
>>> Yeah ... would have liked to, but as you use your own dogfood, the loggin
>>> is used in the other modules, so actually it's quite essential to get the
>>> logging runing before we can even think to get the rest running.
>>> 
>>> Chris
>>> 
>>> ________________________________________
>>> Von: Christophe Herreman <christophe.herre...@gmail.com>
>>> Gesendet: Donnerstag, 11. Februar 2016 11:09
>>> An: dev@flex.apache.org
>>> Betreff: Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons
>>> 
>>> I wouldn't care too much about all the logging framework integrations. We
>>> have no data about usage but I suspect they are not used that much, if at
>>> all. I assume you'll get feedback from users when an integration is missing
>>> in which case it can still be added.
>>> 
>>> - Christophe
>>> 
>>> 2016-02-11 7:58 GMT+01:00 Christofer Dutz <christofer.d...@c-ware.de>:
>>> 
>>>> But if we don't have the libs, a can't compile the optional code. We
>>>> wouldn't require users to have them, but in order to build the lib, we
>>>> would need them ... That's the problem.
>>>> 
>>>> Chris
>>>> 
>>>> 
>>>> 
>>>> Von meinem Samsung Galaxy Smartphone gesendet.
>>>> 
>>>> 
>>>> -------- Ursprüngliche Nachricht --------
>>>> Von: Alex Harui <aha...@adobe.com>
>>>> Datum: 10.02.2016 19:05 (GMT+01:00)
>>>> An: dev@flex.apache.org
>>>> Betreff: Re: AW: Re: AW: [DISCUSS] Adopting AS3Commons
>>>> 
>>>> I haven't looked at the code in detail, but if it is possible to have all
>>>> the logging libraries as external dependencies, it should be ok to accept
>>>> the AS3Commons Logging project, if at least a few of them have compatible
>>>> licenses.
>>>> 
>>>> Let's see where the revival of this discussion takes us.  Maybe we'll
>>>> start a vote next week.
>>>> 
>>>> -Alex
>>>> 
>>>> On 2/10/16, 3:54 AM, "Christofer Dutz" <christofer.d...@c-ware.de>
>>> wrote:
>>>> 
>>>>> Hi Christophe,
>>>>> 
>>>>> I already had a detailed look at as3commons and what I found out is that
>>>>> quite some of the dependencies (especially in the logging part) come
>>> from
>>>>> projects that seem to have been given up. At least I couldn't find a
>>>>> single source for those libraries. I also bet that we wouldn't need to
>>>>> keep support for all of them. I think the logging module was one that I
>>>>> was having most trouble with.
>>>>> 
>>>>> If we were to continue as3commons, I think we should strip out code like
>>>>> that. I wouldn't throw it away, but sort of save it somewhere until
>>>>> someone asks for it and reactivate the code by providing optional
>>> modules
>>>>> for each of these frameworks.
>>>>> 
>>>>> I would be glad to help with this after all I was happy to see that most
>>>>> is built with Flexmojos and I only gave up on non-maven stuff ;-)
>>>>> 
>>>>> Chris
>>>>> 
>>>>> ________________________________________
>>>>> Von: Christophe Herreman <christophe.herre...@gmail.com>
>>>>> Gesendet: Mittwoch, 10. Februar 2016 10:56
>>>>> An: dev@flex.apache.org
>>>>> Betreff: Re: Re: AW: [DISCUSS] Adopting AS3Commons
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> sorry to jump in late here. I'm the original founder and one of the main
>>>>> authors of AS3Commons and wanted to give some feedback on the things I
>>>>> read
>>>>> here:
>>>>> 
>>>>> - renaming: I don't have an issue with this but not sure what the gain
>>> is
>>>>> here, apart from a more consistent and integrated feel with the SDK
>>> (which
>>>>> could be the most important argument). Keep in mind that most of the
>>>>> libraries are not Flex libraries, but rather ActionScript 3 libraries,
>>>>> hence the name of the project. Flex related code is in separate libs
>>>>> (Async
>>>>> and Async-Flex) for instance.
>>>>> 
>>>>> - FZip was indeed donated by Claus Wahlers to AS3Commons.
>>>>> 
>>>>> - The Logging library has support for many other logging libraries and
>>>>> targets, hence the many (optional) dependencies.
>>>>> 
>>>>> - AS3Commons grew out of Spring ActionScript (SAS). This means that SAS
>>>>> has
>>>>> a lot of dependencies on AS3Commons. Perhaps that is something to take
>>>>> into
>>>>> account if you are thinking about renaming or refactoring the packages.
>>>>> 
>>>>> - the domain name as3commons.org (and springactionscript.org) is about
>>> to
>>>>> expire and I'll extend it. There is currently nothing behind these
>>>>> domains.
>>>>> I don't have the time to put up nor maintain a site here. Any
>>> suggestions
>>>>> what we could do here?
>>>>> 
>>>>> regards,
>>>>> Christophe
>>>>> 
>>>>> 2015-12-09 13:40 GMT+01:00 Dev LFM <developer...@gmail.com>:
>>>>> 
>>>>>> Personally I've never used as3commons, but its ok for me..
>>>>>> 
>>>>>> I would also like to see all the experimental stuff that Ted Patrick
>>>>>> donated that is already in the sdk but not official..
>>>>>> 
>>>>>> 2015-12-08 10:58 GMT+00:00 Kessler CTR Mark J
>>>>>> <mark.kessler....@usmc.mil>:
>>>>>> 
>>>>>>> We are talking about adopting the source.  It makes sense to bring
>>>>>> over
>>>>>>> ActionScript utilities that people still actively use.  Even when
>>> they
>>>>>> stop
>>>>>>> being supported in their current site.  It helps keep the echo
>>> system
>>>>>> a
>>>>>>> little stronger.
>>>>>>> 
>>>>>>> 
>>>>>>> -Mark
>>>>>>> 
>>>>>>> -----Original Message-----
>>>>>>> From: lizhi [mailto:s...@qq.com]
>>>>>>> Sent: Tuesday, December 08, 2015 2:15 AM
>>>>>>> To: dev@flex.apache.org
>>>>>>> Subject: Re: AW: [DISCUSS] Adopting AS3Commons
>>>>>>> 
>>>>>>> i thinks it is just a lib.it in the github is good.why put it to
>>>> flex?
>>>>>>> the flex should clear.
>>>>>>> if the flex can not use the lib from github,should fixed,it is a
>>> bug.
>>>>>>> why put some lib in flex?
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>> http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Adopting-AS3
>>>>>> Commons-tp50473p50546.html
>>>>>>> Sent from the Apache Flex Development mailing list archive at
>>>>>> Nabble.com.
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Christophe Herreman
>>>>> http://www.herrodius.com
>>>>> http://www.springactionscript.org
>>>>> http://www.as3commons.org
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Christophe Herreman
>>> http://www.herrodius.com
>>> http://www.springactionscript.org
>>> http://www.as3commons.org
>>> 
>> 
>> 
>> 
>> --
>> Christophe Herreman
>> http://www.herrodius.com
>> http://www.springactionscript.org
>> http://www.as3commons.org
> 

Reply via email to