Re: Maven DIstribution

e-tag and try again and report back. Chris Am 06.05.20, 09:51 schrieb "Christofer Dutz" : Hi all, Just some background to get rid of the confusion: The "with-distribution" enables the distributions you make Maven build the archives ... if

Re: Maven DIstribution

Am 06.05.20, 09:51 schrieb "Christofer Dutz" : Hi all, Just some background to get rid of the confusion: The "with-distribution" enables the distributions you make Maven build the archives ... if you provide the distributionTargetFolder property it also builds an &q

Re: Maven DIstribution

Hi all, Just some background to get rid of the confusion: The "with-distribution" enables the distributions you make Maven build the archives ... if you provide the distributionTargetFolder property it also builds an "exploded" version, which you can directly use in an IDE. If you execute the

Re: Handling of "binary" files such as "afdesign" files?

y and put the output in the resources folder El mar., 5 may. 2020 a las 10:18, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: > Hi folks, > > the discussion on the release brought up the existence of the afdesign > files in one of the examples. &g

Handling of "binary" files such as "afdesign" files?

Hi folks, the discussion on the release brought up the existence of the afdesign files in one of the examples. These file seem to be the source project files Carlos used to create some vector-graphics, so I think it’s good that they are available in the project. However the current location

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

n source packages. IMO, what we don't want to see happen is for folks to not test RC3 and find out some big issue later. My 2 cents, -Alex On 5/4/20, 12:24 PM, "Christofer Dutz" wrote: The more I think about it it's actually not good that the groovy sc

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

mail.com> > Sent: Monday, May 4, 2020 3:04 PM > To: dev@royale.apache.org<mailto:dev@royale.apache.org> > Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7 > > Good catch Chris. I was focusing on the wrong message. > &

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

It seems these "afdesign" files are the source-projects Carlos used to create the SVG's in that blog post with. So generally they could be deleted and the example would still work, but I think it's good they are there, cause this way someone could open them in "Affinity Designer" and modify

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Just some input from the sidelines: - It shouldn't have any impact on the build if you enable/disable profiles that don't exist. All you get is a warning that tells you the profiles don't exist. - The actual failure is because the the path to the prerequisiteCheck script is windows-encoded

Re: wagon:upload problems

edits, I think we should try it, since until now all his contributions made us to go one step closer to solve this problem. Thanks El vie., 1 may. 2020 a las 10:27, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: >

Re: wagon:upload problems

that it is a module or project, and there will be difference that we have to spend time looking for. My 2 cents, -Alex I have to stop work for tonight, so will see where we are in my morning. On 5/1/20, 12:56 AM, "Christofer Dutz" wrote: Hi Yishay, r

Re: wagon:upload problems

pl royale-framework-parent” to the wagon call, but I’d like to make sure this refactor is actually necessary. Frankly, I don’t think it should have been merged in without testing the release steps. Thanks, Yishay From: Christofer Dutz<mailto:christofer.d...@c-ware.de> Sen

Re: wagon:upload problems

les and manualtests as sibling to framework. In the past all 3 of compiler, typedefs, and framework end up in the staging repo. Thus, we need to understand how staging repos work. Does it open a staging repo per IP? Thanks -Alex On 4/30/20, 2:43 PM, "Christofer D

Re: wagon:upload problems

7Ceddb911e5a3e487d495408d7ed4d34ad%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637238788166869279sdata=kqXmKbxqVlrruaSb2WVvOqLvLoa2Sj94m8A6HFBiCnE%3Dreserved=0 On 4/30/20, 12:41 PM, "Christofer Dutz" wrote: Hi folks, Just to try it out ... alm

Re: wagon:upload problems

do what it did? [1] https://paste.apache.org/tpdkh On 4/30/20, 12:41 PM, "Christofer Dutz" wrote: Hi folks, Just to try it out ... almost anyone that has setup his credentials in the settings.xml could try to deploy asjs by running: mvn clean deploy -Papache-

Re: wagon:upload problems

Hi folks, Just to try it out ... almost anyone that has setup his credentials in the settings.xml could try to deploy asjs by running: mvn clean deploy -Papache-release,apache-release,with-distribution,option-with-swf On the develop branch. It would automatically build the same artifacts,

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

om Yishay's home, so it could be a potential timesaver to upload from the CI server. To me and hopefully others, not requiring Macs and not hogging your local computer and network bandwidth are useful improvements. -Alex On 4/29/20, 2:14 AM, "Christofer Dutz" wrote:

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

Ok ... there you go ... haven't tested it though I created a PR for each repo ... be sure that you enable the "_releasesteps-upload-release-to-staging" profile or it will probably not pick up the config. Chris Am 29.04.20, 17:00 schrieb "Christofer Dutz" :

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

I'll whip up a PR. Chris Am 29.04.20, 15:24 schrieb "Yishay Weiss" : Can you guide us through upgrading to 3.4.0? From: Christofer Dutz<mailto:christofer.d...@c-ware.de> Sent: Wednesday, April 29, 2020 9:47 AM To: dev@royale.apache.org<mailto:dev@royale.apac

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

Oh gee ... ok ... so instead of trying to find out what the problem is, you're adding a bunch of additional steps to the already extremely lengthy list? I mean it's not that the internet and especially the maven infrastructure hates you guys and therefore discriminates you. I would assume

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

idual folders -Alex On 4/27/20, 3:07 AM, "Christofer Dutz" wrote: Hi all, a week ago a new version of Wagon was released ... perhaps worth updating to 3.4.0? Chris Am 27.04.20, 11:

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

, 10:24 AM, "Yishay Weiss" wrote: I didn’t get that it was the number of tries per artifact. That could indeed be useful. From: Christofer Dutz<mailto:christofer.d...@c-ware.de> Sent: Tuesday, April 28, 2020 8:04 PM To: dev@royale.apache.org<

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

to package before uploading and resume on failure. There are lots of messages of transfers of ~40 bytes. I don’t know if they’re opening a separate connection for each of these transfers but it seems inefficient and it’s evidently fragile. Thanks, Yishay From: Christofer Dutz<mailto

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

Providers 3.4.0. How would we get the Wagon we use to use Wagon Providers? When the upload fails, Yishay is not given a away to start from the point of failure ("maven -rf ..."). I have suggested using Wagon to upload individual folders -Al

Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

Hi all, a week ago a new version of Wagon was released ... perhaps worth updating to 3.4.0? Chris Am 27.04.20, 11:58 schrieb "Yishay Weiss" : Awesome From: aha...@apache.org Sent: Monday, April 27, 2020 8:56:00 AM To:

Re: [royale-compiler] branch release/0.9.7 updated: Update compiler build tools version

Hi all, Just a question from the sidelines... Where does anything have to be merged at all? Usually the release branches are simply dead ends and they aren't merged back to develop. Some projects merge the release tags to master, but noone merges the release branch back to develop. That would

Re: Separate mailing list for Jenkins notifications

Hi Alex, one of the moderators can also send commands to add the email address to the list of allowed senders. So it doesn't have to be an apache email address, as far as I know. Chris Am 21.04.20, 08:44 schrieb "Alex Harui" : I have a few minutes waiting for step 11 to finish so have

Re: How did you folks get past step 007?

? This is premature in my opinion. We are still working on it, and have not announced a release. From: Christofer Dutz<mailto:christofer.d...@c-ware.de> Sent: Tuesday, April 21, 2020 9:10 AM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: Re: How did you folks get past step 007? P

Re: How did you folks get past step 007?

Ping? I mean if the builds aren't reproducible, what are the reproducible builds worth. Just want to make sure we weren't the only ones accruals respecting this self prescribed rule. Chris Von: Christofer Dutz Gesendet: Montag, 20. April 2020 10:39 An: dev

Re: Maven Plugin Problems

Hi Yishay, Well If you built the release of compiler on the ci server and did the verification on your local one, then the artifacts should exit on both. On a machine with clean maven local repo or one where you haven't built compiler yet, the artifacts don’t exist. So I would suggest you take

Re: Maven Plugin Problems

Hi Yishay, well you only have 0.9.7 if you manually built the release version yourself ... I think Apache only knows about 0.9.6, 0.9.7-SNAPSHOT and 0.9.8-SNAPSHOT. Chris Am 20.04.20, 19:03 schrieb "Yishay Weiss" : From: Yishay Weiss Sent:

How did you folks get past step 007?

Hi all, so as I saw you’re at one of the steps in the framework repo, I thought: “How on earth did they get past 007?” So I dug up the email, set my java version to the same as on the server and ran the scripts … ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7

Re: [royale-compiler] branch develop updated: fix build

cents, -Alex On 4/17/20, 11:13 AM, "Christofer Dutz" wrote: Hi all. So what is the difference between code and documentation? I would say none. So if I would be asked, I'd probably add the headers to all md, adoc, whatsoever files. Chris Am 17.04.20, 19:

Re: [royale-compiler] branch develop updated: fix build

Hi all. So what is the difference between code and documentation? I would say none. So if I would be asked, I'd probably add the headers to all md, adoc, whatsoever files. Chris Am 17.04.20, 19:02 schrieb "Carlos Rovira" : totally El vie., 17 abr. 2020 a las 18:58, Yishay Weiss ()

Re: [DISCUSS] Discuss Release Apache Royale 1.2.0

Geee ... why does everything have to go around in circles here? Is it always about having the last word? At least it feels this way. (and yes, by replying I'm participating. I do see that, but I just wanted to get back on track ... and having started the discussion I felt I should) In this case

Re: [DISCUSS] Discuss Release Apache Royale 1.2.0

Royale not sticking to the typical 72 hour voting timeframe? Chris Am 15.04.20, 10:29 schrieb "Carlos Rovira" : Hi Yishay, build tools and jburg was never released on its own before. Always was part of the global royale release. This is the first time we do this.

Re: Royale Compiler Build Tools Release Step 002 Succeeded

Hi Yishay, ok ... we never talked about comparing the JavaDocs ... just the binary artifacts. I updated the maven-javadoc-plugin to 3.2.0 which is the first reproducible version. Please feel free to merge the PRs (I also disabled the Javadoc in the typedefs as this doesn't make any sense

Re: About Releasing 0.9.7

Hi Alex, well it seems that with JGit you were having a problem before and you sent the folks a patch to fix that which they never accepted as I think they were missing a testcase for it. So the version on the server was a manually patched one. I think this isn't ideal for releases same

Re: Royale Releases

> are needed and welcome. > > > > > > More and better tests are welcome. > > > > > > Do we have agreement? It sounds like it. So I will now be > spending > > my > > > evenings on t

Re: Royale Releases

r me. It's better than nothing however. Chris [1] https://en.wikipedia.org/wiki/Code_coverage Am 02.04.20, 15:39 schrieb "Christofer Dutz" : Hi folks, I would say we have coverage for both maven ant equally as we're building the same code. However we are m

Re: Royale Releases

>> plan to use soon as I can. I think is a great idea, since you get a >> Firefox >>> running test interface of the real use of some concrete royale code. I >>> think passed until now unnoticed by all of us, and seems a powerful tool. >>> There's

Re: Royale Releases

Hi Alex, just a point you are bringing up: "Code coverage". I strongly dislike the idea of "asjs" effectively being the test for the compiler. The reasoning behind this is: yes you do get more code covered, but only the happy-path (ideally) and even if things go wrong, the end results aren't

Re: [DISCUSS] Coming back to collect requirements for the release process

> > I feel like we’re still not talking about the same thing. The > scenario > > as I understood it is about local changes, in which case the CI wouldn’t > > help. > > > > >10) The distribution built by any build system should pr

Re: [DISCUSS] Coming back to collect requirements for the release process

process have not > > > stepped up to examine the build-tools release candidate, one of the > > > outcomes of these Maven changes that you wanted to see. Instead, this > > > effort has cost me considerable time that could have been use > elsewhere.

Re: [DISCUSS] Coming back to collect requirements for the release process

> > Hi Chris, > > thanks. I revise and for me is totally fine :) > > > El lun., 30 mar. 2020 a las 9:33, Harbs () > escribió:

Re: [DISCUSS] Coming back to collect requirements for the release process

gt; find it. Can you expand on this scenario? If this is the > only difference > > you and Chris have I think it’s worth focusing on it. > > > > On 3/30/20, 2:17 AM, "Carlos Rovira" < > carlosrov...@apache.org> wrote:

Re: [DISCUSS] Coming back to collect requirements for the release process

a" wrote: > > Hi Chris, > > thanks. I revise and for me is totally fine :) > > > El lun., 30 mar. 2020 a las 9:33, Harbs () > escribió:

Re: [DISCUSS] Coming back to collect requirements for the release process

Forgot to mention: ... as long as all the artifacts are generated: - Maven artifacts in repos.apache.org - Source bundle - Binary Distribution for use in IDEs Chris Am 31.03.20, 18:55 schrieb "Christofer Dutz" : Well you could make the verification part of the ve

Re: [DISCUSS] Coming back to collect requirements for the release process

me is totally fine :) > > > El lun., 30 mar. 2020 a las 9:33, Harbs () > escribió: > > > Thanks for that. The Google Doc is a great initiative! > >

Re: [DISCUSS] Coming back to collect requirements for the release process

g on it. > > On 3/30/20, 2:17 AM, "Carlos Rovira" wrote: > > Hi Chris, > > thanks. I revise and for me is totally fine :) > > > El lun., 30 mar. 2020 a las 9:33, Harbs () >

Re: [DISCUSS] Coming back to collect requirements for the release process

:) > > > El lun., 30 mar. 2020 a las 9:33, Harbs () > escribió: > > > Thanks for that. The Google Doc is a great initiative! > > > > Harbs > > > > > On Mar 30, 2020, at 10:26 AM, Christofer Du

[DISCUSS] Coming back to collect requirements for the release process

Hi all, as the discussion has gone back to: “the release should be as in the 13 steps”, I’d like to re-focus on the probably more important parts: I already started writing up a list of requirements and options to achieve them:

Re: Can't Push to GitHub

-compiler.git https://gitbox.apache.org/repos/asf/royale-typedefs.git https://gitbox.apache.org/repos/asf/royale-asjs.git Chris Am 29.03.20, 13:39 schrieb "Yishay Weiss" : Hi Chris, I’m not familiar with GitBox. How does that work? Thanks. From: Chris

Re: [Vote] Release Compiler Build Tools 1.2.0

- Tested Tour De Jewel example working as expected El sáb., 28 mar. 2020 a las 12:23, Carlos Rovira () escribió: > Ok Thanks Chris, > I think now is fixed :) > > El sáb., 28 mar. 2020 a las 11:26, Christofer Dutz (< > christofer.d...

Re: Can't Push to GitHub

Hi Yishay, Try pushing to gitbox instead? Chris Am 29.03.20, 13:24 schrieb "Yishay Weiss" : This looks like a problem in my network connection. GitHub is especially slow but so are other sites. From: Yishay Weiss Sent: Saturday, March 28, 2020

Re: [DISCUSS] Discuss Release Compiler Build Tools 1.2.0

Hi All, so I had another look ... and it does contain one class which was donated by Adobe: UnknownTreePatternInputOutput Chris Am 29.03.20, 09:48 schrieb "Christofer Dutz" : Hi Alex, Well actually this code was written by me (I think). The build tools cont

Re: [DISCUSS] Discuss Release Compiler Build Tools 1.2.0

Hi Alex, Well actually this code was written by me (I think). The build tools contained Java goals that do things the Ant build did otherwise. So I think ist's just used by the maven build and all has been developed at apache. Chris Von: Alex Harui Gesendet:

Re: [Vote] Release Compiler Build Tools 1.2.0

Hi Carlos, not checked the release yet however Apache requires sha512 checksums and doesn't like md5 and sha1 ... Please check that you're sort of doing it like described here: https://plc4x.apache.org/developers/release/release.html Chris Am 28.03.20, 11:16 schrieb "Carlos Rovira" : Hi

Re: Instructions for releasing with Maven

-freeze phase and you just want to push it out. So you could do a branch, but I don't see the need to do so. Chris Am 27.03.20, 19:39 schrieb "Alex Harui" : OK, thanks. Why is a branch not needed in this case? -Alex On 3/27/20, 11:25 AM, "Christof

Re: Instructions for releasing with Maven

eate an RC for 0.9.7. What steps will he have to execute for compiler-build-tools? And, to make sure you didn't miss this question: Where would he add the parameters to try to create reproducible binaries? Thanks, -Alex On 3/27/20, 11:14 AM, "Christof

Re: Instructions for releasing with Maven

> C, > > > El vie., 27 mar. 2020 a las 12:33, Harbs () > escribió: > > > Yes. > > > > > On Mar 27, 2020, at 2:30 PM, Christofer Dutz < > christofer.d...@c-ware.de> &

Re: Instructions for releasing with Maven

or him > We now need to do the official release > so the source bundles will be downloaded from the official apache > repository > > HTH > > C, > > > El vie., 27 mar. 2020 a las 12

Re: Instructions for releasing with Maven

> > On Mar 27, 2020, at 2:30 PM, Christofer Dutz > wrote: > > > > Does that explain things? > > -- Carlos Rovira https://nam04.safelinks.protection.outlook.com

Re: Instructions for releasing with Maven

so the source bundles will be downloaded from the official apache repository HTH C, El vie., 27 mar. 2020 a las 12:33, Harbs () escribió: > Yes. > > > On Mar 27, 2020, at 2:30 PM, C

Re: Instructions for releasing with Maven

Hi Chris, You downloaded from where ? pt., 27 mar 2020 o 12:31 Christofer Dutz napisał(a): > And I just: > > 1) downloaded and unpacked the distribution created by the release process. > 2) configured VScode to use that directory as SDK >

Re: Instructions for releasing with Maven

And I just: 1) downloaded and unpacked the distribution created by the release process. 2) configured VScode to use that directory as SDK 3) Built an application and it worked perfectly. Chriis Am 27.03.20, 12:17 schrieb "Christofer Dutz" : And I just 1) Down

Re: Instructions for releasing with Maven

. In case of Royale ... you are technically doing 3 releases as there are 3 repos involved. Does that explain things? Chris Am 27.03.20, 12:21 schrieb "Harbs" : What exactly is source-bundle in Maven land? > On Mar 27, 2020, at 2:16 PM, Christofer Dutz wrote: &

Re: Instructions for releasing with Maven

> I think after this release this would be good to bring and discuss, I > think it would be a huge simplification for this project :) > > El vie., 27 mar. 2020 a las 10:48, Christofer Dutz (< > christofer.d...@c-ware.de>) escribió: &g

Re: Instructions for releasing with Maven

t official 0.9.7 in few hours Thanks! El vie., 27 mar. 2020 a las 10:29, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: > Hi All, > > As I don’t have access to a WIKI … here comes a step by step guide for >

Instructions for releasing with Maven

Hi All, As I don’t have access to a WIKI … here comes a step by step guide for releasing Royale with Maven: Prepare: export FLASHPLAYER_DEBUGGER="/Users/some-username/Devtools/Adobe/Flash/FlashPlayer-32.0/Flash Player.app/Contents/MacOS/Flash Player Debugger"

Re: Maven Distribution SDK fixed and working for IDEs

ug/App.swf > : -compiler.targets=SWF > : command line Error: unable to open > '/themes/JewelTheme/src/main/resources/defaults.css'. > : 0.676110556 seconds > : Compilation of TourDeJewel finished. > > > El jue., 26 mar. 2020 a las 18:20, Christofe

Re: Maven Distribution SDK fixed and working for IDEs

> on > > > the > > > > > > > console at all? > > > > > > > > > > > > > > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira < > > > carlosrov...@apache.org > > > > > > > > > >

Re: Releasing: Finally giving up

ANT build will be launched by maven and produce IDE ready SDK - which could be tested in that way. Thanks, Piotr czw., 26 mar 2020 o 13:38 Christofer Dutz napisał(a): > Hi Piotr, > > generally the build is currently already in a stat

Re: Releasing: Finally giving up

o is recommended but not required, the same as the actual CI server (but this one should be less recommended since is a royale-only practice not seen in any other place). What's the important thing is to release, do it, and do it easily and often. Thanks El jue., 26 mar. 2020 a las 8:24, Christofer Dutz

Re: Releasing: Finally giving up

Ok, I'll write this a last time as I do feel like we're going in circles and will from now on not participate in any discussion involving releasing on a CI server. A correct Maven release would use (There will be some additional profiles to activate to include all modules) 1) the "mvn

Re: Releasing: Finally giving up

ositions and have clear what we can expect in this problematic releasing problem, since is what will make us get more traction or in reverse, end loosing more users and maybe die in the way. Thanks Carlos El mié., 25 mar. 2020 a las

Releasing: Finally giving up

Hi all, after 3-4 days of some times 10-16 hours of working on getting the “process” running, I’m finally giving up. We managed to fix a lot of issues in the way the steps were setup and managed to get to step 7 however there’s no getting past that. The problem are the reproducible builds.

Re: Findings and Changed to the release steps and the CI configuration.

call it a night. Chris Am 24.03.20, 21:50 schrieb "Carlos Rovira" : Thanks for the huge effort Chris, I think it's being tough these days. Let's get rest and see if tomorrow we can get over step 7 :) Carlos El mar., 24 mar. 2020 a las 21:37, Chris

Re: Findings and Changed to the release steps and the CI configuration.

. Chris Am 24.03.20, 20:34 schrieb "Christofer Dutz" : Hi Alex, Well it seems as if the "mod" attribute in the catalog.xml is generated from the zipfile entry xmlWriter.writeAttribute(ATTR_MOD, String.valueOf(file.getLastModified()));

Re: Findings and Changed to the release steps and the CI configuration.

try it myself, so going with that now :) El mar., 24 mar. 2020 a las 15:40, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: > Hi Alex, > > I added a call to set a fixed timezone to the simpleda

Re: Findings and Changed to the release steps and the CI configuration.

Hi Alex, I added a call to set a fixed timezone to the simpledateformat in the SWCWriter ... could you please review this? Chris Am 24.03.20, 15:26 schrieb "Christofer Dutz" : Hi all, so today we made progress ... not only did we fix the version skipping we

Re: Findings and Changed to the release steps and the CI configuration.

. Thanks, Chris Am 24.03.20, 09:36 schrieb "Christofer Dutz" : Hi Alex, I had another look ... I think the version skips one is in step 001a ... There the job checks out develop, applies the update to the new version of the build tools and jburg types, but then this

Re: Findings and Changed to the release steps and the CI configuration.

ote emails by copying other CI steps. I use a Mac and thought I got all binaries to match from the . I'm not sure what properties you are referring to. I'm done for tonight. Will catch up in my morning. -Alex On 3/23/20, 11:15 PM, "Christof

Re: Findings and Changed to the release steps and the CI configuration.

that case it would have been impossible to have a release manager not using Java 8 on a Windows machine. (My changes recently never touched this) Chris Am 23.03.20, 22:59 schrieb "Alex Harui" : On 3/23/20, 2:29 PM, "Christofer Dutz" wrote: H

Re: Findings and Changed to the release steps and the CI configuration.

and break that down into steps on the CI server. HTH, -Alex On 3/23/20, 12:30 PM, "Christofer Dutz" wrote: Another thing we just discovered. The current setup seems to mess up the branches: - 001 creates the branch and updates develop

Re: Ways for dumping the effective-configuration of the compiler?

file path, and it will output the full configuration used in the current session. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Sat, Mar 21, 2020 at 7:50 AM Christofer Dutz wrote: > Hi all, > > is there a way to dump the eff

Re: Findings and Changed to the release steps and the CI configuration.

ws stores a personal access token in Windows Crendetials, so the RM is responsible to remove it when finish all the operations. El lun., 23 mar. 2020 a las 19:44, Alex Harui () escribió: > > > On 3/23/20, 11:32 AM, "Christofer Dutz"

Re: Findings and Changed to the release steps and the CI configuration.

after his release work. Chris Am 23.03.20, 19:44 schrieb "Alex Harui" : On 3/23/20, 11:32 AM, "Christofer Dutz" wrote: Hi Alex, I did check and I didn't directly find any .git .ssh or whatsoever directories ... do you have an I

Re: Findings and Changed to the release steps and the CI configuration.

schrieb "Alex Harui" : On 3/23/20, 9:31 AM, "Christofer Dutz" wrote: Hi Alex, regarding the credentials ... I was just surprised that Carlos didn't have to provide any credentials to push on the CI machine itself. Are you sayi

Re: Findings and Changed to the release steps and the CI configuration.

-tools. Currently we're running step 3 with updated build tools. Let's see if the output then works as we want it to. Chris Am 23.03.20, 17:11 schrieb "Alex Harui" : On 3/23/20, 6:01 AM, "Christofer Dutz" wrote: Here come some things we n

Findings and Changed to the release steps and the CI configuration.

Here come some things we noticed while working on the release steps: * All Jenkins release emails were discarded by my email server, I had to use ponymail to read them Observations: * Step 001 * How can you push without providing credentials on the CI server? It seems that

Re: Memory on the CI server

Hi all, I had a hunch and had a look at windows virtual memory settings and indeed virtual memory was turned off ... turning it on seems to help. So keep your fingers crossed ;-) Chris Am 23.03.20, 10:56 schrieb "Christofer Dutz" : Hi all, as you can see we’re hav

Memory on the CI server

Hi all, as you can see we’re having issues with the release steps … unfortunately we’ve run into one we don’t know how to handle. It seems the CI server has so little memory that Windows is killing the Java process at random times. You can usually see this in form: [DEBUG]

Re: Maven Distribution SDK fixed and working for IDEs

you try again and confirm if all is ok now? > > thanks > > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (< > christofer.d...@c-ware.de>) escribió: > > > Hi Piotr, > > > > I had a look and you are rig

Re: Maven Distribution SDK fixed and working for IDEs

Hi Piotr, I had a look and you are right ... even if this only seems to happen if you haven't built the typedefs on your machine that day before building the distribution. I just pushed a PR that should fix this. Chris Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" : Hi Carlos,

Re: Requirements for Releases

On 3/21/20, 8:19 AM, "Christofer Dutz" wrote: Well in theory the jars in the compiler built by Maven should also work with Ant and the other way around and also should it be possible to use the SWCs build by Maven with Ant. Did you mean "It should be

Re: Requirements for Releases

to test a binary release artifacts/package with their local changes, not just the individual jars/swcs. To be picky, only the Maven artifacts need to be usable by Maven, and only the Ant artifacts need to be usable by Ant, although I'm assuming that's what you meant. HTH,

Re: Requirements for Releases

ts/package with their local changes, not just the individual jars/swcs. To be picky, only the Maven artifacts need to be usable by Maven, and only the Ant artifacts need to be usable by Ant, although I'm assuming that's what you meant. HTH, -Alex On 3/21/20, 2:20 AM, "

Ways for dumping the effective-configuration of the compiler?

Hi all, is there a way to dump the effective configuration used in the compiler in order to see if there are any differences between the maven and the ant configutation? I did find something that sounds like that, but couldn’t find out how to use it. Configuration seems to support some sort

Re: Requirements for Releases

rn whether actually you need to do or not. [1] https://github.com/apache/royale-asjs/wiki/Release-Steps-Jobs-On-Jenkins Thanks, Piotr sob., 21 mar 2020 o 12:17 Christofer Dutz napisał(a): > Hi Yishay, > > I am working on the existin

<    1   2   3   4   5   >