Hi,
yes, I already did some days ago an uploaded to website
If you search for some new class (like jewel SimpleButton) it appears now.
El jue., 10 oct. 2019 a las 11:49, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Hi Carlos,
>
> Did you make an update API doc ? ->
> https://royal
Hi Carlos,
Did you make an update API doc ? ->
https://royale.apache.org/asdoc/index.html
Thanks,
Piotr
pon., 7 paź 2019 o 19:38 Carlos Rovira napisał(a):
> Hi Piotr,
> yes, I'll do in next few hours.
> thanks.
>
> El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>
Hi Piotr,
yes, I'll do in next few hours.
thanks.
El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki ()
escribió:
> Hi Carlos,
>
> Will you be able update website with links for 0.9.6 release ?
>
> Thanks,
> Piotr
>
> niedz., 6 paź 2019 o 10:52 Piotr Zarzycki
> napisał(a):
>
> > Hi Alex,
> >
> > Th
Hi Carlos,
Will you be able update website with links for 0.9.6 release ?
Thanks,
Piotr
niedz., 6 paź 2019 o 10:52 Piotr Zarzycki
napisał(a):
> Hi Alex,
>
> Thank you for the fix. Everything worked fine this time.
>
> Piotr
>
> sob., 5 paź 2019 o 01:51 Alex Harui napisał(a):
>
>> I found some
Hi Alex,
Thank you for the fix. Everything worked fine this time.
Piotr
sob., 5 paź 2019 o 01:51 Alex Harui napisał(a):
> I found some time to try the releasecandidate.xml and found the problem.
> I pushed the fix to release/0.9.6. So try that and see what happens. It
> seemed to do the righ
I found some time to try the releasecandidate.xml and found the problem. I
pushed the fix to release/0.9.6. So try that and see what happens. It seemed
to do the right thing for me on my Windows computer.
You will next likely run into several merge conflicts. I have not looked into
the conf
If we don't fix the release scripts, then the next RM is probably going to run
into the same problem. The time we spend now helps save time in the future.
It is wise to improve the process now in case I get run over by a bus tomorrow.
If you do it manually and make a mistake, we might not cat
Alex,
Can I just do that changes manually on release branch and merge stuff to
develop?
I just don't won't to spend any more minute on release process anymore.
1) I should change build properties
2) I should change all poms
Is there anymore place which I should know to change?
Thanks,
Piotr
O
Piotr,
Again, I am asking you to get in the mindset of a developer and not just a
user. You can see that the Ant script is making some updates. You can verify
that the release branch does not have 0.9.7 for the release.version in
build.properties. You can see there is 1 commit pending in roy
Hi Alex,
Git status after failing for all 3 repos [1].
Here is how build.properties look like after performing update.versions
target [2].
I will skip some part to move forward but update.versions is important.
[1] https://paste.apache.org/l3zs9
[2] https://paste.apache.org/0zvou
Thanks,
Piotr
What does "git status" show in the 3 repos?
The update.versions should have at least changed the build.properties file in
the repo.
You can try skipping over steps by listing the steps on the command line. You
might need to list some pre-requisite steps before or add them to the "depends"
of
Those are the steps from the script which need to be done still:
1)
2)
3)
Number #1 is failing.
czw., 3 paź 2019 o 10:41 Piotr Zarzycki
napisał(a):
> It looks like we already have:
> 1) Successfully published npm:
> https://www.npmjs.com/package/@apache-royale/royale-js
> 2) Successfully
It looks like we already have:
1) Successfully published npm:
https://www.npmjs.com/package/@apache-royale/royale-js
2) Successfully published which can be updated on the website:
https://www.apache.org/dyn/closer.lua/royale/0.9.6/binaries/apache-royale-0.9.6-bin-js.tar.gz
Thanks,
Piotr
czw., 3 p
I have used npm password from private and went trough publishing npm and
it's failed on next step update.version with the same error. Here you go
full log [1].
What will happen if I run publish npm stuff again ? I can omit that part in
the next attempt.
Om can you check whether my npm publish stu
Responses inline...
On 10/2/19, 1:37 AM, "Piotr Zarzycki" wrote:
Just to understand something. releasecandidate script is using tag instead
release branch to whole operation of increase version ?
No, the "get_head_of_rc_branches" target should get you the head.
> Hi,
>
Just to understand something. releasecandidate script is using tag instead
release branch to whole operation of increase version ?
Cause on release branch I have already version increased, so what's the
point of doing anything using tag ?
śr., 2 paź 2019 o 10:27 Piotr Zarzycki
napisał(a):
> Hi,
Hi,
I just tried releasecandidate script. It contains following steps.
One step previous was move in svn binaries from dev folder to release - I
omit that cause I did it already manually. Launching following steps I
reached release.
On Tue, Oct 1, 2019 at 8:32 AM Alex Harui wrote:
> The releasecandidate.xml script will tell you what to do on
> repository.apache.org to release the Maven stuff, and release the npm
> stuff as well. The whole point of these scripts is so you don't have to
> ask for help. If you do end up needi
Releasecandidate.xml can't do steps on repository.apache.org. It will remind
you to go there and release the staged artifacts.
-Alex
On 10/1/19, 6:55 AM, "Piotr Zarzycki" wrote:
I see that releasecandidate.xml script can help me with last steps. Does it
doing Maven releases as well ?
The releasecandidate.xml script will tell you what to do on
repository.apache.org to release the Maven stuff, and release the npm stuff as
well. The whole point of these scripts is so you don't have to ask for help.
If you do end up needing help, then the scripts need improving. We want to
c
I see that releasecandidate.xml script can help me with last steps. Does it
doing Maven releases as well ?
That steps includes also push to svn - I just did it manually, so I will
probably comment out commit part and run script. - I think tomorrow.
wt., 1 paź 2019 o 09:29 Piotr Zarzycki
napisał(a
Hi Om,
What I need to do in order to release stuff on npm. Can you do this for me
once I push release to svn ?
Thanks,
Piotr
wt., 1 paź 2019 o 09:25 Piotr Zarzycki
napisał(a):
> Hi Harbs,
>
> I think we have enough votes. I still have to gather info how actually
> release Maven artifacts. Howe
Hi Harbs,
I think we have enough votes. I still have to gather info how actually
release Maven artifacts. However I'm going to push binaries today in svn.
Thanks,
Piotr
sob., 28 wrz 2019 o 20:02 Harbs napisał(a):
> FYI, I will not be able to test the release until Wednesday.
>
> If the vote is
FYI, I will not be able to test the release until Wednesday.
If the vote is still open, I plan on testing then.
Thanks,
Harbs
> On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki wrote:
>
> Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
> yet, but will do that tomorrow or n
Hi Alex,
About Vars: I have:
- ANT_HOME
- MAVEN_OPTS
- JAVA_HOME,
- GOOG_HOME
- ROYALE_HOME
- ROYALE_COMPILER_HOME
- ROYALE_TYPEDEFS_HOME
- FLEX_HOME (I supposed this last one can be removed too, but didn't
notice
I commented
- PLAYERGLOBAL_HOME
- PLAYERGLOBAL_
What environment variables are set?
What settings did Piotr recommend and what did you actually use?
If you can post a link to the entire log it might help. For example, if you
didn't see the ASCII art for "FLEX" then the extensions did not kick in. By
the time you get around to building a The
Hi,
ok, seems the latest test didn't work. it failed here:
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:38 min
[INFO] Finished at: 201
Hi,
thanks Josh and Alex for your help on this. I finally get the approve xml
method to work on my machine :)
I need to :
- Use the latest Aprove xml
- remove my AIR_HOME and FLASH (player and debugger) env vars.
- and use the settings provided by Piotr. Although I'm making a new try now
with my
Thanks for trying it. I just updated the ApproveRoyale.xml linked to in the
vote thread to try to eliminate people getting the wrong one..
-Alex
On 9/26/19, 1:48 PM, "Josh Tynjala" wrote:
Thank you, Alex! I tried your changes with adobe/royale artifacts deleted
from .m2, and I was ab
Thank you, Alex! I tried your changes with adobe/royale artifacts deleted
from .m2, and I was able to get through both js and js-swf builds
successfully.
Carlos, I think that these changes will allow you to get through the
process now too.
For everyone's convenience, here's a link to the latest A
Yeah, I just saw that myself. That's because I didn't merge in my changes
correctly. I just pushed one that seems to be working better.
-Alex
On 9/26/19, 10:27 AM, "Josh Tynjala" wrote:
Thanks, Alex. The ApproveRoyale.mxml from the latest release/0.9.6 is
working for me if I delete
Thanks, Alex. The ApproveRoyale.mxml from the latest release/0.9.6 is
working for me if I delete all adobe/royale artifacts from my .m2, and if I
omit -Duse-flash=true. However, with -Duse-flash=true, I'm seeing compiler
errors when Maven tries to build the SWF version of Binding.swc.
A couple of
Looks like I missed a commit. I just pushed the ApproveRoyale.xml I was using
to the release branch.
Try that one and see if it works better. It shouldn't require the workaround
you used.
Thanks,
-Alex
On 9/25/19, 4:16 PM, "Josh Tynjala" wrote:
To get the system property working with
To get the system property working with ApproveRoyale.xml, I added the
following line to each of the mvn commands in my local copy of
ApproveRoyale.xml:
This should work for anyone using Bash's yes command to quickly approve the
license headers (after you've already done it once manually, of cou
I deleted all com.adobe artifacts in my Maven .m2 folder, and I can see the
prompt to accept the license for the Adobe dependencies.
The build output suggests that you can set a system property to accept the
agreement, so I tried adding that property to my command, like this:
ant -e -f ApproveRoy
It depends on what you want to test.
If you want to test the js-only (no Adobe stuff) paths, then yes, you need to
make sure there are no Adobe environment variables:
AIR_HOME
PLAYERGLOBAL_HOME
FLASHPLAYER_DEBUGGER
If you want to test with the Adobe stuff, then you will need to set all 3
envir
Hi Josh,
you're right, I have AIR_HOME in my .bash_profile set, since I left all env
vars set (flex, air, playerglobal, royale)
So,
- should I remove some more in addition to AIR_HOME?
additionally:
- Should I use the settings from Piotr too?
- Should I add -Dgenerate.swf.swcs=true and -Dski
Carlos,
Can you check to see if the AIR_HOME environment variable is set or not?
If I'm understanding the logic in ApproveRoyale.xml, then you need to
ensure that AIR_HOME is *NOT* set, unless you include -Duse-flash=true in
your command. If AIR_HOME is set, then you should clear it. It may also
Let's wait to Alex, I suppose something was not working as expected with
the changes he did yesterday to solve this issue.
El mié., 25 sept. 2019 a las 22:57, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Carlos,
>
> I can only propose copy player global in appropriate place and try a
Carlos,
I can only propose copy player global in appropriate place and try again. I
have no idea how to resolve your problem.
Thanks,
Piotr
On Wed, Sep 25, 2019, 10:37 PM Carlos Rovira
wrote:
> Hi, yes, I copied in the RC2 thread what was appearing
>
> btw, I tried again adding the proposed c
Hi, yes, I copied in the RC2 thread what was appearing
btw, I tried again adding the proposed commands with no luck. The fail is
the same as before:
Downloading from central:
https://repo.maven.apache.org/maven2/com/adobe/flash/framework/playerglobal/20.0/playerglobal-20.0.swc
[INFO]
---
By endless loop you mean that script cannot download playerglobal - Asking
for the license?
On Wed, Sep 25, 2019, 8:25 PM Carlos Rovira wrote:
> Hi
> I tried in the meanwhile with your settings and enter in the endless loop
> as in RC2
>
> I'll try to run now adding that to the command and repor
Hi
I tried in the meanwhile with your settings and enter in the endless loop
as in RC2
I'll try to run now adding that to the command and report back
El mié., 25 sept. 2019 a las 18:59, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> The same issue as it was previously. You are missin
The same issue as it was previously. You are missing playerglobal - I don't
know why at all. You can try to switch to my settings - don't forget update
link to maven artifacts in it.
I'm not sure also but maybe you should try to run approve script with this
one: -Dgenerate.swf.swcs=true and -Dskip
Hi,
sorry to report that my try failed. I tried with clean .m2 and my own
settings.xml. Maybe I need to switch to the settings Piotr send to me?
as well I used the instruction provided in email: ant -e -f
ApproveRoyale.xml -Drelease.version=0.9.6 -Drc=3
ache.org/maven2/org/antlr/antlr/3.4/antlr
I'm not sure how it happened this time, but yeah we finally have. ;)
śr., 25 wrz 2019 o 17:54 Carlos Rovira napisał(a):
> Hi Piotr,
> great to see we have different threads in gmail :)
>
> El mié., 25 sept. 2019 a las 16:24, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Ok, new
Hi Piotr,
great to see we have different threads in gmail :)
El mié., 25 sept. 2019 a las 16:24, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
> yet, but will do that tomorrow or next week.
>
> śr., 25 wrz 2019
Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
yet, but will do that tomorrow or next week.
śr., 25 wrz 2019 o 16:23 Apache Royale CI Server
napisał(a):
> This is the discussion thread.
>
> Thanks,
> Piotr
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotr
This is the discussion thread.
Thanks,
Piotr
49 matches
Mail list logo