[jira] [Commented] (FLEX-33558) CameraUI slow return to flex application on certain devices
[ https://issues.apache.org/jira/browse/FLEX-33558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665200#comment-13665200 ] tom chiverton commented on FLEX-33558: -- I'm sure it does break with the extra non-SDK code added. But it's obviously not an SDK bug because the camera feature works fine here with your view without your extra non-SDK code. We should close this issue. > CameraUI slow return to flex application on certain devices > --- > > Key: FLEX-33558 > URL: https://issues.apache.org/jira/browse/FLEX-33558 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.9.0 > Environment: See below >Reporter: Jesse Hellyer > Labels: camera, cameraui > Attachments: JPEGEncoder.as, KPMMobileApplication-app.xml, > MobileData2.as, SDK_4.9.1-testing.fxp, _Super_MobileData2.as, > ViewExistingRegistrationRequests.mxml, ViewProductRegistrationIOS.mxml > > > I have been having very slow results with the CameraUI in flex. Initially, > I was using version 3.1 which was VERY buggy, and I was running into erroring > out returning from the CameraUI, and very slow speeds. > I have since downloaded and installed the newest Apache Flex framework, > 4.9.1. The CameraUI returns VERY fast on our Samsung Tab 7.1 that we bought > a few months ago. On an older Droid Charge phone, that is up to date with > updates, it takes 30-40 seconds to return from the CameraUI into my code. > Same with an iPhone 4 running iOS 6.1. > The line in question is marked in yellow below: > mpLoader.loadFilePromise(mediaPromise); > Essentially, I call the cameraUI when the user hits a button. The native > camera interface opens up right away. A picture is taken. On iOS and > Android both, you have to “save” or “use” the picture. Once you click that > button in the native UI, the camera holds on a black screen for a long time > (up to 30 seconds or so). That’s where the error seems to be, > mpLoader.loadFilePromise(mediaPromise); > You can see in the code I have put output statements to a label showing where > the code is hanging. It hangs right after it writes out -16 > Here is the code: > https://gist.github.com/MrJesse34/5577978 > And here is the XML config file: > https://gist.github.com/MrJesse34/5627336 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33558) CameraUI slow return to flex application on certain devices
[ https://issues.apache.org/jira/browse/FLEX-33558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665177#comment-13665177 ] tom chiverton commented on FLEX-33558: -- Debug build on an iPhone with iOS v6 also works fine. > CameraUI slow return to flex application on certain devices > --- > > Key: FLEX-33558 > URL: https://issues.apache.org/jira/browse/FLEX-33558 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.9.0 > Environment: See below >Reporter: Jesse Hellyer > Labels: camera, cameraui > Attachments: KPMMobileApplication-app.xml, SDK_4.9.1-testing.fxp, > ViewProductRegistrationIOS.mxml > > > I have been having very slow results with the CameraUI in flex. Initially, > I was using version 3.1 which was VERY buggy, and I was running into erroring > out returning from the CameraUI, and very slow speeds. > I have since downloaded and installed the newest Apache Flex framework, > 4.9.1. The CameraUI returns VERY fast on our Samsung Tab 7.1 that we bought > a few months ago. On an older Droid Charge phone, that is up to date with > updates, it takes 30-40 seconds to return from the CameraUI into my code. > Same with an iPhone 4 running iOS 6.1. > The line in question is marked in yellow below: > mpLoader.loadFilePromise(mediaPromise); > Essentially, I call the cameraUI when the user hits a button. The native > camera interface opens up right away. A picture is taken. On iOS and > Android both, you have to “save” or “use” the picture. Once you click that > button in the native UI, the camera holds on a black screen for a long time > (up to 30 seconds or so). That’s where the error seems to be, > mpLoader.loadFilePromise(mediaPromise); > You can see in the code I have put output statements to a label showing where > the code is hanging. It hangs right after it writes out -16 > Here is the code: > https://gist.github.com/MrJesse34/5577978 > And here is the XML config file: > https://gist.github.com/MrJesse34/5627336 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FLEX-33558) CameraUI slow return to flex application on certain devices
[ https://issues.apache.org/jira/browse/FLEX-33558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665025#comment-13665025 ] tom chiverton edited comment on FLEX-33558 at 5/23/13 1:34 PM: --- I hacked the attached view to remove all references to the non-included ViewExistingRegistrationRequests, JPEGEncoder and MobileData2. I found the right button to push from the selection, it opens the camera, I take a picture, and it returns me to the app more or less instantly. Android 2.3, SDK 4.9.1 was (Author: tchiverton): I hacked the attached view to remote all references to the non-included ViewExistingRegistrationRequests, JPEGEncoder and MobileData2. I found the right button to push from the selection, it opens the camera, I take a picture, and it returns me to the app more or less instantly. Android 2.3, SDK 4.9.1 > CameraUI slow return to flex application on certain devices > --- > > Key: FLEX-33558 > URL: https://issues.apache.org/jira/browse/FLEX-33558 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.9.0 > Environment: See below >Reporter: Jesse Hellyer > Labels: camera, cameraui > Attachments: KPMMobileApplication-app.xml, SDK_4.9.1-testing.fxp, > ViewProductRegistrationIOS.mxml > > > I have been having very slow results with the CameraUI in flex. Initially, > I was using version 3.1 which was VERY buggy, and I was running into erroring > out returning from the CameraUI, and very slow speeds. > I have since downloaded and installed the newest Apache Flex framework, > 4.9.1. The CameraUI returns VERY fast on our Samsung Tab 7.1 that we bought > a few months ago. On an older Droid Charge phone, that is up to date with > updates, it takes 30-40 seconds to return from the CameraUI into my code. > Same with an iPhone 4 running iOS 6.1. > The line in question is marked in yellow below: > mpLoader.loadFilePromise(mediaPromise); > Essentially, I call the cameraUI when the user hits a button. The native > camera interface opens up right away. A picture is taken. On iOS and > Android both, you have to “save” or “use” the picture. Once you click that > button in the native UI, the camera holds on a black screen for a long time > (up to 30 seconds or so). That’s where the error seems to be, > mpLoader.loadFilePromise(mediaPromise); > You can see in the code I have put output statements to a label showing where > the code is hanging. It hangs right after it writes out -16 > Here is the code: > https://gist.github.com/MrJesse34/5577978 > And here is the XML config file: > https://gist.github.com/MrJesse34/5627336 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-28913) Scroller's snapElement needs additional check for null dataprovider
[ https://issues.apache.org/jira/browse/FLEX-28913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tom chiverton updated FLEX-28913: - Attachment: SparkAlert.mxml Works as expected in SDK 4.9.1 - clicking the button changes the List height without exception. > Scroller's snapElement needs additional check for null dataprovider > --- > > Key: FLEX-28913 > URL: https://issues.apache.org/jira/browse/FLEX-28913 > Project: Apache Flex > Issue Type: Bug > Components: Spark: Scroller >Affects Versions: Adobe Flex SDK Previous > Environment: Affected OS(s): All OS Platforms > Language Found: English >Reporter: Adobe JIRA > Labels: easyfix, easytest > Attachments: SparkAlert.mxml > > > Found in Adobe ThRead. This occurs when resizing a list with no elements (or > dataprovider=null) + scrollsnapping enabled. > > Actual Results: > TypeError: Error #1009: Cannot access a property or method of a null object > reference. > at > spark.components::Scroller/http://www.adobe.com/2006/flex/mx/internal::snapElement()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:1518] > at > spark.components::Scroller/checkScrollPosition()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:1750] > at > spark.components::Scroller/handleSizeChange()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:1766] > at > spark.components::Scroller/handleSizeChangeOnUpdateComplete()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:2048] > at flash.events::EventDispatcher/dispatchEventFunction() > at flash.events::EventDispatcher/dispatchEvent() > at > mx.core::UIComponent/dispatchEvent()[E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:13152] > at > mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\LayoutManager.as:844] > at > mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1180] > at flash.utils::Timer/_timerDispatch() > at flash.utils::Timer/tick() > > Expected Results: > > > Workaround (if any): -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-30360) Slider can not be set to minimum or maximum value
[
https://issues.apache.org/jira/browse/FLEX-30360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tom chiverton updated FLEX-30360:
-
Attachment: SparkAlert.mxml
Unable to replicate with SDK 4.9.1. Setting slider.value to the maximum value
works as expected. The original automation file appears to be missing though.
> Slider can not be set to minimum or maximum value
> -
>
> Key: FLEX-30360
> URL: https://issues.apache.org/jira/browse/FLEX-30360
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark Components
>Affects Versions: Adobe Flex SDK Previous
> Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>Reporter: Adobe JIRA
> Labels: easytest
> Attachments: SparkAlert.mxml
>
>
> Steps to reproduce:
> 1. use the automation for replaying with the attached file (SliderT.mxml).
> 2. Replay Slider.Change(50) to set the vertical slider to its minimum value
> 50.
>
> Actual Results:
> The Slider is set to 51
>
> Expected Results:
> The Slider is set to 50
>
>
>
> Technical backgroundinformation:
> In the function "SparkSliderBaseAutomationImpl.vSliderValueToPoint" the
> variables adjustedY and adjustedX are set to decimal values (i.e. since the
> thumb size is 11, "thumbW/2" calculates to 5.5 ):
>
> private function vSliderValueToPoint(value:Number):Point
> {
> // we are doing the reverse conversion od the pointToValue in the
> VSlider
> // we even consider the modiifcation done in the mouseDownHanlder for
> the track in the slider
> var thumbRange:Number = slider.track.getLayoutBoundsHeight() -
> slider.thumb.getLayoutBoundsHeight();
> var range:Number = slider.maximum - slider.minimum;
> var localY:Number = thumbRange - ( (Number(value -slider.minimum) /
> range)* thumbRange)
>
> var thumbW:Number = (slider.thumb) ? slider.thumb.width : 0;
> var thumbH:Number = (slider.thumb) ? slider.thumb.height : 0;
>
>
> var adjustedY:Number = localY + (thumbH / 2);
> var adjustedX:Number = thumbW/2;
>
> return new Point(adjustedX,adjustedY);
> }
> The above values are passed to the function "AutomationManager.replayClick",
> where they are assigned to the integers "localX" and "localY" (i.e. the value
> 5.5 is now 5):
>
> public function replayClick(to:IEventDispatcher, sourceEvent:MouseEvent =
> null):Boolean
> {
> sourceEvent = sourceEvent || new MouseEvent(MouseEvent.CLICK);
> pushMouseSimulator(to, sourceEvent);
> map(function(type:String):void
> {
> var localX:int = sourceEvent && !isNaN(sourceEvent.localX) ?
> sourceEvent.localX : 2;
> var localY:int = sourceEvent && !isNaN(sourceEvent.localY) ?
> sourceEvent.localY : 2;
> var event:MouseEvent = new MouseEvent(type, true, false,
> localX, localY);
> event.ctrlKey = sourceEvent.ctrlKey;
> event.shiftKey = sourceEvent.shiftKey;
> event.altKey = sourceEvent.altKey;
> event.buttonDown = (type == MouseEvent.MOUSE_DOWN);
> replayMouseEventInternal(to, event);
> },
> MOUSE_CLICK_TYPES);
> popMouseSimulator();
> return true;
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33558) CameraUI slow return to flex application on certain devices
[ https://issues.apache.org/jira/browse/FLEX-33558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tom chiverton updated FLEX-33558: - Attachment: SDK_4.9.1-testing.fxp > CameraUI slow return to flex application on certain devices > --- > > Key: FLEX-33558 > URL: https://issues.apache.org/jira/browse/FLEX-33558 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.9.0 > Environment: See below >Reporter: Jesse Hellyer > Labels: camera, cameraui > Attachments: KPMMobileApplication-app.xml, SDK_4.9.1-testing.fxp, > ViewProductRegistrationIOS.mxml > > > I have been having very slow results with the CameraUI in flex. Initially, > I was using version 3.1 which was VERY buggy, and I was running into erroring > out returning from the CameraUI, and very slow speeds. > I have since downloaded and installed the newest Apache Flex framework, > 4.9.1. The CameraUI returns VERY fast on our Samsung Tab 7.1 that we bought > a few months ago. On an older Droid Charge phone, that is up to date with > updates, it takes 30-40 seconds to return from the CameraUI into my code. > Same with an iPhone 4 running iOS 6.1. > The line in question is marked in yellow below: > mpLoader.loadFilePromise(mediaPromise); > Essentially, I call the cameraUI when the user hits a button. The native > camera interface opens up right away. A picture is taken. On iOS and > Android both, you have to “save” or “use” the picture. Once you click that > button in the native UI, the camera holds on a black screen for a long time > (up to 30 seconds or so). That’s where the error seems to be, > mpLoader.loadFilePromise(mediaPromise); > You can see in the code I have put output statements to a label showing where > the code is hanging. It hangs right after it writes out -16 > Here is the code: > https://gist.github.com/MrJesse34/5577978 > And here is the XML config file: > https://gist.github.com/MrJesse34/5627336 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33558) CameraUI slow return to flex application on certain devices
[ https://issues.apache.org/jira/browse/FLEX-33558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665025#comment-13665025 ] tom chiverton commented on FLEX-33558: -- I hacked the attached view to remote all references to the non-included ViewExistingRegistrationRequests, JPEGEncoder and MobileData2. I found the right button to push from the selection, it opens the camera, I take a picture, and it returns me to the app more or less instantly. Android 2.3, SDK 4.9.1 > CameraUI slow return to flex application on certain devices > --- > > Key: FLEX-33558 > URL: https://issues.apache.org/jira/browse/FLEX-33558 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.9.0 > Environment: See below >Reporter: Jesse Hellyer > Labels: camera, cameraui > Attachments: KPMMobileApplication-app.xml, SDK_4.9.1-testing.fxp, > ViewProductRegistrationIOS.mxml > > > I have been having very slow results with the CameraUI in flex. Initially, > I was using version 3.1 which was VERY buggy, and I was running into erroring > out returning from the CameraUI, and very slow speeds. > I have since downloaded and installed the newest Apache Flex framework, > 4.9.1. The CameraUI returns VERY fast on our Samsung Tab 7.1 that we bought > a few months ago. On an older Droid Charge phone, that is up to date with > updates, it takes 30-40 seconds to return from the CameraUI into my code. > Same with an iPhone 4 running iOS 6.1. > The line in question is marked in yellow below: > mpLoader.loadFilePromise(mediaPromise); > Essentially, I call the cameraUI when the user hits a button. The native > camera interface opens up right away. A picture is taken. On iOS and > Android both, you have to “save” or “use” the picture. Once you click that > button in the native UI, the camera holds on a black screen for a long time > (up to 30 seconds or so). That’s where the error seems to be, > mpLoader.loadFilePromise(mediaPromise); > You can see in the code I have put output statements to a label showing where > the code is hanging. It hangs right after it writes out -16 > Here is the code: > https://gist.github.com/MrJesse34/5577978 > And here is the XML config file: > https://gist.github.com/MrJesse34/5627336 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33427) Missing translation for postcode components
[ https://issues.apache.org/jira/browse/FLEX-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604954#comment-13604954 ] tom chiverton commented on FLEX-33427: -- wrongFormatPostcodeError is the error an end user will see in the application, incorrectFormatPostcodeError is for the developer to know the string to detect broken ones is itself broken. > Missing translation for postcode components > --- > > Key: FLEX-33427 > URL: https://issues.apache.org/jira/browse/FLEX-33427 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.9.0 >Reporter: Justin Mclean >Priority: Trivial > > Missing translation of error messages for the postcode componets. > In English they are: > invalidCharPostcodeError=The postcode contains invalid characters. > wrongLengthPostcodeError=The postcode is the wrong length. > wrongFormatPostcodeError=The postcode is the wrong format. > incorrectFormatPostcodeError=The postcode format string is incorrect. > Can someone provide translation for this in the following languages: > da_DK - Danish > el_GR - Greek > fi_FL - Finnish > ko_KR - Korean > nb_NO - Norwegian > nl_NL - Dutch > ru_RU - Russian > sw_SE - Swedish > zh_CN - Chinese > zh_TW - Chinese > Done: > de_DE - German > pt_PT - Portuguese (Portugal) > pt_BR - Portuguese (Brazil) > ja_JP - Japanese -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33346) Can only target Flash Player 11.1 in Flash Builder
[ https://issues.apache.org/jira/browse/FLEX-33346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584201#comment-13584201 ] tom chiverton commented on FLEX-33346: -- Right, so lets close this bug then ? > Can only target Flash Player 11.1 in Flash Builder > -- > > Key: FLEX-33346 > URL: https://issues.apache.org/jira/browse/FLEX-33346 > Project: Apache Flex > Issue Type: Bug > Components: Versioning >Affects Versions: Apache Flex 4.9.0 > Environment: Windows 7 x64 - Flash Builder 4.7 >Reporter: Joseph Labrecque > > I've installed Apache Flex 4.9 for use within Flash Builder 4.7 and cannot > specify any target Flash player version below 11.1: > "The currently selected Flex SDK requires minimum Adobe Flash Player version > 11.1.0." > I know that this is a new feature of this SDK (to target 10.2-11.5) but > cannot seem to do it through this software. If there is something that needs > to be modified, I do not see instructions in the release notes. > Requested by Frédéric THOMAS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33346) Can only target Flash Player 11.1 in Flash Builder
[ https://issues.apache.org/jira/browse/FLEX-33346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584162#comment-13584162 ] tom chiverton commented on FLEX-33346: -- Is there any reason I shouldn't send a pull request to make these changes on trunk ? What's the downside to a lower minimum SWF file format version and/or target player ? Because the upside is much greater reach... > Can only target Flash Player 11.1 in Flash Builder > -- > > Key: FLEX-33346 > URL: https://issues.apache.org/jira/browse/FLEX-33346 > Project: Apache Flex > Issue Type: Bug > Components: Versioning >Affects Versions: Apache Flex 4.9.0 > Environment: Windows 7 x64 - Flash Builder 4.7 >Reporter: Joseph Labrecque > > I've installed Apache Flex 4.9 for use within Flash Builder 4.7 and cannot > specify any target Flash player version below 11.1: > "The currently selected Flex SDK requires minimum Adobe Flash Player version > 11.1.0." > I know that this is a new feature of this SDK (to target 10.2-11.5) but > cannot seem to do it through this software. If there is something that needs > to be modified, I do not see instructions in the release notes. > Requested by Frédéric THOMAS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33155) Uncaught exception in compiler, when JRE 1.7 is used
[ https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582352#comment-13582352 ] tom chiverton commented on FLEX-33155: -- On Windows v1.7 is supported. http://www.adobe.com/products/flash-builder/tech-specs.html says "Java™ Virtual Machine (32 bit): Oracle® JRE 1.6 or 1.7" > Uncaught exception in compiler, when JRE 1.7 is used > > > Key: FLEX-33155 > URL: https://issues.apache.org/jira/browse/FLEX-33155 > Project: Apache Flex > Issue Type: Bug > Components: Compiler API >Affects Versions: Apache Flex 4.8 (parity release) > Environment: JRE version 1.7.0_05 , FlashBuilder 4.6 , Apache Flex > 4.8(parity release) >Reporter: Sudhir > Labels: Compiler, java_1.7 > Fix For: Apache Flex 4.9.0 > > Attachments: UncaughtException_Compiler.log > > > Steps to Reproduce: > 1. Download the Apache SDK using AIR tool (available at > http://people.apache.org/~bigosmallm/installapacheflex/ ) which also packages > the SDK to use with Flash builder. > 2. Download JRE 1.7 > 3. Install Flash Builder 4.6 > 4. Go to the installed FB location and delete the JRE folder already present > in the FB installed location > 5. Copy the JRE 1.7 folder into the installed location. (jre folder should be > renamed from jre7 to jre) > FB will now use JRE 1.7 instead of using the bundled 1.6 > 6. Configure FB to use Apache SDK which was downloaded in step 1. > 7. Create a Flex project using Apache SDK > 8. Now create a new AS class inside the new project > Actual result: Internal build error in problems view. The error log says that > there was an uncaught exception in the compiler. > Expected result: There should be no such errors > Workaround: Add a line "-Djava.util.Arrays.useLegacyMergeSort=true" in the > FlashBuilder.ini > Note: This issue is specific to Apache SDK. It is working fine with the > released version of Flex SDK 4.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33155) Uncaught exception in compiler, when JRE 1.7 is used
[ https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582311#comment-13582311 ] tom chiverton commented on FLEX-33155: -- Happens to me in FB 4.7 > Uncaught exception in compiler, when JRE 1.7 is used > > > Key: FLEX-33155 > URL: https://issues.apache.org/jira/browse/FLEX-33155 > Project: Apache Flex > Issue Type: Bug > Components: Compiler API >Affects Versions: Apache Flex 4.8 (parity release) > Environment: JRE version 1.7.0_05 , FlashBuilder 4.6 , Apache Flex > 4.8(parity release) >Reporter: Sudhir > Labels: Compiler, java_1.7 > Fix For: Apache Flex 4.9.0 > > Attachments: UncaughtException_Compiler.log > > > Steps to Reproduce: > 1. Download the Apache SDK using AIR tool (available at > http://people.apache.org/~bigosmallm/installapacheflex/ ) which also packages > the SDK to use with Flash builder. > 2. Download JRE 1.7 > 3. Install Flash Builder 4.6 > 4. Go to the installed FB location and delete the JRE folder already present > in the FB installed location > 5. Copy the JRE 1.7 folder into the installed location. (jre folder should be > renamed from jre7 to jre) > FB will now use JRE 1.7 instead of using the bundled 1.6 > 6. Configure FB to use Apache SDK which was downloaded in step 1. > 7. Create a Flex project using Apache SDK > 8. Now create a new AS class inside the new project > Actual result: Internal build error in problems view. The error log says that > there was an uncaught exception in the compiler. > Expected result: There should be no such errors > Workaround: Add a line "-Djava.util.Arrays.useLegacyMergeSort=true" in the > FlashBuilder.ini > Note: This issue is specific to Apache SDK. It is working fine with the > released version of Flex SDK 4.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33155) Uncaught exception in compiler, when JRE 1.7 is used
[ https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582264#comment-13582264 ] tom chiverton commented on FLEX-33155: -- Thanks for reopening. It doesn't need code attached to reproduce; see the steps already given ? As a quicker alternative, you can start Eclipse with a different JVM by adding to the start of eclipse.ini: -vm c:\Program Files\Java\jdk1.6.0_38\bin\javaw.exe etc. - note it must be on two lines. > Uncaught exception in compiler, when JRE 1.7 is used > > > Key: FLEX-33155 > URL: https://issues.apache.org/jira/browse/FLEX-33155 > Project: Apache Flex > Issue Type: Bug > Components: Compiler API >Affects Versions: Apache Flex 4.8 (parity release) > Environment: JRE version 1.7.0_05 , FlashBuilder 4.6 , Apache Flex > 4.8(parity release) >Reporter: Sudhir > Labels: Compiler, java_1.7 > Fix For: Apache Flex 4.9.0 > > Attachments: UncaughtException_Compiler.log > > > Steps to Reproduce: > 1. Download the Apache SDK using AIR tool (available at > http://people.apache.org/~bigosmallm/installapacheflex/ ) which also packages > the SDK to use with Flash builder. > 2. Download JRE 1.7 > 3. Install Flash Builder 4.6 > 4. Go to the installed FB location and delete the JRE folder already present > in the FB installed location > 5. Copy the JRE 1.7 folder into the installed location. (jre folder should be > renamed from jre7 to jre) > FB will now use JRE 1.7 instead of using the bundled 1.6 > 6. Configure FB to use Apache SDK which was downloaded in step 1. > 7. Create a Flex project using Apache SDK > 8. Now create a new AS class inside the new project > Actual result: Internal build error in problems view. The error log says that > there was an uncaught exception in the compiler. > Expected result: There should be no such errors > Workaround: Add a line "-Djava.util.Arrays.useLegacyMergeSort=true" in the > FlashBuilder.ini > Note: This issue is specific to Apache SDK. It is working fine with the > released version of Flex SDK 4.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33155) Uncaught exception in compiler, when JRE 1.7 is used
[ https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582231#comment-13582231 ] tom chiverton commented on FLEX-33155: -- This shouldn't have been closed should it ? The exception still occurs when using 1.7 unless you work around it. As v1.7 is (now) supported, that's an argument for keeping it open not closing it, no ? > Uncaught exception in compiler, when JRE 1.7 is used > > > Key: FLEX-33155 > URL: https://issues.apache.org/jira/browse/FLEX-33155 > Project: Apache Flex > Issue Type: Bug > Components: Compiler API >Affects Versions: Apache Flex 4.8 (parity release) > Environment: JRE version 1.7.0_05 , FlashBuilder 4.6 , Apache Flex > 4.8(parity release) >Reporter: Sudhir >Assignee: Carol Frampton > Labels: Compiler, java_1.7 > Fix For: Apache Flex 4.9.0 > > Attachments: UncaughtException_Compiler.log > > > Steps to Reproduce: > 1. Download the Apache SDK using AIR tool (available at > http://people.apache.org/~bigosmallm/installapacheflex/ ) which also packages > the SDK to use with Flash builder. > 2. Download JRE 1.7 > 3. Install Flash Builder 4.6 > 4. Go to the installed FB location and delete the JRE folder already present > in the FB installed location > 5. Copy the JRE 1.7 folder into the installed location. (jre folder should be > renamed from jre7 to jre) > FB will now use JRE 1.7 instead of using the bundled 1.6 > 6. Configure FB to use Apache SDK which was downloaded in step 1. > 7. Create a Flex project using Apache SDK > 8. Now create a new AS class inside the new project > Actual result: Internal build error in problems view. The error log says that > there was an uncaught exception in the compiler. > Expected result: There should be no such errors > Workaround: Add a line "-Djava.util.Arrays.useLegacyMergeSort=true" in the > FlashBuilder.ini > Note: This issue is specific to Apache SDK. It is working fine with the > released version of Flex SDK 4.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FLEX-33155) Uncaught exception in compiler, when JRE 1.7 is used
[ https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582042#comment-13582042 ] tom chiverton edited comment on FLEX-33155 at 2/20/13 9:09 AM: --- Java 1.6 is end of life in < two weeks. Any progress ? was (Author: tchiverton): 1.7 is end of life in < two weeks. Any progress ? > Uncaught exception in compiler, when JRE 1.7 is used > > > Key: FLEX-33155 > URL: https://issues.apache.org/jira/browse/FLEX-33155 > Project: Apache Flex > Issue Type: Bug > Components: Compiler API >Affects Versions: Apache Flex 4.8 (parity release) > Environment: JRE version 1.7.0_05 , FlashBuilder 4.6 , Apache Flex > 4.8(parity release) >Reporter: Sudhir > Labels: Compiler, java_1.7 > Attachments: UncaughtException_Compiler.log > > > Steps to Reproduce: > 1. Download the Apache SDK using AIR tool (available at > http://people.apache.org/~bigosmallm/installapacheflex/ ) which also packages > the SDK to use with Flash builder. > 2. Download JRE 1.7 > 3. Install Flash Builder 4.6 > 4. Go to the installed FB location and delete the JRE folder already present > in the FB installed location > 5. Copy the JRE 1.7 folder into the installed location. (jre folder should be > renamed from jre7 to jre) > FB will now use JRE 1.7 instead of using the bundled 1.6 > 6. Configure FB to use Apache SDK which was downloaded in step 1. > 7. Create a Flex project using Apache SDK > 8. Now create a new AS class inside the new project > Actual result: Internal build error in problems view. The error log says that > there was an uncaught exception in the compiler. > Expected result: There should be no such errors > Workaround: Add a line "-Djava.util.Arrays.useLegacyMergeSort=true" in the > FlashBuilder.ini > Note: This issue is specific to Apache SDK. It is working fine with the > released version of Flex SDK 4.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33155) Uncaught exception in compiler, when JRE 1.7 is used
[ https://issues.apache.org/jira/browse/FLEX-33155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582042#comment-13582042 ] tom chiverton commented on FLEX-33155: -- 1.7 is end of life in < two weeks. Any progress ? > Uncaught exception in compiler, when JRE 1.7 is used > > > Key: FLEX-33155 > URL: https://issues.apache.org/jira/browse/FLEX-33155 > Project: Apache Flex > Issue Type: Bug > Components: Compiler API >Affects Versions: Apache Flex 4.8 (parity release) > Environment: JRE version 1.7.0_05 , FlashBuilder 4.6 , Apache Flex > 4.8(parity release) >Reporter: Sudhir > Labels: Compiler, java_1.7 > Attachments: UncaughtException_Compiler.log > > > Steps to Reproduce: > 1. Download the Apache SDK using AIR tool (available at > http://people.apache.org/~bigosmallm/installapacheflex/ ) which also packages > the SDK to use with Flash builder. > 2. Download JRE 1.7 > 3. Install Flash Builder 4.6 > 4. Go to the installed FB location and delete the JRE folder already present > in the FB installed location > 5. Copy the JRE 1.7 folder into the installed location. (jre folder should be > renamed from jre7 to jre) > FB will now use JRE 1.7 instead of using the bundled 1.6 > 6. Configure FB to use Apache SDK which was downloaded in step 1. > 7. Create a Flex project using Apache SDK > 8. Now create a new AS class inside the new project > Actual result: Internal build error in problems view. The error log says that > there was an uncaught exception in the compiler. > Expected result: There should be no such errors > Workaround: Add a line "-Djava.util.Arrays.useLegacyMergeSort=true" in the > FlashBuilder.ini > Note: This issue is specific to Apache SDK. It is working fine with the > released version of Flex SDK 4.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLEX-33404) Compile error with Apache Flex 4.9 and not Adobe 4.1
[
https://issues.apache.org/jira/browse/FLEX-33404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581173#comment-13581173
]
tom chiverton commented on FLEX-33404:
--
" So you just replace that '*' with 'Object' and it'll compile just fine. "
It certainly does.
Probably a more minor bug then; Object should be less generic than * so how
come it doesn't work ?
> Compile error with Apache Flex 4.9 and not Adobe 4.1
>
>
> Key: FLEX-33404
> URL: https://issues.apache.org/jira/browse/FLEX-33404
> Project: Apache Flex
> Issue Type: Bug
> Components: Skinning
>Affects Versions: Apache Flex 4.9.0
> Environment: WinXP 32bit
>Reporter: tom chiverton
>Priority: Minor
> Attachments: src.zip, test skin.fxp
>
>
> I'm trying to build a project that is fine with the Adobe 4.1A SDK using the
> Apache 4.9 SDK, but we have a Skin that says
>
> [HostComponent("com.ev.global.view.components.Dashboard")]
>
> Adding CDATA inside the Metadata doesn't appear to change things.
> Attached is a reproducible test case - this compiles out of the box with the
> Adobe 4.1 compiler, but throws an error with the Apache 4.9 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33404) Compile error with Apache Flex 4.9 and not Adobe 4.1
[
https://issues.apache.org/jira/browse/FLEX-33404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tom chiverton updated FLEX-33404:
-
Priority: Minor (was: Major)
> Compile error with Apache Flex 4.9 and not Adobe 4.1
>
>
> Key: FLEX-33404
> URL: https://issues.apache.org/jira/browse/FLEX-33404
> Project: Apache Flex
> Issue Type: Bug
> Components: Skinning
>Affects Versions: Apache Flex 4.9.0
> Environment: WinXP 32bit
>Reporter: tom chiverton
>Priority: Minor
> Attachments: src.zip, test skin.fxp
>
>
> I'm trying to build a project that is fine with the Adobe 4.1A SDK using the
> Apache 4.9 SDK, but we have a Skin that says
>
> [HostComponent("com.ev.global.view.components.Dashboard")]
>
> Adding CDATA inside the Metadata doesn't appear to change things.
> Attached is a reproducible test case - this compiles out of the box with the
> Adobe 4.1 compiler, but throws an error with the Apache 4.9 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33404) Compile error with Apache Flex 4.9 and not Adobe 4.1
[
https://issues.apache.org/jira/browse/FLEX-33404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tom chiverton updated FLEX-33404:
-
Attachment: test skin.fxp
Exported Flex Builder project
> Compile error with Apache Flex 4.9 and not Adobe 4.1
>
>
> Key: FLEX-33404
> URL: https://issues.apache.org/jira/browse/FLEX-33404
> Project: Apache Flex
> Issue Type: Bug
> Components: Skinning
>Affects Versions: Apache Flex 4.9.0
> Environment: WinXP 32bit
>Reporter: tom chiverton
> Attachments: src.zip, test skin.fxp
>
>
> I'm trying to build a project that is fine with the Adobe 4.1A SDK using the
> Apache 4.9 SDK, but we have a Skin that says
>
> [HostComponent("com.ev.global.view.components.Dashboard")]
>
> Adding CDATA inside the Metadata doesn't appear to change things.
> Attached is a reproducible test case - this compiles out of the box with the
> Adobe 4.1 compiler, but throws an error with the Apache 4.9 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLEX-33404) Compile error with Apache Flex 4.9 and not Adobe 4.1
[
https://issues.apache.org/jira/browse/FLEX-33404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tom chiverton updated FLEX-33404:
-
Attachment: src.zip
Source files
> Compile error with Apache Flex 4.9 and not Adobe 4.1
>
>
> Key: FLEX-33404
> URL: https://issues.apache.org/jira/browse/FLEX-33404
> Project: Apache Flex
> Issue Type: Bug
> Components: Skinning
>Affects Versions: Apache Flex 4.9.0
> Environment: WinXP 32bit
>Reporter: tom chiverton
> Attachments: src.zip, test skin.fxp
>
>
> I'm trying to build a project that is fine with the Adobe 4.1A SDK using the
> Apache 4.9 SDK, but we have a Skin that says
>
> [HostComponent("com.ev.global.view.components.Dashboard")]
>
> Adding CDATA inside the Metadata doesn't appear to change things.
> Attached is a reproducible test case - this compiles out of the box with the
> Adobe 4.1 compiler, but throws an error with the Apache 4.9 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FLEX-33404) Compile error with Apache Flex 4.9 and not Adobe 4.1
tom chiverton created FLEX-33404:
Summary: Compile error with Apache Flex 4.9 and not Adobe 4.1
Key: FLEX-33404
URL: https://issues.apache.org/jira/browse/FLEX-33404
Project: Apache Flex
Issue Type: Bug
Components: Skinning
Affects Versions: Apache Flex 4.9.0
Environment: WinXP 32bit
Reporter: tom chiverton
I'm trying to build a project that is fine with the Adobe 4.1A SDK using the
Apache 4.9 SDK, but we have a Skin that says
[HostComponent("com.ev.global.view.components.Dashboard")]
Adding CDATA inside the Metadata doesn't appear to change things.
Attached is a reproducible test case - this compiles out of the box with the
Adobe 4.1 compiler, but throws an error with the Apache 4.9 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
