Re: [EXTERNAL] about releasing 0.9.8

2021-05-06 Thread Harbs 
> It's VSCode that is complaining that these imports do not exist.

Do you have as3mxml.sdk.editor set in your settings?

> On May 7, 2021, at 4:17 AM, Brian Raymes  wrote:
> 
> I can compile just fine with Maven, , and have never needed to do anything 
> like that in the past. It's VSCode that is complaining that these imports do 
> not exist.
> 
> Assuming the new royale-sdk I built is missing something? Or my asconfig may 
> need to be adjusted for the new sdk changes?
> 
> I followed what Josh explained below, removed "-DdistributionTargetFolder= 
> (including the path) option" and replaced my previously built royale-sdk with 
> the one from a fresh build:
> 
> royale-asjs\distribution\target\apache-royale-0.9.9-SNAPSHOT-bin.zip
> 
> Simply unzipped the above and replace my previous. After doing so, all mx 
> imports are reporting as missing (squiggly underlines).
> 
> -Original Message-
> From: Greg Dove  
> Sent: Thursday, May 6, 2021 5:59 PM
> To: Apache Royale Development 
> Subject: Re: [EXTERNAL] Re: about releasing 0.9.8
> 
> I wonder if you mean the automatic imports
> 
> with maven I often have something like this:
> 
> -compiler.mxml.imports=
>mx.resources.ResourceManager,
>org.apache.royale.events.Event,
>org.apache.royale.events.EventDispatcher,
>org.apache.royale.events.IEventDispatcher,
>mx.events.MouseEvent,
>mx.events.FocusEvent,
>mx.events.KeyboardEvent,
>org.apache.royale.geom.*,
>org.apache.royale.core.ClassFactory,
>org.apache.royale.core.IFactory;
> 
> In the  nested section of the royale compiler 
>  tag
> 
> Is it more that, do you think, or more that you are actually missing the 
> MXRoyale dependency?
> 
> 
> On Fri, May 7, 2021 at 12:49 PM Brian Raymes 
> wrote:
> 
>> I should have mentioned, I use Maven to compile.
>> 
>> -Original Message-
>> From: Brian Raymes 
>> Sent: Thursday, May 6, 2021 5:32 PM
>> To: dev@royale.apache.org
>> Subject: RE: [EXTERNAL] Re: about releasing 0.9.8
>> 
>> Hi Josh,
>> 
>> I've done what you've said, and I can now build successfully, thank you.
>> But.. Now, all MX imports cannot be found in my project. I rely 
>> heavily on AMF with my current project, and now my project within 
>> VSCode is showing hundreds of errors, but can compile successfully.
>> 
>> What could I be missing? I compared the previously built SDK with the 
>> new, and they are definitely structured differently. The MX SWCs are 
>> found within the new.
>> 
>> Thoughts?
>> 
>> Brian
>> 
>> -Original Message-
>> From: Josh Tynjala 
>> Sent: Thursday, April 29, 2021 9:11 AM
>> To: Apache Royale Development 
>> Subject: Re: [EXTERNAL] Re: about releasing 0.9.8
>> 
>> Unfortunately, Adobe no longer provides AIR SDK 20.0. The only version 
>> they still offer is AIR 32.0. On macOS, I believe AIR 32.0 is also 
>> only downloadable in a .dmg format that the Maven plugin doesn't know 
>> how to process, which makes things even harder. Older versions of the 
>> macOS AIR SDK used to be available in a different format, like .tbz2 
>> or .tar.gz or something like that, but Adobe changed to .dmg only at 
>> some point. Anyway, this is why building the distribution is failing. 
>> Those who can still build are lucky enough to have it in their cache 
>> from before Adobe removed all of the files from the servers.
>> 
>> But, there's hope! If you build the distribution without specifying a 
>> target folder, it won't try to include Adobe artifacts. It's only when 
>> you build to a folder that the AIR SDK is used in the build process. 
>> When you don't specify a target folder, the distribution will go into 
>> a zip or tar.gz file instead. When the build completes, you can just 
>> extract that into a folder, and it's basically the same thing. If you 
>> need playerglobal.swc and the AIR SDK, you can merge them manually 
>> (like we used to do with the Adobe Flex SDK before the Apache installer).
>> 
>> Basically, in your distribution build command, just remove the 
>> -DdistributionTargetFolder= (including the path) option, and it should 
>> work without the AIR SDK. I don't know whether there are other issues 
>> on the develop branch that might also cause the Maven distribution 
>> build to fail, but this is how you deal with the AIR SDK part at least.
>> 
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>> 
>> 
>> On Wed, Apr 28, 2021 at 6:17 PM Brian Raymes 
>> 
>> wrote:
>> 
>>> +1 for fixing current state of repo.
>>> 
>>> I haven't been able to successfully build with Maven for quite a 
>>> long while now due to what looks to be shifts with this release.
>>> 
>>> For one, it seems to repeat ask to install the AIR SDK, but fails to 
>>> notify something, then fails to download as they can't be found. 
>>> This happens about 20 times.
>>> 
>>> Example:
>>> 
>>> [INFO]  - Installing Adobe AIR SDK 20.0 Your System-Id: ...

RE: [EXTERNAL] about releasing 0.9.8

2021-05-07 Thread Brian Raymes 
I do not have "as3mxml.sdk.editor" set, but I do have "as3mxml.sdk.framework" 
set in my vscode workspace.

-Original Message-
From: Harbs  
Sent: Thursday, May 6, 2021 10:08 PM
To: Apache Royale Development 
Subject: Re: [EXTERNAL] about releasing 0.9.8

> It's VSCode that is complaining that these imports do not exist.

Do you have as3mxml.sdk.editor set in your settings?

> On May 7, 2021, at 4:17 AM, Brian Raymes  wrote:
> 
> I can compile just fine with Maven, , and have never needed to do anything 
> like that in the past. It's VSCode that is complaining that these imports do 
> not exist.
> 
> Assuming the new royale-sdk I built is missing something? Or my asconfig may 
> need to be adjusted for the new sdk changes?
> 
> I followed what Josh explained below, removed "-DdistributionTargetFolder= 
> (including the path) option" and replaced my previously built royale-sdk with 
> the one from a fresh build:
> 
> royale-asjs\distribution\target\apache-royale-0.9.9-SNAPSHOT-bin.zip
> 
> Simply unzipped the above and replace my previous. After doing so, all mx 
> imports are reporting as missing (squiggly underlines).
> 
> -Original Message-
> From: Greg Dove 
> Sent: Thursday, May 6, 2021 5:59 PM
> To: Apache Royale Development 
> Subject: Re: [EXTERNAL] Re: about releasing 0.9.8
> 
> I wonder if you mean the automatic imports
> 
> with maven I often have something like this:
> 
> -compiler.mxml.imports=
>mx.resources.ResourceManager,
>org.apache.royale.events.Event,
>org.apache.royale.events.EventDispatcher,
>org.apache.royale.events.IEventDispatcher,
>mx.events.MouseEvent,
>mx.events.FocusEvent,
>mx.events.KeyboardEvent,
>org.apache.royale.geom.*,
>org.apache.royale.core.ClassFactory,
>org.apache.royale.core.IFactory;
> 
> In the  nested section of the royale 
> compiler  tag
> 
> Is it more that, do you think, or more that you are actually missing the 
> MXRoyale dependency?
> 
> 
> On Fri, May 7, 2021 at 12:49 PM Brian Raymes 
> 
> wrote:
> 
>> I should have mentioned, I use Maven to compile.
>> 
>> -Original Message-
>> From: Brian Raymes 
>> Sent: Thursday, May 6, 2021 5:32 PM
>> To: dev@royale.apache.org
>> Subject: RE: [EXTERNAL] Re: about releasing 0.9.8
>> 
>> Hi Josh,
>> 
>> I've done what you've said, and I can now build successfully, thank you.
>> But.. Now, all MX imports cannot be found in my project. I rely 
>> heavily on AMF with my current project, and now my project within 
>> VSCode is showing hundreds of errors, but can compile successfully.
>> 
>> What could I be missing? I compared the previously built SDK with the 
>> new, and they are definitely structured differently. The MX SWCs are 
>> found within the new.
>> 
>> Thoughts?
>> 
>> Brian
>> 
>> -Original Message-
>> From: Josh Tynjala 
>> Sent: Thursday, April 29, 2021 9:11 AM
>> To: Apache Royale Development 
>> Subject: Re: [EXTERNAL] Re: about releasing 0.9.8
>> 
>> Unfortunately, Adobe no longer provides AIR SDK 20.0. The only 
>> version they still offer is AIR 32.0. On macOS, I believe AIR 32.0 is 
>> also only downloadable in a .dmg format that the Maven plugin doesn't 
>> know how to process, which makes things even harder. Older versions 
>> of the macOS AIR SDK used to be available in a different format, like 
>> .tbz2 or .tar.gz or something like that, but Adobe changed to .dmg 
>> only at some point. Anyway, this is why building the distribution is failing.
>> Those who can still build are lucky enough to have it in their cache 
>> from before Adobe removed all of the files from the servers.
>> 
>> But, there's hope! If you build the distribution without specifying a 
>> target folder, it won't try to include Adobe artifacts. It's only 
>> when you build to a folder that the AIR SDK is used in the build process.
>> When you don't specify a target folder, the distribution will go into 
>> a zip or tar.gz file instead. When the build completes, you can just 
>> extract that into a folder, and it's basically the same thing. If you 
>> need playerglobal.swc and the AIR SDK, you can merge them manually 
>> (like we used to do with the Adobe Flex SDK before the Apache installer).
>> 
>> Basically, in your distribution build command, just remove the 
>> -DdistributionTargetFolder= (including the path) option, and it 
>> should work

Re: [EXTERNAL] about releasing 0.9.8

2021-05-07 Thread Josh Tynjala 
This is how most people should have it set up, with as3mxml.sdk.framework
only. You generally don't need to use as3mxml.sdk.editor unless you are
using a new compiler option that's available in a nightly build only. It
looks like you are not, so you're good.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Fri, May 7, 2021 at 9:06 AM Brian Raymes 
wrote:

> I do not have "as3mxml.sdk.editor" set, but I do have
> "as3mxml.sdk.framework" set in my vscode workspace.
>
> -Original Message-
> From: Harbs 
> Sent: Thursday, May 6, 2021 10:08 PM
> To: Apache Royale Development 
> Subject: Re: [EXTERNAL] about releasing 0.9.8
>
> > It's VSCode that is complaining that these imports do not exist.
>
> Do you have as3mxml.sdk.editor set in your settings?
>
> > On May 7, 2021, at 4:17 AM, Brian Raymes 
> wrote:
> >
> > I can compile just fine with Maven, , and have never needed to do
> anything like that in the past. It's VSCode that is complaining that these
> imports do not exist.
> >
> > Assuming the new royale-sdk I built is missing something? Or my asconfig
> may need to be adjusted for the new sdk changes?
> >
> > I followed what Josh explained below, removed
> "-DdistributionTargetFolder= (including the path) option" and replaced my
> previously built royale-sdk with the one from a fresh build:
> >
> > royale-asjs\distribution\target\apache-royale-0.9.9-SNAPSHOT-bin.zip
> >
> > Simply unzipped the above and replace my previous. After doing so, all
> mx imports are reporting as missing (squiggly underlines).
> >
> > -Original Message-
> > From: Greg Dove 
> > Sent: Thursday, May 6, 2021 5:59 PM
> > To: Apache Royale Development 
> > Subject: Re: [EXTERNAL] Re: about releasing 0.9.8
> >
> > I wonder if you mean the automatic imports
> >
> > with maven I often have something like this:
> >
> > -compiler.mxml.imports=
> >mx.resources.ResourceManager,
> >org.apache.royale.events.Event,
> >org.apache.royale.events.EventDispatcher,
> >org.apache.royale.events.IEventDispatcher,
> >mx.events.MouseEvent,
> >mx.events.FocusEvent,
> >mx.events.KeyboardEvent,
> >org.apache.royale.geom.*,
> >org.apache.royale.core.ClassFactory,
> >org.apache.royale.core.IFactory;
> >
> > In the  nested section of the royale
> > compiler  tag
> >
> > Is it more that, do you think, or more that you are actually missing the
> MXRoyale dependency?
> >
> >
> > On Fri, May 7, 2021 at 12:49 PM Brian Raymes
> > 
> > wrote:
> >
> >> I should have mentioned, I use Maven to compile.
> >>
> >> -Original Message-
> >> From: Brian Raymes 
> >> Sent: Thursday, May 6, 2021 5:32 PM
> >> To: dev@royale.apache.org
> >> Subject: RE: [EXTERNAL] Re: about releasing 0.9.8
> >>
> >> Hi Josh,
> >>
> >> I've done what you've said, and I can now build successfully, thank you.
> >> But.. Now, all MX imports cannot be found in my project. I rely
> >> heavily on AMF with my current project, and now my project within
> >> VSCode is showing hundreds of errors, but can compile successfully.
> >>
> >> What could I be missing? I compared the previously built SDK with the
> >> new, and they are definitely structured differently. The MX SWCs are
> >> found within the new.
> >>
> >> Thoughts?
> >>
> >> Brian
> >>
> >> -Original Message-
> >> From: Josh Tynjala 
> >> Sent: Thursday, April 29, 2021 9:11 AM
> >> To: Apache Royale Development 
> >> Subject: Re: [EXTERNAL] Re: about releasing 0.9.8
> >>
> >> Unfortunately, Adobe no longer provides AIR SDK 20.0. The only
> >> version they still offer is AIR 32.0. On macOS, I believe AIR 32.0 is
> >> also only downloadable in a .dmg format that the Maven plugin doesn't
> >> know how to process, which makes things even harder. Older versions
> >> of the macOS AIR SDK used to be available in a different format, like
> >> .tbz2 or .tar.gz or something like that, but Adobe changed to .dmg
> >> only at some point. Anyway, this is why building the distribution is
> failing.
> >> Those who can still build are lucky enough to have it in their cache
> >> from before Adobe removed all of the files from the servers.
> >>
> >>