Build failed in Jenkins: royale-asjs #1412

See Changes: [aharui] add LocaleUtils to get language [aharui] first cut at ResourceManager -- [...truncated 91.56 KB...] clean: [delete]

Re: Apache Royale - Where are all the Flash Guys

I'm a flash guy where should I push? I have full time job developing as3 mxml desktop apps so not much to sphere. I will wait untill holiday season when hopfully I would get the time to give royale a nother chance at porting some of my work. On Sun, Sep 30, 2018, 18:58 Carlos Rovira wrote: >

Build failed in Jenkins: royale-typedefs #756

See -- Started by timer Building on master in workspace > git.exe rev-parse

Build failed in Jenkins: royale-asjs #1411

See Changes: [aharui] get Jewel TextInput to sort of work on SWF -- [...truncated 94.55 KB...] checkintests-clean: [delete] Deleting:

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

See

Build failed in Jenkins: royale-asjs_jsonly #1655

See Changes: [aharui] handle more complex CSS from Jewel [aharui] Jewel needs more sophisticated CSS handling for SWF side [aharui] get more Jewel components to show up without

Royale AMF not working on SWF side

At some point the RemoteObjectAMFTest broke for SWF. This is rather annoying as it was a good test bed for debugging the compiler output and comparing the JS code to the SWF code. One thing that broke it was upgrading the UI to use Jewel components because Jewel isn't working that well in

Re: Maven builds for Royale can't deploy from windows-2012-1

Hi Chris, I guess we should assume that C:\.m2\settings.xml exists, otherwise our builds probably would have failed saying that file doesn't exist. Before you go delete it, can you check its contents? I switched our builds to use C:/Users/Jenkins/.m2/settings.xml and the first build got past

Re: Maven builds for Royale can't deploy from windows-2012-1

No, the file that's under Puppet is C:/Users/Jenkins/.m2/settings.xml, here is the line in the config https://github.com/apache/infrastructure-puppet/blob/5f15dc612c273d9a453bebcf7358783147fff38b/environments/windows/modules/jenkins_slave_windows/manifests/init.pp#L153 I have no clue how that

Re: Maven builds for Royale can't deploy from windows-2012-1

Hi Chris, I started another build and it failed with the same issue. The build on 9/28 succeeded. The next build was on 9/30 and failed. We've only had failures since. I didn't report it sooner because I figured other Maven builds would have the same issue and someone would have figured it

Re: Maven builds for Royale can't deploy from windows-2012-1

I've updated the password for repository.a.o last week and it's correct on disk. Dollars to donuts the node needed bounced to pick up the new creds. I went through and bounced the nodes when there weren't any builds, maybe an hour or so ago. Please kick of another build and we can troubleshoot

Re: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)

If you are using some GUI tool for Git, you should find out if it can change tags or not. I don't see how it could have happened via command line. The tag change came in my mailbox before the latest commit, so it is also possible the tag change was pending. But I didn't compare timestamps.

Re: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)

Hi Alex, I must to say that don't know what this is really :? I didn't change a tag never, so don't know how this has happen Maybe could be caused to my latest commit? I suppose that Om stop for now the release process and revert all. I'm more really surprised of this. So please, let me apologize

Re: Trying to solve de flexunit problem when create the SDK with ANT

Hi Alex, after various attempts, I didn't find other way but remove the flexunit flex swc. With this, all is ok. I think we can revisit this with more time to see what's really going on, but my ANT knowledge is limited and maybe is more simple than that El lun., 1 oct. 2018 a las 18:45, Alex

Re: [royale-typedefs] annotated tag org.apache.royale.typedefs-0.9.4-rc1 updated (0774539 -> be658de)

Changing tags without agreement is, IMO, a bad practice. You don't know how far into the release process we are. It might be too late to pick up the changes. -Alex On 10/1/18, 3:30 PM, "carlosrov...@apache.org" wrote: This is an automated email from the ASF dual-hosted git repository.

Re: [royale-typedefs] branch develop updated: when pass first ant and then maven rat-plugin complain about files created by ant in ace/target. add the path to rat-plugin exclusions to avoid maven fail

I don't think this is right. If you use Ant and then want to use Maven, use "ant wipe" to remove all Ant-generated files. Maven's "clean" goal won't know how to remove these Ant-generated files and it is probably a bad idea to have them around. I have separate working copies for Ant and

Build failed in Jenkins: royale-asjs #1409

See Changes: [aharui] add a few things to the release notes -- [...truncated 2.32 MB...] [mxmlc] Dependencies calculated for 'ExitWhenDone'

Build failed in Jenkins: royale-typedefs #755

See Changes: [carlosrovira] when pass first ant and then maven rat-plugin complain about files -- Started by an SCM change Building on master

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

See

Maven builds for Royale can't deploy from windows-2012-1

Hi builds@, We've been getting this "Unauthorized" error for several builds now: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project royale-framework-parent: Failed to deploy artifacts: Could not transfer artifact

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Jewel is mentioned in there. I added mention of the migration components and tour de flex. Not sure if I got the formatting right. I think it is good enough. -Alex On 10/1/18, 12:13 PM, "OmPrakash Muppirala" wrote: I updated it, although it looks a bit sparse now. Can we list a few

Build failed in Jenkins: royale-asjs #1408

See Changes: [om] Revert released version tag back to 0.9.3 [om] Update Release notes -- [...truncated 2.32 MB...] [mxmlc] Dependencies

Build failed in Jenkins: royale-asjs_jsonly #1652

yale-asjs_jsonly/ws/frameworks/mxml-manifest.xml> [delete] Deleting: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/spark-manifest.xml> [delete] Deleting: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws

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

See

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

I updated it, although it looks a bit sparse now. Can we list a few major highlights here, that I can go add to the release notes? Jewel should at least have several updates. Thanks, Om On Mon, Oct 1, 2018 at 12:09 PM Alex Harui wrote: > Hey, I just noticed that nobody put a 0.9.4 section in

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Hey, I just noticed that nobody put a 0.9.4 section in the RELEASE_NOTES. Maybe just rename the 0.9.3 section? -Alex On 10/1/18, 12:07 PM, "OmPrakash Muppirala" wrote: Good catch! I just pushed a fix for that. Thanks, Om On Mon, Oct 1, 2018 at 11:04 AM Alex Harui

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Good catch! I just pushed a fix for that. Thanks, Om On Mon, Oct 1, 2018 at 11:04 AM Alex Harui wrote: > Om, > > I think the release/0.9.4 in royale-asjs/pom.xml needs to be > reverted back to 0.9.3. > > Everything else looks ok from my quick examination. > > Thanks and good luck, > -Alex > >

Build failed in Jenkins: royale-asjs #1407

See Changes: [noreply] Update RadioButtonGroup.as [om] Revert everything back to 0.9.4 -- [...truncated 979.79 KB...] [java] module.exports =

Jenkins build is back to normal : royale-typedefs #754

See

Build failed in Jenkins: royale-typedefs #753

See Changes: [om] Revert everything back to 0.9.4 -- Started by an SCM change Building on master in workspace

Build failed in Jenkins: royale-asjs_jsonly #1650

e] Deleting: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/ide/flashbuilder/flashbuilder-config.xml> create-description: [echo] build.number is 20181001 js-output-royale-description: swf-js-output-royale-description: create-config: playerglobal-setswfvers

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Om, I think the release/0.9.4 in royale-asjs/pom.xml needs to be reverted back to 0.9.3. Everything else looks ok from my quick examination. Thanks and good luck, -Alex On 10/1/18, 10:29 AM, "Piotr Zarzycki" wrote: I saw your commit and I think you should be ok. pon., 1 paź

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

I saw your commit and I think you should be ok. pon., 1 paź 2018 o 19:21 OmPrakash Muppirala napisał(a): > Okay, I did the following to reset: > > For all three repos: > * Reverted all references of 0.9.5 to 0.9.4 > * Deleted 0.9.4-rc1 tag > * Deleted branch: release/0.9.4 > > Can someone

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Okay, I did the following to reset: For all three repos: * Reverted all references of 0.9.5 to 0.9.4 * Deleted 0.9.4-rc1 tag * Deleted branch: release/0.9.4 Can someone please make sure that we are good before starting work? Thanks, Om On Mon, Oct 1, 2018 at 1:51 AM Carlos Rovira wrote: > Hi

Re: Trying to solve de flexunit problem when create the SDK with ANT

Without taking time to look closely, the "better fix" is to explicitly name the SWC instead of the folder of SWCs. HTH, -Alex On 10/1/18, 3:12 AM, "Carlos Rovira" wrote: Hi, I'm trying to figure the problem when we create an SDK with ANT before trying to fix Maven

Re: [royale-asjs] branch develop updated: Jewel example pom is not updated to 0.9.4

I did not look closely, but it appeared from the commit message that the part of the pom Carlos changed was inside a comment. Maven does not search comments when updating versions, it works from the project model. I wouldn't be surprised if Maven has a philosophy that you shouldn't comment

Build failed in Jenkins: royale-asjs #1406

See -- [...truncated 2.32 MB...] [mxmlc] Dependencies calculated for 'ExitWhenDone' [mxmlc] Dependencies calculated for 'RoyaleContext' [mxmlc]

Jenkins build is back to normal : royale-typedefs #752

See

Jenkins build is back to normal : royale-compiler #474

See

Trying to solve de flexunit problem when create the SDK with ANT

Hi, I'm trying to figure the problem when we create an SDK with ANT before trying to fix Maven distribution to create an SDK. The problem: When doing "ant all" from royale-asjs folder at some point we get flexunit on "in" folder. Then inside that folder we have ;

Build failed in Jenkins: royale-asjs #1405

See -- [...truncated 2.32 MB...] [mxmlc] Dependencies calculated for 'ExitWhenDone' [mxmlc] Dependencies calculated for 'RoyaleContext' [mxmlc]

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Hi Om, is related to flash player debugger not launched? are you on Mac? I think on Mac I have to make *.swf files be always opened by Flash Player debugger. In the other hand, I need to commit during the day some fixes, one on typedefs and expect more on compiler. So if you plan to try again

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

I provided path to Chrome via -Dbrowser, but I got an error that ant was not able to access the application. So, I tried installing firefox and that seemed to work. On Mon, Oct 1, 2018 at 1:26 AM Piotr Zarzycki wrote: > Hi Om, > > You did use Firefox for that purpose ? I had to specify

Build failed in Jenkins: royale-asjs #1404

in/royale> clean: super-clean: [delete] Deleting directory <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Spark> create-description: [echo] build.number is 20181001 js-output-royale-description: swf-js-output-royale-description: create-

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Hi Om, You did use Firefox for that purpose ? I had to specify -Dbrowser=path to firefox.exe Thanks, Piotr pon., 1 paź 2018 o 10:22 OmPrakash Muppirala napisał(a): > Okay, I made several attempts through the day, making progress each time. > The last run failed because the browser could not

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Okay, I made several attempts through the day, making progress each time. The last run failed because the browser could not be launched. I am going to pause on this and try again tomorrow (or later) . If someone else wants to give this a go in the meantimne, they are welcome :-) Thanks, Om On

Re: [royale-asjs] branch develop updated: Jewel example pom is not updated to 0.9.4

ok, I'll take that account for now on, and will only comment in this list. thanks! El lun., 1 oct. 2018 a las 9:58, Piotr Zarzycki () escribió: > Probably Maven doesn't have some part of the project in chain of hierarchy. > We can manually adjust those poms once RC1 will be created. However I

Re: [royale-asjs] branch develop updated: Jewel example pom is not updated to 0.9.4

Probably Maven doesn't have some part of the project in chain of hierarchy. We can manually adjust those poms once RC1 will be created. However I would say it should be done once RC1 turns into release, because we may VOTE -1 than process will start from scratch. - It would be harder manually

Re: [royale-asjs] branch develop updated: Jewel example pom is not updated to 0.9.4

Ok, I can left poms untouched from now on. it's very strange that some poms are not updated to the right version, since that in concrete is linked from parent in modules. El lun., 1 oct. 2018 a las 9:41, Piotr Zarzycki () escribió: > Carlos, > > It shouldn't be unless Om let you know that he

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

See

Re: [royale-asjs] branch develop updated: Jewel example pom is not updated to 0.9.4

Carlos, It shouldn't be unless Om let you know that he succeed with creating RC1. You should probably do not manually change anything. Piotr pon., 1 paź 2018 o 09:36 Carlos Rovira napisał(a): > Hi, > just found this pom was not in 0.9.5 > > El lun., 1 oct. 2018 a las 9:34, escribió: > > >

Re: [royale-asjs] branch develop updated: Jewel example pom is not updated to 0.9.4

Hi, just found this pom was not in 0.9.5 El lun., 1 oct. 2018 a las 9:34, escribió: > This is an automated email from the ASF dual-hosted git repository. > > carlosrovira pushed a commit to branch develop > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git > > > The following

Re: [royale-asjs] branch develop updated: fix version in poms. some poms still was in 0.9.4-SNAPSHOT. We should take a look about why this ones was not changed to 0.9.6-SNAPSHOT

Ok! Good luck! :) El lun., 1 oct. 2018 a las 7:18, OmPrakash Muppirala () escribió: > Okay, reverted everything back to 0.9.4 in all three repos and trying again > :-) > > On Sun, Sep 30, 2018 at 9:10 PM Piotr Zarzycki > wrote: > > > Starting point in Dev is 0.9.4-SNAPSHOT. If you run script

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Hi Om, no, I Thought this was due to different tries of the release process but most of the poms are in 0.9.6-SNAPSHOT. You can search the entire repo for "0.9.X-SNAPSHOT" string to see that now X is 6. thanks El lun., 1 oct. 2018 a las 2:07, OmPrakash Muppirala () escribió: > On Sun, Sep 30,

Build failed in Jenkins: royale-compiler #473

See Changes: [om] Revert everything to 0.9.4 [om] [maven-release-plugin] prepare branch release/0.9.4 [om] [maven-release-plugin] prepare for next development iteration

Build failed in Jenkins: royale-typedefs #751

See Changes: [om] Revert everything to 0.9.4 [om] [maven-release-plugin] prepare branch release/0.9.4 [om] [maven-release-plugin] prepare for next development iteration

Jenkins build is back to normal : royale-typedefs #750

See

Jenkins build is back to normal : royale-compiler #472

See

Build failed in Jenkins: royale-asjs #1403

See Changes: [om] Revert everything to 0.9.4. [om] [maven-release-plugin] prepare for next development iteration -- [...truncated 786.96 KB...]

Build failed in Jenkins: royale-typedefs #749

See Changes: [om] Revert everything to 0.9.4 [om] [maven-release-plugin] prepare branch release/0.9.4 [om] [maven-release-plugin] prepare for next development iteration

Build failed in Jenkins: royale-asjs_jsonly #1645

See Changes: [om] Revert everything to 0.9.4. [om] [maven-release-plugin] prepare for next development iteration -- [...truncated 132.12