Re: Maven build broken

See old posts on dev@flex from Chris Dutz about the Mavenizer. IIRC, you need to be on a pretty recent version of Maven and/or convert your own Apache Flex SDK. Once we remove Flash dependencies from our tests, we might be able to move some of these dependencies into Flash-specific profiles.

Re: Maven build broken

Hi, I tried to build with maven localy and while all goes ok with -DskipTests (good work!, it's a goo starting point! :)), then I tried to remove all .m2 folder and try again. In this scenario I get [ERROR] Failed to execute goal on project compiler: Could not resolve dependencies for project

Re: Maven build broken

The build seems to be working with Selenium 3.4.0, GeckoDriver 0.18.0, and FireFox 54. On my Mac, I am using Selenium 2.53.0, GeckoDriver 0.16.0 and FireFox 46 since that is how the Ant build is also currently configured. -Alex On 10/19/17, 9:18 PM, "Alex Harui"

Re: Maven build broken

I filed https://issues.apache.org/jira/browse/INFRA-15328. We don't know if that will fix the problem or not. It is just a guess given that the current gecko driver is old (0.13.0) and I'm running 0.16.0 and documentation implies that you need 0.18.0 for Firefox 54. -Alex On 10/19/17, 6:44 PM,

Re: Maven build broken

Piotr, Dave is referring to the builds@ mailing list. Where we can ask for help. And maybe get permission to make changes to the Windows machine if one of us wants to learn how Infra installs software. And then worry that we'll screw up any other project that was happy with that version of

Re: Maven build broken

Hi Dave, I'm sorry what is the "builds ML"? Maybe we can upgrade something on the Machines. Piotr On Fri, Oct 20, 2017, 00:21 Dave Fisher wrote: > Hi Alex, > > There is a builds ML and I suspect that you might be able to get some keys > to one if you ask nicely. You are

Re: Maven build broken

Hi Alex, There is a builds ML and I suspect that you might be able to get some keys to one if you ask nicely. You are a Member. Regards, Dave > On Oct 19, 2017, at 3:17 PM, Alex Harui wrote: > > Hi Piotr, > > The integration tests passed for me with an older

Re: Maven build broken

Hi Piotr, The integration tests passed for me with an older Firefox and Selenium. But this new Selenium may not be compatible with the version of GeckoDriver used on builds.a.o. This is a problem with using builds.a.o: we don't have full control over all of the pieces. This is why I pay for

Re: Maven build broken

Alex, I saw you push to the repo with selenium upgrade, now those tests failing in other place. I have to admit that I didn't have time to look into that. I hope to try setup selenium locally tomorrow, but if you have some idea earlier try it please. Thanks, Piotr 2017-10-19 10:01 GMT+02:00

Re: Maven build broken

Anyone has setup selenium locally ? Piotr 2017-10-19 9:21 GMT+02:00 Piotr Zarzycki : > Just build locally all examples by Maven and Royale Store looks perfectly > fine. > > Piotr > > 2017-10-19 9:20 GMT+02:00 Alex Harui : > >> I don't know

Re: Maven build broken

Just build locally all examples by Maven and Royale Store looks perfectly fine. Piotr 2017-10-19 9:20 GMT+02:00 Alex Harui : > I don't know for sure, I didn't create the tests. I believe they are > looking for certain UI widgets in RoyaleStore. > > I'm still syncing

Re: Maven build broken

I don't know for sure, I didn't create the tests. I believe they are looking for certain UI widgets in RoyaleStore. I'm still syncing up to build everything locally, but if you have time, it might be worth just running RoyaleStore to see if it runs properly. If the examples aren't generating a

Re: Maven build broken

Hi Alex, Just trying to understand what actually is doing that test. :) Piotr 2017-10-19 9:07 GMT+02:00 Alex Harui : > The node tests passed, it failed in IntegrationTests. See the list of > goals near the end of the output. > > -Alex > > On 10/18/17, 11:46 PM,

Re: Maven build broken

The node tests passed, it failed in IntegrationTests. See the list of goals near the end of the output. -Alex On 10/18/17, 11:46 PM, "Harbs" wrote: >To me it looks like the “JSNode” target for the node test is not working. > >I’m a bit confused, because setting the

Re: Maven build broken

To me it looks like the “JSNode” target for the node test is not working. I’m a bit confused, because setting the config to “node” works for me in node targets. What’s JSNode used for? Harbs > On Oct 19, 2017, at 2:13 AM, Alex Harui wrote: > > The change I made was

Re: Maven build broken

The change I made was to add a second Maven build and move the original Maven build's goals to that second Maven build, then change the first Maven build's goals to build with the utils profile first. That appears to work. Now the tests are failing so I just added -DskipTests to the second goal

Re: Maven build broken

Hi, > I just made a change to the maven configuration. Let's see if it works. I assume you mean in the Jerkins job? What was that change and will it help people compile locally? Thanks, Justin

Re: Maven build broken

Harbs, Two maven projects need to be build before main build happen: compiler-jburg-types and compiler-build-tools. I believe that maybe this file [1] can help to achieve that. Alex made the changes there nad pipeline runs [2]. [1]

Re: Maven build broken

Well, the artifacts are probably missing because the compiler build is failing: https://builds.apache.org/job/Royale-compiler/23/console It looks like there’s some problem with the poms related to jburg, but I don’t understand maven

Re: Maven build broken

Harbs, Maybe something wasn't merge properly. It look like reason is in that file [1]. [1] https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/flex/compiler/internal/codegen/js/JSWriter.java Piotr On Wed, Oct 18, 2017, 14:03 Harbs

Re: Maven build broken

For some reason it’s looking for org.apache.flex.compiler.codegen instead of org.apache.royale.compiler.codegen > On Oct 18, 2017, at 2:52 PM, Piotr Zarzycki wrote: > > Again a bit farther - Now it's pointing to some problems in code [1]. > > [1]

Re: Maven build broken

Again a bit farther - Now it's pointing to some problems in code [1]. [1] http://apacheflexbuild.cloudapp.net:8080/job/royale-compiler/30/ Piotr On Wed, Oct 18, 2017, 13:18 Piotr Zarzycki wrote: > I remember that there is some work to do on Tests, they were

Re: Maven build broken

I remember that there is some work to do on Tests, they were temporary disabled. I'm doing it also on develop for ANT build. Removing royale.dependent.tests. Piotr On Wed, Oct 18, 2017, 12:57 Harbs wrote: > Good luck. Let me know if you need my help working on this. > >

Re: Maven build broken

Good luck. Let me know if you need my help working on this. > On Oct 18, 2017, at 1:11 PM, Piotr Zarzycki wrote: > > Maven failed again, but I have found reason of failing in case of ANT > build. Let's see whether it will work. > > Piotr > > On Wed, Oct 18, 2017,

Re: Maven build broken

I don’t have ASJS_HOME set at all and it builds correctly. Can you try removing the environment variable on the Jenkins server? (I don’t remember the login.) > On Oct 18, 2017, at 1:46 PM, Piotr Zarzycki wrote: > > Harbs, > > Now we are a bit farther, cause there

Re: Maven build broken

Harbs, Now we are a bit farther, cause there is some problems with environment variables [1]. If you could look into that. Maybe your local build will also fail. [1] http://apacheflexbuild.cloudapp.net:8080/job/royale-compiler/28/ Thanks, Piotr On Wed, Oct 18, 2017, 12:11 Piotr Zarzycki

Re: Maven build broken

Maven failed again, but I have found reason of failing in case of ANT build. Let's see whether it will work. Piotr On Wed, Oct 18, 2017, 11:49 Piotr Zarzycki wrote: > Harbs, > > I think I got it. I have switched to other windows machine. Let's see what > happens. > >

Re: Maven build broken

I know what happens. In case of Maven first need to be build projects: compiler-jburg-types and compiler-build-tools and than the rest one. Not sure yet how to trigger that. Maybe we need to change "Jenkins" file. Piotr 2017-10-18 11:42 GMT+02:00 Harbs : > Nope. Failed. >

Re: Maven build broken

Harbs, Will be great! :) Thanks for doing that! I hope you didn't have any ugly conflicts. :) Piotre 2017-10-18 10:41 GMT+02:00 Harbs : > Fingers crossed… ;-) > > > On Oct 18, 2017, at 11:39 AM, Piotr Zarzycki > wrote: > > > > Justin, > > > >

Re: Maven build broken

Fingers crossed… ;-) > On Oct 18, 2017, at 11:39 AM, Piotr Zarzycki > wrote: > > Justin, > > I saw that Harbs just pushed merge to develop, so I run Royale-compiler for > Maven [1] - let's see what happens. > > [1] https://builds.apache.org/job/Royale-compiler/ >

Re: Maven build broken

Justin, I saw that Harbs just pushed merge to develop, so I run Royale-compiler for Maven [1] - let's see what happens. [1] https://builds.apache.org/job/Royale-compiler/ Piotr 2017-10-18 10:36 GMT+02:00 Justin Mclean : > Hi, > > BTW Jenkins is also reporting

Re: Maven build broken

Hi, BTW Jenkins is also reporting failures to compile the develop branch of royale-asjs [1] for the last two builds. That’s since the rename branch has been merged. Thanks, Justin 1. https://builds.apache.org/job/Royale-asjs/

Re: Maven build broken

Yes. I forgot to do that yesterday. I was planning on doing it soon. > On Oct 18, 2017, at 8:22 AM, Justin Mclean wrote: > > Hi, > > Looks like the rename branches on the royale-compile and royale-typedefs > repos haven’t been merged into develop but the royale-asjs