Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <DB5PR05MB12850AB3E43F922F66E1CAC5A26E0@DB5PR05MB1285.eurprd05.prod.outlook.com>
References: <D3356F42.67A2B%aharui@adobe.com>
	<8lt024ji49n3rm1i086f69n6.1460698967273@email.android.com>
	<DB5PR05MB1285B0BEB7205D9E5EB2EF27A26E0@DB5PR05MB1285.eurprd05.prod.outlook.com>
	<DB5PR05MB12850AB3E43F922F66E1CAC5A26E0@DB5PR05MB1285.eurprd05.prod.outlook.com>
Date: Thu, 21 Apr 2016 07:42:16 -0700
Message-ID: 
 <CADZSWG5+MUdqLnnyQnAi-OaXXnG93S1BodfKhJf0vnR7Uv2Z8w@mail.gmail.com>
Subject: Re: AW: AW: [FlexJS] Status on Maven migration
From: Josh Tynjala <joshtynjala@gmail.com>
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=001a11c15f527ed6e80530ffb7a3

--001a11c15f527ed6e80530ffb7a3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Things are commented out by externc when they are explicitly excluded.
Those look like some things I re-included in the config XML for js.swc
(which I assume you'd still use with Maven...) after fixing some bugs.

- Josh
On Apr 21, 2016 2:46 AM, "Christofer Dutz" <christofer.dutz@c-ware.de>
wrote:

> I'm currently having a problem with the JS extern.
> EXTERNC seems to be generating commented out methods and I have no idea
> why:
>
> Here the generated code for Generator.as where I get a compile error caus=
e
> next is commented out :-(
>
>
> package {
>
> /**
>  * @see
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_=
Objects/Generator
>  * @see [es6]
>  * @constructor implements Iterator  */
> public class Generator implements Iterator {
>
>     /**
>      * @see
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_=
Objects/Generator
>      * @see [es6]
>      */
>     public function Generator() {
>         super();
>     }
>
>     /**
>      * @param opt_value [?]
>      * @see [es6]
>      * @returns {{done: boolean, value: (VALUE|null)}}
>      */
> //    public function next(value:Object =3D null):Object {  return null; =
}
>
>     /**
>      * @param exception [?]
>      * @see [es6]
>      * @returns {{done: boolean, value: (VALUE|null)}}
>      */
> //    public function throw(exception:Object /* ? */):Object {  return
> null; }
>
>     /**
>      * @param value [(VALUE|null)]
>      * @see [es6]
>      * @returns {{done: boolean, value: (VALUE|null)}}
>      */
> //    public function return(value:Object):Object {  return null; }
>
> }
> }
>
>
> Chris
> ________________________________________
> Von: Christofer Dutz <christofer.dutz@c-ware.de>
> Gesendet: Donnerstag, 21. April 2016 10:38
> An: dev@flex.apache.org
> Betreff: AW: AW: [FlexJS] Status on Maven migration
>
> Ok ... so today I'm feeling like I'm wasting my time again :-(
>
> I merged the changes from develop up to my feature/maven-migration-test
> ... unfortunately I had do manually merge quite some stuff, but that's ok=
.
> Now my build no longer worked. The Externs no longer compiled. So I
> switched to my Ant version, updated and did a "clean-all" and "all" build
> ... this too didn't work, even if I got different errors. So as a measure
> of last resort, I did that "wipe-all" and then an "all" build. Now at lea=
st
> the Ant build worked again. Unfortunately I couldn't see what has changed
> :-(
>
> Could you guys please post to this list if you change any downloads or
> change things in the build? It's one thing to port something, but it's a
> completely different thing to find problems that now occur in a previousl=
y
> ported part :-(
>
> I think it would eventually be a good idea to do the maven switch pretty
> soon cause I'm loosing more and more of my time in keeping things in sync
> ... time I would prefer to be investing on pushing the migration of ASJS
> forward.
>
> Chris
>
> ________________________________________
> Von: Christofer Dutz <christofer.dutz@c-ware.de>
> Gesendet: Freitag, 15. April 2016 07:44
> An: dev@flex.apache.org
> Betreff: AW: AW: [FlexJS] Status on Maven migration
>
> In the cleanup script I simply removed all non Maven related stuff. What =
I
> could do, was to have my IntelliJ to generate an ant build from the Maven
> build. Eventually that would get rid of some of the problems if the old a=
nt
> build.
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> -------- Urspr=C3=BCngliche Nachricht --------
> Von: Alex Harui <aharui@adobe.com>
> Datum: 15.04.16 01:02 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: AW: [FlexJS] Status on Maven migration
>
>
>
> On 4/14/16, 9:30 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:
>
> >The structure is final, I'm just working on the details now. I also
> >noticed that hit seems to be able to sync updates even if the structure
> >is changed :-)
> >
> >But how about giving Maven a try? Eclipse does support that with the
> >m2eclipse plugin.
>
> I might try that once you get snapshots working in one build.
>
> I got the maven-migration-test branch.  There is no build.xml at the
> top-level.  Any reason I can't put one there?
>
> Thanks,
> -Alex
>

--001a11c15f527ed6e80530ffb7a3--