Would it be possible to eliminate some of the warnings while generating the
externs?
I am getting tons of:
WARNUNG: [es6]:1083: WARNING - Keywords and reserved words are not allowed as
unquoted property names in older versions of JavaScript. If you are targeting
newer versions of JavaScript, set the appropriate language_in option.
So I started ignoring the red text printed out in my console ... now I noticed
that some CRITICAL have mixed themselves between all of these warnings. If we
could set that "language_in" option, it would make things easier and I could
make the generator fail if there is output on the error stream.
Chris
________________________________________
Von: Christofer Dutz <christofer.d...@c-ware.de>
Gesendet: Donnerstag, 21. April 2016 11:46
An: dev@flex.apache.org
Betreff: AW: AW: [FlexJS] Status on Maven migration
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 cause 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 = 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.d...@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 least 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 previously 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.d...@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 ant
build.
Chris
Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------
Von: Alex Harui <aha...@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.d...@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
