Re: Maven DIstribution

FWIW, I added -DdistributionTargetFolder= and still the same failure. On 5/5/20, 4:29 PM, "Alex Harui" wrote: Maybe. I can't find how to do that in the instructions. I assumed it would end up in a "target" folder. On 5/5/20, 3:09 PM, "Piotr Zarzycki" wrote:

Build failed in Jenkins: royale-compiler-integration-tests #871

See Changes: -- [...truncated 47.00 KB...] [junit] [junit] May 06, 2020 5:17:20 AM

RE: Maven DIstribution

I’m close to starting a vote on rc4. I need to know whether or not to hold up the release for this. Is this something we need in 0.9.7 or can it wait for 0.9.8 ? Thanks. From: Alex Harui Sent: Wednesday, May 6, 2020 2:29:19 AM To: dev@royale.apache.org

Build failed in Jenkins: royale-asjs-agent2 #69

See Changes: -- [...truncated 2.05 MB...] tweak-for-jsonly: ide: post-build: [mkdir] Created dir:

Release Step 013 Succeeded

Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and that you have PlayerGlobal installed under /11.7/playerglobal.swc >From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.7 -Droyale.swc-date="06/05/20 9:06 -0800"

Build failed in Jenkins: royale-asjs-agent2 #68

See Changes: -- [...truncated 2.05 MB...] tweak-for-jsonly: ide: post-build: [mkdir] Created dir:

Re: Maven DIstribution

Maybe. I can't find how to do that in the instructions. I assumed it would end up in a "target" folder. On 5/5/20, 3:09 PM, "Piotr Zarzycki" wrote: Shouldn't you add path where distribution will be saved? On Tue, May 5, 2020, 7:25 PM Alex Harui wrote: > It may be too

Re: Maven DIstribution

Shouldn't you add path where distribution will be saved? On Tue, May 5, 2020, 7:25 PM Alex Harui wrote: > It may be too early in the morning for me, but I switched to the > release/0.9.7 branch in all 3 repos, did a "mvn clean install" all of them, > then back in royale-asjs I ran > "mvn

Build failed in Jenkins: royale-asjs-agent2 #67

See Changes: [greg.dove] Add another test that relates to the location of the 'replacement' -- [...truncated 2.05 MB...] tweak-for-jsonly:

Build failed in Jenkins: royale-compiler-integration-tests #870

See Changes: -- [...truncated 46.09 KB...] [junit]

Jenkins build is back to normal : royale-asjs #1159

See

Build failed in Jenkins: royale-asjs-agent2 #66

See Changes: [greg.dove] Fix empty XMLList assignment to XML, added 2 tests [greg.dove] More tests and fix for other variations of XMLList assignment.

Build failed in Jenkins: royale-asjs #1158

See Changes: [carlosrovira] rat-check: exclude src/assets/** like *.afdesign or other files that [carlosrovira] jewel-datagrid: solve focus issue between column and listArea

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

See

Release Step 011 Succeeded

Warning: this step requires a secret key, so it should not be performed on the CI server. It's probably best to perform it on your PC. >From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip

Maven DIstribution

It may be too early in the morning for me, but I switched to the release/0.9.7 branch in all 3 repos, did a "mvn clean install" all of them, then back in royale-asjs I ran "mvn -Pwith-distribution clean install" and got an error: Failed to create assembly: Error adding file to archive:

Release Step 010 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.7-rc4 You will need your Apache/Github username and 2FA token.

Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant

Release Step 006 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.7-rc4 You will need your Apache/Github username and 2FA token.

Re: Issue with rowHeight and big amount of data in cells

Carlos, In "1" are you saying that each row would be a HeaderList type of object ? - This is your idea? wt., 5 maj 2020 o 17:04 Carlos Rovira napisał(a): > Hi Piotr, > > I was trying to expose a plan to do and I see mainly two routes: > > 1 List/VirtualList > 2 Table (will need VirtualTable

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Ysihay, to be as short as possible, for me is like if we are making build systems suffer due to release needs (that I at least do not see as a real need), or at least is what I understand. I think build is over release. At the end release is a need to put some concrete bytes for public

Re: Issue with rowHeight and big amount of data in cells

Hi Piotr, I was trying to expose a plan to do and I see mainly two routes: 1 List/VirtualList 2 Table (will need VirtualTable too) If we go 1 (List/VirtualList), then will have a HeaderList that is basically a DG without more implications (sorting, editing, column reordering), and I think

Release Step 003 Succeeded

>From the royale-compiler repo: 1. Run: ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7 This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

>And Alex, considering the intensity of you insisting everything to be >reproducible on Ant and Maven and all sorts of >additional hoops Apache is not >even asking for, it puzzles me how you could even consider releasing something >>that doesn't build with one of the two equally supported

Release Step 002 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.7-rc4 You will need your Apache/Github username and 2FA token.

Re: Issue with rowHeight and big amount of data in cells

Carlos, Unfortunately I don't understand which of your points resolve issue from this email thread. Thanks, Piotr wt., 5 maj 2020 o 14:47 Carlos Rovira napisał(a): > Hi, > > thinking about this a bit more: > > * Basic components are List and VirtualList > * Then a HeaderList could be next

Re: Issue with rowHeight and big amount of data in cells

Hi, thinking about this a bit more: * Basic components are List and VirtualList * Then a HeaderList could be next step by just incorporating a Header (There will be a Virtual version too) * Next DataGrid could be a HeaderList that implements sorting. Maybe this will not be that hard since it

Build failed in Jenkins: royale-compiler #393

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. FATAL: java.nio.channels.ClosedChannelException

Re: Issue with rowHeight and big amount of data in cells

Hi Carlos, Thanks for your thoughts. I believe you are right that we may have a headache in case of column reordering and sorting later on. However I'm wondering whether this problems wouldn't be less painful than current one. To me DG in current state is unusable fully for bigger amount of data

Re: Performance in lists

Hi Raúl, I think we are not dealing with height 100% in the virtual layout class. Basic and Jewel are very similar ones in that part I think. Something to look without doubt. Maybe I can fix it in a similar way I deal with percentage heights in DataGrid. Will try as I get some time. thanks

Re: Issue with rowHeight and big amount of data in cells

Hi, sorry for my late response here. flooded these days with lots of things. I think the manage of row height is a problem since it needs to sync with the rest of columns, maybe this could be big problem. About to go rows instead columns, I think that will work better for that case, but in that

Re: Performance in lists

Hi: Yishay -> debug mode Alex: Virtual List Jewel Anyway, my problem was in the height of Virtual List. With 100% height, all items in the list are displayed. If I use a fixed height, performance is good. Thanks!! El lun., 4 may. 2020 a las 21:27, Alex Harui () escribió: > Which list? Mx,

Build failed in Jenkins: royale-asjs-agent2 #64

See Changes: [carlosrovira] rat-check: exclude src/assets/** like *.afdesign or other files that -- [...truncated 2.05 MB...]

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

Hi, just commit that change El mar., 5 may. 2020 a las 10:49, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: > Hi Carlos, > > I have no objections to that ... however then I would also add some more > explanation to the exclusion in the pom files rat-exclusion. > > > Chris > > > Am

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

Hi Carlos, I have no objections to that ... however then I would also add some more explanation to the exclusion in the pom files rat-exclusion. Chris Am 05.05.20, 10:33 schrieb "Carlos Rovira" : Hi Chris, I'd like to have it "at hand" in the project. What about to move to some

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

Hi Chris, I'd like to have it "at hand" in the project. What about to move to some location. I think you suggested /src/assets or something like that Moving to other separate repo or CMS make it very cumbersome. I think that way we get both: not add it to a final output and as well get closer to

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

The CI Jobs indicate that my changes worked and the groovy files will be in the unified source package. I also reverted the pom changes made by the release-plugin so the branches should be ready to go. That said, you might want to wait until other PMC members have reviewed RC3. HTH, -Alex

Build failed in Jenkins: royale-compiler-integration-tests #869

See Changes: [thomas.darocha] Add namespace qualifier in metadata [thomas.darocha] Accept and replace config variables --

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

I removed TDF and ASDoc from running after asjs. That should reduce the changes you get blocked by something that takes a long time. We can put it back later. -Alex On 5/4/20, 11:29 PM, "Yishay Weiss" wrote: Great. Thanks to Alex and Chris for reviewing this. Om, is there any chance

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

Great. Thanks to Alex and Chris for reviewing this. Om, is there any chance you can look at the CI configuration and see if the jobs are still distributed between the 2 agents? Last time I looked it looked like they were all configured to work with agent1, which would mean TDF slowing down the

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Thanks Yishay. I am putting together CI jobs to verify that my changes will pick up the groovy files. The files that changed are part of the source package and were tagged as RC3 and one of them is in royale-compiler which is why we must start essentially from the beginning. You can skip the

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

Hi Yishay, Thank you very much for that. I was starting to get worried after seeing Alex' response. And replying to that (Alex' email): - Apache releases sources, not binaries (The binaries are convenience). So releasing something that doesn't build is topmost-validity reason for a -1 vote. -