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
> > D
endet: 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'
;
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> Ursprüngliche Nachricht
> Von: Alex Harui
> 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
Von: Alex Harui
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 AS3Co
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
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 n
