Well I'm planning on starting to setup an integration test suite which will contain lots of separate Maven projects. If we can dramatically reduce the time, this would be huge. And the build time of the Maven build seems to be a lot faster than the ant build. So if there is a way to speed up things even more, we should do that.
Von meinem Samsung Galaxy Smartphone gesendet. -------- Ursprüngliche Nachricht -------- Von: Carlos Rovira <[email protected]> Datum: 04.10.16 23:47 (GMT+01:00) An: Christofer Dutz <[email protected]> Betreff: Re: AW: AW: AW: AW: Jenkins still red I could say that the almost most of the time is spent between final file compilation: Compiling file: /Users/carlosrovira/Dev/Flex/projects/flexjs/maven/flexjstest/target/javascript/bin/js-debug/MyComponent.js and using the first SWC: using SWC: /Users/carlosrovira/.m2/repository/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.swc I think maven is building js + set outputs instead of only js, while NextGenAS is building only js output. But, as I say, maybe is not the time to deep inside this, since there's much more things that I want to explore, just is worth to know about this to solve as there's more room. Thanks 2016-10-04 23:23 GMT+02:00 Christofer Dutz <[email protected]<mailto:[email protected]>>: Ok so that is quite a difference. As I don't use a different compiler and the only difference might be the compiler options and the config files, it would be worth investigating the difference. The Maven plugin dumps the config files to the target directory and doesn't use compiler options above that, it should be easy to find out what's different. Chris Von meinem Samsung Galaxy Smartphone gesendet. -------- Ursprüngliche Nachricht -------- Von: Carlos Rovira <[email protected]<mailto:[email protected]>> Datum: 04.10.16 23:04 (GMT+01:00) An: Christofer Dutz <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Betreff: Re: AW: AW: AW: AW: Jenkins still red This is so cool Chris, thanks for the great effort, I know the cost and how hard is to get to this point, but you got it! :) 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 config params at hand to make the build process more simple and fast?. Although maybe this is not really important since I think the final point with maven is to make it run in a CI env, but maybe could it be interesting to take into account with an IDE like IntelliJ that a good support of maven...don't know the level of usability we could get there. >From here I'm more interested in explore CSS possibilities with the clues Alex >gave in other thread... Thanks Carlos 2016-10-04 22:45 GMT+02:00 Christofer Dutz <[email protected]<mailto:[email protected]>>: Yup ... I just came back home and had a look at the changes. All seems to be a-ok :-) Thanks for fixing it. I hope it helped get a little insight on how maven works and that it helps getting comfortable with it. One thing though ... if the output is set to a file it adds the js output inside the existing archive and if it's a directory it outputs stuff in to a directory structure. Is it a valid usecase to have output generated to a directory? If yes it would be better to name the property something neutral ... ("output" for example) and to have the swc default, but a user could override the default and have stuff generated to a directory. And @Carlos Rovira<mailto:[email protected]> I'm happy to hear that you finally managed to execute the archetype. I hope it will help getting started with the maven build. I will definitely continue to add different archetypes for different scenarios and start writing more documentation as soon as I have gotten rid of a little of the workload I got dumped on my desk today :-) Chris ________________________________ Von: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> im Auftrag von Carlos Rovira <[email protected]<mailto:[email protected]>> Gesendet: Dienstag, 4. Oktober 2016 22:26:44 An: [email protected]<mailto:[email protected]> 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 GMT+02:00 Alex Harui <[email protected]<mailto:[email protected]>>: > OK, I think I got it working! > > I've pushed the changes in both repos. The Maven builds worked locally > for me. We'll see how it goes on builds@ > > Thanks for the pointers. > -Alex > > On 10/4/16, 11:04 AM, "Christofer Dutz" > <[email protected]<mailto:[email protected]>> wrote: > > >Just build the plugin module (go into the plugin directory and do a "mvn > >clean install") or do a "mvn clean install" of the complete compiler > >project. > > > >Chris > > > > > >Von meinem Samsung Galaxy Smartphone gesendet. > > > > > >-------- Ursprüngliche Nachricht -------- > >Von: Alex Harui <[email protected]<mailto:[email protected]>> > >Datum: 04.10.16 19:00 (GMT+01:00) > >An: [email protected]<mailto:[email protected]> > >Betreff: Re: AW: AW: AW: Jenkins still red > > > > > > > >On 10/4/16, 9:52 AM, "Christofer Dutz" > ><[email protected]<mailto:[email protected]>> 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. > > > >Next question: If I make a change in flex-falcon/flexjs-maven-plugin > what > >do I need to do to use those changes to build flex-asjs? > > > >Thanks, > >-Alex > > > > -- Carlos Rovira Director General M: +34 607 22 60 05<tel:%2B34%20607%2022%2060%2005> 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. -- [http://www.codeoscopic.com/wp-content/uploads/2016/05/logo_codeoscopic_170x70t.png] Carlos Rovira Director General M: +34 607 22 60 05<tel:%2B34%20607%2022%2060%2005> http://www.codeoscopic.com http://www.avant2.es<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. -- [http://www.codeoscopic.com/wp-content/uploads/2016/05/logo_codeoscopic_170x70t.png] Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es<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.
