Re: [Discuss] Start release process 0.9.3

The weirdest thing is that I cannot use anymore sourcetree after that update. I'm getting wrong password and user name on other repositories which are private. git version 2.19.1.windows.1 However after update I was able to continue process of release. Update fixes for me some problems with gpg.

Re: [Discuss] Start release process 0.9.3

I was able to delete the tag. What version of Git are you using? I'm concerned other problems may arise. If you run into a problem like this again, you might want to try just giving up on rc1 and calling it rc2 so the tag names don't conflict. HTH, -Alex On 10/12/18, 9:42 AM, "Piotr

Re: [Discuss] Start release process 0.9.3

I logged in without the problem. Om was on the stage where he was able to upload something. I hope he will respond. Maybe he had some special settings in file. Piotr pt., 12 paź 2018 o 17:55 Alex Harui napisał(a): > Hi Piotr, > > Yes, I have the same settings (username aharui, password is my

Re: [Discuss] Start release process 0.9.3

Hi Piotr, Yes, I have the same settings (username aharui, password is my apache password). Try logging into repository.apache.org from your browser. I don't know for sure that repository.a.o uses LDAP, it might be I just used the same username and password to be lazy). I will also say that

Re: [Discuss] Start release process 0.9.3

I would like to ask also someone for delete tag org.apache.royale.compiler-0.9.4-rc1 - I'm not sure what has happened but after updating git I cannot do that. I can commit stuff, but doing delete tag I'm getting remote: Permission to apache/royale-compiler.git denied to piotrzarzycki21. fatal:

Re: [Discuss] Start release process 0.9.3

I was too focused on the credentials and didn't notice that your settings didn't have HTTPS. apache.releases.https aharui ... apache.snapshots.https aharui ... HTH, -Alex On 10/12/18,

Re: Proxy method calls with RemoteObject

Hi Carlos, The Maven build for the RO example was using a template and the compiler wasn't using the right variable. In MXRoyale projects the main class name is not the same as the MXML file name because we generate a SystemManager subclass like Flex does. Also, the MXRoyale.swc wasn't

Re: [Discuss] Start release process 0.9.3

You could ask on the Maven mailing lists. HTH, -Alex On 10/12/18, 2:05 PM, "Piotr Zarzycki" wrote: Yes! A lot was successful. It looks like it is total random. Probably some kind of problem with connection, but I doubt that is on my sight. I notice one thing when I click for the

Re: Proxy method calls with RemoteObject

Hi Carlos, It is not possible for me to have tested every feature of RemoteObject. I'm sure there are bugs. Debug into the code and fix some of them. I've hardly ever used RemoteObject so you know better than me what it can do. Regarding VSCode, those errors sound like it is not using the

Re: Proxy method calls with RemoteObject

VSCode is using released version of the compiler, that's why I have started whole process to provide for Josh new version. pt., 12 paź 2018 o 18:06 Alex Harui napisał(a): > Hi Carlos, > > It is not possible for me to have tested every feature of RemoteObject. > I'm sure there are bugs. Debug

Re: [Discuss] Start release process 0.9.3

Yes! A lot was successful. It looks like it is total random. Probably some kind of problem with connection, but I doubt that is on my sight. I notice one thing when I click for the first time on the link to the central repository - I was in a connecting state forever. I had to refresh website,

Re: [Discuss] Start release process 0.9.3

Unfortunately I got the same result as OM :( Something is really wrong with Maven central, cause I can't believe that we all have bad internet connection. :) https://paste.apache.org/eqN9 Piotr pt., 12 paź 2018 o 19:14 Piotr Zarzycki napisał(a): > The weirdest thing is that I cannot use

Build failed in Jenkins: royale-asjs_MXTests #52

See Changes: [aharui] need defaults.css -- [...truncated 1.96 MB...] [mxmlc] using source file:

Re: [Discuss] Start release process 0.9.3

Piotr, Did any transfers succeed? -Alex On 10/12/18, 1:02 PM, "Piotr Zarzycki" wrote: Unfortunately I got the same result as OM :( Something is really wrong with Maven central, cause I can't believe that we all have bad internet connection. :)

Re: [Discuss] Start release process 0.9.3

No, some people think the script was trying to upload the RC to Maven Central instead of repository.apache.org. From my reading of the logs, you had a problem downloading a Maven plugin from Maven Central which is allowed, while Om was having trouble uploading to repository.apache.org. I

Re: [Discuss] Start release process 0.9.3

Hi Jason, I think Piotr's failure was an attempt to download a dependency of a Maven plugin which should come from Maven Central. Om's errors were from uploading to repository.a.o and not Maven Central. I found this article about proxies and Maven:

Re: [Discuss] Start release process 0.9.3

Sent from my iPhone > On Oct 12, 2018, at 2:33 PM, Guild, Jason A (DOT) > wrote: > > Forgive my asking perhaps silly questions. +1 > > Why in the world does the Royale release script have a dependency on > publishing directly to Maven Central? That is likely against Apache Release

Re: [Discuss] Start release process 0.9.3

Alex, I'm not running behind the proxy. Hi Dave, We are publishing only RC. Why it is against? Piotr On Sat, Oct 13, 2018, 1:05 AM Dave Fisher wrote: > > > Sent from my iPhone > > > On Oct 12, 2018, at 2:33 PM, Guild, Jason A (DOT) < > jason.gu...@alaska.gov> wrote: > > > > Forgive my

Jenkins build is back to normal : royale-asjs_MXTests #53

See

Re: [Discuss] Start release process 0.9.3

So the difference is that when we vote successful y for release we are uploading manually those artifacts? Automatic is not allowed? This is how I understand. Piotr On Sat, Oct 13, 2018, 7:40 AM Piotr Zarzycki wrote: > Alex, > > I'm not running behind the proxy. > > Hi Dave, > > We are

Re: [Discuss] Start release process 0.9.3

I my problems were with downloading plugin maybe it was temporary. I could try again. On Sat, Oct 13, 2018, 7:47 AM Piotr Zarzycki wrote: > So the difference is that when we vote successful y for release we are > uploading manually those artifacts? > > Automatic is not allowed? This is how I

Re: [Discuss] Start release process 0.9.3

Forgive my asking perhaps silly questions. Why in the world does the Royale release script have a dependency on publishing directly to Maven Central? Doesn't Apache maintain its own Maven repository of apache-produced artifacts? Isn't that what repo.maven.apache.org is? Why can't Royale

Re: [Discuss] Start release process 0.9.3

Alex, Om, I'm a bit farther. I had a lot of problems on my sight with gpg, but I was able to configure it properly in GitBash. I reached point with artifacts upload. It's failed cause it looks like my password was incorrect. I would like to make sure that I'm having similar configuration as you.

Re: [Discuss] Start release process 0.9.3

Hi, @Piotr, I know all you're talking about, and that's ok, not saying at all that you must make release in a day. The fact is we have a problem in various points, and is not anyone guilty, just the technologies we are using and that we want to make many things happen: 1.- The release process,

Fwd: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1 deleted (was be658de)

Hi, this is not the same my git client is doing? @Piotr, it was intentional? if not maybe is a global problem and not something related to my Sourcetree doing things in its own thanks -- Forwarded message - From: Date: vie., 12 oct. 2018 a las 8:39 Subject: [royale-typedefs]

Re: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1 deleted (was be658de)

No this is part of release process which I'm running. This was done for purpose using script. Piotr pt., 12 paź 2018 o 10:50 Carlos Rovira napisał(a): > Hi, > > this is not the same my git client is doing? > @Piotr, it was intentional? if not maybe is a global problem and not > something

Jenkins build is back to normal : royale-asjs_jsonly #1729

See

Build failed in Jenkins: royale-asjs_jsonly #1728

See Changes: [piotrzarzycki21] Test commit to check access to the repository -- [...truncated 848.72 KB...] [junit] Tests run: 1,

Re: Proxy method calls with RemoteObject

Hi Alex, I see you fixed poms and now all is building correctly in maven in my .m2 with 0.9.5-SNAPSHOT. I remove all .m2 artificats to build from a clean state. Thanks, since all is now more clear. When I tried to run the MX RO example build with maven it fails with this: TypeError: null is not

Re: Proxy method calls with RemoteObject

Hi Alex, while example in mx doesn't work form me as I reported in latest email (due to *viewBead.beforeLayout* error), I was able to make MX RO work on a custom simple example I'm creating as a duplicate of the old net RO test. This are my findings: 1.- I can't get event result working at