No you I am talking about the Ant build.
I am realistic enough that I know that Ant won't go away soon. We are now in a state, where we are in a parity state. Users can choose which build they want to use. Alex and the others invested quite some time to make ASJS and Falcon build in Eclipse by checking in the config files. These reference the libraries with their ANT names and not the ones Maven produces. If we were to adjust the Ant build to produce the same files in the same locations, the eclipse settings could be adjusted and then the Maven workflow for ad-hoc fixes should be a lot simpler. Currently the maven plugin is part of falcon ... I will definitely move this over to become the flex-maven-plugin (currently it's flexJS-maven-plugin). As soon as we have released one version of the two other modules I think we should reference these and only do a new release if we need one. Then I'll also change the build of the externs not to use the flexjs-maven-plugin and hereby resolve the last cycle ... then we'll be down to one simple "mvn clean install". Chris ________________________________ Von: carlos.rov...@gmail.com <carlos.rov...@gmail.com> im Auftrag von Carlos Rovira <carlos.rov...@codeoscopic.com> Gesendet: Donnerstag, 7. Juli 2016 12:16:47 An: dev@flex.apache.org Betreff: Re: [FlexJS] Developer Setup Hi Chris, sorry, if I ask something obvious, maybe I'm a bit lost here, but, you talk about a "Ant build". So, you still need to run an ant build? I was expecting to make the 4 mvn operations to build falcon and asjs artifacts only, and then use IntelliJ to create a pom based on some pom.xml from examples folder. So Ant, will end to be a second citizen, maybe could be maintained if people wants, but, I understand that maven should be the way to go for all of us, isn't it? I expect, someday we could reduce 4 mvn instructions to only one "mvn clean install" and continue working (maybe that's not today due to the baby just born, isn't it?) Maybe I'm missing something Thanks! 2016-07-07 9:57 GMT+02:00 Christofer Dutz <christofer.d...@c-ware.de>: > Hi Carlos, > > > well I would like to claim that the JavaScript part is as finished as I > can be, currently working on some final quirks with resources and font > handling in the Flash versions. > > > I think if we setup the Ant build to produce the output files with the > same name and in the same location as the Maven build does, I think nothing > would be preventing us from simply doing a "mvn clean install" of any > changed artifact and we should be able to continue working in Eclipse > without interruption. I would not prefer to go the other way around and > change the default Maven naming convention producing the same names as the > Ant build, as I think ArtifactId+Version is superior over just ArtifactId. > > > Chris > > ________________________________ > Von: carlos.rov...@gmail.com <carlos.rov...@gmail.com> im Auftrag von > Carlos Rovira <carlos.rov...@codeoscopic.com> > Gesendet: Donnerstag, 7. Juli 2016 09:44:34 > An: dev@flex.apache.org > Betreff: Re: [FlexJS] Developer Setup > > Hi Alex, > > I thought Maven build was now the preferred way of building FlexJS over ant > With Maven all this complicated recipe will be over (thank to god) and will > only need to pass maven > to build in his local repository and the create a pom based on some of the > examples > (Maybe this last part is dependent on some last work Chris is making this > days, at least I'm waiting anxiously for that and laready build with maven) > > Thanks > > > > > 2016-07-07 7:40 GMT+02:00 Alex Harui <aha...@adobe.com>: > > > In theory, there is a better way. Try the following and report where it > > doesn't work and we'll see if we can figure out how to make it work. > > > > First, run ant in the repo. This should generate all of the JS files. > > > > There should be Flash Builder project files in the repo in each > > frameworks/projects folder and frameworks/js/FlexJS/projects folders. > > Create a new workspace, add the nightly as a Flex SDK, import all of the > > projects. You will probably have to fix up the projects to use the > > nightly SDK. > > > > Now add/create a test application. The test application should select > the > > nightly as its SDK. From the Project menu, choose Properties, then > choose > > Flex Build Path from the left-side list and make sure library path is > > shown on the right. > > > > Expand the SDK entry in the list. > > Click on each SWC other than playerglobal.swc and choose Remove to remove > > it from the list. > > Click on Add Project and add each of the projects it needs. > > > > At this point, changing an AS file in any project should result in a new > > SWF with the changes. However, for me, changes to Core.swc cause FB to > > hang and I have to restart FB (sometimes twice) to get back to working > > again. That might be a good reason to make SWC changes in a SWC other > > than Core. > > > > To build the JS version, you should be able to run the FlexJS (JS CompC) > > on the project with the changes. This should generate a fresh set of JS > > files. Double-check to make sure they are going in the correct folder. > > > > Then, from the Run menu, choose External Tools then External Tools > > Configuration. Make a copy of FlexJS (FalconJX Debug Build). In that > > copy, in the arguments before the -fb option, add sdk-js-lib=<path to > > generated-source folder> for each of the SWCs you need in your app. > Then, > > when you run that config, it should use the newly generated-source > folders. > > > > HTH, > > -Alex > > > > > > On 7/6/16, 8:59 PM, "yishayw" <yishayj...@hotmail.com> wrote: > > > > >I'd like to optimize my SDK development workflow. Currently I have a > > >folder > > >which contains the nightly build, and a separate folder which has the > > >latest > > >develop branch of flex-asjs. My main FlashBuilder project is configured > to > > >use the nightly build as the SDK. > > > > > > > > >When I make changes to flex-asjs develop, I clean my project from > > >FlashBuilder, compile from the command line, and use the following > > >(windows) > > >commands to copy the compiled files: > > > > > >---- > > >copy C:\dev\flexjs\flex-asjs\frameworks\js\FlexJS\libs\*.swc > > >C:\dev\flexjs_builds\nightly_07\frameworks\js\FlexJS\libs > > > > > >copy C:\dev\flexjs\flex-asjs\frameworks\libs\*.swc > > >C:\dev\flexjs_builds\nightly_07\frameworks\libs > > > > > >xcopy /E /Y > C:\dev\flexjs\flex-asjs\frameworks\js\FlexJS\generated-sources > > >C:\dev\flexjs_builds\nightly_07\frameworks\js\FlexJS\generated-sources > > >----- > > > > > >Then I can see the SDK changes in my main project. > > > > > >Is there a better way to do this? Ideally, I'd like to edit a file from > > >the > > >SDK in FlashBuilder and have my main project recognize the changes > > >immediately. > > > > > > > > > > > > > > >-- > > >View this message in context: > > > > > > http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Developer-Setu > > >p-tp53729.html > > >Sent from the Apache Flex Development mailing list archive at > Nabble.com. > > > > > > > -- > > Carlos Rovira > Director General > M: +34 607 22 60 05 > 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. > -- Carlos Rovira Director General M: +34 607 22 60 05 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.
