Re: AW: AW: AW: AW: AW: Jenkins still red

2016-10-05 Thread Alex Harui
On 10/5/16, 8:20 AM, "Alex Harui" wrote: > > >On 10/5/16, 2:30 AM, "Christofer Dutz" wrote: > >>But it doesn't explain why the Maven build builds a lot faster than the >>Ant build. So it can't be a problem that I unpack the entire closure lib >>... we should compare it to the NPM thingy (Don't

Re: AW: AW: AW: AW: AW: Jenkins still red

2016-10-05 Thread Alex Harui
On 10/5/16, 2:30 AM, "Christofer Dutz" wrote: >But it doesn't explain why the Maven build builds a lot faster than the >Ant build. So it can't be a problem that I unpack the entire closure lib >... we should compare it to the NPM thingy (Don't really know what that's >doing). > > >I'll have a l

AW: AW: AW: AW: AW: Jenkins still red

2016-10-05 Thread Christofer Dutz
tz Cc: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: Jenkins still red Hi Chris, I see the arquetype generated pom only refers to one execution. This is an excerpt form my pom.xml (not notified by me): compile-javascript

Re: AW: AW: AW: AW: Jenkins still red

2016-10-05 Thread Carlos Rovira
> *Von:* carlos.rov...@gmail.com im Auftrag von > Carlos Rovira > *Gesendet:* Mittwoch, 5. Oktober 2016 08:39:00 > *An:* dev@flex.apache.org > *Cc:* Christofer Dutz > *Betreff:* Re: AW: AW: AW: AW: Jenkins still red > > That sounds to be the problem

AW: AW: AW: AW: AW: Jenkins still red

2016-10-05 Thread Christofer Dutz
I configured the compilation for the examples to build both the swf and the js version. Chris Von: carlos.rov...@gmail.com im Auftrag von Carlos Rovira Gesendet: Mittwoch, 5. Oktober 2016 08:39:00 An: dev@flex.apache.org Cc: Christofer Dutz Betreff: Re: AW:

AW: AW: AW: AW: AW: Jenkins still red

2016-10-05 Thread Christofer Dutz
dev@flex.apache.org Cc: Christofer Dutz Betreff: Re: AW: AW: AW: AW: Jenkins still red That sounds to be the problem ( as well making 2 builds js+swf at a time) 2016-10-05 1:23 GMT+02:00 Alex Harui mailto:aha...@adobe.com>>: On 10/4/16, 2:04 PM, "carlos.rov...@gmail.com<mailto:car

Re: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Carlos Rovira
That sounds to be the problem ( as well making 2 builds js+swf at a time) 2016-10-05 1:23 GMT+02:00 Alex Harui : > > > On 10/4/16, 2:04 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" > > wrote: > > >Right now, I have maven build as well VSCode/NextGenAS IDE build. Maven is > >more slow

Re: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Alex Harui
On 10/4/16, 2:04 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Right now, I have maven build as well VSCode/NextGenAS IDE build. Maven is >more slow that Josh's (40 sec vs 5 sec for a hello world), I suppose this >is due to lots of checks maven do. Maybe do you have some conf

Re: AW: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Alex Harui
On 10/4/16, 1:45 PM, "Christofer Dutz" wrote: > > >Thanks for fixing it. I hope it helped get a little insight on how maven >works and that it helps getting comfortable with it. Yes, it helped me learn a bit more about Maven. > > >One thing though ... if the output is set to a file it adds th

AW: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Christofer Dutz
ed up things even more, we should do that. Von meinem Samsung Galaxy Smartphone gesendet. Ursprüngliche Nachricht Von: Carlos Rovira Datum: 04.10.16 23:47 (GMT+01:00) An: Christofer Dutz Betreff: Re: AW: AW: AW: AW: Jenkins still red I could say that the almost most of the ti

Re: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Carlos Rovira
ov...@gmail.com im Auftrag von > Carlos Rovira > *Gesendet:* Dienstag, 4. Oktober 2016 22:26:44 > *An:* dev@flex.apache.org > *Betreff:* Re: AW: AW: AW: AW: Jenkins still red > > Amazing!, it works Alex. Thanks! > > I finaly could build my flexjs test project generated with the a

AW: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Christofer Dutz
enstag, 4. Oktober 2016 22:26:44 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: Jenkins still red Amazing!, it works Alex. Thanks! I finaly could build my flexjs test project generated with the archetype and run it :) So for me this is a huge milestone for flexjs :D 2016-10-04 20:11 GM

Re: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Carlos Rovira
gt; >clean install") or do a "mvn clean install" of the complete compiler > >project. > > > >Chris > > > > > >Von meinem Samsung Galaxy Smartphone gesendet. > > > > > > Ursprüngliche Nachricht ---- > >Von: Al

Re: AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Alex Harui
m: 04.10.16 19:00 (GMT+01:00) >An: dev@flex.apache.org >Betreff: Re: AW: AW: AW: Jenkins still red > > > >On 10/4/16, 9:52 AM, "Christofer Dutz" wrote: > >>Well you could override it in the pom, but I don't think that I do that. >>It should always be the def

AW: AW: AW: AW: Jenkins still red

2016-10-04 Thread Christofer Dutz
.10.16 19:00 (GMT+01:00) An: dev@flex.apache.org Betreff: Re: AW: AW: AW: Jenkins still red On 10/4/16, 9:52 AM, "Christofer Dutz" wrote: >Well you could override it in the pom, but I don't think that I do that. >It should always be the default defines in the mojo. I only

Re: AW: AW: AW: Jenkins still red

2016-10-04 Thread Alex Harui
On 10/4/16, 9:52 AM, "Christofer Dutz" wrote: >Well you could override it in the pom, but I don't think that I do that. >It should always be the default defines in the mojo. I only expose config >options to customize, the default should apply in most cases, especially >the framework build. OK.

Re: AW: AW: Jenkins still red

2016-10-04 Thread Alex Harui
On 10/4/16, 9:42 AM, "Alex Harui" wrote: > >It looks like the pom.xml files specify the output as well. Can you >quickly answer if the pom.xml overrides the getOutput in CompileJSMojo? Wait, never mind. I didn't see it in the pom it was in the generated compile-js-config.xml. I'll figure it

AW: AW: AW: Jenkins still red

2016-10-04 Thread Christofer Dutz
phone gesendet. Ursprüngliche Nachricht Von: Alex Harui Datum: 04.10.16 18:43 (GMT+01:00) An: dev@flex.apache.org Betreff: Re: AW: AW: Jenkins still red On 10/4/16, 9:13 AM, "Christofer Dutz" wrote: >Hi Alex, > > >I noticed how late it must have been at you

Re: AW: AW: Jenkins still red

2016-10-04 Thread Alex Harui
On 10/4/16, 9:13 AM, "Christofer Dutz" wrote: >Hi Alex, > > >I noticed how late it must have been at your end after sending my mail. >So sorry for that. > >I guess I'm just totally frustrated, that I keep on cleaning up stuff, >and as soon as it's done I have to start again. IMO, your goal sho

AW: AW: Jenkins still red

2016-10-04 Thread Christofer Dutz
ly simply have to change what you return here. Chris Von: Alex Harui Gesendet: Dienstag, 4. Oktober 2016 16:52:44 An: dev@flex.apache.org Betreff: Re: AW: Jenkins still red On 10/4/16, 3:22 AM, "Christofer Dutz" wrote: >Hi Alex, > > &

Re: AW: Jenkins still red

2016-10-04 Thread Alex Harui
On 10/4/16, 3:22 AM, "Christofer Dutz" wrote: >Hi Alex, > > >as you seem to be responding to everything else I guess you missed my >asking you to rollback your changes and move them to a feature branch. >Are you going to revert > >b8d8c48b11f41ea435eefafc94eb0927229e8a4b > >It's ok that it "sli

AW: Jenkins still red

2016-10-04 Thread Christofer Dutz
lf or write that documentation immediately and I would prefer a little discussion on what's changed and not having to reverse engineer mentioned commit. Chris Von: Christofer Dutz Gesendet: Dienstag, 4. Oktober 2016 08:35:33 An: dev@flex.apache.org Betreff:

AW: Jenkins still red

2016-10-03 Thread Christofer Dutz
I agree ... the Plugin is not broken, but the compiler changed without the plugin having the chance to be adjusted to those changes. Yes most of the build logic is in the plugin itself. That's the way things are done in Maven. If you change the way things are built, you have to adjust the plug