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

See

Build failed in Jenkins: royale-compiler #642

See -- [...truncated 196.04 KB...] [junit] Unexpected compilation problems: [junit] [junit] Generating test: [junit] Compiling test: [junit

Build failed in Jenkins: royale-compiler #641

See Changes: [aharui] update closure compiler and guava required by closure [aharui] also this pom [aharui] force guava upgrade. Not sure which dependency is using older guava --

Build failed in Jenkins: royale-compiler #640

See Changes: [aharui] upgrade Closure Compiler to 20181210 which requires Guava 25.1 [aharui] update APIs for new Closure version [aharui] interface changed in Guava [aharui] API was

Build failed in Jenkins: royale-asjs_MXTests #296

See -- [...truncated 2.41 MB...] [mxmlc] using source file:

Build failed in Jenkins: royale-asjs_MXTests #295

See -- [...truncated 2.41 MB...] [mxmlc] using source file:

Re: Royale Java versions

Ok, For royale-compiler, I tried to have an IDE working for that and I still wasn't able to do that. Of course is cause I didn't follow the Eclipse installation in our wiki so is my fault. But I want to set up with VSCode for Java that uses Eclipse core for this extensions, but I was stuck in crea

Re: Trying to add MXML content to a sub component of the document

Hi Alex, El mar., 25 dic. 2018 a las 18:19, Alex Harui () escribió: > Ideally, there won't be any Royale components that are "MXML-only", > meaning they can only be used in MXML. Right, this component should be used in AS, maybe I was mixing my use case in the explanation, but I always think in

Re: Trying to add MXML content to a sub component of the document

Ideally, there won't be any Royale components that are "MXML-only", meaning they can only be used in MXML. MXML is a declarative language which implies you can declare all of the children at compile-time. There is probably always some scenario for any Royale component that requires determinin

Re: Royale Java versions

Yishay is using Flash Builder. I’m personally happy that he is. Choices is a good thing. FWIW, the discussion here is about Eclipse and compiling Royale-compiler — not FB. > On Dec 25, 2018, at 2:03 PM, Carlos Rovira wrote: > > mmm... is hard to me think that someone is still using FB for Roy

Build failed in Jenkins: royale-asjs_MXTests #294

See Changes: [harbs] Missing parameter types [harbs] Missing nativeEvent -- [...truncated 2.41 MB...] [mxmlc] using source file:

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

See

Trying to add MXML content to a sub component of the document

Hi for Tour de Jewel I'm trying to create a component in AS that could be extended in MXML. The component creates a Tab and two SectionContent. One is for the current example and the other shows the source code loaded from GitHub. So when I add content in mxml to an instance of this component, I

Re: Royale Java versions

mmm... is hard to me think that someone is still using FB for Royale. It's a pretty old software and with no support this days. Maybe we should open a thread and ask who is using FB. I think the response should be near 0 or equal to 0. El mar., 25 dic. 2018 a las 10:10, Harbs () escribió: > No. I

Re: Royale Java versions

No. I’m saying a newer version should be fine. I was just suggesting that if someone is using an older version, they can probably get it to work. > On Dec 25, 2018, at 10:04 AM, Alex Harui wrote: > > Are you saying we should use something older? > > Currently, we say Helios is the version to

Build failed in Jenkins: royale-asjs_jsonly #2097

See -- Started by an SCM change Building remotely on agent1 in workspace c:\jenkins\workspace\royale-asjs_jsonly FATAL: java.nio.channels.ClosedChannelExcep

Re: Royale Java versions

Are you saying we should use something older? Currently, we say Helios is the version to use, primarily because that's what was used by the Adobe team at the time the code base was donated to Apache, and partially out of concern of being able to generate the Flash Builder plugin that required J