[svn] 1531: update the flex-sdk-description to 3.0.1

Revision: 1531
Author: [email protected]
Date: 2008-05-02 08:38:50 -0700 (Fri, 02 May 2008)
Log Message:
update the flex-sdk-description to 3.0.1
update the manifest variables so the versions will be in sync with the description file
bug: https://bugs.adobe.com/jira/browse/SDK-15416
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15416
Modified Paths:
flex/sdk/branches/3.0.x/build.properties

Hi,
Have you tried updating to Flex Builder 3.0.2 and then using Flex SDK 3.5?
Updates are available here: http://www.adobe.com/support/flex/downloads_updaters.html#flex3
Alternatively, Flash Builder 4 also provides full support for Flex SDK 3.5.
Thanks,
Andrew
Senior Product Manager, Flash Builder

Similar Messages

[svn] 2756: -make the flex-sdk-description.xml process work like the trunk.

Revision: 2756
Author: [email protected]
Date: 2008-08-06 08:53:11 -0700 (Wed, 06 Aug 2008)
Log Message:
-make the flex-sdk-description.xml process work like the trunk. don't copy the file, create one by echoing the values needed to it.
-update build.properties, make the release value equal the actual release as in this case 3.1
bug:https://bugs.adobe.com/jira/browse/SDK-16367
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16367
Modified Paths:
flex/sdk/branches/3.1.0/build.properties
flex/sdk/branches/3.1.0/build.xml
Removed Paths:
flex/sdk/branches/3.1.0/collateral/en_US/flex-sdk-description.xml

Revision: 2756
Author: [email protected]
Date: 2008-08-06 08:53:11 -0700 (Wed, 06 Aug 2008)
Log Message:
-make the flex-sdk-description.xml process work like the trunk. don't copy the file, create one by echoing the values needed to it.
-update build.properties, make the release value equal the actual release as in this case 3.1
bug:https://bugs.adobe.com/jira/browse/SDK-16367
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16367
Modified Paths:
flex/sdk/branches/3.1.0/build.properties
flex/sdk/branches/3.1.0/build.xml
Removed Paths:
flex/sdk/branches/3.1.0/collateral/en_US/flex-sdk-description.xml

[svn] 1190: Clean the flex-sdk-description. xml during the clean stage of the build so the build starts from a "clean" state.

Revision: 1190
Author: [email protected]
Date: 2008-04-11 07:06:59 -0700 (Fri, 11 Apr 2008)
Log Message:
Clean the flex-sdk-description.xml during the clean stage of the build so the build starts from a "clean" state.
-Set the antTasks.compiled property if the flexTasks have already been compiled to avoid having a failure when calling ant main checkintests package
Modified Paths:
flex/sdk/branches/3.0.x/build.xml

Somewhere in your pom.xml where you are configuring your build dependancies there will be a line <scope>caching</scope> this line is configuring the build to use a flex runtime shared library. This line is generating the error because caching is not a valid dependancy scope in maven 3 however mojos uses it anyway. There was a defect opened against flexmojos; I've linked it below. Froeder's response to the issue was that it was not fixable, that the warning is expected and that we'll have to live with it for now.
https://issues.sonatype.org/browse/FLEXMOJOS-363?page=com.atlassian.jira.plugin.system.iss uetabpanels%3Achangehistory-tabpanel

[svn] 762: -update the 3.0 branch to use build. properties to create the flex-sdk-description.xml

Revision: 762
Author: [email protected]
Date: 2008-03-10 07:44:49 -0700 (Mon, 10 Mar 2008)
Log Message:
-update the 3.0 branch to use build.properties to create the flex-sdk-description.xml
Modified Paths:
flex/sdk/branches/3.0.x/build.properties
flex/sdk/branches/3.0.x/build.xml
Added Paths:
flex/sdk/branches/3.0.x/collateral/en_US/flex-sdk-description.xml

By the way, simply adding the quotes around the lexical names in the sql statement doesn't work. That causes the lexical references to be ignored as simple string values:
SELECT
   '&FLEX_GL_BALANCING_APROMPT' alias_gl_balancing_aprompt
,'&FLEX_GL_ACCOUNT_LPROMPT'   alias_gl_account_lprompt
,'&ACCT_BAL_LPROMPT'          alias_acct_bal_lprompt
FROM dualI turned on statement-level debugging via xdodebug.cfg and saw how it compiled the lexicals. By replicating the call to apps.fnd_flex_xml_publisher_apis.kff_segments_metadata that I found there, I was able to hack together a workaround for this issue.
Please point me to a better way of doing this if possible, as I had to GRANT EXECUTE on this apps package to my custom code schema. Is there a better lexical/flexfields reference than the XML Publisher documentation?
Here is the call I made in my before-report trigger:
--set ACCT_BAL_LPROMPT flexfield segment metadata lexical
begin
apps.fnd_flex_xml_publisher_apis.kff_segments_metadata(
'FLEX_ACCT_BAL_LPROMPT',
'SQLGL',
'GL#',
101,
'GL_BALANCING',
'Y',
'LEFT_PROMPT',
c_FLEX_ACCT_BAL_LPROMPT
end;

[svn:fx-trunk] 10602: -include the flex-sdk-description in the mpl package

Revision: 10602
Author:   [email protected]
Date:     2009-09-25 14:27:02 -0700 (Fri, 25 Sep 2009)
Log Message:
-include the flex-sdk-description in the mpl package
bug: sdk-22539
-fix up the build.xml that we include in the packaged sdk. This has no bearing on building the sdk, but only when someone wants to rebuild the swcs from within a packaged sdk.
bug:sdk-23302
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-22539
    http://bugs.adobe.com/jira/browse/sdk-23302
Modified Paths:
    flex/sdk/trunk/build.xml
    flex/sdk/trunk/frameworks/build_framework.xml

[svn] 746: creating flex-sdk-description. xml is no longer a build machine only function, it will happen in the build .xml.

Revision: 746
Author: [email protected]
Date: 2008-03-05 10:49:48 -0800 (Wed, 05 Mar 2008)
Log Message:
creating flex-sdk-description.xml is no longer a build machine only function, it will happen in the build.xml. There are 3 tokens in the flex-sdk-description.xml file in collateral/en_US/. The release and version vars are set in the build.properties file. build.number can be manually set in the properties in build.xml or can be passed in when building the SDK by using -Dbuild.number= , the default is "workspace"
Modified Paths:
flex/sdk/trunk/build.properties
flex/sdk/trunk/build.xml
Added Paths:
flex/sdk/trunk/collateral/en_US/flex-sdk-description.xml

I'll add that when I run devenv.exe with the flag /TFSLink, VS opens a Team Explorer window that contains the following text:
An exception was encountered while constructing the content of this frame. This information is also logged in "C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.xml".Exception details:System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.VisualStudio.Shell.Interop.IVsShell5.LoadPackageWithContext(Guid& packageGuid, Int32 reason, Guid& context) at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.GetPackage() at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()

[svn] 962: fix SDK-15020 get the proper values in flex-sdk-description. xml when packaging flex_sdk_4.zip

Revision: 962
Author: [email protected]
Date: 2008-03-27 09:49:15 -0700 (Thu, 27 Mar 2008)
Log Message:
fix SDK-15020 get the proper values in flex-sdk-description.xml when packaging flex_sdk_4.zip
-also add setup.sh.build.xml,build.properties
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15020
Modified Paths:
flex/sdk/trunk/build.xml

Revision: 962
Author: [email protected]
Date: 2008-03-27 09:49:15 -0700 (Thu, 27 Mar 2008)
Log Message:
fix SDK-15020 get the proper values in flex-sdk-description.xml when packaging flex_sdk_4.zip
-also add setup.sh.build.xml,build.properties
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15020
Modified Paths:
flex/sdk/trunk/build.xml

[svn] 2942: Add webapps/webtier/WEB-INF/flex/flex-sdk-description. xml to the ignore list.

Revision: 2942
Author: [email protected]
Date: 2008-08-21 07:52:24 -0700 (Thu, 21 Aug 2008)
Log Message:
Add webapps/webtier/WEB-INF/flex/flex-sdk-description.xml to the ignore list.
Property Changed:
flex/sdk/trunk/webapps/webtier/WEB-INF/flex/

java.lang.ClassNotFoundException: flex.messaging.HttpFlexSession
This class exists in flex-messaging-core.jar
Looks like BlazeDS libraries are not loaded. Check if BlazeDS libraries exists in your WEB-INF/lib directory.
webapps\{yourwebapp}\WEB-INF\lib
Hope it helps you.

[svn:fx-trunk] 20696: update build. properties values that are used for flex-sdk-description.xml.

Revision: 20696
Revision: 20696
Author:   [email protected]
Date:     2011-03-08 14:09:49 -0800 (Tue, 08 Mar 2011)
Log Message:
update build.properties values that are used for flex-sdk-description.xml. release.version = 4.5.1 release = Superhero
QE notes: no
Doc notes: no
Bugs: no
Reviewer: lauren
Tests run: no
Is noteworthy for integration: most likely FB will have to be aware of this
Modified Paths:
    flex/sdk/trunk/build.properties

Thats good news.

[svn:osmf:] 11242: Updating the Flex project file to take into account the NetStreamContentProtectableTrait 's name change.

Revision: 11242
Author:   [email protected]
Date:     2009-10-28 13:26:52 -0700 (Wed, 28 Oct 2009)
Log Message:
Updating the Flex project file to take into account the NetStreamContentProtectableTrait's name change.
Modified Paths:
    osmf/trunk/framework/MediaFramework/.actionScriptProperties
    osmf/trunk/framework/MediaFramework/.flexLibProperties

Hi,
This topic seems to be related to VBA coding, better to post your question to the forum for Excel Developer
http://social.msdn.microsoft.com/Forums/office/en-US/home?forum=exceldev
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Tony Chen
TechNet Community Support

For pure AS3 development do we still need to overlay the FLEX SDK?

Hi Guys
I've found this whole SDK overlay business a mess and very confusing. I've found this document
http://www.adobe.com/devnet/air/articles/ane-android-devices.html
which states
"The distribution of the AIR SDK with ASC 2.0 is for pure ActionScript development only. It should not be combined with an existing Flex SDK.
To support Flex application development with newer versions of the AIR SDK, an AIR SDK overlay distribution that does not include ASC 2.0 needs to be overlaid over the Flex SDK bundled with Flash Builder 4.7."
So if we are doing pure AS3 development there is no longer any need to do any 'overlaying' of one SDK Folder onto another. We just need to get the latest AIR SDK with complier ( http://www.adobe.com/devnet/air/air-sdk-download.html )
We should then update the AIR SDK if using Flash Builder via ( http://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder. html ) (Note it still uses the term 'overlay' but you are not really overlaying but replacing).
Is this conclusion correct. Do we just need the SDK with the new compilier and nothing else ?
Can someone from Adobe confirm please ?
Thanks
PS - I've asked this question on the Flash Builder Forom but there's been no response.

Yes, that's correct, for pure AS3 development you need not use the Flex SDK overlay. For this you should use asc2 compiler available at http://www.adobe.com/devnet/air/air-sdk-download.html . Also below are step to overlay your AIR SDK with Flash builder 4.7
1. Exit Flash Builder.
2. Back up the AIR SDK availabe at Application/FB4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/ by copying the entire directory and rename it to something AIRSDKversion. Now, you have two folder AIRSDK(default one) and AIRSDKversion(copied one).
3. Download the appropriate AIR SDK file for your operating system e.g. http://www.adobe.com/devnet/air/air-sdk-download.html unzip and save it on your MAC OS X.
4. On Terminal, run the below command
sudo ditto /path/air3-8_sdk_sa_mac /Applications/Adobe\ Flash\ Builder\ 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK
/path/air3-8_sdk_sa_mac -> path where you downloaded the AIR SDK
/Applications/Adobe\ Flash\ Builder\ 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK -> path where you overlay the new AIR SDK
5. (Optional) To access the new AIR 3.8 APIs, update your application descriptor file to the 3.8 namespace.
To update the namespace, change the xmlns attribute in your application descriptor to: <application xmlns="http://ns.adobe.com/air/application/3.8">
6. (Optional) To ensure that the output SWF file targets SWF version 21, pass an additional compiler argument: -swf-version=21.
Hope this will help.
Regards,
Nimit

Any tutorials on how to use the daily build of the Flex SDK to create Flash Player 10 content?

Is there a tutorial on Adobe on how to use the daily build of
the Flex SDK to create Flash Player 10 content?

The approach you take might depend on a few things, but it boils down to using mouse interactive coding to trigger whatever effect you eventually realize. The code you use will depend on the version of Actionscript you plan to use.
You could make this as a movieclip that is normally stopped at its first frame and when you mouseover or click the movieclip, it animates along its own timeline to its enlarged state. If the thumbnail is very small and the larger version is substantially larger, and both need to be clear images, this might be the better approach.
If this only involves enlarging something, you could also probably realize it just using Actionscript Tween coding rather than timeline animation.

Do I need flash builder 4 to work with the flex sdk?

Is it necessary to use flash builder 4 to work with the flex sdk?
Can you build apps just using the open source flex sdk. If so are there tutorials and books on how to do so?
Thanks in advance for your help.

No, you don't need Flash Builder to use the Flex SDK. If you download the SDK and unzip it, you'll find a 'bin' directory that has the mxmlc compiler in it. You can compile Actionscript or MXML files using that.
./mxmlc MyFlexApp.mxml
If you are building an AIR application, you will use amxmlc
./amxmlc MyAIRFlexApp.mxml
Then, launch your AIR application using adl
./adl.exe MyAIRFlexApp-app.xml
Hope this helps,
Joan

Using Eclipse project definitions to build the Flex SDK

It would be great if someone from Adobe could post on the recommended usage of the Eclipse project definitions in the development/eclipse/ subdirectory of the 3.0.x trunk distribution. I would like to debug some compiler modifications that I am working on.
I saw Peter Farland demo this setup at 360Flex, but was unable to capture all the details of the Eclipse configuration that he discussed in his talk.
thanks!

If you go to the framework project’s properties, there is a section called Flex Library Compiler, you want to use a specific flex sdk (add a new sdk which points to the trunk, and use that) — you are probably building /against/ the wrong sdk, right code, wrong compiler.
- Jono
From: Ben Clinkinbeard <[email protected]>
Reply-To: <[email protected]>
Date: Thu, 3 Apr 2008 12:56:01 -0700
To: <[email protected]>
Subject: Re: Using Eclipse project definitions to build the Flex SDK
A new message was posted by Ben Clinkinbeard in
Developers --
  Using Eclipse project definitions to build the Flex SDK
Sorry, I'm not following. My SDK project is from the trunk.
Thanks,
Ben
On Thu, Apr 3, 2008 at 3:32 PM, Jono Spiro <[email protected]> wrote:
A new message was posted by Jono Spiro in
Developers --
  Using Eclipse project definitions to build the Flex SDK
Try changing the sdk for the framework lib project to trunk (you'll need to add a new flex sdk, name it whatever you want) -- it's in the project properties. It's using the wrong compiler.
- Jono
From: Ben Clinkinbeard <[email protected]>
Reply-To: <[email protected]>
Date: Thu, 3 Apr 2008 05:13:43 -0700
To: <[email protected]>
Subject: Re: Using Eclipse project definitions to build the Flex SDK
A new message was posted by Ben Clinkinbeard in
Developers --
  Using Eclipse project definitions to build the Flex SDK
I am running FB on top of Eclipse 3.3.2.
<http://3.3.2.> <
<http://3.3.2.>
http://3.3.2.> I checked out the whole SDK trunk and can build the main ant task with no errors. I used the instructions mentioned above to create a Flex framework library project and thats where the error comes in. (I had tried to manually build a framework project a few times and it was a nightmare.) I would probably prefer to work on the 3.0.x branch/tag as I hope to submit a patch or two but saw Joe mention that the project defs only existed in the trunk.
Searching Google for the oem error turns up lots of links about projects that had assets deleted and the build got confused but following the instructions on how to fix proved unsuccessful.
Thanks,
Ben
On Thu, Apr 3, 2008 at 1:45 AM, Jono Spiro <[email protected]> wrote:
A new message was posted by Jono Spiro in
Developers --
  Using Eclipse project definitions to build the Flex SDK
I always forget what that error means when it comes up -- though it's been ages since I've seen it last, literally.
Joe: Since you mention Java 1.5, I'm guessing the errors are in the asdoc package? Those should be turned off (read: turned into a warning) -- Eclipse is a little too persnickety about that particular error. There's a preference for this in the Java section under warnings and errors. It's turned off in the trunk dev projects. Otherwise, you should be able to run the compiler directly with no problems (okay, one more caveat: there's a class loader issue with the OEM, fixed in trunk if you look for my Java 1.5 checkin).
Ben: What is your setup? What are you building (Ryan mentions trunk, Joe mentions 30x), which Eclipse, which dev projects, did you build the sdk from the commandline first, etc.?
Cheers,
Jono
View/reply at Using Eclipse project definitions to build the Flex SDK <
<http://www.adobeforums.com/webx?13@@.59b4a9d4/3>
http://www.adobeforums.com/webx?13@@.59b4a9d4/3>
Replies by email are OK.
Use the unsubscribe <
<http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>
http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3> form to cancel your email subscription.
View/reply at Using Eclipse project definitions to build the Flex SDK <
<http://www.adobeforums.com/webx?13@@.59b4a9d4/5>
http://www.adobeforums.com/webx?13@@.59b4a9d4/5>
Replies by email are OK.
Use the unsubscribe <
<http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>
http://www.adobeforums.com/webx?280@@.59b4a9d4!folder=.3c060fa3
<http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3> > form to cancel your email subscription.
View/reply at Using Eclipse project definitions to build the Flex SDK
<http://www.adobeforums.com/webx?13@@.59b4a9d4/6>
Replies by email are OK.
Use the unsubscribe
<http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3> form to cancel your email subscription.
View/reply at Using Eclipse project definitions to build the Flex SDK
<http://www.adobeforums.com/webx?13@@.59b4a9d4/7>
Replies by email are OK.
Use the unsubscribe
<http://www.adobeforums.com/webx?280@@.59b4a9d4!folder=.3c060fa3> form to cancel your email subscription.

'Use minimum version required by the Flex SDK' setting question

Hi,
Can someone explain why after downloading the latest stable Hero SDK (build 19786), which only has fp10.2 support in the framwork/libs/player directory, would the 'Use minimum version required by the Flex SDK' build property still tell Flash Builder to build for fp10.1?
In my flex-config.xml file from this new SDK, I see the target-player attribute is set to 10.2. Is there a bug in burrito that would fail for that value to be used?

No. That should work. Builder also reads the minimum value from flex-config.xml.
Just to check - you added this as a new SDK in Preferences -> Flash Builder -> Installed Flex SDKs and either made that the default SDK or changed the project to use the new SDK, right?

[svn] 1531: update the flex-sdk-description to 3.0.1

Similar Messages

Maybe you are looking for