You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Carol Frampton <cf...@adobe.com> on 2012/06/22 23:18:31 UTC
time to help test the release candidate
The kits have been refreshed at http://people.apache.org/~cframpton/ApacheFlexRC/current/.
All the code for the parity release of Apache Flex 4.8.0 is now in svn.
The only kitting issue I am aware of, and will fix, is that the swcs are missing from samples/themes. My to-do list is bouncing off of zero items. We're getting really close.
To get started:
* download the source and binary kits
* read the README and try to build each kit
* build your favorite app and run it
* if you use the automation, verify it still works (I have to remove some license check code)
If you are curious, here is the release management guide, http://incubator.apache.org/guides/releasemanagement.html.
We will need to document our release management process. Some examples from other projects are http://incubator.apache.org/airavata/development/release-management.html and http://incubator.apache.org/kato/site/release-process.html.
Carol
AW: AW: AW: time to help test the release candidate
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
No Maven itself and the JDK are required to use Maven at all.
Usually it's not the normal Maven way to force you do deploy a lot of essential libraries manually.
I am not saying that it's not possible to manually deploy the artifacts, it's just something that would easily avoidable.
If Adobe has no objections deploying it would make life for all a lot easier.
And I particularly found this step (Adding the playerglobal to my systems environment variables)
in the compilation of the Apache SDK rather strange.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 28. Juni 2012 16:24
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: time to help test the release candidate
On 6/28/12 12:34 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> I thought about this problem for quite some time yesterday.
>
> Regarding the adt.jar and Air integration. I think the best solution
> would be to split up the flexmojos maven plugin to have a separate flex and air module.
> The current mixture does have some disadvantages. In case of Flex
> being shipped without AIR even more. Will it still be possible to
> build an Air application using Apache Flex?
Yes it will. Are build tools like a JDK also managed by Maven or are they a "prerequisite"? The latter is what we are saying for the Ant scripts. You have to download the platform build tools including playerglobal.
>
> Regarding the fontkit. I think I'll have a loot at what it is used for anyway.
> If the Apache Flex SDK can do without it, perhaps it's usage is some
> legacy functionality, which I could make optional. I could immagine
> that this is related to one of the several ways how fonts can be
> embedded in Flex. I guess it would be ok that if a user tried to use
> one that depended on fontkit, that Flexmojos could issue an error
> complaining about the missing fontkit implementation.
Fontkit is required to embed fonts for Spark. I am hopeful we can replace our dependency on it as I think all it does is convert other font files to CFF format.
>
> Currently I don't have any problems getting my handy on a version of
> fontkit and adt, but they are not part of the SDK and currently
> Flexmojos uses that exclusively and I don't want to add hard-coded
> deps to those missing libraries (They are all available im Maven Central ... so this wouldn't be a problem).
>
> Chris
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 27. Juni 2012 19:01
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: time to help test the release candidate
>
>
>
>
> On 6/27/12 9:36 AM, "christofer.dutz@c-ware.de"
> <ch...@c-ware.de>
> wrote:
>
>> While velocity is no problem. I simply added a new dependency. More
>> troubeling is the absence of adt.jar and flex-fontkit.jar.
>> Without these I will not be able to build Flexmojos. Are they not yet
>> donated to Apache, or is refactoring Flexmojos better in this case?
>> (Eventually Breaking Backward compatability).
> Adt.jar is part of the Adobe AIR SDK and will not be donated.
> Flex-fontkit.jar relies on font processing code used in many Adobe
> products and is not going to be donated.
>
> The build script require Adobe AIR SDK as a pre-requisite. The
> scripts give you the option of downloading an Adobe Flex SDK and using
> the flex-fonkit.jar within.
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
On 6/28/12 8 :54AM, "Yennick Trevels" <ye...@gmail.com> wrote:
>I've been trying out GradleFx with the Flex 4.8 incubator release, but I'm
>getting some errors.
>One of them occurs when compiling an air application:
> D:\Program
>files\sdks\flex_sdk_4.8.0_incubating\frameworks\air-config.xml(64): Error:
>cannot open '{airHome}/frameworks/libs/air/airglobal.swc'
>
>Another one occurs when running the unittests with FlexUnit:
> D:\Program
>files\sdks\flex_sdk_4.8.0_incubating\frameworks\flex-config.xml(62):
>Error:
>cannot open '{playerglobalHome}/11.1/playerglobal.swc'
>
>GradleFx is using the default Flex SDK distribution (zip file) and uses
>the
>mxmlc.jar, compc.jar etc. files to compile the applications. Apparently
>those airHome and playerglobalHome variables are new in 4.8. Are these new
>command line options?
Read the install prerequisites section in
http://people.apache.org/~cframpton/ApacheFlexRC/current/readme
Carol
>
>
>-Yennick
>GradleFx co-founder
Re: AW: time to help test the release candidate
Posted by Yennick Trevels <ye...@gmail.com>.
I've been trying out GradleFx with the Flex 4.8 incubator release, but I'm
getting some errors.
One of them occurs when compiling an air application:
D:\Program
files\sdks\flex_sdk_4.8.0_incubating\frameworks\air-config.xml(64): Error:
cannot open '{airHome}/frameworks/libs/air/airglobal.swc'
Another one occurs when running the unittests with FlexUnit:
D:\Program
files\sdks\flex_sdk_4.8.0_incubating\frameworks\flex-config.xml(62): Error:
cannot open '{playerglobalHome}/11.1/playerglobal.swc'
GradleFx is using the default Flex SDK distribution (zip file) and uses the
mxmlc.jar, compc.jar etc. files to compile the applications. Apparently
those airHome and playerglobalHome variables are new in 4.8. Are these new
command line options?
-Yennick
GradleFx co-founder
Re: AW: AW: time to help test the release candidate
Posted by Alex Harui <ah...@adobe.com>.
On 6/28/12 12:34 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> I thought about this problem for quite some time yesterday.
>
> Regarding the adt.jar and Air integration. I think the best solution would be
> to split up the flexmojos maven plugin to have a separate flex and air module.
> The current mixture does have some disadvantages. In case of Flex being
> shipped without AIR even more. Will it still be possible to build an Air
> application using Apache Flex?
Yes it will. Are build tools like a JDK also managed by Maven or are they a
"prerequisite"? The latter is what we are saying for the Ant scripts. You
have to download the platform build tools including playerglobal.
>
> Regarding the fontkit. I think I'll have a loot at what it is used for anyway.
> If the Apache Flex SDK can do without it, perhaps it's usage is some legacy
> functionality, which I could make optional. I could immagine that this is
> related to one of the several ways how fonts can be embedded in Flex. I guess
> it would be ok that if a user tried to use one that depended on fontkit, that
> Flexmojos could issue an error complaining about the missing fontkit
> implementation.
Fontkit is required to embed fonts for Spark. I am hopeful we can replace
our dependency on it as I think all it does is convert other font files to
CFF format.
>
> Currently I don't have any problems getting my handy on a version of fontkit
> and adt, but they are not part of the SDK and currently Flexmojos uses that
> exclusively and I don't want to add hard-coded deps to those missing libraries
> (They are all available im Maven Central ... so this wouldn't be a problem).
>
> Chris
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Alex Harui [mailto:aharui@adobe.com]
> Gesendet: Mittwoch, 27. Juni 2012 19:01
> An: flex-dev@incubator.apache.org
> Betreff: Re: AW: time to help test the release candidate
>
>
>
>
> On 6/27/12 9:36 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
> wrote:
>
>> While velocity is no problem. I simply added a new dependency. More
>> troubeling is the absence of adt.jar and flex-fontkit.jar.
>> Without these I will not be able to build Flexmojos. Are they not yet
>> donated to Apache, or is refactoring Flexmojos better in this case?
>> (Eventually Breaking Backward compatability).
> Adt.jar is part of the Adobe AIR SDK and will not be donated.
> Flex-fontkit.jar relies on font processing code used in many Adobe products
> and is not going to be donated.
>
> The build script require Adobe AIR SDK as a pre-requisite. The scripts give
> you the option of downloading an Adobe Flex SDK and using the flex-fonkit.jar
> within.
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: AW: time to help test the release candidate
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
I thought about this problem for quite some time yesterday.
Regarding the adt.jar and Air integration. I think the best solution would be to split up the flexmojos maven plugin to have a separate flex and air module. The current mixture does have some disadvantages. In case of Flex being shipped without AIR even more. Will it still be possible to build an Air application using Apache Flex?
Regarding the fontkit. I think I'll have a loot at what it is used for anyway. If the Apache Flex SDK can do without it, perhaps it's usage is some legacy functionality, which I could make optional. I could immagine that this is related to one of the several ways how fonts can be embedded in Flex. I guess it would be ok that if a user tried to use one that depended on fontkit, that Flexmojos could issue an error complaining about the missing fontkit implementation.
Currently I don't have any problems getting my handy on a version of fontkit and adt, but they are not part of the SDK and currently Flexmojos uses that exclusively and I don't want to add hard-coded deps to those missing libraries (They are all available im Maven Central ... so this wouldn't be a problem).
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Mittwoch, 27. Juni 2012 19:01
An: flex-dev@incubator.apache.org
Betreff: Re: AW: time to help test the release candidate
On 6/27/12 9:36 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> While velocity is no problem. I simply added a new dependency. More
> troubeling is the absence of adt.jar and flex-fontkit.jar.
> Without these I will not be able to build Flexmojos. Are they not yet
> donated to Apache, or is refactoring Flexmojos better in this case?
> (Eventually Breaking Backward compatability).
Adt.jar is part of the Adobe AIR SDK and will not be donated.
Flex-fontkit.jar relies on font processing code used in many Adobe products and is not going to be donated.
The build script require Adobe AIR SDK as a pre-requisite. The scripts give you the option of downloading an Adobe Flex SDK and using the flex-fonkit.jar within.
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: AW: time to help test the release candidate
Posted by Alex Harui <ah...@adobe.com>.
On 6/27/12 9:36 AM, "christofer.dutz@c-ware.de" <ch...@c-ware.de>
wrote:
> While velocity is no problem. I simply added a new dependency. More troubeling
> is the absence of adt.jar and flex-fontkit.jar.
> Without these I will not be able to build Flexmojos. Are they not yet donated
> to Apache, or is refactoring Flexmojos better in this case?
> (Eventually Breaking Backward compatability).
Adt.jar is part of the Adobe AIR SDK and will not be donated.
Flex-fontkit.jar relies on font processing code used in many Adobe products
and is not going to be donated.
The build script require Adobe AIR SDK as a pre-requisite. The scripts give
you the option of downloading an Adobe Flex SDK and using the
flex-fonkit.jar within.
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
AW: time to help test the release candidate
Posted by "christofer.dutz@c-ware.de" <ch...@c-ware.de>.
Hi,
Now it's time for me to give a short report.
Currently I'm trying to get Flexmojos to build with the 4.8.0. I manually created a Mavenized form of this and changed Flexmojos to use that instead.
Unfortunately there are a few resources that Flexmojos depends on, that are no longer part of the SDK:
- velocity is no longer part of the compiler. Needed extra dependency to: org.apache.velocity:velocity:1.5
- air stuff no longer provided (no adt.jar). Needed extre dependency to: com.adobe.flex.compiler:adt:4.6.0.23201
- flex-fontkit is missing: com.adobe.flex.compiler:flex-fontkit:4.5.0.20967A
While velocity is no problem. I simply added a new dependency. More troubeling is the absence of adt.jar and flex-fontkit.jar.
Without these I will not be able to build Flexmojos. Are they not yet donated to Apache, or is refactoring Flexmojos better in this case?
(Eventually Breaking Backward compatability).
Currently I simply added the latest versions of both from Adobe SDKs to have the plugin build. And it did build.
Currently I'm working on getting the testsuite to run properly, but I think most of the work I'll have to do here first is getting the Maven build to work with a group-id of
"org.apache.flex" instead of "com.adobe.flex". Hopefully as soon as I have fixed this I will be able to give some more detailed reports.
Velo did a real good job creating testcases for Flexmojos and hence for the Flex Compiler and SDK. I think this will be really valuable data.
I guess if the testsuite was green and as soon as I change the SDK and it's not green anymore, thats a pretty good probability, that something in the SDK works differently.
-----Ursprüngliche Nachricht-----
Von: Carol Frampton [mailto:cframpto@adobe.com]
Gesendet: Mittwoch, 27. Juni 2012 17:56
An: flex-dev@incubator.apache.org
Betreff: Re: time to help test the release candidate
On 6/27/12 11 :37AM, "Dasa Paddock" <dp...@esri.com> wrote:
>I just ran the latest makeApacheFlexForFlashBuilder.sh and the resulting
>4.8 SDK is missing swfobject.js in the templates/swfobject folder. It's
>also missing playerProductInstall.swf as compared to SDK 4.6.0. This
>means that when I create a new Flex Project based on my 4.8 SDK and try
>to run it, it fails to run since the swfobject.js is 404.
swfobject.js gets downloaded from google as part of the build
playerProductInstall.swf has been replaced by expressInstall.swf and it
comes from the same download
>
>Should these files be in the SVN trunk or should
>makeApacheFlexForFlashBuilder.sh download them?
I am rekitting right now and will be using
makeApacheFlexForFlashBuilder.sh to test out a fix for your flex library
issue. I will check this issue as well.
Carol
Re: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
On 6/27/12 11 :37AM, "Dasa Paddock" <dp...@esri.com> wrote:
>I just ran the latest makeApacheFlexForFlashBuilder.sh and the resulting
>4.8 SDK is missing swfobject.js in the templates/swfobject folder. It's
>also missing playerProductInstall.swf as compared to SDK 4.6.0. This
>means that when I create a new Flex Project based on my 4.8 SDK and try
>to run it, it fails to run since the swfobject.js is 404.
swfobject.js gets downloaded from google as part of the build
playerProductInstall.swf has been replaced by expressInstall.swf and it
comes from the same download
>
>Should these files be in the SVN trunk or should
>makeApacheFlexForFlashBuilder.sh download them?
I am rekitting right now and will be using
makeApacheFlexForFlashBuilder.sh to test out a fix for your flex library
issue. I will check this issue as well.
Carol
Re: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
On 6/27/12 11 :37AM, "Dasa Paddock" <dp...@esri.com> wrote:
>I just ran the latest makeApacheFlexForFlashBuilder.sh and the resulting
>4.8 SDK is missing swfobject.js in the templates/swfobject folder. It's
>also missing playerProductInstall.swf as compared to SDK 4.6.0. This
>means that when I create a new Flex Project based on my 4.8 SDK and try
>to run it, it fails to run since the swfobject.js is 404.
>
>Should these files be in the SVN trunk or should
>makeApacheFlexForFlashBuilder.sh download them?
makeApacheFlexForFlashBuilder.sh is a bit out of date since Om's tool sort
of supercedes this. My current thinking is I will keep the sh script
current since I use it and it issn't that hard to keep it current but I
will abandon the bat version since it is also out of date and much
hard/time consuming to keep current and it isn't clear it can be used in
many environments because vbs scripts aren't allowed.
swfobject.as/expressInstall.swf/textLayout.swc/osmf.swc all come from
elsewhere (these have reciprocal licenses to the Apache v2 license)
optionally flex-message-common.jar and the Adobe embedded font support
jars come from elsewhere (these have priopriatary licenses, hence they are
optional)
>
>--Dasa
Re: time to help test the release candidate
Posted by Dasa Paddock <dp...@esri.com>.
I just ran the latest makeApacheFlexForFlashBuilder.sh and the resulting 4.8 SDK is missing swfobject.js in the templates/swfobject folder. It's also missing playerProductInstall.swf as compared to SDK 4.6.0. This means that when I create a new Flex Project based on my 4.8 SDK and try to run it, it fails to run since the swfobject.js is 404.
Should these files be in the SVN trunk or should makeApacheFlexForFlashBuilder.sh download them?
--Dasa
Re: time to help test the release candidate
Posted by Raju Bitter <r....@googlemail.com>.
Great, thanks, look forward to testing that functionality.
- Raju
Re: time to help test the release candidate
Posted by Om <bi...@gmail.com>.
Raju,
I am finalizing the code for prompting/downloading the additional tools
(blazeds and font jars) I will be posting an update soon.
Thanks,
Om
On Mon, Jun 25, 2012 at 9:43 AM, Raju Bitter <
r.bitter.mailinglists@googlemail.com> wrote:
> Thanks, found it, is https://issues.apache.org/jira/browse/FLEX-33106 now.
>
> - Raju
>
Re: time to help test the release candidate
Posted by Raju Bitter <r....@googlemail.com>.
Thanks, found it, is https://issues.apache.org/jira/browse/FLEX-33106 now.
- Raju
Re: time to help test the release candidate
Posted by Alex Harui <ah...@adobe.com>.
There is a Jira issue tracking it. It used to be FLEX-61 but got renumbered
on the import. Look for " AIR version of makeApacheFlexForFlashBuilder for
Windows"
On 6/25/12 8:38 AM, "Raju Bitter" <r....@googlemail.com>
wrote:
> Thanks, Alex. I just saw that the comment has been updated in
> flex-config.xml to reflect these changes:
> http://mail-archives.apache.org/mod_mbox/incubator-flex-commits/201206.mbox/%3
> C20120601170314.E6A912388962@eris.apache.org%3E
>
> <!-- Compiler font manager classes, in policy resolution order -->
> <!-- NOTE: For Apache Flex -->
> <!-- AFEFontManager and CFFFontManager both use proprietary
> technology. -->
> <!-- You must install the optional font jars if you wish to
> use embedded fonts -->
> <!-- directly or you can use fontswf to precompile the font
> as a swf. -->
> <managers>
> <manager-class>flash.fonts.JREFontManager</manager-class>
> <manager-class>flash.fonts.BatikFontManager</manager-class>
> <manager-class>flash.fonts.AFEFontManager</manager-class>
> <manager-class>flash.fonts.CFFFontManager</manager-class>
> </managers>
>
> I assume that
> <!-- You must install the optional font jars if you wish to
> use embedded fonts -->
> refers to JARs contained in the Adobe Flex 4.6 SDK, right?
>
> I didn't know that Om is working on such a tool, that's great! What is
> the status of that tool? Is that based on the fontforge project?
> http://fontforge.sourceforge.net/
>
> - Raju
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: time to help test the release candidate
Posted by Raju Bitter <r....@googlemail.com>.
Thanks, Alex. I just saw that the comment has been updated in
flex-config.xml to reflect these changes:
http://mail-archives.apache.org/mod_mbox/incubator-flex-commits/201206.mbox/%3C20120601170314.E6A912388962@eris.apache.org%3E
<!-- Compiler font manager classes, in policy resolution order -->
<!-- NOTE: For Apache Flex -->
<!-- AFEFontManager and CFFFontManager both use proprietary
technology. -->
<!-- You must install the optional font jars if you wish to
use embedded fonts -->
<!-- directly or you can use fontswf to precompile the font
as a swf. -->
<managers>
<manager-class>flash.fonts.JREFontManager</manager-class>
<manager-class>flash.fonts.BatikFontManager</manager-class>
<manager-class>flash.fonts.AFEFontManager</manager-class>
<manager-class>flash.fonts.CFFFontManager</manager-class>
</managers>
I assume that
<!-- You must install the optional font jars if you wish to
use embedded fonts -->
refers to JARs contained in the Adobe Flex 4.6 SDK, right?
I didn't know that Om is working on such a tool, that's great! What is
the status of that tool? Is that based on the fontforge project?
http://fontforge.sourceforge.net/
- Raju
Re: time to help test the release candidate
Posted by Alex Harui <ah...@adobe.com>.
On 6/24/12 10:45 AM, "Raju Bitter" <r....@googlemail.com>
wrote:
> Thanks, Carol. I'll do some tests later this week.
>
> But I remember that it was mentioned on the list that there might be a
> change regarding CFF fonts compared to the 4.6.0. Has there been any
> change for that with the 4.8.0 SDK (like requiring an external to
> convert fonts for CFF)?
The Adobe-owned font managers that handle CFF embedding were not donated, so
a pure Apache release cannot embed CFF fonts. You can use an Adobe Flex
release to create font swfs and embed fonts from the SWFs, or you can use
the tool that Om has been working on to take the Apache kit and copy in the
Adobe font managers and embed CFF fonts directly.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: time to help test the release candidate
Posted by Raju Bitter <r....@googlemail.com>.
Thanks, Carol. I'll do some tests later this week.
But I remember that it was mentioned on the list that there might be a
change regarding CFF fonts compared to the 4.6.0. Has there been any
change for that with the 4.8.0 SDK (like requiring an external to
convert fonts for CFF)?
- Raju
Re: time to help test the release candidate
Posted by Pepe <pe...@gmail.com>.
Hi, Carol.
add defaults.css into the library project
set -include-file compiler option and point the defaults.css
add a class into library project at least
then, you will get warnings.
thanks
Shigeru Nakagaki
2012/6/27 Carol Frampton <cf...@adobe.com>:
>
>
> On 6/26/12 11 :56AM, "Dasa Paddock" <dp...@esri.com> wrote:
>
>>
>>On Jun 26, 2012, at 8:13 AM, Carol Frampton wrote:
>>
>>>
>>>
>>> On 6/22/12 6 :46PM, "Dasa Paddock" <dp...@esri.com> wrote:
>>>
>>>> I downloaded the latest from
>>>> http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the
>>>> makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in
>>>>Flash
>>>> Builder 4.6. I updated my Flex Library Project to use my new 4.8.0 SDK
>>>> and my project compiles, but I get four warnings like this:
>>>>
>>>> "The swc '/Applications/Adobe Flash Builder
>>>> 4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is in
>>>> the library-path, which means dependencies will be linked in without
>>>>the
>>>> styles. This can cause applications, which use the output swc, to have
>>>> missing skins. The swc should be put in the external-library-path."
>>>>
>>>> When I look at my project settings under Flex Library Build Path ->
>>>> Library path, the Framework linkage is "Use default (external)".
>>>>
>>>> If I then expand the charts.swc under Apache Flex 4.8.0, the Link Type
>>>>is
>>>> "Merged into code".
>>>>
>>>> Do I need to manually change it to External like it was for 4.6.0?
>>>>When I
>>>> double click on that, the options dialog that opens does not have "Same
>>>> as framework" checked.
>>>>
>>>> Can this be changed so that it behaves the same as for SDK 4.6.0?
>>>
>>> I'm not sure what you want changed.
>>>
>>> I built a FlashBuilder SDK yesterday afternoon with
>>> makeApacheFlexForFlashBuilder.sh
>>>
>>> In FlashBuilder v4.6, I added my Apache Flex 4.8.0 SDK. I created a new
>>> Flex project called charts, selected the Apache Flex 4.8.0 SDK, and took
>>> all the defaults. I then cut and pasted the contents of BasicPie.mxml
>>> from
>>>
>>>http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf656
>>>8f
>>> -8000.html into the chart.mxml. It build cleanly.
>>>
>>> If I look at the project's Properties -> Library Path the Framework
>>> linkage is "Use SDK default (merged into code)". If I click into
>>> charts.swc the Link Type is "merged into code".
>>>
>>> Caro
>>
>>
>>It is fine for a regular Flex Project. My issue is when creating a new
>>"Flex Library Project". If you try that, the "Framework linkage" is "Use
>>default (external)", but all the swcs are set to merge and their Linkage
>>"Same as framework" checkbox is not checked. I don't think library
>>projects should merge in the Flex SDK swcs and this was working fine with
>>SDK 4.6.0.
>
> I see what you are describing in the Flex Library Build Path however I
> don't get the style warning. I will need to talk to the Flash Builder
> folks and see if they can help diagnose what the issue is.
>
>>
>>Thanks,
>>--Dasa
>
Re: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
On 6/26/12 11 :56AM, "Dasa Paddock" <dp...@esri.com> wrote:
>
>On Jun 26, 2012, at 8:13 AM, Carol Frampton wrote:
>
>>
>>
>> On 6/22/12 6 :46PM, "Dasa Paddock" <dp...@esri.com> wrote:
>>
>>> I downloaded the latest from
>>> http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the
>>> makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in
>>>Flash
>>> Builder 4.6. I updated my Flex Library Project to use my new 4.8.0 SDK
>>> and my project compiles, but I get four warnings like this:
>>>
>>> "The swc '/Applications/Adobe Flash Builder
>>> 4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is in
>>> the library-path, which means dependencies will be linked in without
>>>the
>>> styles. This can cause applications, which use the output swc, to have
>>> missing skins. The swc should be put in the external-library-path."
>>>
>>> When I look at my project settings under Flex Library Build Path ->
>>> Library path, the Framework linkage is "Use default (external)".
>>>
>>> If I then expand the charts.swc under Apache Flex 4.8.0, the Link Type
>>>is
>>> "Merged into code".
>>>
>>> Do I need to manually change it to External like it was for 4.6.0?
>>>When I
>>> double click on that, the options dialog that opens does not have "Same
>>> as framework" checked.
>>>
>>> Can this be changed so that it behaves the same as for SDK 4.6.0?
>>
>> I'm not sure what you want changed.
>>
>> I built a FlashBuilder SDK yesterday afternoon with
>> makeApacheFlexForFlashBuilder.sh
>>
>> In FlashBuilder v4.6, I added my Apache Flex 4.8.0 SDK. I created a new
>> Flex project called charts, selected the Apache Flex 4.8.0 SDK, and took
>> all the defaults. I then cut and pasted the contents of BasicPie.mxml
>> from
>>
>>http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf656
>>8f
>> -8000.html into the chart.mxml. It build cleanly.
>>
>> If I look at the project's Properties -> Library Path the Framework
>> linkage is "Use SDK default (merged into code)". If I click into
>> charts.swc the Link Type is "merged into code".
>>
>> Caro
>
>
>It is fine for a regular Flex Project. My issue is when creating a new
>"Flex Library Project". If you try that, the "Framework linkage" is "Use
>default (external)", but all the swcs are set to merge and their Linkage
>"Same as framework" checkbox is not checked. I don't think library
>projects should merge in the Flex SDK swcs and this was working fine with
>SDK 4.6.0.
I see what you are describing in the Flex Library Build Path however I
don't get the style warning. I will need to talk to the Flash Builder
folks and see if they can help diagnose what the issue is.
>
>Thanks,
>--Dasa
Re: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
The kits were just refreshed again at
http://people.apache.org/~cframpton/ApacheFlexRC/current/
This is getting pretty near final so please check it out.
Alex ran the mustella tests in-house on the kit before this one and there
were 13,000+ passes and about 160 failures (most due to an fxg problem
introduced when we replaced the binary .fla files with source .fxg files).
The fixes for the fxg issues are in this kit.
I added RELEASE_NOTES. Since this is suppose to be a parity release I
thought we should highlight the differences necessitated by both Apache
guidelines and licensing issues. Edits are welcome.
We'd like to start a vote on this kit at the end of day tomorrow (but
don't ask whose day).
Carol
Re: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
On 6/27/12 7 :13PM, "Dasa Paddock" <dp...@esri.com> wrote:
>This build does fix the issue below with Flex Library projects trying to
>merge in the Flex SDK swcs. My previous warnings are gone.
>
>Now the problem is that the textLayout.swc is missing so I'm getting
>errors about Interface IOperation was not found since my code imports
>flashx.undo.IOperation.
>
>I also tried creating a regular new Flex web project with this build, and
>it doesn't compile either since it gets a "ISWFContext was not found"
>error which also comes from textLayout.swc . This is just with Flash
>Builder's default application mxml file.
Yes. textLayout.swc and osmf.swc were incorrectly in the bin kit and I
fixed that bug yesterday.
>
>Is the plan for makeApacheFlexForFlashBuilder.sh to also add the
>textLayout.swc?
I think the majority of people will use Om's tool
(https://issues.apache.org/jira/browse/FLEX-33106) which will take care of
these.
I've been thinking about makeApacheFlexForFlashBuilder.sh and how to
incorporate all the downloads. I plan to do something about that today.
For now, after you build a Flex SDK with the script, cd to the frameworks
directory of the new Flex SDK and type "ant thirdparty-downloads" and that
will get you swfobject, textLayout.swc and osmf.swc downloaded into your
Flex SDK. You will still be missing the BlazeDS integration and the
embedded font jars.
Carol
>
>Thanks,
>--Dasa
>
>On Jun 27, 2012, at 2:55 PM, Carol Frampton wrote:
>
>> http://people.apache.org/~cframpton/ApacheFlexRC/1354725/ which is the
>> currently, the current kit should have the fix for this problem. If you
>> could give it a try I'd appreciate it.
>>
>>
>> Carol
>>
>> On 6/26/12 11 :56AM, "Dasa Paddock" <dp...@esri.com> wrote:
>>
>>>
>>> On Jun 26, 2012, at 8:13 AM, Carol Frampton wrote:
>>>
>>>>
>>>>
>>>> On 6/22/12 6 :46PM, "Dasa Paddock" <dp...@esri.com> wrote:
>>>>
>>>>> I downloaded the latest from
>>>>> http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the
>>>>> makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in
>>>>> Flash
>>>>> Builder 4.6. I updated my Flex Library Project to use my new 4.8.0
>>>>>SDK
>>>>> and my project compiles, but I get four warnings like this:
>>>>>
>>>>> "The swc '/Applications/Adobe Flash Builder
>>>>> 4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is
>>>>>in
>>>>> the library-path, which means dependencies will be linked in without
>>>>> the
>>>>> styles. This can cause applications, which use the output swc, to
>>>>>have
>>>>> missing skins. The swc should be put in the external-library-path."
>>>>>
>>>>> When I look at my project settings under Flex Library Build Path ->
>>>>> Library path, the Framework linkage is "Use default (external)".
>>>>>
>>>>> If I then expand the charts.swc under Apache Flex 4.8.0, the Link
>>>>>Type
>>>>> is
>>>>> "Merged into code".
>>>>>
>>>>> Do I need to manually change it to External like it was for 4.6.0?
>>>>> When I
>>>>> double click on that, the options dialog that opens does not have
>>>>>"Same
>>>>> as framework" checked.
>>>>>
>>>>> Can this be changed so that it behaves the same as for SDK 4.6.0?
>>>>
>>>> I'm not sure what you want changed.
>>>>
>>>> I built a FlashBuilder SDK yesterday afternoon with
>>>> makeApacheFlexForFlashBuilder.sh
>>>>
>>>> In FlashBuilder v4.6, I added my Apache Flex 4.8.0 SDK. I created a
>>>>new
>>>> Flex project called charts, selected the Apache Flex 4.8.0 SDK, and
>>>>took
>>>> all the defaults. I then cut and pasted the contents of BasicPie.mxml
>>>> from
>>>>
>>>>
>>>>http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf6
>>>>56
>>>> 8f
>>>> -8000.html into the chart.mxml. It build cleanly.
>>>>
>>>> If I look at the project's Properties -> Library Path the Framework
>>>> linkage is "Use SDK default (merged into code)". If I click into
>>>> charts.swc the Link Type is "merged into code".
>>>>
>>>> Caro
>>>
>>>
>>> It is fine for a regular Flex Project. My issue is when creating a new
>>> "Flex Library Project". If you try that, the "Framework linkage" is
>>>"Use
>>> default (external)", but all the swcs are set to merge and their
>>>Linkage
>>> "Same as framework" checkbox is not checked. I don't think library
>>> projects should merge in the Flex SDK swcs and this was working fine
>>>with
>>> SDK 4.6.0.
>>>
>>> Thanks,
>>> --Dasa
>>
>>
>
Re: time to help test the release candidate
Posted by Dasa Paddock <dp...@esri.com>.
This build does fix the issue below with Flex Library projects trying to merge in the Flex SDK swcs. My previous warnings are gone.
Now the problem is that the textLayout.swc is missing so I'm getting errors about Interface IOperation was not found since my code imports flashx.undo.IOperation.
I also tried creating a regular new Flex web project with this build, and it doesn't compile either since it gets a "ISWFContext was not found" error which also comes from textLayout.swc . This is just with Flash Builder's default application mxml file.
Is the plan for makeApacheFlexForFlashBuilder.sh to also add the textLayout.swc?
Thanks,
--Dasa
On Jun 27, 2012, at 2:55 PM, Carol Frampton wrote:
> http://people.apache.org/~cframpton/ApacheFlexRC/1354725/ which is the
> currently, the current kit should have the fix for this problem. If you
> could give it a try I'd appreciate it.
>
>
> Carol
>
> On 6/26/12 11 :56AM, "Dasa Paddock" <dp...@esri.com> wrote:
>
>>
>> On Jun 26, 2012, at 8:13 AM, Carol Frampton wrote:
>>
>>>
>>>
>>> On 6/22/12 6 :46PM, "Dasa Paddock" <dp...@esri.com> wrote:
>>>
>>>> I downloaded the latest from
>>>> http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the
>>>> makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in
>>>> Flash
>>>> Builder 4.6. I updated my Flex Library Project to use my new 4.8.0 SDK
>>>> and my project compiles, but I get four warnings like this:
>>>>
>>>> "The swc '/Applications/Adobe Flash Builder
>>>> 4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is in
>>>> the library-path, which means dependencies will be linked in without
>>>> the
>>>> styles. This can cause applications, which use the output swc, to have
>>>> missing skins. The swc should be put in the external-library-path."
>>>>
>>>> When I look at my project settings under Flex Library Build Path ->
>>>> Library path, the Framework linkage is "Use default (external)".
>>>>
>>>> If I then expand the charts.swc under Apache Flex 4.8.0, the Link Type
>>>> is
>>>> "Merged into code".
>>>>
>>>> Do I need to manually change it to External like it was for 4.6.0?
>>>> When I
>>>> double click on that, the options dialog that opens does not have "Same
>>>> as framework" checked.
>>>>
>>>> Can this be changed so that it behaves the same as for SDK 4.6.0?
>>>
>>> I'm not sure what you want changed.
>>>
>>> I built a FlashBuilder SDK yesterday afternoon with
>>> makeApacheFlexForFlashBuilder.sh
>>>
>>> In FlashBuilder v4.6, I added my Apache Flex 4.8.0 SDK. I created a new
>>> Flex project called charts, selected the Apache Flex 4.8.0 SDK, and took
>>> all the defaults. I then cut and pasted the contents of BasicPie.mxml
>>> from
>>>
>>> http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf656
>>> 8f
>>> -8000.html into the chart.mxml. It build cleanly.
>>>
>>> If I look at the project's Properties -> Library Path the Framework
>>> linkage is "Use SDK default (merged into code)". If I click into
>>> charts.swc the Link Type is "merged into code".
>>>
>>> Caro
>>
>>
>> It is fine for a regular Flex Project. My issue is when creating a new
>> "Flex Library Project". If you try that, the "Framework linkage" is "Use
>> default (external)", but all the swcs are set to merge and their Linkage
>> "Same as framework" checkbox is not checked. I don't think library
>> projects should merge in the Flex SDK swcs and this was working fine with
>> SDK 4.6.0.
>>
>> Thanks,
>> --Dasa
>
>
Re: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
http://people.apache.org/~cframpton/ApacheFlexRC/1354725/ which is the
currently, the current kit should have the fix for this problem. If you
could give it a try I'd appreciate it.
Carol
On 6/26/12 11 :56AM, "Dasa Paddock" <dp...@esri.com> wrote:
>
>On Jun 26, 2012, at 8:13 AM, Carol Frampton wrote:
>
>>
>>
>> On 6/22/12 6 :46PM, "Dasa Paddock" <dp...@esri.com> wrote:
>>
>>> I downloaded the latest from
>>> http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the
>>> makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in
>>>Flash
>>> Builder 4.6. I updated my Flex Library Project to use my new 4.8.0 SDK
>>> and my project compiles, but I get four warnings like this:
>>>
>>> "The swc '/Applications/Adobe Flash Builder
>>> 4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is in
>>> the library-path, which means dependencies will be linked in without
>>>the
>>> styles. This can cause applications, which use the output swc, to have
>>> missing skins. The swc should be put in the external-library-path."
>>>
>>> When I look at my project settings under Flex Library Build Path ->
>>> Library path, the Framework linkage is "Use default (external)".
>>>
>>> If I then expand the charts.swc under Apache Flex 4.8.0, the Link Type
>>>is
>>> "Merged into code".
>>>
>>> Do I need to manually change it to External like it was for 4.6.0?
>>>When I
>>> double click on that, the options dialog that opens does not have "Same
>>> as framework" checked.
>>>
>>> Can this be changed so that it behaves the same as for SDK 4.6.0?
>>
>> I'm not sure what you want changed.
>>
>> I built a FlashBuilder SDK yesterday afternoon with
>> makeApacheFlexForFlashBuilder.sh
>>
>> In FlashBuilder v4.6, I added my Apache Flex 4.8.0 SDK. I created a new
>> Flex project called charts, selected the Apache Flex 4.8.0 SDK, and took
>> all the defaults. I then cut and pasted the contents of BasicPie.mxml
>> from
>>
>>http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf656
>>8f
>> -8000.html into the chart.mxml. It build cleanly.
>>
>> If I look at the project's Properties -> Library Path the Framework
>> linkage is "Use SDK default (merged into code)". If I click into
>> charts.swc the Link Type is "merged into code".
>>
>> Caro
>
>
>It is fine for a regular Flex Project. My issue is when creating a new
>"Flex Library Project". If you try that, the "Framework linkage" is "Use
>default (external)", but all the swcs are set to merge and their Linkage
>"Same as framework" checkbox is not checked. I don't think library
>projects should merge in the Flex SDK swcs and this was working fine with
>SDK 4.6.0.
>
>Thanks,
>--Dasa
Re: time to help test the release candidate
Posted by Dasa Paddock <dp...@esri.com>.
On Jun 26, 2012, at 8:13 AM, Carol Frampton wrote:
>
>
> On 6/22/12 6 :46PM, "Dasa Paddock" <dp...@esri.com> wrote:
>
>> I downloaded the latest from
>> http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the
>> makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in Flash
>> Builder 4.6. I updated my Flex Library Project to use my new 4.8.0 SDK
>> and my project compiles, but I get four warnings like this:
>>
>> "The swc '/Applications/Adobe Flash Builder
>> 4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is in
>> the library-path, which means dependencies will be linked in without the
>> styles. This can cause applications, which use the output swc, to have
>> missing skins. The swc should be put in the external-library-path."
>>
>> When I look at my project settings under Flex Library Build Path ->
>> Library path, the Framework linkage is "Use default (external)".
>>
>> If I then expand the charts.swc under Apache Flex 4.8.0, the Link Type is
>> "Merged into code".
>>
>> Do I need to manually change it to External like it was for 4.6.0? When I
>> double click on that, the options dialog that opens does not have "Same
>> as framework" checked.
>>
>> Can this be changed so that it behaves the same as for SDK 4.6.0?
>
> I'm not sure what you want changed.
>
> I built a FlashBuilder SDK yesterday afternoon with
> makeApacheFlexForFlashBuilder.sh
>
> In FlashBuilder v4.6, I added my Apache Flex 4.8.0 SDK. I created a new
> Flex project called charts, selected the Apache Flex 4.8.0 SDK, and took
> all the defaults. I then cut and pasted the contents of BasicPie.mxml
> from
> http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf6568f
> -8000.html into the chart.mxml. It build cleanly.
>
> If I look at the project's Properties -> Library Path the Framework
> linkage is "Use SDK default (merged into code)". If I click into
> charts.swc the Link Type is "merged into code".
>
> Caro
It is fine for a regular Flex Project. My issue is when creating a new "Flex Library Project". If you try that, the "Framework linkage" is "Use default (external)", but all the swcs are set to merge and their Linkage "Same as framework" checkbox is not checked. I don't think library projects should merge in the Flex SDK swcs and this was working fine with SDK 4.6.0.
Thanks,
--Dasa
Re: time to help test the release candidate
Posted by Carol Frampton <cf...@adobe.com>.
On 6/22/12 6 :46PM, "Dasa Paddock" <dp...@esri.com> wrote:
>I downloaded the latest from
>http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the
>makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in Flash
>Builder 4.6. I updated my Flex Library Project to use my new 4.8.0 SDK
>and my project compiles, but I get four warnings like this:
>
>"The swc '/Applications/Adobe Flash Builder
>4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is in
>the library-path, which means dependencies will be linked in without the
>styles. This can cause applications, which use the output swc, to have
>missing skins. The swc should be put in the external-library-path."
>
>When I look at my project settings under Flex Library Build Path ->
>Library path, the Framework linkage is "Use default (external)".
>
>If I then expand the charts.swc under Apache Flex 4.8.0, the Link Type is
>"Merged into code".
>
>Do I need to manually change it to External like it was for 4.6.0? When I
>double click on that, the options dialog that opens does not have "Same
>as framework" checked.
>
>Can this be changed so that it behaves the same as for SDK 4.6.0?
I'm not sure what you want changed.
I built a FlashBuilder SDK yesterday afternoon with
makeApacheFlexForFlashBuilder.sh
In FlashBuilder v4.6, I added my Apache Flex 4.8.0 SDK. I created a new
Flex project called charts, selected the Apache Flex 4.8.0 SDK, and took
all the defaults. I then cut and pasted the contents of BasicPie.mxml
from
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf6568f
-8000.html into the chart.mxml. It build cleanly.
If I look at the project's Properties -> Library Path the Framework
linkage is "Use SDK default (merged into code)". If I click into
charts.swc the Link Type is "merged into code".
Caro
Re: time to help test the release candidate
Posted by Dasa Paddock <dp...@esri.com>.
I downloaded the latest from http://people.apache.org/~cframpton/ApacheFlexRC/current/, ran the makeApacheFlexForFlashBuilder.sh tool and then created a new SDK in Flash Builder 4.6. I updated my Flex Library Project to use my new 4.8.0 SDK and my project compiles, but I get four warnings like this:
"The swc '/Applications/Adobe Flash Builder 4.6/sdks/4.8.0/frameworks/libs/charts.swc' has style defaults and is in the library-path, which means dependencies will be linked in without the styles. This can cause applications, which use the output swc, to have missing skins. The swc should be put in the external-library-path."
When I look at my project settings under Flex Library Build Path -> Library path, the Framework linkage is "Use default (external)".
If I then expand the charts.swc under Apache Flex 4.8.0, the Link Type is "Merged into code".
Do I need to manually change it to External like it was for 4.6.0? When I double click on that, the options dialog that opens does not have "Same as framework" checked.
Can this be changed so that it behaves the same as for SDK 4.6.0?
Thanks,
--Dasa