Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2
OK, I think I saw Maven build with and without the Flash stuff. I pushed the changes to the release branch. The changes required reverting the version numbers on royale-compiler and royale-asjs but not royale-typedefs. To build with the Adobe stuff with Maven, you will have to use system properties (as well as profiles): -Dgenerate.swf.swcs=true Or for examples: -Dgenerate.swf=true Thanks, -Alex On 9/23/19, 1:29 PM, "Alex Harui" wrote: The reason I am unsure about this release is that, in theory, we all agreed to be PMC members to make growing the community our primary goal. To achieve that goal, we should be doing things to attract not just new users, but even more importantly, new committers. We know we've got tons of bugs and features to work on, so we want someone to grab the release, try it, and when they find a problem, we want them to try to fix it. And right now, they won't be able to build with Ant or Maven without the Adobe stuff. I imagine you are quite frustrated by now, but I am also frustrated because I see people spending energy on guessing at workarounds instead of actually taking the time to analyze and propose solutions. And then I end up putting off my other tasks to do the analysis, and IMO, that doesn't help the community nearly as much as having other committers/PMC members develop the skills to solve problems like this in the future. My 2 cents, -Alex On 9/23/19, 8:59 AM, "Piotr Zarzycki" wrote: My point is that all those fixes are for SDK Developers, not for Users. I would like to satisfy users not SDK developers, the first one are waiting too long for release. pon., 23 wrz 2019 o 17:53 Alex Harui napisał(a): > Depends on your definition of small. The .mvn/extensions.xml is missing > from royale-compiler. That's why it won't auto-download the Adobe stuff. > > Then almost every pom.xml needs to be changed to support js-only. > > -Alex > > On 9/23/19, 8:50 AM, "Piotr Zarzycki" wrote: > > Alex, > > Carlos is able to build framework by ANT so to me it's enough to go > with > release. I have pushed him to try cause I thought that with some small > workarounds he will be able to build that as well. > > Thanks, > Piotr > > pon., 23 wrz 2019 o 17:46 Alex Harui > napisał(a): > > > Update: There is definitely a problem with the source package that > > prevents building the source with Maven from a truly clean machine. > I have > > some changes pending. This is going to be a pretty large commit as > if > > affects a lot of files. I'm not sure why Piotr is have Carlos > continue to > > try things. That seems like duplication of effort to me. I will > hopefully > > have this working by end of my day today. > > > > -Alex > > > > On 9/21/19, 4:51 PM, "Alex Harui" wrote: > > > > I changed the subject to try to keep the threads separated. > > > > Please remember that the scripts and instructions are biased > towards > > js-only. If you have PLAYERGLOBAL_HOME, AIR_HOME, and > FLASHPLAYER_DEBUGGER > > set then you will need different profiles. > > > > Looks like this failure is caused by change 228f4fbd1. There > should > > not be hard dependencies on Adobe stuff in order to support js-only. > > > > In testing a fix, I found out how to reproduce Josh's first > issue with > > the Maven build from a clean machine (remove all adobe and royale > artifacts > > from local repo) for js-only. More changes to the poms are > necessary. I > > will try to figure it out. > > > > And so, this means that a few more folks are likely to have > trouble > > building from source. Again, most folks are going to just use the > > binaries, but I'm worried about first impressions for those who do > use the > > source. > > > > -Alex > > > > On 9/21/19, 2:32 PM, "Carlos Rovira" > wrote: > > > > HI Piotr, > > > > since I have work to do on docs, I prefer to try with some > > concrete info, > > or I'll end going like chicken without head :) > > I can test with and without vars on my .bash_profile too. > > > >
Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2
The reason I am unsure about this release is that, in theory, we all agreed to be PMC members to make growing the community our primary goal. To achieve that goal, we should be doing things to attract not just new users, but even more importantly, new committers. We know we've got tons of bugs and features to work on, so we want someone to grab the release, try it, and when they find a problem, we want them to try to fix it. And right now, they won't be able to build with Ant or Maven without the Adobe stuff. I imagine you are quite frustrated by now, but I am also frustrated because I see people spending energy on guessing at workarounds instead of actually taking the time to analyze and propose solutions. And then I end up putting off my other tasks to do the analysis, and IMO, that doesn't help the community nearly as much as having other committers/PMC members develop the skills to solve problems like this in the future. My 2 cents, -Alex On 9/23/19, 8:59 AM, "Piotr Zarzycki" wrote: My point is that all those fixes are for SDK Developers, not for Users. I would like to satisfy users not SDK developers, the first one are waiting too long for release. pon., 23 wrz 2019 o 17:53 Alex Harui napisał(a): > Depends on your definition of small. The .mvn/extensions.xml is missing > from royale-compiler. That's why it won't auto-download the Adobe stuff. > > Then almost every pom.xml needs to be changed to support js-only. > > -Alex > > On 9/23/19, 8:50 AM, "Piotr Zarzycki" wrote: > > Alex, > > Carlos is able to build framework by ANT so to me it's enough to go > with > release. I have pushed him to try cause I thought that with some small > workarounds he will be able to build that as well. > > Thanks, > Piotr > > pon., 23 wrz 2019 o 17:46 Alex Harui > napisał(a): > > > Update: There is definitely a problem with the source package that > > prevents building the source with Maven from a truly clean machine. > I have > > some changes pending. This is going to be a pretty large commit as > if > > affects a lot of files. I'm not sure why Piotr is have Carlos > continue to > > try things. That seems like duplication of effort to me. I will > hopefully > > have this working by end of my day today. > > > > -Alex > > > > On 9/21/19, 4:51 PM, "Alex Harui" wrote: > > > > I changed the subject to try to keep the threads separated. > > > > Please remember that the scripts and instructions are biased > towards > > js-only. If you have PLAYERGLOBAL_HOME, AIR_HOME, and > FLASHPLAYER_DEBUGGER > > set then you will need different profiles. > > > > Looks like this failure is caused by change 228f4fbd1. There > should > > not be hard dependencies on Adobe stuff in order to support js-only. > > > > In testing a fix, I found out how to reproduce Josh's first > issue with > > the Maven build from a clean machine (remove all adobe and royale > artifacts > > from local repo) for js-only. More changes to the poms are > necessary. I > > will try to figure it out. > > > > And so, this means that a few more folks are likely to have > trouble > > building from source. Again, most folks are going to just use the > > binaries, but I'm worried about first impressions for those who do > use the > > source. > > > > -Alex > > > > On 9/21/19, 2:32 PM, "Carlos Rovira" > wrote: > > > > HI Piotr, > > > > since I have work to do on docs, I prefer to try with some > > concrete info, > > or I'll end going like chicken without head :) > > I can test with and without vars on my .bash_profile too. > > > > Even we can release 0.9.6 and left this issues for 0.9.7 > > > > thanks > > > > Carlos > > > > > > > > > > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (< > > piotrzarzyck...@gmail.com>) escribió: > > > > > You have example of such file in repository. Just based on > that > > setup > > > staging link repository. Currently in that file you have > > Snapshot links and > > > release. Based on this you can setup staging. > > > > > > Apart of that I have shared such file some time ago in the > > previous > > > releases. > > > > > > I'm not sure even if that
[Discuss] Discuss Release Apache Royale 0.9.6 RC2
Carlos, Well I don't see importance from user perspective to that changes at all. It means that you are not going to vote? Thanks, Piotr On Mon, Sep 23, 2019, 7:22 PM Carlos Rovira wrote: > Hi, > > I will stop for today, want to work a bit on royale-docs mobile layout that > I have near finish, so I'll wait for Alex changes and try tomorrow. IMHO > this stuff is important, so it's worth the waiting time of a day or two. > > Thanks > > > > > > El lun., 23 sept. 201. 9 a las 17:59, Piotr Zarzycki (< > piotrzarzyck...@gmail.com>) escribió: > > > My point is that all those fixes are for SDK Developers, not for Users. I > > would like to satisfy users not SDK developers, the first one are waiting > > too long for release. > > > > pon., 23 wrz 2019 o 17:53 Alex Harui > > napisał(a): > > > > > Depends on your definition of small. The .mvn/extensions.xml is > missing > > > from royale-compiler. That's why it won't auto-download the Adobe > stuff. > > > > > > Then almost every pom.xml needs to be changed to support js-only. > > > > > > -Alex > > > > > > On 9/23/19, 8:50 AM, "Piotr Zarzycki" > > wrote: > > > > > > Alex, > > > > > > Carlos is able to build framework by ANT so to me it's enough to go > > > with > > > release. I have pushed him to try cause I thought that with some > > small > > > workarounds he will be able to build that as well. > > > > > > Thanks, > > > Piotr > > > > > > pon., 23 wrz 2019 o 17:46 Alex Harui > > > napisał(a): > > > > > > > Update: There is definitely a problem with the source package > that > > > > prevents building the source with Maven from a truly clean > machine. > > > I have > > > > some changes pending. This is going to be a pretty large commit > as > > > if > > > > affects a lot of files. I'm not sure why Piotr is have Carlos > > > continue to > > > > try things. That seems like duplication of effort to me. I will > > > hopefully > > > > have this working by end of my day today. > > > > > > > > -Alex > > > > > > > > On 9/21/19, 4:51 PM, "Alex Harui" > > wrote: > > > > > > > > I changed the subject to try to keep the threads separated. > > > > > > > > Please remember that the scripts and instructions are biased > > > towards > > > > js-only. If you have PLAYERGLOBAL_HOME, AIR_HOME, and > > > FLASHPLAYER_DEBUGGER > > > > set then you will need different profiles. > > > > > > > > Looks like this failure is caused by change 228f4fbd1. There > > > should > > > > not be hard dependencies on Adobe stuff in order to support > > js-only. > > > > > > > > In testing a fix, I found out how to reproduce Josh's first > > > issue with > > > > the Maven build from a clean machine (remove all adobe and royale > > > artifacts > > > > from local repo) for js-only. More changes to the poms are > > > necessary. I > > > > will try to figure it out. > > > > > > > > And so, this means that a few more folks are likely to have > > > trouble > > > > building from source. Again, most folks are going to just use > the > > > > binaries, but I'm worried about first impressions for those who > do > > > use the > > > > source. > > > > > > > > -Alex > > > > > > > > On 9/21/19, 2:32 PM, "Carlos Rovira" < > carlosrov...@apache.org> > > > wrote: > > > > > > > > HI Piotr, > > > > > > > > since I have work to do on docs, I prefer to try with > some > > > > concrete info, > > > > or I'll end going like chicken without head :) > > > > I can test with and without vars on my .bash_profile too. > > > > > > > > Even we can release 0.9.6 and left this issues for 0.9.7 > > > > > > > > thanks > > > > > > > > Carlos > > > > > > > > > > > > > > > > > > > > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (< > > > > piotrzarzyck...@gmail.com>) escribió: > > > > > > > > > You have example of such file in repository. Just based > > on > > > that > > > > setup > > > > > staging link repository. Currently in that file you > have > > > > Snapshot links and > > > > > release. Based on this you can setup staging. > > > > > > > > > > Apart of that I have shared such file some time ago in > > the > > > > previous > > > > > releases. > > > > > > > > > > I'm not sure even if that is needed it's just I wanted > to > > > > confirm that is > > > > > really not needed. > > > > > > > > > > Do you have player global setup env variable? > > > > > > > > > > If you won't figure out stuff I will share it on > Monday. > > > > > > > > > > Thanks, > > > > > Piotr > > > > > >
Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2
Hi, I will stop for today, want to work a bit on royale-docs mobile layout that I have near finish, so I'll wait for Alex changes and try tomorrow. IMHO this stuff is important, so it's worth the waiting time of a day or two. Thanks El lun., 23 sept. 201. 9 a las 17:59, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > My point is that all those fixes are for SDK Developers, not for Users. I > would like to satisfy users not SDK developers, the first one are waiting > too long for release. > > pon., 23 wrz 2019 o 17:53 Alex Harui > napisał(a): > > > Depends on your definition of small. The .mvn/extensions.xml is missing > > from royale-compiler. That's why it won't auto-download the Adobe stuff. > > > > Then almost every pom.xml needs to be changed to support js-only. > > > > -Alex > > > > On 9/23/19, 8:50 AM, "Piotr Zarzycki" > wrote: > > > > Alex, > > > > Carlos is able to build framework by ANT so to me it's enough to go > > with > > release. I have pushed him to try cause I thought that with some > small > > workarounds he will be able to build that as well. > > > > Thanks, > > Piotr > > > > pon., 23 wrz 2019 o 17:46 Alex Harui > > napisał(a): > > > > > Update: There is definitely a problem with the source package that > > > prevents building the source with Maven from a truly clean machine. > > I have > > > some changes pending. This is going to be a pretty large commit as > > if > > > affects a lot of files. I'm not sure why Piotr is have Carlos > > continue to > > > try things. That seems like duplication of effort to me. I will > > hopefully > > > have this working by end of my day today. > > > > > > -Alex > > > > > > On 9/21/19, 4:51 PM, "Alex Harui" > wrote: > > > > > > I changed the subject to try to keep the threads separated. > > > > > > Please remember that the scripts and instructions are biased > > towards > > > js-only. If you have PLAYERGLOBAL_HOME, AIR_HOME, and > > FLASHPLAYER_DEBUGGER > > > set then you will need different profiles. > > > > > > Looks like this failure is caused by change 228f4fbd1. There > > should > > > not be hard dependencies on Adobe stuff in order to support > js-only. > > > > > > In testing a fix, I found out how to reproduce Josh's first > > issue with > > > the Maven build from a clean machine (remove all adobe and royale > > artifacts > > > from local repo) for js-only. More changes to the poms are > > necessary. I > > > will try to figure it out. > > > > > > And so, this means that a few more folks are likely to have > > trouble > > > building from source. Again, most folks are going to just use the > > > binaries, but I'm worried about first impressions for those who do > > use the > > > source. > > > > > > -Alex > > > > > > On 9/21/19, 2:32 PM, "Carlos Rovira" > > wrote: > > > > > > HI Piotr, > > > > > > since I have work to do on docs, I prefer to try with some > > > concrete info, > > > or I'll end going like chicken without head :) > > > I can test with and without vars on my .bash_profile too. > > > > > > Even we can release 0.9.6 and left this issues for 0.9.7 > > > > > > thanks > > > > > > Carlos > > > > > > > > > > > > > > > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (< > > > piotrzarzyck...@gmail.com>) escribió: > > > > > > > You have example of such file in repository. Just based > on > > that > > > setup > > > > staging link repository. Currently in that file you have > > > Snapshot links and > > > > release. Based on this you can setup staging. > > > > > > > > Apart of that I have shared such file some time ago in > the > > > previous > > > > releases. > > > > > > > > I'm not sure even if that is needed it's just I wanted to > > > confirm that is > > > > really not needed. > > > > > > > > Do you have player global setup env variable? > > > > > > > > If you won't figure out stuff I will share it on Monday. > > > > > > > > Thanks, > > > > Piotr > > > > > > > > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira < > > > carlosrov...@apache.org> > > > > wrote: > > > > > > > > > Hi Piort, > > > > > > > > > > can you share here the set of links to add to my > > > .m2/settings.xml? > > > > > > > > > > thanks > > > > > > > > > > > > > > > > > > > > > > > > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki
Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2
My point is that all those fixes are for SDK Developers, not for Users. I would like to satisfy users not SDK developers, the first one are waiting too long for release. pon., 23 wrz 2019 o 17:53 Alex Harui napisał(a): > Depends on your definition of small. The .mvn/extensions.xml is missing > from royale-compiler. That's why it won't auto-download the Adobe stuff. > > Then almost every pom.xml needs to be changed to support js-only. > > -Alex > > On 9/23/19, 8:50 AM, "Piotr Zarzycki" wrote: > > Alex, > > Carlos is able to build framework by ANT so to me it's enough to go > with > release. I have pushed him to try cause I thought that with some small > workarounds he will be able to build that as well. > > Thanks, > Piotr > > pon., 23 wrz 2019 o 17:46 Alex Harui > napisał(a): > > > Update: There is definitely a problem with the source package that > > prevents building the source with Maven from a truly clean machine. > I have > > some changes pending. This is going to be a pretty large commit as > if > > affects a lot of files. I'm not sure why Piotr is have Carlos > continue to > > try things. That seems like duplication of effort to me. I will > hopefully > > have this working by end of my day today. > > > > -Alex > > > > On 9/21/19, 4:51 PM, "Alex Harui" wrote: > > > > I changed the subject to try to keep the threads separated. > > > > Please remember that the scripts and instructions are biased > towards > > js-only. If you have PLAYERGLOBAL_HOME, AIR_HOME, and > FLASHPLAYER_DEBUGGER > > set then you will need different profiles. > > > > Looks like this failure is caused by change 228f4fbd1. There > should > > not be hard dependencies on Adobe stuff in order to support js-only. > > > > In testing a fix, I found out how to reproduce Josh's first > issue with > > the Maven build from a clean machine (remove all adobe and royale > artifacts > > from local repo) for js-only. More changes to the poms are > necessary. I > > will try to figure it out. > > > > And so, this means that a few more folks are likely to have > trouble > > building from source. Again, most folks are going to just use the > > binaries, but I'm worried about first impressions for those who do > use the > > source. > > > > -Alex > > > > On 9/21/19, 2:32 PM, "Carlos Rovira" > wrote: > > > > HI Piotr, > > > > since I have work to do on docs, I prefer to try with some > > concrete info, > > or I'll end going like chicken without head :) > > I can test with and without vars on my .bash_profile too. > > > > Even we can release 0.9.6 and left this issues for 0.9.7 > > > > thanks > > > > Carlos > > > > > > > > > > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (< > > piotrzarzyck...@gmail.com>) escribió: > > > > > You have example of such file in repository. Just based on > that > > setup > > > staging link repository. Currently in that file you have > > Snapshot links and > > > release. Based on this you can setup staging. > > > > > > Apart of that I have shared such file some time ago in the > > previous > > > releases. > > > > > > I'm not sure even if that is needed it's just I wanted to > > confirm that is > > > really not needed. > > > > > > Do you have player global setup env variable? > > > > > > If you won't figure out stuff I will share it on Monday. > > > > > > Thanks, > > > Piotr > > > > > > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira < > > carlosrov...@apache.org> > > > wrote: > > > > > > > Hi Piort, > > > > > > > > can you share here the set of links to add to my > > .m2/settings.xml? > > > > > > > > thanks > > > > > > > > > > > > > > > > > > > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (< > > > > piotrzarzyck...@gmail.com>) escribió: > > > > > > > > > Switching subject to discuss. > > > > > > > > > > Carlos can you put in your settings link toavem staging > > artifacts? And > > > > run > > > > > approve script again. > > > > > > > > > > Thanks, > > > > > Piotr > > > > > > > > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira < > > carlosrov...@apache.org> > > > > > wrote: > > > > > > > > > > > Curious
Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2
Alex, Carlos is able to build framework by ANT so to me it's enough to go with release. I have pushed him to try cause I thought that with some small workarounds he will be able to build that as well. Thanks, Piotr pon., 23 wrz 2019 o 17:46 Alex Harui napisał(a): > Update: There is definitely a problem with the source package that > prevents building the source with Maven from a truly clean machine. I have > some changes pending. This is going to be a pretty large commit as if > affects a lot of files. I'm not sure why Piotr is have Carlos continue to > try things. That seems like duplication of effort to me. I will hopefully > have this working by end of my day today. > > -Alex > > On 9/21/19, 4:51 PM, "Alex Harui" wrote: > > I changed the subject to try to keep the threads separated. > > Please remember that the scripts and instructions are biased towards > js-only. If you have PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER > set then you will need different profiles. > > Looks like this failure is caused by change 228f4fbd1. There should > not be hard dependencies on Adobe stuff in order to support js-only. > > In testing a fix, I found out how to reproduce Josh's first issue with > the Maven build from a clean machine (remove all adobe and royale artifacts > from local repo) for js-only. More changes to the poms are necessary. I > will try to figure it out. > > And so, this means that a few more folks are likely to have trouble > building from source. Again, most folks are going to just use the > binaries, but I'm worried about first impressions for those who do use the > source. > > -Alex > > On 9/21/19, 2:32 PM, "Carlos Rovira" wrote: > > HI Piotr, > > since I have work to do on docs, I prefer to try with some > concrete info, > or I'll end going like chicken without head :) > I can test with and without vars on my .bash_profile too. > > Even we can release 0.9.6 and left this issues for 0.9.7 > > thanks > > Carlos > > > > > El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (< > piotrzarzyck...@gmail.com>) escribió: > > > You have example of such file in repository. Just based on that > setup > > staging link repository. Currently in that file you have > Snapshot links and > > release. Based on this you can setup staging. > > > > Apart of that I have shared such file some time ago in the > previous > > releases. > > > > I'm not sure even if that is needed it's just I wanted to > confirm that is > > really not needed. > > > > Do you have player global setup env variable? > > > > If you won't figure out stuff I will share it on Monday. > > > > Thanks, > > Piotr > > > > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira < > carlosrov...@apache.org> > > wrote: > > > > > Hi Piort, > > > > > > can you share here the set of links to add to my > .m2/settings.xml? > > > > > > thanks > > > > > > > > > > > > > > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (< > > > piotrzarzyck...@gmail.com>) escribió: > > > > > > > Switching subject to discuss. > > > > > > > > Carlos can you put in your settings link toavem staging > artifacts? And > > > run > > > > approve script again. > > > > > > > > Thanks, > > > > Piotr > > > > > > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira < > carlosrov...@apache.org> > > > > wrote: > > > > > > > > > Curious thing is: > > > > > > > > > > if I run in my source tree royale-compiler folder this: > > > > > > > > > > mvn -s settings-template.xml -DskipTests clean install > > > > > > > > > > > > > > > with clean .m2 all ends properly. > > > > > > > > > > > > > > > if I run it in the downloaded RC2 folder it fails: > > > > > > > > > > > > > > > Downloaded from central: > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Forg%2Fcodehaus%2Fplexus%2Fplexus-container-default%2F1.0-alpha-9-stable-1%2Fplexus-container-default-1.0-alpha-9-stable-1.jardata=02%7C01%7Caharui%40adobe.com%7C102bbce2a6b94f47599408d73eeea986%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637047067078793068sdata=QhbpGC%2BtKlQ4dxLvri%2FmYdSerlKFUTjqXkGfDeBE0c0%3Dreserved=0 > > > > > (194 kB at 290 kB/s) > > > > > > > > > > Downloaded from central: > > > > > > > >
Re: [Discuss] Discuss Release Apache Royale 0.9.6 RC2
Update: There is definitely a problem with the source package that prevents building the source with Maven from a truly clean machine. I have some changes pending. This is going to be a pretty large commit as if affects a lot of files. I'm not sure why Piotr is have Carlos continue to try things. That seems like duplication of effort to me. I will hopefully have this working by end of my day today. -Alex On 9/21/19, 4:51 PM, "Alex Harui" wrote: I changed the subject to try to keep the threads separated. Please remember that the scripts and instructions are biased towards js-only. If you have PLAYERGLOBAL_HOME, AIR_HOME, and FLASHPLAYER_DEBUGGER set then you will need different profiles. Looks like this failure is caused by change 228f4fbd1. There should not be hard dependencies on Adobe stuff in order to support js-only. In testing a fix, I found out how to reproduce Josh's first issue with the Maven build from a clean machine (remove all adobe and royale artifacts from local repo) for js-only. More changes to the poms are necessary. I will try to figure it out. And so, this means that a few more folks are likely to have trouble building from source. Again, most folks are going to just use the binaries, but I'm worried about first impressions for those who do use the source. -Alex On 9/21/19, 2:32 PM, "Carlos Rovira" wrote: HI Piotr, since I have work to do on docs, I prefer to try with some concrete info, or I'll end going like chicken without head :) I can test with and without vars on my .bash_profile too. Even we can release 0.9.6 and left this issues for 0.9.7 thanks Carlos El sáb., 21 sept. 2019 a las 22:44, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > You have example of such file in repository. Just based on that setup > staging link repository. Currently in that file you have Snapshot links and > release. Based on this you can setup staging. > > Apart of that I have shared such file some time ago in the previous > releases. > > I'm not sure even if that is needed it's just I wanted to confirm that is > really not needed. > > Do you have player global setup env variable? > > If you won't figure out stuff I will share it on Monday. > > Thanks, > Piotr > > On Sat, Sep 21, 2019, 8:06 PM Carlos Rovira > wrote: > > > Hi Piort, > > > > can you share here the set of links to add to my .m2/settings.xml? > > > > thanks > > > > > > > > > > El sáb., 21 sept. 2019 a las 19:02, Piotr Zarzycki (< > > piotrzarzyck...@gmail.com>) escribió: > > > > > Switching subject to discuss. > > > > > > Carlos can you put in your settings link toavem staging artifacts? And > > run > > > approve script again. > > > > > > Thanks, > > > Piotr > > > > > > On Sat, Sep 21, 2019, 6:49 PM Carlos Rovira > > > wrote: > > > > > > > Curious thing is: > > > > > > > > if I run in my source tree royale-compiler folder this: > > > > > > > > mvn -s settings-template.xml -DskipTests clean install > > > > > > > > > > > > with clean .m2 all ends properly. > > > > > > > > > > > > if I run it in the downloaded RC2 folder it fails: > > > > > > > > > > > > Downloaded from central: > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Forg%2Fcodehaus%2Fplexus%2Fplexus-container-default%2F1.0-alpha-9-stable-1%2Fplexus-container-default-1.0-alpha-9-stable-1.jardata=02%7C01%7Caharui%40adobe.com%7C102bbce2a6b94f47599408d73eeea986%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637047067078793068sdata=QhbpGC%2BtKlQ4dxLvri%2FmYdSerlKFUTjqXkGfDeBE0c0%3Dreserved=0 > > > > (194 kB at 290 kB/s) > > > > > > > > Downloaded from central: > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2%2Forg%2Fantlr%2FST4%2F4.0.4%2FST4-4.0.4.jardata=02%7C01%7Caharui%40adobe.com%7C102bbce2a6b94f47599408d73eeea986%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637047067078793068sdata=C%2BMVzWH3QNeEH42YUkHU4Mrx64sXvaPbfwjWcbSlOnA%3Dreserved=0 > > > > (237 > > > > kB at 345 kB/s) > > > > > > > > [*ERROR*] [ERROR] Some problems were encountered while processing the > > > POMs: > > > > > > > > [ERROR]
