Currently working on setting up SonarQube analysis on ASF Infra ... 

This will make it easy to find potentially dangerous stuff. I doubt creating 
issues would be ideal, but people could start picking reported issues and work 
on them.

Chris


Am 15.12.16, 20:46 schrieb "Josh Tynjala" <joshtynj...@gmail.com>:

    I am currently working on updating Closure compiler in FalconJX.
    
    - Josh
    
    On Thu, Dec 15, 2016 at 9:54 AM, Alex Harui <aha...@adobe.com> wrote:
    
    > If one of you is planning to work on this issue, please assign the JIRA to
    > yourself.  Otherwise I will look into it.
    >
    > -Alex
    >
    > On 12/15/16, 3:33 AM, "Josh Tynjala" <joshtynj...@gmail.com> wrote:
    >
    > >Indeed, Chris, those aren't a waste of time, and no one would disagree
    > >with
    > >that. When the compiler errors with a stack trace, that's a serious bug
    > >and
    > >should be reported on JIRA.
    > >
    > >- Josh
    > >
    > >
    > >On Dec 15, 2016 3:09 AM, "Christofer Dutz" <christofer.d...@c-ware.de>
    > >wrote:
    > >
    > >Hi Carlos,
    > >
    > >unfortunately this type of problem often originates from some of the
    > >problems in Falcon. Falcon hadles the case in which code and 
configuration
    > >is correct nicely. I reported the presence of a lot of problems in Falcon
    > >when compiling not correct code as a large number of execution paths in
    > >the
    > >compiler for example are guaranteed to produce NullPointerExceptions if
    > >not
    > >compiling correct code. Tracking down these errors is quite frustrating 
as
    > >due to the NPE the context gets lost (I had to do that quite a lot in
    > >order
    > >to get the initial Maven version of the build running).
    > >
    > >I still think working on these issues is not a waste of time.
    > >
    > >Chris
    > >
    > >
    > >Am 14.12.16, 19:42 schrieb "carlos.rov...@gmail.com im Auftrag von Carlos
    > >Rovira" <carlos.rov...@gmail.com im Auftrag von
    > >carlos.rov...@codeoscopic.com>:
    > >
    > >    Just created one:
    > >
    > >    FLEX-35218 - FlexJS Errors unable to debug
    > >    <https://issues.apache.org/jira/browse/FLEX-35218>
    > >
    > >    2016-12-14 2:38 GMT+01:00 Alex Harui <aha...@adobe.com>:
    > >
    > >    > File a bug with a test case.
    > >    >
    > >    > On 12/13/16, 5:23 PM, "carlos.rov...@gmail.com on behalf of Carlos
    > >Rovira"
    > >    > <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org>
    > >wrote:
    > >    >
    > >    > >> >
    > >    > >> >Could not find file for class:
    > >    > >> >org.apache.flex.html.beads.models.ToggleButtonModel
    > >    > >> >File not found: org.apache.flex.html.beads.mod
    > >els.ToggleButtonModel
    > >    > >>
    > >    > >> This file in not in one of the SWCs in the project, but some 
code
    > >needs
    > >    > >>it.
    > >    > >
    > >    > >
    > >    > >
    > >    > >But that's not the problem Alex. The change I introduced from one
    > >    > >successful compilation to one failing is this line in the new
    > >TextNode.as
    > >    > >
    > >    > >var e:HTMLElement = textNode.parentNode;
    > >    > >e.innerHTML = text;
    > >    > >
    > >    > >If I introuduced that and compiler reports that something wrong
    > >goes
    > >with
    > >    > >ToggleButtonModel is clear that something wrong is going in some
    > >internals
    > >    > >in falcon...
    > >    >
    > >    >
    > >
    > >
    > >    --
    > >
    > >    Carlos Rovira
    > >    Director General
    > >    M: +34 607 22 60 05
    > >    http://www.codeoscopic.com
    > >    http://www.avant2.es
    > >
    > >    Este mensaje se dirige exclusivamente a su destinatario y puede
    > >contener
    > >    información privilegiada o confidencial. Si ha recibido este mensaje
    > >por
    > >    error, le rogamos que nos lo comunique inmediatamente por esta misma
    > >vía y
    > >    proceda a su destrucción.
    > >
    > >    De la vigente Ley Orgánica de Protección de Datos (15/1999), le
    > >comunicamos
    > >    que sus datos forman parte de un fichero cuyo responsable es
    > >CODEOSCOPIC
    > >    S.A. La finalidad de dicho tratamiento es facilitar la prestación del
    > >    servicio o información solicitados, teniendo usted derecho de acceso,
    > >    rectificación, cancelación y oposición de sus datos dirigiéndose a
    > >nuestras
    > >    oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
    > >documentación
    > >    necesaria.
    >
    >
    

Reply via email to