Hi Alex,
I have had this too several times. This usually is a timing problem of multiple build jobs on a windows system. In this case usually two builds are running in parallel. If the ASJS build uses a jar that is currently built by another Job and that Job replaces the jar in the Maven local repo, then some times you get this effect. I think I should check that the build jobs should not work in parallel or each use it's own maven local repo directory. Chris ________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Mittwoch, 7. September 2016 07:18:38 An: dev@flex.apache.org Betreff: FW: [MAVEN-BUILD] FlexJS Framework (maven) - Build # 238 - Failure Chris, how do we interpret this? It is building fine for me with Ant. All I did was add a new interface. -Alex On 9/6/16, 10:01 PM, "Apache Jenkins Server" <jenk...@builds.apache.org> wrote: >The Apache Jenkins build system has built FlexJS Framework (maven) (build >#238) > >Status: Failure > >Check console output at >https://builds.apache.org/job/FlexJS%20Framework%20(maven)/238/ to view >the results.
