id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
811 |
TISTUD-2647
|
10/25/2012 18:45:36
|
Window type is used as global namespace for all JS files
|
We explicitly make use of "Window" as the assumed global namespace for all JS files. This is only correct if the file is intended to be run inside a browser. With the use of TiMobile JS and Node.JS, in that environment, "Global" is the type we should be querying - not Window. We may need to alter indexing/CA to determine the proper Global type to use based on the file's location, or project nature. We can safely assume that any inline JS in an HTML file will use Window. Beyond that we may just want to assume Window for all except Titanium Mobile or Node.ACS projects.
| 8 |
812 |
TISTUD-2650
|
10/25/2012 22:59:56
|
Studio locks when packaging a MobileWeb app
|
When packaging a MobileWeb app using the Packaging Wizard, the Studio locks and the progress bar is showing that the process is waiting. The only way to get out of it is to restart.
| 8 |
813 |
TISTUD-2653
|
10/26/2012 00:42:11
|
Dashboard: Configure: MobileWeb: configure link open general browser settings instead of mobileweb runtime settings
|
Dashboard > Configure > MobileWeb > 'here' opens General Browser Preferences instead of MobileWeb sdk runtime preferences.
| 3 |
814 |
TISTUD-2654
|
10/26/2012 00:53:07
|
Android: pass in jdk bin to python scripts
|
If jdk bin is not on the path, the android build scripts will fail. Studio needs to pass in this variable to the python scripts so the user does not have to set the path. Build Console: {code} [INFO] logfile = C:\Users\tester\Desktop\TISTUD-RC\workspace\Project\build.log [INFO] Building Project for Android ... one moment [ERROR] JDK version 'javac' is not recognized as an internal or external command, operable program or batch file. detected, but at least 1.6.0 is required [ERROR] Application Installer abnormal process termination. Process exit value was 1 {code} Steps to Reproduce: 1. Remove jdk../bin from the path (the one that has 'javac'). 2. Launch Titanium Studio. 3. Run a Titanium SDK Android project. Actual Result: javac error. Expected Result: Project builds and launches correctly.
| 5 |
815 |
TISTUD-2662
|
10/26/2012 18:39:50
|
JS Content Assist doesn't contain ECMAScript 6 types/properties
|
There are no entries for some of the new APIs introduced in ECMAScript 6/Harmony. Keep in mind that this spec is still under development and much of it is experimental. Firefox tends to be a little ahead of the game, with Chrome also working on some of it. Note that this involves adding 4 new types: Map, Set, WeakMap, Proxy Additionally there are a number of new properties/methods on existing types. We need to add metadata for the new items added in ECMAScript 6. See: - http://kangax.github.com/es5-compat-table/es6/ - https://developer.mozilla.org/en-US/docs/JavaScript/ECMAScript_6_support_in_Mozilla - http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts
| 0 |
816 |
TISTUD-2664
|
10/26/2012 21:07:19
|
Enable debugging of Alloy projects in Studio
|
As a developer I want to debug my Alloy projects using the Studio debugger
| 0 |
817 |
TISTUD-2672
|
10/27/2012 17:05:30
|
Create Tizen project target
|
Like iOS, Android, BlackBerry and Windows, Tizen needs to have a Project template. A developer should be able to create a Tizen project and then build and run to emulator or device.
| 0 |
818 |
TISTUD-2674
|
10/29/2012 19:57:05
|
Unify the installation process of npm components on both Mac and Linux
|
Currently, the installation mechanism of npm components (alloy, acs, cli) is inconsistent between Mac and Linux. On Mac, we prompt for password only once for the installation of all components during startup. However on linux, we prompt password for installation of every component (as we still use gksudo). Since we have our password prompt dialog now, it can be used in Linux as well to have consistent behavior across all platforms.
| 0 |
819 |
TISTUD-2676
|
10/29/2012 21:29:12
|
Windows installer: installer shows old splash screen on startup.
|
The Titanium Studio 3.0.0.201210271747 installer shows the old splash screen before loading the new installer. Steps to reproduce: 1. Install Titanium Studio on Windows 7. Expected results: The install should flash the new splash screen. Actual results: The installer flashes the old splash screen.
| 2 |
820 |
TISTUD-2677
|
10/29/2012 22:37:08
|
Run Diagnostic Test: improve diagnostics to include more fields and better format for testing
|
Currently the diagnostic log needs a core set of fields at the top that can be used for bug environments (see this bug environment for ideal/suggested/proposed example). Suggested Top Fields: {code} Host OS: Mac OS X Host OS Version: Mountain Lion 10.8.2 // different format w/new info Android SDK Version: r20.0.3 // new Android NDK Version: r8b // new Xcode Version: 4.5.1 // new Titanium Studio Version: 3.0.0.201210271747 // different format/location Latest Titanium SDK: 3.0.0.v20121026170116 // new Titanium CLI Version: 3.0.11 Titanium CLI Enabled: false // new Alloy Version: 0.3.0 Node.ACS Version: 0.9.24 {code} Current Diagnostic Log: {code} Host OS: Mac OS X OS Arch: x86 JRE Version: 1.6.0_37 JRE Vendor: Apple Inc. JRE Home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Install Directory: file:/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/ Version: 3.0.0.201210271747 VM Arguments: -Dtitanium.dashboardUrl=http://preview.appcelerator.com/dashboard/index.php -Dtitanium.sdkRequirementsUrl=http://preview.appcelerator.com/dashboard/sdk_info.json -Xms40m -Xmx1024m -Declipse.p2.unsignedPolicy=allow -Declipse.log.size.max=10000 -Declipse.log.backup.max=5 -Xdock:icon=../Resources/titanium.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=256m -Djava.class.path=/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/TitaniumStudio.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar Workspace Directory: file:/Users/dhyde/Desktop/TISTUD-RC/workspace/ Language: en_US Titanium SDK Version: 1.7.5 Mobile SDK Timestamp: 11/02/11 17:00 Mobile SDK Build Number: ab20af7 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.7.5 Titanium SDK Version: 1.8.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 12/22/11 13:09 Mobile SDK Build Number: fbdc96f Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.8.0.1 Titanium SDK Version: 1.8.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 01/27/12 17:31 Mobile SDK Build Number: a24502a Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.8.1 Titanium SDK Version: 1.8.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 02/23/12 17:46 Mobile SDK Build Number: 59b3a90 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.8.2 Titanium SDK Version: 2.0.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 03/30/12 10:32 Mobile SDK Build Number: b091bae Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.0.GA Titanium SDK Version: 2.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 04/12/12 16:33 Mobile SDK Build Number: 999c68a Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA Titanium SDK Version: 2.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 04/12/12 16:33 Mobile SDK Build Number: 999c68a Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2 Titanium SDK Version: 2.0.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 05/30/12 10:21 Mobile SDK Build Number: 2ff31a3 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.2.GA Titanium SDK Version: 2.1.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 06/28/12 12:16 Mobile SDK Build Number: 6e3cab6 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.0.GA Titanium SDK Version: 2.1.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 07/27/12 14:01 Mobile SDK Build Number: 0fd84a2 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.1.GA Titanium SDK Version: 2.1.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 08/24/12 14:46 Mobile SDK Build Number: ed7f777 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.2.GA Titanium SDK Version: 2.1.3 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 10/02/12 16:16 Mobile SDK Build Number: 15997d0 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.3.GA Titanium SDK Version: 3.0.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 10/26/12 17:01 Mobile SDK Build Number: e552b27 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121026170116 Titanium CLI Version: 3.0.11 Alloy Version: 0.3.0 Node.ACS Version: 0.9.24 {code} Suggested Diagnostic Log: {code} Host OS: Mac OS X Host OS Version: Mountain Lion 10.8.2 Android SDK Version: r20.0.3 Android NDK Version: r8b Xcode Version: 4.5.1 Titanium Studio Version: 3.0.0.201210271747 Latest Titanium SDK: 3.0.0.v20121026170116 Titanium CLI Version: 3.0.11 Titanium CLI Enabled: false Alloy Version: 0.3.0 Node.ACS Version: 0.9.24 OS Arch: x86 JRE Version: 1.6.0_37 JRE Vendor: Apple Inc. JRE Home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Install Directory: file:/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/ Version: 3.0.0.201210271747 VM Arguments: -Dtitanium.dashboardUrl=http://preview.appcelerator.com/dashboard/index.php -Dtitanium.sdkRequirementsUrl=http://preview.appcelerator.com/dashboard/sdk_info.json -Xms40m -Xmx1024m -Declipse.p2.unsignedPolicy=allow -Declipse.log.size.max=10000 -Declipse.log.backup.max=5 -Xdock:icon=../Resources/titanium.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=256m -Djava.class.path=/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/TitaniumStudio.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar Workspace Directory: file:/Users/dhyde/Desktop/TISTUD-RC/workspace/ Language: en_US Titanium SDK Version: 1.7.5 Mobile SDK Timestamp: 11/02/11 17:00 Mobile SDK Build Number: ab20af7 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.7.5 Titanium SDK Version: 1.8.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 12/22/11 13:09 Mobile SDK Build Number: fbdc96f Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.8.0.1 Titanium SDK Version: 1.8.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 01/27/12 17:31 Mobile SDK Build Number: a24502a Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.8.1 Titanium SDK Version: 1.8.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 02/23/12 17:46 Mobile SDK Build Number: 59b3a90 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/1.8.2 Titanium SDK Version: 2.0.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 03/30/12 10:32 Mobile SDK Build Number: b091bae Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.0.GA Titanium SDK Version: 2.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 04/12/12 16:33 Mobile SDK Build Number: 999c68a Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA Titanium SDK Version: 2.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 04/12/12 16:33 Mobile SDK Build Number: 999c68a Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2 Titanium SDK Version: 2.0.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 05/30/12 10:21 Mobile SDK Build Number: 2ff31a3 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.0.2.GA Titanium SDK Version: 2.1.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 06/28/12 12:16 Mobile SDK Build Number: 6e3cab6 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.0.GA Titanium SDK Version: 2.1.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 07/27/12 14:01 Mobile SDK Build Number: 0fd84a2 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.1.GA Titanium SDK Version: 2.1.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 08/24/12 14:46 Mobile SDK Build Number: ed7f777 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.2.GA Titanium SDK Version: 2.1.3 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 10/02/12 16:16 Mobile SDK Build Number: 15997d0 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/2.1.3.GA Titanium SDK Version: 3.0.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 10/26/12 17:01 Mobile SDK Build Number: e552b27 Titanium SDK Location: /Users/dhyde/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121026170116 {code}
| 8 |
821 |
TISTUD-2678
|
10/29/2012 23:38:21
|
JSCodeScanner: Token not mapped: 7 warnings in log for large text file
|
When a large file is edited in Studio, there are many of these warnings in the log: {code} !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.861 !MESSAGE (Build 3.0.0.201210271747) [WARNING] JSCodeScanner: Token not mapped: 7>>"Close Window"<< !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.861 !MESSAGE (Build 3.0.0.201210271747) [WARNING] JSCodeScanner: Token not mapped: 7>>"click"<< !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.861 !MESSAGE (Build 3.0.0.201210271747) [WARNING] JSCodeScanner: Token not mapped: 7>>"white"<< !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.861 !MESSAGE (Build 3.0.0.201210271747) [WARNING] JSCodeScanner: Token not mapped: 7>>"black"<< !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.861 !MESSAGE (Build 3.0.0.201210271747) [WARNING] JSCodeScanner: Token not mapped: 7>>"auto"<< !ENTRY com.aptana.editor.js 2 0 2012-10-29 16:26:55.862 !MESSAGE (Build 3.0.0.201210271747) [WARNING] JSCodeScanner: Token not mapped: 7>>"auto"<< {code} This does not occur in Studio 2.1.2. This appears to be a regression. Steps to Reproduce: 1. Open giant file in studio (attached). 2. Save the file, scroll up and down (from top of file to bottom of file). 3. Check log for warnings. Actual Result: Many Token not mapped warnings. Expected Result: No Token not mapped warnings.
| 8 |
822 |
TISTUD-2679
|
10/30/2012 00:18:32
|
Unhandled event loop exception Java heap space crash and freeze when editing large file
|
Editing the large attached file reliably crashes and freezes studio. 3 system crash logs attached. Studio often will crash when it reloads after the first crash. This does not occur with Studio 2.1.2, but there is some slow-down. Steps to Reproduce: 1. Edit large attached file in studio. 2. Scroll top to bottom, copy the contents, delete the contents, paste them back, save, repeat. Actual Result: Studio freezes, jstack doesn't work, heap error, system crash reports. Expected Result: Perhaps some slow-down.
| 8 |
823 |
TISTUD-2688
|
10/31/2012 19:15:18
|
iOS: Ti.API: some console logging calls with array args do not print array to console
|
Some console logging calls with array args do not print array to console. The cases are: Ti.API.log('freeform', ['arg0', 'arg1']) and Ti.API.timestamp(['arg0', 'arg1']) This does not occur in MobileWeb or Android. This is a parity issue. This does not occur to other array printing calls in iOS. This is an internal inconsistency. Steps to Reproduce: 1. Run code: {code} Ti.API.log('log', ['Ti.API.log.0', 'Ti.API.log.1']); Ti.API.timestamp(['Ti.API.timestamp.0', 'Ti.API.timestamp.1']); {code} Actual Result: {code} [LOG] ( [TIMESTAMP] 373334748.160333 ( {code} Expected Result: {code} [LOG] ( arg0, arg1 ) [TIMESTAMP] 373334748.160333 ( arg0, arg1 ) {code} There are issues with both the old python and the new CLI with how the multi-line strings are outputted. When we fix it, we should make sure it works for both CLIs
| 8 |
824 |
TISTUD-2689
|
10/31/2012 20:31:14
|
Project Explorer: file not visible when pasted into project from filesystem until after project refresh
|
If a file is pasted into a project from the filesystem, the file is not visible until the project is refreshed. This is a regression. This did not occur in Studio 2.1.2. No errors in log. Steps to Reproduce: 1. Create a Titanium Project. 2. View in Project Explorer. 3. Copy/Paste a .js file from the filesystem to the project (e.g., right click on project Resources and select Paste). Actual Result: File not visible in project explorer. Project > Refresh will make the file visible. Expected Result: File should be visible immediately after it is pasted.
| 5 |
825 |
TISTUD-2696
|
11/01/2012 18:19:23
|
Adopt AppDirect module uuid field
|
The AppDirect call now returns module ids. We need to compare the module ids with the ones returned from the modulesInfo portal call to properly label modules with the status buttons.
| 5 |
826 |
TISTUD-2698
|
11/01/2012 21:38:35
|
Console: no colors on new lines in debug output
|
Console: no colors on new lines in debug output (see screenshot). Steps to Reproduce: 1. Run code: {code} Ti.API.trace('line0\nline1\nline2\nline3'); Ti.API.trace(['Ti.API TRACE', 'ARG1', 'ARG2']); Ti.API.debug('line0\nline1\nline2\nline3'); Ti.API.debug(['Ti.API DEBUG', 'ARG1', 'ARG2']); Ti.API.info('line0\nline1\nline2\nline3'); Ti.API.info(['Ti.API INFO', 'ARG1', 'ARG2']); Ti.API.warn('line0\nline1\nline2\nline3'); Ti.API.warn(['Ti.API WARN', 'ARG1', 'ARG2']); Ti.API.error('line0\nline1\nline2\nline3'); Ti.API.error(['Ti.API ERROR', 'ARG1', 'ARG2']); {code} Actual Result: No log-level colors on new lines. Expected Result: Log-level colors on new lines should match.
| 8 |
827 |
TISTUD-2699
|
11/02/2012 20:29:42
|
Add CLI command support for packaging a iOS Titanium Module
|
Add support for the packaging command via the CLI extension. V1: {code} project-dir/build.py Working directory: [project-dir] {code} V2: {code} titanium build --package [project-dir] {code}
| 8 |
828 |
TISTUD-2708
|
11/05/2012 22:26:44
|
Improvements to Update wizard
|
The below changes are required in the Titanium update wizard to improve the user experience - 1) Change the wizard image on the top to look like an installer image. 2) Add user id field to the password sudo page. 3) Gray out 'Titanium SDK' field in the Installer main page to indicate that it is mandatory and as the user can not de-select it. Also, the text of NodeJS should dynamically switch to 'NodeJS (required)' if the user selects any of components (acs, alloy, or cli).
| 0 |
829 |
TISTUD-2713
|
11/05/2012 23:16:14
|
CLI: remove UI for switching build scripts, should be command line only
|
Remove UI in Preferences > Titanium to toggle CLI. CLI should be command line only as per Ingo.
| 3 |
830 |
TISTUD-2716
|
11/05/2012 23:54:29
|
Changing focus to AppExplorer with Node.ACS project calls acs list ~20 times
|
Steps: 1. Create a Node.ACS project 2. Open the App Explorer 3. Enable troubleshooting for all debug/error messages 4. Change the focus from an editor to the App Explorer Expected Results: At most one call to acs list Actual Results: 20 calls of the following: !ENTRY com.aptana.core 1 0 2012-11-05 15:51:15.714 !MESSAGE (Build 0.0.0.qualifier) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "list" "hhhhhhhPPP333" "--no-banner" "--no-colors" Working directory: /Users/nle/Documents/runtime-titanium.product/hhhhhhhPPP333 Environment: {APTANA_VERSION=3.1.0.qualifier, Apple_PubSub_Socket_Render=/tmp/launch-uPb950/Render, Apple_Ubiquity_Message=/tmp/launch-yfOSD1/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, HOME=/Users/nle, LANG=en_US.UTF-8, LOGNAME=nle, PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin, PWD=/Users/nle/Documents/runtime-titanium.product/hhhhhhhPPP333, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-GhzCh4/Listeners, TMPDIR=/var/folders/zw/n1jmn7z52yb6x0rfd2cn5bgr0000gq/T/, USER=nle, __CF_USER_TEXT_ENCODING=0x1F7:0:0, com.apple.java.jvmMode=client, com.apple.java.jvmTask=JNI.java} We shouldn't need to make so many calls
| 8 |
831 |
TISTUD-2717
|
11/05/2012 23:54:42
|
NPE when running on iOS device
|
When Clayton tested in Mac OS 10.8.2 using Titanium Studio, build: 3.1.0.201211021811, he saw the following error when building for device: {code} !ENTRY org.eclipse.core.jobs 4 2 2012-11-05 14:11:58.663 !MESSAGE An internal error occurred during: "Launching Titanium iOS on Device - IOS_no_ACS (1)". !STACK 0 java.lang.NullPointerException at com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.build(IOSNodeJSCommandsHelper.java:142) at com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.installOnDevice(IOSNodeJSCommandsHelper.java:112) at com.appcelerator.titanium.mobile.cli.IOSCommandsHelper.runOnDevice(IOSCommandsHelper.java:136) at com.appcelerator.titanium.mobile.cli.nodejs.NodeTitaniumSDKCommandsHandler.run(NodeTitaniumSDKCommandsHandler.java:443) at com.appcelerator.titanium.mobile.ui.iphone.launch.IOSDebugOnDeviceLaunchConfigurationDelegate.launch(IOSDebugOnDeviceLaunchConfigurationDelegate.java:47) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 2 |
832 |
TISTUD-2718
|
11/05/2012 23:59:15
|
Improve the first page of Update wizard
|
1. Grey out 'Titanium SDK' field in the installer main page to indicate that it is mandatory and as the user can not de-select it and add " (required)" to the text. This should only apply to the case where user doesn't have a SDK installed; if a SDK already exists, the field will be de-selectable. 2. The text of NodeJS should dynamically switch to 'NodeJS (required)' if the user selects any of the npm packages. 3. When NodeJS is selected, the release note section should be updated with at least the default text.
| 5 |
833 |
TISTUD-2720
|
11/06/2012 00:09:42
|
Titanium Updates: change sudo prompt to mock system modal dialog
|
Change studio 3.0.1 sudo prompt to a modal dialog (that existed in studio 3.0.0). This is a regression, studio 3.0.0 had a nice system-style dialog. See screenshots. Steps to Reproduce: 1. Uninstall the CLI (or ACS, Alloy, NodeJS). 2. Open Studio. Take Titanium Updates. Actual Result: Sudo prompt appears in a wizard, appears non-standard. Expected Result: Sudo prompt appears as it does in studio 3.0.0, as a modal dialog that mocks the system dialog.
| 5 |
834 |
TISTUD-2726
|
11/06/2012 17:15:07
|
Windows 8: Errors running builder 'Studio Unified Builder' on project,URI is not absolute
|
While testing TISTUD-2625 on Windows I ran hit this error: {code} Errors occurred during the build. Errors running builder 'Studio Unified Builder' on project 'RSS Reader'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'SDK213'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'SDK214'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'Todo List'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'Win8NoACS'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'Win8_2.1.2'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'html5'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'masterdetail'. URI is not absolute Errors running builder 'Studio Unified Builder' on project 'win8test'. URI is not absolute {code} Which output this into the log: {code} !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:25.458 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:25.465 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:25.490 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.354 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.366 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.375 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.383 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.391 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.399 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.406 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.415 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 2 2012-11-06 09:10:36.423 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.eclipse.core.resources 4 75 2012-11-06 09:10:36.425 !MESSAGE Errors occurred during the build. !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.425 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'RSS Reader'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.425 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'SDK213'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.425 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'SDK214'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.426 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'Todo List'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.426 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'Win8NoACS'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.426 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'Win8_2.1.2'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.426 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'html5'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.426 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'masterdetail'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-11-06 09:10:36.426 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'win8test'. !STACK 0 java.lang.IllegalArgumentException: URI is not absolute at java.io.File.<init>(Unknown Source) at com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) at com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) at com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) at com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) at com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) at com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) at com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} Steps to reproduce: 1. Open Titanium Studio. 2. Invoke a clean on all projects (Project > Clean) Expected results: Project build files should be cleaned and recreated. Actual result: The above error is thrown.
| 5 |
835 |
TISTUD-2730
|
11/06/2012 20:04:09
|
The toast popup after successfully installing npm packages should show version numbers
|
When NodeJS is not installed on the system along with our npm packages, the update dialog will show N/A in the version column since we don't have a way to query for version without npm. That is OK; however, after they are installed, we should display the versions in the toast since now we could query for them.
| 5 |
836 |
TISTUD-2733
|
11/06/2012 22:45:59
|
Investigate if we can create local npm package with all dependencies
|
From Chris: "npm pack can create a tarball that we can use to install. Need to investigate if this also includes dependencies underneath it.“
| 8 |
837 |
TISTUD-2734
|
11/06/2012 23:03:08
|
Distribute iOS: Xcode reloads for every provisioning profile and hangs studio
|
'Titanium Project > Distribute iOS iTunes' causes Xcode to reload for every provisioning profile, hangs studio, can take a few minutes, appears extremely broken. See attached video to believe: 'provisioning-profile-load - Cellular.m4v' Steps to Reproduce: 1. Make sure you have multiple ios provisioning profiles. 2. Open Studio with a new workspace. 3. Create a Titanium Project. 4. Close Xcode. 5. Distribute > iOS iTunes. Actual Result: Xcode opens and closes multiple times until all provisioning profiles are loaded, hangs studio. Expected Result: The distribution menu opens right away.
| 0 |
838 |
TISTUD-2735
|
11/06/2012 23:07:59
|
Alloy: add alloy icon to alloy project context menu commands
|
Alloy project context menu commands are missing the alloy icon. In contrast, Node.ACS project context commands have the Node.ACS icons. The current behavior looks odd. Steps to Reproduce: 1. Create Alloy project. 2. Right click on the project and select 'New'. Actual Result: Alloy commands have no icon, are misaligned with other commands. Expected Result: Alloy commands have Alloy icons, are aligned with other commands, and on par with Node.ACS context commands.
| 5 |
839 |
TISTUD-2741
|
11/08/2012 00:38:31
|
Node.ACS Service: publish does not include save prompt
|
When publishing a node.acs service from a titanium app, there is no prompt to save dirty files. Steps to Reproduce: 1. Create Titanium app. 2. Create New Node.ACS Service within Titanium app (project right-click > New > Service). 3. Edit acs <main>.js or package.json file without saving. 4. Publish > Node.ACS Service. Actual Result: Service is published without save prompt. Expected Result: Save prompt, followed by either publish or cancel.
| 5 |
840 |
TISTUD-2743
|
11/08/2012 16:57:23
|
Node.ACS: Can not import removed Node.ACS project
|
After removing (but not deleting) an ACS Node project that has been published from the workspace, Titanium studio can not import the project. The import project wizard does not have an ACS project choice, and trying to promote the folder to a project throws the following error: {code} !ENTRY org.eclipse.ui 4 0 2012-11-08 08:50:55.974 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at com.aptana.ui.wizards.WizardFolderImportPage.validate(WizardFolderImportPage.java:387) at com.aptana.ui.wizards.WizardFolderImportPage$InputModifyListener.modifyText(WizardFolderImportPage.java:787) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058) at org.eclipse.swt.widgets.Text.wmCommandChild(Text.java:2610) at org.eclipse.swt.widgets.Control.WM_COMMAND(Control.java:4669) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4531) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2425) at org.eclipse.swt.widgets.Text.callWindowProc(Text.java:255) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623) at org.eclipse.swt.widgets.Text.windowProc(Text.java:2254) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) at org.eclipse.swt.internal.win32.OS.SetWindowTextW(Native Method) at org.eclipse.swt.internal.win32.OS.SetWindowText(OS.java:3446) at org.eclipse.swt.widgets.Text.setText(Text.java:1977) at com.aptana.ui.wizards.WizardFolderImportPage.setProjectName(WizardFolderImportPage.java:483) at com.aptana.ui.wizards.WizardFolderImportPage.createControl(WizardFolderImportPage.java:240) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at com.aptana.projects.actions.PromoteToProjectHandler.execute(PromoteToProjectHandler.java:59) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} This is not a regression. Steps to reproduce: 1. Create a new Node.ACS project. 2. Publish the project. 3. From the project Explorer remove the project from the workspace without removing the published app. 4. Try to import the project back into the workspace. Expected result: Import should give a warning that the published project exists and might be overwritten and allow the user to continue. Actual results: Import wizard does not recognized the project type. Creating from a folder causes NPE.
| 5 |
841 |
TISTUD-2744
|
11/08/2012 17:58:53
|
Node.JS: allow studio to recover from failed node updates
|
Allow studio to recover from failed node.js module updates. For example: {code} I updated the cli at the same time as updating studio and the cli update failed, resulting in a missing /usr/local/bin/titanium alias. Any further runtime-related studio commands started to fail (run on simulator). Checking for updates showed no updates available. {code} Can we change our node module detection to include the alias? Steps to Reproduce: 1. Fail a node module update (or just delete the node module alias). 2. Check for Titanium updates. Actual Result: No updates found. Build scripts fail with missing node module alias errors. Expected Result: Updates found.
| 5 |
842 |
TISTUD-2746
|
11/08/2012 22:37:16
|
Node.ACS: open main js file and json file when project is first created
|
Node.ACS: open main js file and json file when project is first created. This applies both to a Node.ACS Project and Titanium Project with New Node.ACS Service. This is usability and parity issue with Titanium Projects as app.js and tiapp.xml open when a Titanium Project is first created. Steps to Reproduce: 1. Create Node.ACS Project. Actual Result: main json file opens in editor, but main js file does not Expected Result: both json and main js file open in editor 2. Create Titanium Project. 3. Add New Node.ACS Service to project. Actual Result: No files open. Expected Result: both the main json and js file should open for the new service
| 5 |
843 |
TISTUD-2748
|
11/08/2012 22:50:05
|
Node.ACS: Publish: deployment options lack icons
|
Node.ACS Project and Service Publish deployment options lack icons. See screenshots. The only exception is Node.ACS Service does have an icon. This is a parity issue as all other Titanium deployment options have icons. Steps to Reproduce: 1. Create Node.ACS Project or Service. 2. Select Publish > ... Actual Result: None of the deployment options have a Node.ACS icon on the left (except Node.ACS Service). Expected Result: All deployment options should have an associated icon.
| 2 |
844 |
TISTUD-2750
|
11/08/2012 23:11:00
|
Improve the iOS debug on device build error message prompt
|
When an iOS debug on device session fails due to a fatal "Check dependencies" error, we display a generic message that tells the user to look at the console in order to understand what went wrong. Once TIMOB-11710 is done, we'll be able to easily grab the error reason from the launch error-stream and display that to the user.
| 5 |
845 |
TISTUD-2752
|
11/08/2012 23:58:35
|
Make the Node.ACS server Run configuration private
|
The discussion stemmed from parity on having Run > Run Configuration... menu for Node.ACS project. We decided to implement the following two things: 1. Make the launch configuration for running local Node.ACS server private; 2. Add "Edit Node.ACS Server Settings..." under Run menu to allow user to edit the server settings such as port number. NOTE: For now, this ticket only deals with making the launch configuration private. Doesn't look like there is a point in controlling the ACS server port number when the project launch is ignoring it anyway ;) New tickets will be created to deal with the other issues.
| 2 |
846 |
TISTUD-2754
|
11/09/2012 00:02:36
|
Publish: Web Deployment Wizard: Capistrano missing icon
|
Publish: Web Deployment Wizard: Capistrano missing icon. See screenshot. Steps to Reproduce: 1. Create Web Project. 2. Publish > Web Deployment Wizard... Actual Result: Capistrano missing icon. Expected Result: All options have an icon.
| 5 |
847 |
TISTUD-2755
|
11/09/2012 00:07:52
|
Remove Run Web Deployment Wizard option from the Node.ACS Project
|
Node.ACS: Titanium Project Service Publish missing Web Deployment Wizard option. See screenshot. Steps to Reproduce: 1. Create Titanium Project. 2. Add New Node.ACS Service to project. 3. Select Publish > ... Actual Result: There is no 'Run Web Deployment Wizard...' option with the other ACS options. Expected Result: Titanium Project Services should have same deployment options as Node.ACS Projects. 'Run Web Deployment Wizard...' should appear for both.
| 5 |
848 |
TISTUD-2756
|
11/09/2012 00:40:12
|
Node.ACS: Manually created run config fails to launch with error=2 No such file or directory
|
Running a Node.ACS project from a manually created run config fails. Running from a default run config works. Error: {code} Cannot run program "/usr/local/bin/acs" (in directory ""): error=2, No such file or directory Cannot run program "/usr/local/bin/acs" (in directory ""): error=2, No such file or directory {code} Failure Log w/acs command (manually created run config): {code} !ENTRY com.aptana.core 1 0 2012-11-08 16:25:52.406 !MESSAGE (Build 3.0.0.201211071923) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "run" "-d" "" "-p" "51514" "--no-banner" "--no-colors" Working directory: /Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/TitaniumStudio.app/Contents/MacOS Environment: {ANDROID_NDK=/Users/dhyde/Desktop/android/android-ndk-r8b, ANDROID_SDK=/Users/dhyde/Desktop/android/android-sdk-macosx, APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-uOBKPF/Render, Apple_Ubiquity_Message=/tmp/launch-zMAdSZ/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-xxuSXL/ServiceProcessSocket, HOME=/Users/dhyde, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/dhyde/Desktop/android/android-sdk-macosx/tools:/Users/dhyde/Desktop/android/android-sdk-macosx/platform-tools, PWD=/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/TitaniumStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-WTnmk6/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} !ENTRY com.appcelerator.titanium.acs.core 4 0 2012-11-08 16:25:52.426 !MESSAGE Cannot run program "/usr/local/bin/acs" (in directory ""): error=2, No such file or directory !STACK 0 java.io.IOException: Cannot run program "/usr/local/bin/acs" (in directory ""): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) at com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327) at com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322) at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273) at com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235) at com.appcelerator.titanium.acs.internal.core.NodeACSManager.runLocalServer(NodeACSManager.java:502) at com.appcelerator.titanium.acs.internal.core.NodeACSManager.start(NodeACSManager.java:402) at com.appcelerator.titanium.acs.internal.core.launch.NodeACSLaunchConfigurationDelegate.launch(NodeACSLaunchConfigurationDelegate.java:51) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:53) at java.lang.ProcessImpl.start(ProcessImpl.java:91) at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) ... 12 more {code} Success w/acs command (default auto-created run config): {code} !ENTRY com.aptana.core 1 0 2012-11-08 16:32:58.264 !MESSAGE (Build 3.0.0.201211071923) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "run" "-d" "/Users/dhyde/Desktop/TISTUD-RC/workspace/project" "-p" "59408" "--no-banner" "--no-colors" Working directory: /Users/dhyde/Desktop/TISTUD-RC/workspace/project Environment: {ANDROID_NDK=/Users/dhyde/Desktop/android/android-ndk-r8b, ANDROID_SDK=/Users/dhyde/Desktop/android/android-sdk-macosx, APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-uOBKPF/Render, Apple_Ubiquity_Message=/tmp/launch-zMAdSZ/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-xxuSXL/ServiceProcessSocket, HOME=/Users/dhyde, LANG=en_US.UTF-8, LOGNAME=dhyde, NUM_CPUS=4, PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/dhyde/Desktop/android/android-sdk-macosx/tools:/Users/dhyde/Desktop/android/android-sdk-macosx/platform-tools, PWD=/Users/dhyde/Desktop/TISTUD-RC/workspace/project, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-WTnmk6/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI} {code} Steps to Reproduce: 1. Create Node.ACS Project. 2. Go to Top Menu: Run > Run Configurations... 3. Add a new Local Node.ACS Server run config and select the created project. 4. Run the config. Actual Result: Fail. Expected Result: Same as with if no run config were previously created and user selects Run > Local Node.ACS Server.
| 0 |
849 |
TISTUD-2757
|
11/09/2012 00:44:11
|
Node.ACS: add custom icon for Node.ACS projects instead of Titanium Classic icons
|
Currently the Node.ACS natures are using Titanium Classic icons. This causes visual conflict and contextual conflict. See deployment menus, project explorer, new project icons, and project nature icons to see the context of this issue. Ideally Titanium Projects and Modules would use the Titanium Classic icons for all these scenarios, and Node.ACS features would have a separate icon. See screenshots.
| 8 |
850 |
TISTUD-2758
|
11/09/2012 01:04:41
|
Node.ACS: Titanium Project with Service changes tiapp.xml localhost without prompt after local deployment
|
In a Titanium Project with a Node.ACS Service. If you set the localhost in the tiapp.xml, it gets overridden randomly without prompt and defaults to some standard port value. Included log and screenshots. Steps to Reproduce: 1. Create Titanium Project. 2. Add New > Node.ACS Service. 3. Publish > Node.ACS Service and copy url to tiapp.xml localhost field (acs-service-baseurl), save. 4. Click around the editor, possibly launch project to Local Node.ACS Server. Actual Result: Eventually the tiapp.xml localhost mysteriously changes to some default port value without prompt or reason. Expected Result: tiapp.xml localhost value should never change without prompt or user action.
| 0 |
851 |
TISTUD-2764
|
11/09/2012 21:20:18
|
Node.ACS: post-publish url pop-up has spelling and info errors
|
When a user publishes a node.acs service, and the pop-up appears that contains the url, there is one spelling error and some outdated info. See screenshot. 'apps' should be 'app's' version should be '' (removed as it no longer applies) Steps to Reproduce: 1. Create Node.ACS Project. 2. Publish and view URL dialog. Actual Result: Spelling and factual errors. Expected Result: No spelling or factual errors.
| 1 |
852 |
TISTUD-6269
|
11/12/2012 15:23:53
|
Ti Studio should be smart enough to know when your trying to add a New Controller to a Widget
|
From the App Explorer Window in Ti Studio - right click the custom widget folder that you would like to add a controller. Select New->Alloy Controller Expected Behavior: A new alloy controller is created in your widget Actual Behavior A new alloy controller is added to the main app folder tree
| 5 |
853 |
TISTUD-2766
|
11/12/2012 17:20:51
|
Failed to execute runnable (java.lang.IllegalArgumentException: Index out of bounds)
|
Found while testing TISTUD-2679: {code} !ENTRY org.eclipse.ui 4 0 2012-11-08 12:48:37.161 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Index out of bounds) at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) Caused by: java.lang.IllegalArgumentException: Index out of bounds at org.eclipse.swt.SWT.error(SWT.java:4263) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.custom.StyledText.setStyleRanges(StyledText.java:9661) at org.eclipse.swt.custom.StyledText.replaceStyleRanges(StyledText.java:7713) at org.eclipse.jface.text.TextViewer.addPresentation(TextViewer.java:4811) at org.eclipse.jface.text.TextViewer.changeTextPresentation(TextViewer.java:4890) at com.aptana.editor.common.text.reconciler.CommonPresentationReconciler$1.run(CommonPresentationReconciler.java:227) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 22 more !ENTRY com.aptana.editor.common 2 0 2012-11-08 12:48:37.163 !MESSAGE (Build 3.0.0.201211071923) [WARNING] Was unable to add folding position. Start: 1,545,140, end: 0 {code} Steps to Reproduce: 1. Edit large attached file in studio. 2. Scroll top to bottom 3. Cut the contents 4. Paste them back 5. Save the file 6. Repeat steps 3 thru 5. Actual Result: The above output Expected Result: Studio should not throw an error.
| 8 |
854 |
TISTUD-2768
|
11/12/2012 23:46:36
|
Splash: login fields need focus when menu appears
|
When splash screen logins are loaded, the user field does not have focus. This occurs for registration and login. See screenshots for current and expected behavior. This is not a regression. Steps to Reproduce: 1. Logout and restart Studio. 2. Select either 'Login' or 'Register' from radio button and click 'Next'. Actual Result: User field is not selected, user must manually select field to edit. Expected Result: User field should have focus, user should be able to begin typing right away.
| 3 |
855 |
TISTUD-2770
|
11/13/2012 20:31:46
|
Windows 8: npm isn't recognized as installed until restart
|
Windows 8: npm isn't recognized as installed until restart. See log attached. There is a GUI error. Steps to Reproduce: 1. Clean install Titanium Studio. 2. Take all Titanium Updates. Actual Result: npm error. node modules not installed. restart allows modules to install. Expected Result: npm installs correctly. node modules install correctly. studio does not require restart.
| 8 |
856 |
TISTUD-2776
|
11/14/2012 01:13:16
|
Titanium CLI: Pass in Titanium SDK directory to CLI
|
If the Titanium SDK is in a non-default location, the cli will not recognize the new location unless it is explicitly passed in from studio. See TIMOB-11753 for cli commands. Steps to Reproduce: 1. Move Titanium SDK to Desktop. 2. Set Titanium SDK to new location in Studio Preferences. 3. Create a new Titanium project using Titanium SDK 3.0.0+. Actual Result: Fail. This works in Studio 2.1.2. Expected Result: Studio passes in the Titanium SDK to the cli at some point, and the scripts work.
| 8 |
857 |
TISTUD-2777
|
11/14/2012 14:54:20
|
Project imported from git cannot be built
|
h1. Problem description I've imported a project from git in 3 different ways: 1. clone the repository and then use "Import" 2. clone the repository and then use "Promote to project" 3. using the integrated "Import from git" feature In all cases, the project does not show any option to build. The tiapp.xml has the right settings (Android, iPhone and iPad are active), but the menu does not show any build option. The debug button is disabled.
| 5 |
858 |
TISTUD-2778
|
11/14/2012 19:12:56
|
Showing Toolbar does not persist after restart when in simple Studio perspective
|
1. Start Titanium Studio on a new empty workspace; 2. Select Window > Show Toolbar from the main menu to make toolbar visible; 3. Restart Studio. Expected result: the toolbar stays visible. Actual result: the toolbar is hidden again. Workaround: after making toolbar visible, switch to extended Studio perpsective, then restart Studio. After that, switch back to simple perspective and the toolbar will persist afterward.
| 5 |
859 |
TISTUD-2780
|
11/15/2012 00:14:50
|
Checkbox not appearing in splash screen on Windows when system has a large font size
|
See the attached screenshot. We should use a fix size instead of relying on system's font size.
| 3 |
860 |
TISTUD-2783
|
11/15/2012 17:31:54
|
Provide Content Assist for Alloy Elements in view XML files
|
Alloy uses XML files to define views. We should provide content assist for the elements (tags). {code:xml} <Alloy> <View /> </Alloy> {code} The list of elements is defined as Titanium.UI.* types. There will likely be a need to further refine/filter the subtypes that make sense. Additionally Alloy uses some non-standard namespace mappings for some elements, so there are tags which are not Titanium.UI.* such as {{Toolbar}} which is mapped to {{Titanium.UI.iOS.Toolbar}}. Lastly, the root tag is {{Alloy}} and you can have {{<Require>}} tags.
| 13 |
861 |
TISTUD-2784
|
11/15/2012 17:32:34
|
Provide Content Assist for attribute names in Alloy view XML files
|
Alloy uses XML files to define views. We should provide content assist for the attributes of elements. {code:xml} <Alloy> <View class="my_class" id="myLabel" onClick="" /> </Alloy> {code} For attribute CA we need to look up the properties for the given element's type in the JS index, as well as the events. To look up the type name, we take the element name as the type name and determine the namespace prefix. The default prefix is {{Titanium.UI.}}. If there is an {{ns}} attribute, use it's value as the namespace. Alloy will provide us with the exceptions to the rule for namespace mappings. e.g. {{View}} -> {{Titanium.UI.View}} {{Label}} -> {{Titanium.UI.Label}} {{<View ns="Ti.Map"/>}} -> {{Titanium.Map.View}} {{Toolbar}} -> {{Titanium.UI.iOS.Toolbar}} The list of attribute name proposals is: # The list of properties of the type # The list of events of the type. Each event name is transformed to be {{"on" + Character.toUppercase(event.name().charAt(0)) + event.name().substring(1);}} - i.e. "click" -> "onClick" # The common set of attributes: {{class}}, {{id}} and {{ns}}. It should be noted that the {{Alloy}} element may only have {{class}} and {{id}} attributes. The special {{Require}} element may have {{class}}, {{id}}, {{src}}, and {{type}}.
| 13 |
862 |
TISTUD-2785
|
11/15/2012 17:43:55
|
Hook up a special Content Assist processor for Alloy view XML files
|
We need to provide Content Assist specific to Alloy view XML files. They use a standard *.xml file extension. We'll need to add an Alloy XML Editor and hook up a specialized content assist processor so that for *.xml files in an alloy project (under the app/view/ tree) we have the Alloy-specific CA hooked up.
| 8 |
863 |
TISTUD-2789
|
11/15/2012 18:25:50
|
Create a TSS lexer
|
We need to generate a TSS lexer to feed the parser. See the PEGJS grammar here: https://github.com/appcelerator/alloy/blob/master/Alloy/grammar/tss.pegjs We'll need to extract a JFlex TSS.lex file from the rules there.
| 13 |
864 |
TISTUD-2790
|
11/15/2012 18:26:04
|
Create a TSS parser
|
We need to generate a TSS Parser. See the PEGJS grammar here: https://github.com/appcelerator/alloy/blob/master/Alloy/grammar/tss.pegjs We'll need to generate an LALR grammar from that and then use beaver to generate a parser. We may be able to simply copy the JSON.grammar and modify slightly to handle the changes that alloy introduces.
| 13 |
865 |
TISTUD-2791
|
11/15/2012 18:34:49
|
Create a TSS editor
|
Once we have a TSS grammar and lexer, we need to create a TSS editor and associate it with *.tss files. We should remove the old association between JSON and *.tss.
| 8 |
866 |
TISTUD-2792
|
11/15/2012 18:37:26
|
Colorize TSS files
|
Once we have a TSS editor, we'll need to hook up coloring. This involves setting up partitions, a partition scanner, and token scanners for the partitions. We can look to {{JSONSourceConfiguration}} as the example to copy and slightly modify. We can likely re-use the lexer/grammar that the TSS parser uses.
| 8 |
867 |
TISTUD-2793
|
11/15/2012 18:38:55
|
Validate TSS file syntax
|
Once we have a proper parser we can use it to highlight syntax errors. This will involve creating a build participant that simply grabs the context's AST, asks for the SyntaxErrors and hooks them as problems to the BuildContext. See {{JSParserValidator}}
| 8 |
868 |
TISTUD-2796
|
11/15/2012 19:10:06
|
Offer content assist on TSS keys - UI types
|
We need to offer up content assist for the keys of the JSON like objects in TSS files. {code} "Window": { backgroundColor: '#fff' } {code} The {{"Window"}} token is what we'd suggest. The list of elements to suggest is the same list of types of elements we'd suggest in the XML view files from TISTUD-2783. Please see that ticket for the list of types.
| 8 |
869 |
TISTUD-2797
|
11/15/2012 19:11:02
|
Offer content assist on TSS keys - classes and IDs
|
We need to offer up content assist for the keys of the JSON-like objects in TSS files. This ticket specifically addresses offerring up the list of classes and IDs found in the view files. {code} <!-- index.xml --> <Label id="myLabel"/> // index.tss "#myLabel": { text: 'some text' } {code} The {{"#myLabel"}} token is what we'd suggest. IDs use a {{#}} prefix like in CSS, and classes use {{.}}. The list of classes and ids is found by querying the indexed values from TISTUD-2798. app.tss should query all files. For other tss files we can limit the scope to just the associated view (same hierarchy and basename).
| 8 |
870 |
TISTUD-2798
|
11/15/2012 19:21:18
|
Index Alloy view XML files to record id and class declarations with type info
|
We'll need to begin indexing alloy's XML files to record the list of classes and ids used. This will then be used for TSS code assist. The involves adding a new IndexBuildParticipant for XML files. In the participant we may filter when we activate to only projects with alloy nature and files under app/views/. The participant would parse the XMl file and traverse the AST to get the class/id attribute info. When we record a class or id reference, we will likely also want to record the fully qualified type name of the element it is on. {code} <!-- index.xml --> <Alloy> <Window> <!-- implicit id of "index" --> <Label id="myLabel"/> </Window> </Alloy> {code} In this case we'd record that index.xml has a Titanium.UI.Label with an id value of "myLabel". The type is required to determine the property list in TSS content assist, as well as content assist in controller JS. The type namespace mapping is the same as in TISTUD-2783. Please note that the top-level widget (the child under the {{<Alloy>}} tag) in a view has an implicit id of the file's basename, so the top-level {{Window}} of index.xml would have an id of "index").
| 8 |
871 |
TISTUD-2799
|
11/15/2012 19:28:09
|
Provide content assist for property names in TSS
|
We need to provide content assist for the list of property names for a given element in TSS files. {code} "Window": { backgroundColor: '#fff' } {code} {{backgroundColor}} is the token we'd suggest. We should take the string which is the key of the surrounding object, convert it to a fully qualified type name (see TISTUD-2783), then query the list of properties for that type. If the string is not the name of a type, but is a class or id, we need to query the class/id index from the view files to resolve it to the type it is hanging off.
| 8 |
872 |
TISTUD-2806
|
11/16/2012 22:52:10
|
Fresh installation of Titanium SDK does not appear in the project creation dialog
|
Have a newly installed Studio, and no Titanium SDK. # Install an SDK via the "Install Specific Titanium SDK..." menu, or via the Studio prompt to install on startup. # Let the Studio complete the installation. # Click to create a new Mobile project. Notice that the Titanium SDK version drop-down is empty. Restarting the Studio fixes the problem. This issue does not effect versions where there is already (at least) one SDK version installed.
| 5 |
873 |
TISTUD-2812
|
11/17/2012 02:01:29
|
Add content assist support for Alloy projects
|
We need the ability to have a library of pre-canned Alloy widgets to help developers out of the box. Alloy is fantastic that developers can create their own widgets. But we need to have common widgets out of the box. We need to work with PS to get their ideas as to what they would like and what they have created for customers.
| 0 |
874 |
TISTUD-2813
|
11/17/2012 02:05:29
|
Studio: node.acs - Cannot set cname for a deployed node.acs project
|
*Details:* After deploying a node.acs app, I cannot set the cname for the deployed app. *Steps to reproduce:* 1. In TiStudio, right-click on the Project Explorer and go to New > Node.ACS Project 2. Specify a project name and press finish 3. Right-click on the newly created project and go to Publish > Deploy App 4. Wait for published URL to appear and press ok 5. Link the published URL in your domain DNS setting 6. Back in TiStudio, right-click on the project and go to Node.ACS > Set CNAME 7. Enter your cname URL *Actual:* Studio returns a "Failed to Set CName" error dialog. See attachments. *Expected:* Studio should allow you to set the cname. *Note:* Steps to work around this: 1. Open your terminal/cmd 2. cd into node.acs project 3. Use the following command: *acs cname --set <CNAME_URL>*
| 2 |
875 |
TISTUD-2829
|
11/20/2012 00:23:03
|
Node.ACS: adopt standard capitalization on tail logs and set cname menu commands
|
currently the capitalization of the node.acs tail logs and set cname menu commands is non-standard. See screenshot. Current Capitalization: Tail logs, Set CNAME Expected Capitalization: Tail Logs, Set CName Steps to Reproduce: 1. Create Node.ACS Project. 2. Context Click > Node.ACS > ...
| 2 |
876 |
TISTUD-2831
|
11/20/2012 11:22:44
|
Cannot open the browser correctly when running MobileWeb code
|
Not a regression. h1. Problem description When running an app using "MobileWeb Preview in Browser", the chosen browser is not correctly used. Sometimes, Firefox is used (although I set the default browser or Chrome), other times I get this error: "Could not launch external web browser for http://127.0.0.1:8020/index.html. Check the Web Browser Preferences." Attached the settings screen: as you can see, the Chrome browser is chosen.
| 8 |
877 |
TISTUD-2837
|
11/20/2012 23:38:27
|
Android Preferences: android sdks not detected until titanium sdk path is set and studio restarts
|
In the Titanium Preferences, if the titanium sdk path is set for the first time, then the android sdk path is set for the first time, the android sdks will not list and there is an error. Restarting studio fixes the issue. This did not occur in Studio 2.1.2. This is a regression. Titanium Preferences: {code} Problems detected with the SDK settings. {code} Titanium Preferences Details: {code} An error was detected with the SDKs configuration. Reason: [ANDROID SDK Home] No platform SDKs were found. Click 'Configure' to install new platforms. {code} Steps to Reproduce: 1. Open Titanium Studio. 2. Open Preferences > Titanium. 3. Delete Titanium SDK path. 4. Delete Android SDK path. 5. Apply changes. 6. Enter valid Titanium SDK path. 7. Enter valid Android SDK path. Actual Result: Errors in preferences, can't select android sdk. Android SDK is correctly installed. Restarting studio fixes issue. Expected Result: No errors. Android SDKs listed.
| 5 |
878 |
TISTUD-2842
|
11/21/2012 16:09:08
|
ACS: no protocol: Unable to parse URL for publish
|
When trying to publish an ACS project on Windows 8, I get the success window with the error no protocol: Unable to parse URL for publish. I get the following error in my log file: {code} !ENTRY com.aptana.ui 4 0 2012-11-21 07:59:21.018 !MESSAGE (Build 3.0.0.201211202053) [ERROR] no protocol: Unable to parse URL for publish !STACK 0 java.net.MalformedURLException: no protocol: Unable to parse URL for publish at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at com.aptana.ui.util.WorkbenchBrowserUtil.launchExternalBrowser(WorkbenchBrowserUtil.java:35) at com.aptana.ui.dialogs.HyperlinkMessageDialog.openLink(HyperlinkMessageDialog.java:115) at com.aptana.ui.dialogs.HyperlinkMessageDialog$1.widgetSelected(HyperlinkMessageDialog.java:89) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1094) at org.eclipse.swt.widgets.Link.wmNotifyChild(Link.java:1071) at org.eclipse.swt.widgets.Control.wmNotify(Control.java:5534) at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1896) at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:5086) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4584) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1610) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2061) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2425) at org.eclipse.swt.widgets.Link.callWindowProc(Link.java:172) at org.eclipse.swt.widgets.Widget.wmLButtonUp(Widget.java:2057) at org.eclipse.swt.widgets.Control.WM_LBUTTONUP(Control.java:4912) at org.eclipse.swt.widgets.Link.WM_LBUTTONUP(Link.java:909) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4565) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4985) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) at com.appcelerator.titanium.acs.ui.deploy.NodeACSDeployProvider$4.run(NodeACSDeployProvider.java:254) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} This is a regression as ACS previously published. Steps to reproduce: 1. Create a new ACS project. 2. Publish ACS (Publish > Deploy App) Expected result: The project should correctly publish to ACS servers Actual result: The project fails to publish and throws the above error.
| 5 |
879 |
TISTUD-2843
|
11/21/2012 20:15:50
|
Studio repeatedly prompts to install the same node.js modules NPM_CONFIG_PREFIX
|
I'm repeatedly prompted to install the same Node.js packages (CLI, ACS, and Alloy), despite the fact that they appear to install successfully each time. It appears (since Studio is prompting me with the admin password) that it is failing to respect the NPM_CONFIG_PREFIX I have set in my environment, but that when node is actually invoked, it's looking for modules based on the NPM_CONFIG_PREFIX. I have Node configured to install modules under $HOME specifically so I don't have to do sudo to install modules. Studio should provide a means to configure the NPM_CONFIG_PREFIX so it can use the correct set.
| 13 |
880 |
TISTUD-2844
|
11/21/2012 21:18:53
|
Projects: non-default save location should be pre-populated with old path and have existing file warnings
|
In the new project wizard (for any project type), if the user selects the 'non-default location' checkbox, the previously readonly path should remain, and if the non-default location contains existing files, there should be a warning in the new project wizard. This is not standard eclipse behavior, but it is standard ADT behavior, and it is a major usability issue. Steps to Reproduce: 1. Create a new folder with a new file (i.e., Downloads/myfolder/myfile). 2. Bring up New Project Wizard in Studio (any project type, Titanium Project for example). 3. Select 'non-default location' for project location. 4. Select the 'newfolder' as project location. Actual Result: No pre-existing 'workspace/newproject' path in the text field. User must manually select path. No warnings of existing files in new selected folder. Expected Result: Old 'workspace/newproject' path is in the text field. Selecting a folder with existing files generates a warning in the wizard.
| 5 |
881 |
TISTUD-2847
|
11/21/2012 23:27:32
|
dirty files not selected for save when binding Node.ACS service to titanium project
|
When a titanium project has a dirty app.js file and 'project context click > node.acs > bind node.acs service' is called, the app.js file is not selected by default. Steps to Reproduce: 1. Create Titanium Project. 2. Create Node.ACS Project. 3. Edit titanium project app.js, don't save. 4. Titanium Project Context Click > Node.ACS > Bind Node.ACS Service and proceed to the save menu. Actual Result: app.js is not selected, the process will quit Expected Result: app.js should be selected by default, as with other save prompts
| 5 |
882 |
TISTUD-2850
|
11/22/2012 13:12:03
|
Windows 7: Error :"URI is not absolute " is coming while creating titanium project.
|
Test Steps: 1. Open Titanium Studio. 2.Create default titanium studio project. Expected results: Project should be created. Actual result: Error is thrown.Please see logs and screenshot attached.
| 3 |
883 |
TISTUD-2852
|
11/23/2012 08:54:23
|
Studio: Create Alloy project option does not appear even after complete installation. "Unable to find 'alloy' binary." exception occurs.
|
Steps to Reproduce: 1. Install Studio 3.0 with all updates. 2. Go to File>New>Titanium Project Actual: Observe option to create alloy project does not appear. And Studio Logs show "org.eclipse.core.runtime.CoreException: Unable to find 'alloy' binary." exception. [Note: If Logs do not show any message then Restart studio and run 2nd step again.] Expected: No exception must appear and Create Alloy project option must appear. Also Run Diagnostic test must display correct information about installed and uninstalled programs. Refer Diagnostic.png
| 5 |
884 |
TISTUD-2853
|
11/23/2012 09:09:06
|
Studio: Installation issues with node.ACS shown even after complete installation of ACS
|
Steps to Reproduce: 1. Install Studio 3.0 with all updates. 2. Go to File>New>Node.ACS Project 3. Provide any appropriate name and click Finish. Actual: "Node.ACS is not configured properly. The "acs" executable/node package is not installed." message appears. Expected: Project must get created without ny ero
| 5 |
885 |
TISTUD-2855
|
11/23/2012 11:29:24
|
Content Assist: Content Assist window does not display "Ti" in suggestions.
|
Steps To Reproduce: 1. Install 3.0 with all updates. 2. Create a project and open app.js 4. Press Ctrl+space to bring content assist window. Ex: No suggestions for "Ti.API.info("");" or Ti.UI.Window Actual: "Ti." does not appear in suggestions. Expected: "Ti." must appear in content assist window.
| 5 |
886 |
TISTUD-2859
|
11/25/2012 19:24:23
|
Update the version of Node.js we download to 0.8.14
|
The current version we host is 0.8.3. We should update to the latest 0.8.14 to avoid issues like NODEJS-493.
| 3 |
887 |
TISTUD-2861
|
11/26/2012 09:45:11
|
Studio: "java.lang.UnsupportedOperationException" occurs while switching on new workspace and initializing node.ACS.
|
Steps to Reproduce: 1. Install 3.0 latest version studio. 2. Now switch to new workspace. Actual: An internal error occurred during: "Initializing Node.ACS". "java.lang.UnsupportedOperationException" occurs after switching to new workspace. [Refer attached Screenshot and text log.] Expected: No exception should appear.
| 3 |
888 |
TISTUD-2863
|
11/26/2012 22:11:08
|
Dashboard: Update Android SDK to r21 on Staging
|
Dashboard: Update Android SDK to 21 on Staging
| 3 |
889 |
TISTUD-2865
|
11/27/2012 00:20:57
|
TiStudio: Projects - A pane is missing when creating the default Titanium project on Ubuntu 12.04
|
Details: If you try to create the default Titanium project on Ubuntu 12.04, then the pane is missing. This bug *does not appear* on Mac OS X Lion (10.7.5), Windows 7, and Ubuntu 10.04 Steps to reproduce: 1. On Ubuntu 12.04, Open TiStudio 2. Right-click in the Project Explorer space 3. Select New > Titanium Project Actual: A pane is missing on the right side (see ubuntu_1204.png) Expected: A pane should appear on the right side (see on_mac.png)
| 5 |
890 |
TISTUD-2866
|
11/27/2012 10:36:19
|
Xcode 4.3.3 : Distribute Ad hoc/ Enterprise with 'ipa' format is throwing error
|
Test Steps: 1.Install latest studio . 2.Install Xcode 4.3.3 . 3.Create a Titanium Mobile project with iphone only. 4.Package the iPhone Project with Distribute Ad hoc/ Enterprise. 5. Select 'ipa' as format. 6.Create a new folder and browse to that specified location. 7.Select 'Publish' P.S. : The provisioning file is working fine . I am able to package same project with 'app' format .Also "Distribute Apple iTune store' publish option is working fine. Actual result: [ERROR] Error copying iOS ipa output to destination.
| 8 |
891 |
TISTUD-2889
|
11/27/2012 15:31:03
|
Allow user to set preference to NodeJS source path
|
NodeJS's core modules are defined in JS files under the lib subdir of the Node source package. This is not installed when the binary is. If the user has a source package on their system, we should allow them to point to it so we can look up those core modules. This would involve setting up a preference constant to use as the key to store the path, as well as the UI fields to set/edit it in the Node preference page (which already exists and has a field for setting the path to the binary install).
| 5 |
892 |
TISTUD-2890
|
11/27/2012 15:32:14
|
Index NodeJS source install's core modules under lib dir
|
Once the user is able to set the path to the NodeJS source folder we need to be able to index it to get the details of the core modules under lib. These are straight JS files, so we can index them using our current mechanism. This should be treated like a 3rd-party library that can be attached to JS projects (much like an external JAR for JDT, possibly even just attaching "Node" to a project entirely which would be like attaching a JDK so it attaches the core modules form source and the $NODE_PATH from the binary install).
| 8 |
893 |
TISTUD-2871
|
11/27/2012 15:50:26
|
Allow pluggable inferencing/lookup of require calls
|
Titanium SDK's usage of {{require}} is slightly different than what NodeJS/CommonJS uses as it has an implicit base path of {{<project>/Resources}} An example: {code} var r = require('http'); {code} In Node, we'd load the core 'http' module. In Titanium we'd look for {{<project>/Resources/http.js}}. Additionally, Titanium merges the platform-specific subfolders of Resources. So... {code} var taskWindow = require('ui/TaskWindow'); {code} Would look up {{Resources/iphone/ui/TaskWindow.js}} and {{Resources/android/ui/TaskWindow.js}} Additionally you can specify a native Titanium module id to load.
| 13 |
894 |
TISTUD-2892
|
11/28/2012 21:08:10
|
Add button to download and unzip NodeJS source for user
|
To make things easier for users we should offer to download and unzip the NodeJS source for them. That way they don't need to google it download it and then hook up the location.
| 8 |
895 |
TISTUD-2880
|
11/28/2012 21:16:24
|
Allow user to install Node.ACS feature from the dashboard
|
Add a link in dashboard to install Node.ACS into Studio (need a mock up). We also need to check a portal action exists to install plugins from a specific url.
| 8 |
896 |
TISTUD-2881
|
11/29/2012 00:13:29
|
Preferences: Android SDK List Persists When Path Deleted
|
Not a regression. If Android SDK path is deleted in the Preferences, the Default Android SDKs list is still populated. The list should clear if there is no valid path selected. The list will correctly go away if the Preferences are reloaded. Steps to Reproduce: 1. Open Preferences > Titanium. 2. Delete Android SDK path. Actual Result: Default Android SDK List Persists. Expected Result: Default Android SDK List Disappears. Screen Types List Disappears.
| 5 |
897 |
TISTUD-2882
|
11/29/2012 01:02:12
|
Dashboard: Previous Android SDK Installations Not Recognized
|
Not a regression. If Android SDK is installed, and that path is used to install the Android SDK using the dashboard config utility, the SDK will download again and ignore the current SDK installation at that path. Steps to Reproduce: 1. Have existing Android SDK installation. 2. Delete Android SDK path in Studio Preferences. 3. Run Dashboard Configure Android and enter path to existing Android SDK. 4. Begin Installation. Actual Result: Android SDK downloads again. Expected Result: Currently existing Android SDK in the specified path should be recognized and the SDK Manager should launch.
| 5 |
898 |
TISTUD-2884
|
11/29/2012 01:35:25
|
Verify the existence of a Local Node.ACS Server when launching one for a Node.ACS project
|
Currently, when a Node.ACS project is being created, the Studio adds a local server settings in the Servers view. # Create a new Node.ACS project. # Open the Studio's Servers view. # Delete the created server. # Click the project and select the 'Run' option to launch a 'Local Node.ACS Server' The launch happens, even without the server in the servers view, and no server is being recreated. Expected: A recreation of the local server.
| 5 |
899 |
TISTUD-2885
|
11/29/2012 01:39:58
|
A Local Node.ACS launch is not using its defined server's settings
|
When creating a new Node.ACS project, a new server is being added to the Servers view. # Create a new Node.ACS project. # Open the Studio's Servers View. # Click to edit the port number for the newly added server. # Launch the project's 'Run -> Local Node.ACS Server'. Result: The console indicate that the server is running. However, the port is not the same as the one that was defined. Changing the port again and re-launching does not make any difference. The Server settings and the server that runs seem as un-connected.
| 5 |
900 |
TISTUD-2886
|
11/29/2012 01:42:44
|
Deleting a Node.ACS project does not delete its local server definition
|
When creating a new Node.ASC project, the Studio creates a new Server setting in the Servers view. # When deleting the project, the server is there to stay. # When launching the server via the Run menu, and then deleting the project, the server is still running. Expected: Shut down the server and remove it when needed.
| 3 |
901 |
TISTUD-2899
|
11/29/2012 20:15:14
|
Preferences: Android SDK List Not Updated After Android SDK Install From Dashboard Until Studio Restart
|
When Android SDK is installed from Dashboard, the Android SDK list in the Preferences is not updated until Studio restart. This does not occur in Studio 2.1.2. This is a regression. Steps to Reproduce: 1. Delete Android SDK path in Preferences. 2. Install Android SDK from Dashboard. 3. In SDK Manager, install at least one compatible Google API SDK and the all the tools. 4. When update finishes, close SDK Manager, and open Studio Preferences > Titanium. Actual Result: Android SDK path is set, but Android SDKs are not listed until Studio restart. Expected Result: Android SDK path is set, Android SDKs and screen types are listed below without Studio restart.
| 5 |
902 |
TISTUD-2900
|
11/29/2012 21:12:24
|
TiApp Editor: Titanium SDK List Not Updated Until TiApp editor Restart
|
If the Titanium SDK path is switched to another valid SDK path, the SDK list in the TiApp Editor is not updated in realtime. Studio must be restarted. This does not occur in Studio 2.1.2. This is a regression. Steps to Reproduce: 1. Copy full Titanium (sdk) folder to another location. 2. In the Titanium copy, delete a few SDKs (to provide contrast). 3. Open a Titanium Project. Open tiapp.xml, note the drop-down list of SDKs. 4. Change Preferences > Titanium SDK Path to another SDK installation (i.e., the copy). 5. Open the drop-down list in the tiapp.xml again. Actual Result: The SDK list is the same because it wasn't refreshed on Preference change. The TiApp editor must be restarted. Expected Result: SDK list immediately updated as it is in Studio 2.1.2.
| 5 |
903 |
TISTUD-2901
|
11/29/2012 23:25:03
|
Dashboard: Installing Android SDK - Selecting an existing SDK directory still starts a download
|
# Remove any Android SDK paths from the Titanium Preferences. # Open the Dashboard and click the Android SDK installation button. # When the disk location dialog appears, select a location that has an existing Android SDK installation. # Click OK. Result: A download process begins. Expected: The selected location is a valid existing SDK installation, so we should just show the Android package dialog. No need to download a new SDK.
| 5 |
904 |
TISTUD-2902
|
11/30/2012 00:53:04
|
Windows 8 Clean Install: NPM not recognized when File > Restart is run
|
When NPM is first installed and studio is restarted using File > Restart, npm is never recognized. Studio must be Exited to recognize npm. Steps to Reproduce: 1. Install node.js. 2. File > Restart. 3. check for titanium updates Actual Result: npm not found error, alerts user to restart studio as a work-around Expected Result: file > restart behaves the same as exit-reopen, npm is recognized if it is installed
| 8 |
905 |
TISTUD-2903
|
11/30/2012 01:08:39
|
Ubuntu: splash screen radio buttons have odd rendering
|
The login splash has odd rendering near the radio buttons. There is a strange orange half-rectangle to the right of the buttons. Steps to Reproduce: 1. Logout and restart studio. Actual Result: Radio buttons have odd rendering just to the right of the buttons. Expected Result: Radio buttons render 'correctly'.
| 5 |
906 |
TISTUD-2905
|
11/30/2012 01:42:52
|
TiApp editor: Grayed out deployment targets and modules when switching to a different Ti SDK
|
# Have two different Titanium SDKlocations. Have them contain different SDKs. # Create a Mobile app and have the TiApp editor open. # Go to the Titanium preferences and pick a different Titanium SDK location. # Apply and OK. Result: You will notice that the SDK combo changes its values. However, the 'Deployment Targets' and the 'Modules' sections are getting grayed out and have warnings.
| 3 |
907 |
TISTUD-2909
|
11/30/2012 10:20:18
|
Content assist : JS Built in Types for 'Ma' and 'Docu' are not displayed in Content Assist for app.js file
|
1. Install Titanium Studio, build: 3.0.0.201211291910 2. Create a new project. 3. Create a new .JS file in the Resources folder 4. Type 'Ma' or 'Docu' After Step 3: Content Assist should appear and 'Math' and 'Document' respectively should be highlighted
| 5 |
908 |
TISTUD-2912
|
11/30/2012 11:40:05
|
Titanium Studio: Android Updater prompt which appears at the bottom right hand side of studio displays 'OK' which is unnecessary.
|
This is not a regression bug. Test Steps : Install latest studio and set path for Android SDK . Dashboard > Configure > Android. Update the android and after update process finishes , close that window. Observe that Android Updater prompt which appears at the bottom right hand side of titanium studio contais 'OK' which is unnecessary.Please refer attached screenshot.
| 2 |
909 |
TISTUD-2913
|
11/30/2012 16:38:10
|
Investigate JS indexing of Alloy source/JSDuck comments
|
We'd like to provide CA for alloy APIs. We need to look into whether we can simply index the alloy source with the JSDuck comments to do so. We may need to extend our SDoc support to cover more tags provided by JSDuck (https://github.com/senchalabs/jsduck) If we can simply index the JS files with the JSDuck comments, then we can pretty easily fold this into our general node modules indexing, since the source will be available in the alloy module (/usr/local/lib/alloy/Alloy)
| 8 |
910 |
TISTUD-2914
|
11/30/2012 16:42:44
|
Index NodeJS/npm modules
|
We should be able to index NodeJS/npm install's node modules. We can query npm for the install paths and then index all the modules we find underneath. We'd need a way to attach these loadpaths/indices to a project. Our current load provider support re-uses the index for the project, which isn't really correct - and it is assumed to return a lit of files to index, which we can do, but it may be easier to just return the directories. Ideally the NodeJS install as a whole would be a single "entry" (like a JRE/KDK for JDT) and it resolves to it's various paths and is indexed to it's own index/indices. Then the projects just add them to their list of indices to search/query.
| 13 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.