issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-2522
|
Error thrown while updating CLI in Ubuntu 12.04
|
When trying to install updates in Ubuntu 12.04 I get the following error: {code} !ENTRY com.appcelerator.titanium.update 4 4 2012-10-15 08:25:56.113 !MESSAGE Error encountered during update !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2012-10-15 08:25:56.113 !MESSAGE Cannot run program "gksudo --message='Titanium Studio would like to install Titanium CLI.'": java.io.IOException: error=2, No such file or directory !STACK 0 java.io.IOException: Cannot run program "gksudo --message='Titanium Studio would like to install Titanium CLI.'": java.io.IOException: error=2, No such file or directory java.lang.ProcessBuilder.start(ProcessBuilder.java:475) com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327) com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322) com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273) com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235) com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.install(NodePackageManager.java:112) com.appcelerator.titanium.update.TitaniumNPMRelease.install(TitaniumNPMRelease.java:37) com.appcelerator.titanium.update.TitaniumSDKUpdater.installTitaniumUpdates(TitaniumSDKUpdater.java:561) com.appcelerator.titanium.update.TitaniumSDKUpdater.access$1(TitaniumSDKUpdater.java:510) com.appcelerator.titanium.update.TitaniumSDKUpdater$2.run(TitaniumSDKUpdater.java:345) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory java.lang.UNIXProcess.<init>(UNIXProcess.java:164) java.lang.ProcessImpl.start(ProcessImpl.java:81) java.lang.ProcessBuilder.start(ProcessBuilder.java:468) ... 10 more {code} Steps to reproduce: 1. Start Titanium Studio 2. Attempt to install the new CLI through the toast popup (or Help > Check for Titanium Updates) Expected result: The Titanium CLI should correctly install into Titanium Studio. Actual result: The above error.
| 3 |
train
|
TISTUD-2524
|
Unable to install project on device - CLI path is not being located.
|
An Exception error during project installation, could not locate the CLI path. See an attachment. Tried to run 2.1.3 - the same error
| 8 |
train
|
TISTUD-2568
|
No logs are shown in Studio when building Mobile Web using the new CLI
|
When builds are run in TiStudio, via the new CLI, for iOS and Android, build logs show up in the console window as expected. This does not happen for mobileweb. Mobileweb shows absolutely nothing in the console window. The build process is working, but it is showing no output, which could be critical for developers debugging applications. You can exhibit this behavior by building a new Alloy application in TiStudio and running it for mobileweb. It should run successfully, but it will show no output whatsoever in the console window.
| 8 |
train
|
TISTUD-2527
|
CLI: cli not prompted for install on studio startup
|
When studio first starts, the cli is not prompted to update, but alloy and node.acs are. NPM Installer Log: {code} DHydeMBP:workspace dhyde$ '/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/plugins/com.aptana.libraries_3.0.0.1346444124/os/macosx/cocoa sudo' '--prompt=Titanium Studio would like to install acs.' '/usr/local/bin/npm' '-g' 'install' 'acs' 2>&1 | tee install.log DHydeMBP:workspace dhyde$ '/Users/dhyde/Desktop/TISTUD-RC/Titanium Studio/plugins/com.aptana.libraries_3.0.0.1346444124/os/macosx/cocoa sudo' '--prompt=Titanium Studio would like to install alloy.' '/usr/local/bin/npm' '-g' 'install' 'alloy' 2>&1 | tee install.log {code} Steps to Reproduce: 1. Uninstall titanium cli (i.e. delete titanium folder from npm folder). 2. Start studio. Actual Result: No prompt to install cli. However, there are prompts to install alloy and acs. Expected Result: Prompt to install titanium cli if it is not installed (along with alloy and acs).
| 5 |
train
|
TISTUD-2531
|
Titanium Updates: cancelled updates that were successful have false error message
|
If the user takes a CLI, Alloy, or Node.ACS update, and cancels the process using the 'Cancel' button after entering the system password in the prompt, the update will be successful (just as with SDK updates, this is ideal behavior), but there is a failure message. There should be a success message as with the SDK. See screenshots. Steps to Reproduce: 1. Update either CLI, Node.ACS, or Alloy from Studio (Check for Titanium Updates). 2. After entering user password for install prompt, cancel the install using the 'Cancel' button in the process dialog. Actual Result: Fail message, and fail dialog, fail messages in log. Expected Result: The installation was successful, which is ideal because we don't want half-installed software, and there should be a success toast in the lower-right corner, as with SDK downloads that are cancelled late during the extraction process.
| 5 |
train
|
TISTUD-2535
|
Titanium Project: new project caused error Problems occurred while refreshing local changes
|
When creating a new titanium project, I received an error that I could not reproduce on further attempts: error: {code} !ENTRY org.eclipse.core.resources 4 1 2012-10-16 09:21:00.473 !MESSAGE Problems occurred while refreshing local changes !SUBENTRY 1 org.eclipse.core.resources 4 1 2012-10-16 09:21:00.473 !MESSAGE Problems occurred while refreshing local changes !STACK 1 org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system. org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923) org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904) org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1663) org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:167) org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Contains: The project description file (.project) for 'MyProject' is missing. This file contains important information about the project. The project will not function properly until this file is restored. !SUBENTRY 2 org.eclipse.core.resources 4 271 2012-10-16 09:21:00.475 !MESSAGE Errors occurred while refreshing resources with the local file system. !SUBENTRY 3 org.eclipse.core.resources 4 567 2012-10-16 09:21:00.475 !MESSAGE The project description file (.project) for 'MyProject' is missing. This file contains important information about the project. The project will not function properly until this file is restored. {code} Steps to Reproduce: 1. Create a Titanium Project. Actual Result: Error. Expected Result: New Titanium Project.
| 5 |
train
|
TISTUD-2537
|
content-assist: Doc pages show broken links
|
When testing the deprecation fixes in SDK, I noticed that studio is now displaying links (yay!) except that they don't go anywhere (boo!). Specifically, Studio used to strip out tags, so we didn't bother to in the JSCA. So links to Titanium types, for example, show up as something like this: {code} <a href="Titanium.Proxy.applyProperties">applyProperties</a> {code} So, we either need to remove the links from the JSCA or Studio needs to handle these in some useful fashion.
| 8 |
train
|
TISTUD-2538
|
NPM: npm install not validated on studio startup
|
When studio first starts, the npm is not prompted to install if it is not installed, this will prevent Alloy, CLI, and ACS from installing. Note this is not a typical use case and npm is assumed to be installed along with node.js. This is an improvement that would make studio a bit more robust. Studio Error Log: {code} !ENTRY com.appcelerator.titanium.update 4 0 2012-10-16 14:10:27.465 !MESSAGE (Build 3.0.0.201210151149) [ERROR] NPM is not installed. !STACK 1 org.eclipse.core.runtime.CoreException: NPM is not installed. com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.getInstalledVersion(NodePackageManager.java:259) com.appcelerator.titanium.update.TitaniumSDKUpdater.getPackageLatestVersion(TitaniumSDKUpdater.java:619) com.appcelerator.titanium.update.TitaniumSDKUpdater.getCLIUpdates(TitaniumSDKUpdater.java:637) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasCLIUpdates(TitaniumSDKUpdater.java:227) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasUpdates(TitaniumSDKUpdater.java:164) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler.execute(TitaniumUpdateHandler.java:34) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2012-10-16 14:10:27.466 !MESSAGE NPM is not installed. !ENTRY com.appcelerator.titanium.update 4 0 2012-10-16 14:10:27.468 !MESSAGE (Build 3.0.0.201210151149) [ERROR] NPM is not installed. !STACK 1 org.eclipse.core.runtime.CoreException: NPM is not installed. com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.getInstalledVersion(NodePackageManager.java:259) com.appcelerator.titanium.update.TitaniumSDKUpdater.getPackageLatestVersion(TitaniumSDKUpdater.java:619) com.appcelerator.titanium.update.TitaniumSDKUpdater.getAlloyUpdates(TitaniumSDKUpdater.java:662) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasAlloyUpdates(TitaniumSDKUpdater.java:253) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasUpdates(TitaniumSDKUpdater.java:164) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler.execute(TitaniumUpdateHandler.java:34) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2012-10-16 14:10:27.469 !MESSAGE NPM is not installed. !ENTRY com.appcelerator.titanium.update 4 0 2012-10-16 14:10:27.470 !MESSAGE (Build 3.0.0.201210151149) [ERROR] NPM is not installed. !STACK 1 org.eclipse.core.runtime.CoreException: NPM is not installed. com.appcelerator.titanium.nodejs.internal.core.NodePackageManager.getInstalledVersion(NodePackageManager.java:259) com.appcelerator.titanium.update.TitaniumSDKUpdater.getPackageLatestVersion(TitaniumSDKUpdater.java:619) com.appcelerator.titanium.update.TitaniumSDKUpdater.getACSUpdates(TitaniumSDKUpdater.java:650) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasACSUpdates(TitaniumSDKUpdater.java:240) com.appcelerator.titanium.update.TitaniumSDKUpdater.hasUpdates(TitaniumSDKUpdater.java:164) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler.execute(TitaniumUpdateHandler.java:34) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) !SUBENTRY 1 com.appcelerator.titanium.nodejs.core 4 0 2012-10-16 14:10:27.471 !MESSAGE NPM is not installed. {code} Steps to Reproduce: 1. Uninstall npm (i.e. delete npm folder from node_modules). 2. Start studio. Actual Result: No prompt to install npm. No prompts to install alloy, acs, or titanium, and no future updates for those node modules. Expected Result: Prompt to install npm if it is not installed.
| 5 |
train
|
TISTUD-2539
|
JS Parser Validation: Failed to parse file Cannot recover from the syntax error
|
Saw this in the log. I created two projects, inserted two breakpoints, and ran both in android device. They were default projects, one with an extra event listener. Log: {code} !ENTRY com.aptana.editor.js 4 0 2012-10-16 15:29:36.290 !MESSAGE (Build 3.0.0.201210151149) [ERROR] Failed to parse file:/Users/dhyde/Desktop/TISTUD-RC/workspace/MyProject/Resources/app.js for JS Parser Validation !STACK 1 org.eclipse.core.runtime.CoreException: Cannot recover from the syntax error com.aptana.index.core.build.BuildContext.getAST(BuildContext.java:129) com.aptana.index.core.build.BuildContext.getAST(BuildContext.java:97) com.aptana.editor.js.validator.JSParserValidator.buildFile(JSParserValidator.java:145) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.runParticipants(CommonReconcilingStrategy.java:333) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:273) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:231) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.fullReconcile(CommonReconcilingStrategy.java:437) com.aptana.editor.common.text.reconciler.CommonReconciler.process(CommonReconciler.java:162) org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:206) Caused by: beaver.Parser$Exception: Cannot recover from the syntax error beaver.Parser.recoverFromError(Parser.java:697) com.aptana.editor.js.parsing.JSParser.recoverFromError(JSParser.java:557) beaver.Parser.parse(Parser.java:498) beaver.Parser.parse(Parser.java:439) com.aptana.editor.js.parsing.JSParser.parse(JSParser.java:383) com.aptana.editor.js.parsing.JSParser.parse(JSParser.java:345) com.aptana.parsing.ParsingEngine.noCacheParse(ParsingEngine.java:424) com.aptana.parsing.ParsingEngine.parse(ParsingEngine.java:229) com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:230) com.aptana.index.core.build.BuildContext.parse(BuildContext.java:150) com.aptana.index.core.build.BuildContext.getAST(BuildContext.java:121) ... 9 more !SUBENTRY 1 com.aptana.index.core 4 0 2012-10-16 15:29:36.290 !MESSAGE Cannot recover from the syntax error !STACK 0 beaver.Parser$Exception: Cannot recover from the syntax error beaver.Parser.recoverFromError(Parser.java:697) com.aptana.editor.js.parsing.JSParser.recoverFromError(JSParser.java:557) beaver.Parser.parse(Parser.java:498) beaver.Parser.parse(Parser.java:439) com.aptana.editor.js.parsing.JSParser.parse(JSParser.java:383) com.aptana.editor.js.parsing.JSParser.parse(JSParser.java:345) com.aptana.parsing.ParsingEngine.noCacheParse(ParsingEngine.java:424) com.aptana.parsing.ParsingEngine.parse(ParsingEngine.java:229) com.aptana.parsing.ParserPoolFactory.parse(ParserPoolFactory.java:230) com.aptana.index.core.build.BuildContext.parse(BuildContext.java:150) com.aptana.index.core.build.BuildContext.getAST(BuildContext.java:121) com.aptana.index.core.build.BuildContext.getAST(BuildContext.java:97) com.aptana.editor.js.validator.JSParserValidator.buildFile(JSParserValidator.java:145) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.runParticipants(CommonReconcilingStrategy.java:333) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:273) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:231) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.fullReconcile(CommonReconcilingStrategy.java:437) com.aptana.editor.common.text.reconciler.CommonReconciler.process(CommonReconciler.java:162) org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:206) {code} app.js {code} // this sets the background color of the master UIView (when there are no windows/tab groups on it) Titanium.UI.setBackgroundColor('#000'); // create tab group var tabGroup = Titanium.UI.createTabGroup(); // // create base UI tab and root window // var win1 = Titanium.UI.createWindow({ title:'Tab 1', backgroundColor:'red' }); var tab1 = Titanium.UI.createTab({ icon:'KS_nav_views.png', title:'Tab 1', window:win1 }); var label1 = Titanium.UI.createLabel({ color:'#999', text:'I am Window 1', font:{fontSize:20,fontFamily:'Helvetica Neue'}, textAlign:'center', width:'auto' }); win1.add(label1); // // create controls tab and root window // var win2 = Titanium.UI.createWindow({ title:'Tab 2', backgroundColor:'#fff' }); var tab2 = Titanium.UI.createTab({ icon:'KS_nav_ui.png', title:'Tab 2', window:win2 }); var label2 = Titanium.UI.createLabel({ color:'#999', text:'I am Window 2', font:{fontSize:20,fontFamily:'Helvetica Neue'}, textAlign:'center', width:'auto' }); win2.add(label2); // // add tabs // tabGroup.addTab(tab1); tabGroup.addTab(tab2); // open tab group tabGroup.open(); win1.addEventListener('click', function(){ win1.backgroundColor = win1.backgroundColor == 'red' ? 'blue' : 'red'; }); {code}
| 3 |
train
|
TISTUD-2540
|
WARNING: Prevented recursive attempt to activate part com.aptana.editor.js while still in the middle of activating part com.aptana.editor.text
|
Saw this in the log. Created a default project and ran in a android device debugger. Log: {code} !ENTRY org.eclipse.ui.workbench 4 0 2012-10-16 16:43:38.751 !MESSAGE WARNING: Prevented recursive attempt to activate part com.aptana.editor.js while still in the middle of activating part com.aptana.editor.text !STACK 0 java.lang.RuntimeException: WARNING: Prevented recursive attempt to activate part com.aptana.editor.js while still in the middle of activating part com.aptana.editor.text org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3586) org.eclipse.ui.internal.WorkbenchPage.internalActivate(WorkbenchPage.java:691) org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:663) org.eclipse.ui.internal.WorkbenchPage.makeActive(WorkbenchPage.java:1324) org.eclipse.ui.internal.WorkbenchPage.bringToTop(WorkbenchPage.java:918) org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:270) org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.display(SourceLookupFacility.java:219) org.eclipse.debug.ui.DebugUITools.displaySource(DebugUITools.java:973) org.eclipse.debug.internal.ui.elements.adapters.StackFrameSourceDisplayAdapter$SourceDisplayJob.runInUIThread(StackFrameSourceDisplayAdapter.java:157) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:364) org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:463) org.eclipse.ui.texteditor.AbstractTextEditor.handleEditorInputChanged(AbstractTextEditor.java:4757) org.eclipse.ui.texteditor.StatusTextEditor.handleEditorInputChanged(StatusTextEditor.java:267) org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.handleEditorInputChanged(AbstractDecoratedTextEditor.java:1474) com.aptana.editor.common.internal.AbstractFoldingEditor.handleEditorInputChanged(AbstractFoldingEditor.java:252) org.eclipse.ui.texteditor.AbstractTextEditor.sanityCheckState(AbstractTextEditor.java:4887) org.eclipse.ui.texteditor.StatusTextEditor.sanityCheckState(StatusTextEditor.java:257) org.eclipse.ui.texteditor.AbstractTextEditor.safelySanityCheckState(AbstractTextEditor.java:4865) org.eclipse.ui.texteditor.AbstractTextEditor$ActivationListener.handleActivation(AbstractTextEditor.java:984) org.eclipse.ui.texteditor.AbstractTextEditor$ActivationListener.partActivated(AbstractTextEditor.java:941) org.eclipse.ui.internal.PartListenerList$1.run(PartListenerList.java:72) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.runtime.Platform.run(Platform.java:888) org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:57) org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:70) org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:187) org.eclipse.ui.internal.PartService.setActivePart(PartService.java:306) org.eclipse.ui.internal.WWinPartService.updateActivePart(WWinPartService.java:134) org.eclipse.ui.internal.WWinPartService.access$0(WWinPartService.java:125) org.eclipse.ui.internal.WWinPartService$WWinListener.partDeactivated(WWinPartService.java:50) org.eclipse.ui.internal.PartListenerList2$4.run(PartListenerList2.java:115) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.runtime.Platform.run(Platform.java:888) org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:55) org.eclipse.ui.internal.PartListenerList2.firePartDeactivated(PartListenerList2.java:113) org.eclipse.ui.internal.PartService.firePartDeactivated(PartService.java:242) org.eclipse.ui.internal.PartService.setActivePart(PartService.java:300) org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:57) org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136) org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3636) org.eclipse.ui.internal.WorkbenchPage.internalActivate(WorkbenchPage.java:691) org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:663) org.eclipse.ui.internal.WorkbenchPage.makeActive(WorkbenchPage.java:1324) org.eclipse.ui.internal.WorkbenchPage.updateActivePart(WorkbenchPage.java:1304) org.eclipse.ui.internal.WorkbenchPage.updateVisibility(WorkbenchPage.java:3779) org.eclipse.ui.internal.WorkbenchPage.setPerspective(WorkbenchPage.java:3719) org.eclipse.ui.internal.WorkbenchPage.busySetPerspective(WorkbenchPage.java:1115) org.eclipse.ui.internal.WorkbenchPage.access$16(WorkbenchPage.java:1099) org.eclipse.ui.internal.WorkbenchPage$19.run(WorkbenchPage.java:3814) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.WorkbenchPage.setPerspective(WorkbenchPage.java:3812) org.eclipse.ui.internal.Workbench.showPerspective(Workbench.java:2795) org.eclipse.debug.internal.ui.launchConfigurations.PerspectiveManager.switchToPerspective(PerspectiveManager.java:316) org.eclipse.debug.internal.ui.launchConfigurations.PerspectiveManager$4.runInUIThread(PerspectiveManager.java:395) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 8 |
train
|
TISTUD-2541
|
Android Device Debugger: console log process not terminated in debug view
|
When debug process thread is terminated, the console log process is not terminated, and the entire session process is not terminated. Steps to Reproduce: 1. Debug in Android Device (default project w/one breakpoint). 2. When breakpoint is hit, and thread is selected in debug view, press 'terminate'. Actual Result: Console log process is still active. Session process is still active. Expected Result: All associated session processes should be terminated. Console log process and session should be terminated.
| 5 |
train
|
TISTUD-2545
|
Titanium: Project Creation - When you create the default app with ACS enabled, the guid in the tiapp.xml does not match with the guid in my.appcelerator.com
|
Details: If you create the default Titanium app with ACS enabled from Studio, the guid in the tiapp.xml does not match with the guid in my.appcelerator.com \\ \\ If you create the default Titanium app *without* ACS enabled, then the guid in the tiapp.xml will match with the guid in my.appcelerator.com \\ \\ Steps to reproduce: 1. Create default Titanium app with ACS enabled 2. Go to my.appcelerator.com and find your app 3. Click on *App Details* link \\ \\ Actual: The guid in the tiapp.xml does not match with the guid in my.appcelerator.com (see tiapp_xml.png and my_apps.png). And if you go to my.appcelerator.com/app/<guid_in_tiapp>, the my apps page does not recognize it (see no_guid.png) \\ \\ Expected: The guids generated in Studio should match guid in the my apps page.
| 5 |
train
|
TISTUD-2542
|
Android Device Debugger: empty project console view appears
|
When android debug on device is run, the empty project console view blocks the console log view. Does this empty view serve a purpose? Steps to Reproduce: 1. Debug in Android Device. Actual Result: Empty project console view appears, no console log output, appears broken. Expected Result: Console log view appears, console output appears.
| 5 |
train
|
TISTUD-2544
|
No Alloy templates appear in Titanium project wizard when the alloy installation path differs from default
|
Gabe has an issue where alloy is getting installed into /opt/local/bin and /opt/local/lib/node_modules instead of the default /usr/local directory, probably due to the $PATH he has set in the system. When that happened, opening New > Titanium Project would show no Alloy project templates, even after we created symlinks in /usr/local/bin and /usr/local/lib/node_modules.
| 8 |
train
|
TISTUD-2546
|
Add File > New > Node.ACS Project to the simple Studio perspective
|
This is not a regression issue. Steps To Reproduce: 1. Download 2.1.2 studio installer and upgrade it to 3.0 2. Delete plugin files from /usr/local/lib/node_modules folder. 3. Go to Help > Check for Titanium Updates. From the window install, alloy, CLI and acs updates. Actual: After successful installation of all plugins, File > New > Node.ACS option does not appear. Expected: File > New > Node.ACS option must appear.
| 5 |
train
|
TISTUD-2549
|
Sync common preferences between Studio and titanium CLI
|
I'm not sure if CLI wants us to be setting global values in config to match or not, but I'm guessing by default we should sync up the values for things like Android SDK path. If a user sets the path in Titanium Studio we should pass that along to the CLI to store as well. We may also need to do the reverse on startup - look up what CLI has in it's config and push that into our prefs (with some sanity check to see if the value is valid - or at least "more valid" than what we have set).
| 8 |
train
|
TISTUD-2550
|
Issue install using NPM to install within Titanium Studio in Windows 7
|
The following is shown in the NPM Installer Window during start up: {code} qatester@QATESTER-CH1 ~/My Documents/Titanium_Studio_Workspace $ "c:\Program Files (x86)\nodejs\npm.CMD" -g install titanium > install.log | type install.log c:\Program Files (x86)\nodejs\npm.CMD: line 1: unexpected EOF while looking for matching `'' c:\Program Files (x86)\nodejs\npm.CMD: line 7: syntax error: unexpected end of file install.log is ./install.log qatester@QATESTER-CH1 ~/My Documents/Titanium_Studio_Workspace $ "c:\Program Files (x86)\nodejs\npm.CMD" -g install alloy > install.log | type install.log install.log is ./install.log c:\Program Files (x86)\nodejs\npm.CMD: line 1: unexpected EOF while looking for matching `'' c:\Program Files (x86)\nodejs\npm.CMD: line 7: syntax error: unexpected end of file qatester@QATESTER-CH1 ~/My Documents/Titanium_Studio_Workspace $ "c:\Program Files (x86)\nodejs\npm.CMD" -g install acs > install.log | type install.log c:\Program Files (x86)\nodejs\npm.CMD: line 1: unexpected EOF while looking for matching `'' c:\Program Files (x86)\nodejs\npm.CMD: line 7: syntax error: unexpected end of file install.log is ./install.log {code} The ./install.log contains no data, blank file with 0kb size. This looks like a failed install for Titanium CLI, ACS and Alloy. Steps to reproduce: 1. Without Titanium, ACS, or Alloy installed start Titanium Studio. Expected results: Plugins should be correctly installed. Actual results: The above issue.
| 8 |
train
|
TISTUD-2553
|
Titanium Updates: update menu appeared with no entries
|
An update prompt appeared in the lower right corner of studio, when the titanium updates menu came up, it did not contain any entries. See screenshot. See log. This is intermittent. Steps to Reproduce: 1. Open Titanium Studio. 2. Wait for updates prompt in lower right corner. 3. Click on it to bring up the updates menu. Actual Result: No entries. Expected Result: Should contain the update that initiated the prompt.
| 5 |
train
|
TISTUD-2559
|
Studio: Preferences: takes 3 seconds to load default android sdk and screen types
|
Preferences > Titanium Studio > Titanium > Default Android SDK takes 3 seconds to load. This is a regression. Steps to Reproduce: 1. Run Preferences > Titanium Studio > Titanium > Default Android SDK takes 3 seconds to load. Actual Result: 3 seconds to load, initially looks broken. Expected Result: Instant load. Note: As per Shalom, here is the command-line arg to get this preferences info: titanium info -o json
| 8 |
train
|
TISTUD-2561
|
Titanium Updates: Unhandled event loop exception after installing updates
|
After installing alloy, get log exception: {code} !ENTRY com.aptana.core 1 0 2012-10-18 09:06:49.822 !MESSAGE (Build 3.0.0.201210172118) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/npm" "-p" "list" "alloy" "-g" Working directory: null 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-EeKGAL/Render, Apple_Ubiquity_Message=/tmp/launch-SW45KT/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-9CZqFn/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-0sLjqp/Listeners, TI_DEBUG=0, TMPDIR=/var/folders/6f/wxjmlj0n7kl5w8kmq5hrrbch0000gp/T/, USER=dhyde, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmTask=JNI, redirectErrorStream=} !ENTRY com.aptana.core 1 0 2012-10-18 09:06:49.842 !MESSAGE (Build 3.0.0.201210172118) [INFO] com.aptana.core/debug/shell Searching for titanium in PATH locations: /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 !ENTRY com.aptana.core 1 0 2012-10-18 09:06:49.843 !MESSAGE (Build 3.0.0.201210172118) [INFO] com.aptana.core/debug/shell Found executable on PATH: /usr/local/bin/titanium !ENTRY org.eclipse.ui 4 0 2012-10-18 09:07:46.255 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException java.lang.String.<init>(String.java:210) com.aptana.terminal.internal.emulator.ThemedTextLineRenderer.drawLine(ThemedTextLineRenderer.java:95) org.eclipse.tm.internal.terminal.textcanvas.TextCanvas.drawLine(TextCanvas.java:343) org.eclipse.tm.internal.terminal.textcanvas.GridCanvas.paint(GridCanvas.java:80) org.eclipse.tm.internal.terminal.textcanvas.VirtualCanvas$1.handleEvent(VirtualCanvas.java:48) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Control.drawWidget(Control.java:1244) org.eclipse.swt.widgets.Canvas.drawWidget(Canvas.java:163) org.eclipse.swt.widgets.Widget.drawRect(Widget.java:740) org.eclipse.swt.widgets.Canvas.drawRect(Canvas.java:158) org.eclipse.swt.widgets.Display.windowProc(Display.java:5449) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSView.displayIfNeeded(NSView.java:142) org.eclipse.swt.widgets.Control.update(Control.java:4890) org.eclipse.swt.widgets.Control.update(Control.java:4876) org.eclipse.tm.internal.terminal.textcanvas.VirtualCanvas.repaint(VirtualCanvas.java:145) org.eclipse.tm.internal.terminal.textcanvas.TextCanvas.repaintRange(TextCanvas.java:340) org.eclipse.tm.internal.terminal.textcanvas.TextCanvas$1.rangeChanged(TextCanvas.java:96) org.eclipse.tm.internal.terminal.textcanvas.AbstractTextCanvasModel.fireCellRangeChanged(AbstractTextCanvasModel.java:60) org.eclipse.tm.internal.terminal.textcanvas.AbstractTextCanvasModel.updateCursor(AbstractTextCanvasModel.java:183) org.eclipse.tm.internal.terminal.textcanvas.AbstractTextCanvasModel.update(AbstractTextCanvasModel.java:118) org.eclipse.tm.internal.terminal.textcanvas.PollingTextCanvasModel$1.run(PollingTextCanvasModel.java:28) org.eclipse.swt.widgets.Display.runTimers(Display.java:4106) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3604) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} Steps to Reproduce: 1. Install alloy. 2. View log. Actual Result: Exception. Expected Result: No exceptions.
| 8 |
train
|
TISTUD-2562
|
Titanium Updates: inform user all updates will be installed on studio launch
|
Entering user password on studio launch once installs all titanium updates regardless of user wishes. If the prompt is going to install everything, it should message that to the user. NMP Installer Log: {code} DHydeMBP:workspace dhyde$ read -s PASSWORD DHydeMBP:workspace dhyde$ echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'acs' 2>&1 | tee install.log npm http GET https://registry.npmjs.org/acs echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'alloy' 2>&1 | tee install.log echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'titanium' 2>&1 | tee install.log read -s PASSWORD npm http 304 https://registry.npmjs.org/acs npm http GET https://registry.npmjs.org/colors/0.6.0-1 npm http GET https://registry.npmjs.org/commander/0.6.1 npm http GET https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.4 npm http GET https://registry.npmjs.org/connect/2.3.5 npm http GET https://registry.npmjs.org/express/2.5.11 npm http GET https://registry.npmjs.org/ejs/0.8.0 npm http GET https://registry.npmjs.org/log4js/0.5.1 npm http GET https://registry.npmjs.org/longjohn/0.0.3 npm http GET https://registry.npmjs.org/pkginfo/0.2.2 npm http GET https://registry.npmjs.org/fstream/0.1.18 npm http GET https://registry.npmjs.org/connect-mongo/0.1.9 npm http GET https://registry.npmjs.org/node-uuid/1.3.3 npm http GET https://registry.npmjs.org/wrench/1.3.9 npm http GET https://registry.npmjs.org/mkdirp/0.3.3 npm http GET https://registry.npmjs.org/tar/0.1.13 npm http GET https://registry.npmjs.org/socket.io/0.9.6 npm http GET https://registry.npmjs.org/temp/0.4.0 npm http GET https://registry.npmjs.org/underscore/1.3.3 npm http GET https://registry.npmjs.org/uglify-js/1.3.2 npm http 304 https://registry.npmjs.org/colors/0.6.0-1 npm http 304 https://registry.npmjs.org/commander/0.6.1 npm http 304 https://registry.npmjs.org/connect/2.3.5 npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/express/2.5.11 npm http 304 https://registry.npmjs.org/ejs/0.8.0 npm http 304 https://registry.npmjs.org/log4js/0.5.1 npm http 304 https://registry.npmjs.org/longjohn/0.0.3 npm http 304 https://registry.npmjs.org/pkginfo/0.2.2 npm http 304 https://registry.npmjs.org/fstream/0.1.18 npm http 304 https://registry.npmjs.org/connect-mongo/0.1.9 npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/mkdirp/0.3.3 npm http 200 https://registry.npmjs.org/node-uuid/1.3.3 npm http 304 https://registry.npmjs.org/wrench/1.3.9 npm http GET https://registry.npmjs.org/node-uuid/-/node-uuid-1.3.3.tgz npm http 304 https://registry.npmjs.org/tar/0.1.13 npm http 304 https://registry.npmjs.org/socket.io/0.9.6 npm http 200 https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.4 npm http 304 https://registry.npmjs.org/underscore/1.3.3 npm http 304 https://registry.npmjs.org/temp/0.4.0 npm http 200 https://registry.npmjs.org/node-uuid/-/node-uuid-1.3.3.tgz npm http 304 https://registry.npmjs.org/uglify-js/1.3.2 npm http GET https://registry.npmjs.org/rimraf npm http GET https://registry.npmjs.org/graceful-fs npm http GET https://registry.npmjs.org/inherits npm http GET https://registry.npmjs.org/mongodb npm http GET https://registry.npmjs.org/inherits npm http GET https://registry.npmjs.org/policyfile/0.0.4 npm http GET https://registry.npmjs.org/block-stream npm http GET https://registry.npmjs.org/connect npm http GET https://registry.npmjs.org/redis/0.6.7 npm http GET https://registry.npmjs.org/mkdirp/0.3.0 npm http GET https://registry.npmjs.org/qs npm http GET https://registry.npmjs.org/socket.io-client/0.9.6 npm http GET https://registry.npmjs.org/mime/1.2.4 npm http GET https://registry.npmjs.org/async/0.1.15 npm http GET https://registry.npmjs.org/qs/0.4.2 npm http GET https://registry.npmjs.org/formidable/1.0.11 npm http GET https://registry.npmjs.org/crc/0.2.0 npm http GET https://registry.npmjs.org/cookie/0.0.4 npm http GET https://registry.npmjs.org/bytes/0.0.1 npm http GET https://registry.npmjs.org/fresh/0.0.1 npm http GET https://registry.npmjs.org/range-parser/0.0.4 npm http GET https://registry.npmjs.org/debug npm http 304 https://registry.npmjs.org/rimraf npm http 304 https://registry.npmjs.org/graceful-fs npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/mongodb npm http 304 https://registry.npmjs.org/policyfile/0.0.4 npm http 304 https://registry.npmjs.org/block-stream npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/connect npm http 304 https://registry.npmjs.org/redis/0.6.7 npm WARN package.json [email protected] No README.md file found! npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/qs npm http 304 https://registry.npmjs.org/mkdirp/0.3.0 npm http 304 https://registry.npmjs.org/socket.io-client/0.9.6 npm http 304 https://registry.npmjs.org/mime/1.2.4 npm http 304 https://registry.npmjs.org/async/0.1.15 npm http 304 https://registry.npmjs.org/formidable/1.0.11 npm http 304 https://registry.npmjs.org/cookie/0.0.4 npm http 304 https://registry.npmjs.org/bytes/0.0.1 npm http 304 https://registry.npmjs.org/qs/0.4.2 npm http 304 https://registry.npmjs.org/crc/0.2.0 npm http 304 https://registry.npmjs.org/fresh/0.0.1 npm http 304 https://registry.npmjs.org/range-parser/0.0.4 npm http 304 https://registry.npmjs.org/debug npm http GET https://registry.npmjs.org/formidable npm http GET https://registry.npmjs.org/bson/0.0.4 npm http GET https://registry.npmjs.org/uglify-js/1.2.5 npm http GET https://registry.npmjs.org/ws npm http GET https://registry.npmjs.org/xmlhttprequest/1.2.2 npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1 npm http 304 https://registry.npmjs.org/formidable npm http 304 https://registry.npmjs.org/bson/0.0.4 npm WARN package.json [email protected] No README.md file found! > [email protected] install /usr/local/lib/node_modules/acs/node_modules/connect-mongo/node_modules/mongodb/node_modules/bson > node install.js npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1 ================================================================================ = = = To install with C++ bson parser do <npm install mongodb --mongodb:native> = = = ================================================================================ npm http 304 https://registry.npmjs.org/uglify-js/1.2.5 npm http 304 https://registry.npmjs.org/ws npm http 304 https://registry.npmjs.org/xmlhttprequest/1.2.2 npm http GET https://registry.npmjs.org/zeparser/0.0.5 npm http GET https://registry.npmjs.org/tinycolor npm http GET https://registry.npmjs.org/options npm http 304 https://registry.npmjs.org/zeparser/0.0.5 npm http 304 https://registry.npmjs.org/tinycolor npm http 304 https://registry.npmjs.org/options > [email protected] install /usr/local/lib/node_modules/acs/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws > node install.js [ws v0.4.22] Attempting to compile blazing fast native extensions. [ws v0.4.22] Native extension compilation successful! /usr/local/bin/acs -> /usr/local/lib/node_modules/acs/bin/acs [email protected] /usr/local/lib/node_modules/acs ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected], [email protected], [email protected]) ├── [email protected] ([email protected], [email protected]) ├── [email protected] ([email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], formida [email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected]) ├── [email protected] ([email protected]) └── [email protected] ([email protected], [email protected], [email protected]) DHydeMBP:workspace dhyde$ echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'alloy' 2>&1 | tee install.log npm http GET https://registry.npmjs.org/alloy npm http 304 https://registry.npmjs.org/alloy npm http GET https://registry.npmjs.org/colors/0.6.0-1 npm http GET https://registry.npmjs.org/pkginfo/0.2.2 npm http GET https://registry.npmjs.org/commander/0.6.1 npm http GET https://registry.npmjs.org/wrench/1.3.9 npm http GET https://registry.npmjs.org/xmldom/0.1.13 npm http GET https://registry.npmjs.org/jsonlint/1.5.1 npm http GET https://registry.npmjs.org/stripcolorcodes/0.1.0 npm http GET https://registry.npmjs.org/jake npm http 304 https://registry.npmjs.org/colors/0.6.0-1 npm http 304 https://registry.npmjs.org/pkginfo/0.2.2 npm http 304 https://registry.npmjs.org/jsonlint/1.5.1 npm http 304 https://registry.npmjs.org/xmldom/0.1.13 npm http 304 https://registry.npmjs.org/commander/0.6.1 npm http 304 https://registry.npmjs.org/wrench/1.3.9 npm http 304 https://registry.npmjs.org/stripcolorcodes/0.1.0 npm http 304 https://registry.npmjs.org/jake npm http GET https://registry.npmjs.org/minimatch npm http GET https://registry.npmjs.org/utilities npm http GET https://registry.npmjs.org/nomnom npm http GET https://registry.npmjs.org/JSV npm http 304 https://registry.npmjs.org/minimatch npm http 304 https://registry.npmjs.org/utilities npm http GET https://registry.npmjs.org/lru-cache npm http 304 https://registry.npmjs.org/nomnom npm http 304 https://registry.npmjs.org/JSV npm http GET https://registry.npmjs.org/underscore npm http GET https://registry.npmjs.org/colors npm http 304 https://registry.npmjs.org/lru-cache npm http 304 https://registry.npmjs.org/underscore npm http 304 https://registry.npmjs.org/colors /usr/local/bin/alloy -> /usr/local/lib/node_modules/alloy/bin/alloy [email protected] /usr/local/lib/node_modules/alloy ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected], [email protected]) └── [email protected] ([email protected], [email protected]) DHydeMBP:workspace dhyde$ echo $PASSWORD | sudo -S '/usr/local/bin/npm' '-g' 'install' 'titanium' 2>&1 | tee install.log npm http GET https://registry.npmjs.org/titanium npm http 304 https://registry.npmjs.org/titanium npm http GET https://registry.npmjs.org/colors npm http GET https://registry.npmjs.org/async npm http GET https://registry.npmjs.org/longjohn npm http GET https://registry.npmjs.org/node-appc npm http GET https://registry.npmjs.org/temp/0.4.0 npm http GET https://registry.npmjs.org/prompt npm http GET https://registry.npmjs.org/semver npm http GET https://registry.npmjs.org/wrench npm http GET https://registry.npmjs.org/request npm http GET https://registry.npmjs.org/winston npm http GET https://registry.npmjs.org/revalidator npm http GET https://registry.npmjs.org/sprintf npm http 304 https://registry.npmjs.org/colors npm http 304 https://registry.npmjs.org/async npm http 304 https://registry.npmjs.org/longjohn npm http 304 https://registry.npmjs.org/node-appc npm http 304 https://registry.npmjs.org/temp/0.4.0 npm http 304 https://registry.npmjs.org/prompt npm http 304 https://registry.npmjs.org/semver npm http 304 https://registry.npmjs.org/wrench npm http 304 https://registry.npmjs.org/request npm http 304 https://registry.npmjs.org/winston npm http 304 https://registry.npmjs.org/sprintf npm http 200 https://registry.npmjs.org/revalidator npm http GET https://registry.npmjs.org/revalidator/-/revalidator-0.1.3.tgz npm http 200 https://registry.npmjs.org/revalidator/-/revalidator-0.1.3.tgz npm http GET https://registry.npmjs.org/read npm http GET https://registry.npmjs.org/utile npm http GET https://registry.npmjs.org/pkginfo npm http GET https://registry.npmjs.org/cycle npm http GET https://registry.npmjs.org/eyes npm http GET https://registry.npmjs.org/pkginfo npm http GET https://registry.npmjs.org/stack-trace npm http GET https://registry.npmjs.org/node-uuid npm http GET https://registry.npmjs.org/uglify-js npm http GET https://registry.npmjs.org/xmldom/0.1.11 npm http 304 https://registry.npmjs.org/read npm http 304 https://registry.npmjs.org/utile npm http 304 https://registry.npmjs.org/pkginfo npm http 304 https://registry.npmjs.org/cycle npm http 304 https://registry.npmjs.org/eyes npm http 304 https://registry.npmjs.org/pkginfo npm http 304 https://registry.npmjs.org/stack-trace npm WARN package.json [email protected] No README.md file found! npm http 304 https://registry.npmjs.org/uglify-js npm http 304 https://registry.npmjs.org/xmldom/0.1.11 npm http GET https://registry.npmjs.org/mute-stream npm http GET https://registry.npmjs.org/deep-equal npm http GET https://registry.npmjs.org/rimraf npm http GET https://registry.npmjs.org/i npm http GET https://registry.npmjs.org/mkdirp npm http GET https://registry.npmjs.org/ncp npm http 200 https://registry.npmjs.org/node-uuid npm http 304 https://registry.npmjs.org/mkdirp npm http 304 https://registry.npmjs.org/ncp npm http 304 https://registry.npmjs.org/mute-stream npm http 304 https://registry.npmjs.org/deep-equal npm http 304 https://registry.npmjs.org/rimraf npm http 304 https://registry.npmjs.org/i /usr/local/bin/titanium -> /usr/local/lib/node_modules/titanium/bin/titanium [email protected] /usr/local/lib/node_modules/titanium ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ├── [email protected] ([email protected], [email protected], [email protected], [email protected]) ├── [email protected] ([email protected], [email protected], [email protected]) └── [email protected] ([email protected], [email protected], [email protected]) DHydeMBP:workspace dhyde$ read -s PASSWORD DHydeMBP:workspace dhyde$ {code} Steps to Reproduce: 1. Uninstall cli, alloy, and acs. 2. Load studio and enter user password on prompt. Actual Result: Everything is installed, not just the prompted update. Expected Result: Each update is installed one by one, and user enters password for each.
| 5 |
train
|
TISTUD-2563
|
Add extension point for contributing programmatic project templates
|
Currently we "hack" in support for alloy templates by registering templates programmatically during an IStartup. We really should have a way to register templates using some extension point so that they get loaded on-demand when we gather up templates. Using an IStartup is hacky and forces the alloy UI plugin to load on startup even if never used.
| 8 |
train
|
TISTUD-2564
|
TiStudio: Project - If you create the default Titanium project, then the ti.cloud module will not appear in the tiapp.xml
|
Details: After creating the default Titanium app, the ti.cloud module does not appear in the tiapp.xml even though the ACS server is returning the 200 success in the log. The issue still appears with SDK 2.1.3 \\ \\ Steps to reproduce: 1. Open TiStudio and create the default Titanium app \\ \\ Actual: ti.cloud module does not appear in the tiapp.xml (see tiapp.png) and ACS is not enabled for app even though 200 success code is returned (see studio_log.txt). \\ \\ But, if I try to *Enable Cloud Services* again, I get the 400 error code (see error.png) \\ \\ Expected: After creating the default app, you should be able to see the ti.cloud module in tiapp.
| 8 |
train
|
TISTUD-2565
|
Portal Module info call needs to return module guids
|
The appdirect call to return the module updates info now contains module guids so we can map the modules to the installed modules. Unfortunately the current portal call to retrieve module info does not contain guids. The call needs to return multiple guids for modules with both iOS and android components, since the guids may differ in those instances.
| 8 |
train
|
TISTUD-2569
|
Alloy templates do not show up after alloy is installed until Studio restarts
|
Steps to reproduce: 1. Uninstall alloy (sudo npm uninstall -g alloy); 2. Start Studio and allow it to install alloy; 3. Open File > New > Titanium Project. Expected result: alloy templates should appear. Actual result: no alloy templates appear. Workaround: restarting Studio and then repeat step 3 would see alloy templates.
| 3 |
train
|
TISTUD-2570
|
Installer: full installer links should always have content
|
http://preview.appcelerator.com/studio/ full installers for mac and windows are dead: http://preview.appcelerator.com/appcelerator/studio/standalone/install/rc/Titanium_Studio.exe {code} Not Found The requested URL /appcelerator/studio/standalone/install/rc/Titanium_Studio.exe was not found on this server. {code} http://preview.appcelerator.com/appcelerator/studio/standalone/install/rc/Titanium_Studio.dmg {code} Not Found The requested URL /appcelerator/studio/standalone/install/rc/Titanium_Studio.dmg was not found on this server. {code} Steps to Reproduce: 1. Go to http://preview.appcelerator.com/studio/ 2. Download the full installers for Windows 7 and OSX. Actual Result: Dead links. Expected Result: Alive links.
| 8 |
train
|
TISTUD-2573
|
Studio should not ask for password when updating Titanium SDK
|
This is a regression. Steps to reproduce: 1. Remove 2.1.3 SDK from the Titanium SDK folder; 2. Run Help > Check for Titanium Updates; 3. If there are other updates (CLI/Alloy/ACS) shown in the dialog, uncheck them to leave only Titanium SDK checked; 4. Click Install. Expected result: Studio should install SDK without prompting for password. Actual result: the Authentication dialog appear for password.
| 3 |
train
|
TISTUD-2575
|
Use same sudo prompt UI for Node and npm packages
|
On a clean install we get prompted to install Node. After accepting we get a sudo prompt from cocoasudo. After that finishes we then get a prompt to install acs using a different prompt UI (but again for sudo password). We should have a consistent UI for prompting the sudo password. Additionally, since less than my sudo password expiration time passed between the two, hopefully I wouldn't even get prompted (for my password, but maybe for acceptance) the second time.
| 5 |
train
|
TISTUD-2576
|
Unify the handling of installing and updating processes
|
Our handling of installing requirements are pretty inconsistent. We have the Titanium SDK Updater which checks on startup for updates to Titanium SDK, titanium CLI, alloy, and acs. But we also have separate IStartup checks for acs and alloy. Additionally our check for Node is done entirely separately. Ideally we'd have the check for updates _always_ run regardless of prefs. And we should have the notion of required installs versus optional (so user can ignore updates that aren't required, but must install/update required things).
| 13 |
train
|
TISTUD-2577
|
Troubleshooting: add select and deselect all to debug specific component
|
Troubleshooting: add select and deselect all to debug specific component checkboxes
| 5 |
train
|
TISTUD-2578
|
System Password Prompt: add parity with native password prompt
|
System Password Prompt: add parity with native password prompt. The native prompt allows the user to enter a different user name. It's not clear to the user if this is a system prompt. Steps to Reproduce: 1. Uninstall the CLI. 2. Restart studio. Actual Result: Prompt appears, is different than system prompt. Expected Result: Clearly defined system prompt similar to os prompt.
| 13 |
train
|
TISTUD-2582
|
First Launch : After installing the 32-bit zip on Ubuntu 12.04, when launching for the first time I received an error opening dashboard
|
Steps to reproduce: 1. I downloaded and installed the 32-bit zip version of Ti Studio 2. I then logged in and upon login, an error dialog was presented. Actual result: *See screenshots* Expected result: Ti Studio launches normally
| 5 |
train
|
TISTUD-2587
|
Updates: prevent incomplete updates from occurring
|
When I updated the RC stream, I received an incomplete update. As per Ingo: It's just a rsync Basically, I would have it rsync everything but the content.jar file (or whatever that file is now), and then do a separate script to just do that one. Error: {code} An error occurred while collecting items to be installed session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Artifact not found: osgi.bundle,com.appcelerator.titanium.alloy.core,2.2.0.201210181648. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.alloy.core_2.2.0.201210181648.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.alloy.ui,2.2.0.201210181648. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.alloy.ui_2.2.0.201210181648.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.core,2.2.0.1350579241. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.core_2.2.0.1350579241.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.mobile,1.0.0.1350601983. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.mobile_1.0.0.1350601983.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.nodejs.core,1.0.0.1350601983. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.nodejs.core_1.0.0.1350601983.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.rcp,3.0.0.201210181724. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.rcp_3.0.0.201210181724.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.rcp.studio,1.0.0.201210181724. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.rcp.studio_1.0.0.201210181724.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.studio.rcp.override,1.0.0.201210181724. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.studio.rcp.override_1.0.0.201210181724.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.ui,1.1.0.1350584625. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.ui_1.1.0.1350584625.jar Artifact not found: osgi.bundle,com.appcelerator.titanium.update,2.1.1.1350601983. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.appcelerator.titanium.update_2.1.1.1350601983.jar Artifact not found: osgi.bundle,com.aptana.core,3.3.0.1350601913. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.aptana.core_3.3.0.1350601913.jar Artifact not found: osgi.bundle,com.aptana.projects,3.0.0.1350595577. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.aptana.projects_3.0.0.1350595577.jar Artifact not found: osgi.bundle,com.aptana.usage,3.0.0.1350601913. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/plugins/com.aptana.usage_3.0.0.1350601913.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.acs.feature,3.0.0.201210181647-3--59D39CEDB5. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.acs.feature_3.0.0.201210181647-3--59D39CEDB5.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.alloy.feature,3.0.0.201210181648-53-77357535J5FBJ. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.alloy.feature_3.0.0.201210181648-53-77357535J5FBJ.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.feature,3.0.0.1350601983-7M7G-7SOZPXKOA_nP0ZwxQG7ILQJ. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.feature_3.0.0.1350601983-7M7G-7SOZPXKOA_nP0ZwxQG7ILQJ.jar Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.feature.rcp,3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.feature.rcp_3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz.jar Artifact not found: binary,com.appcelerator.titanium.feature.rcp_root,3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/binary/com.appcelerator.titanium.feature.rcp_root_3.0.0.201210181724-7m7fFDBFFdIwz-fbpjUw_kLuKObz Artifact not found: binary,com.appcelerator.titanium.rcp.product.root.feature_root,3.0.0.201210181724-18102012172652. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/binary/com.appcelerator.titanium.rcp.product.root.feature_root_3.0.0.201210181724-18102012172652 Artifact not found: binary,com.appcelerator.titanium.rcp.product_root.cocoa.macosx.x86,3.0.0.201210181724-18102012172652. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/binary/com.appcelerator.titanium.rcp.product_root.cocoa.macosx.x86_3.0.0.201210181724-18102012172652 Artifact not found: org.eclipse.update.feature,com.appcelerator.titanium.studio,3.0.0.1350601983-7N7717oKYgjBpqpV. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.appcelerator.titanium.studio_3.0.0.1350601983-7N7717oKYgjBpqpV.jar Artifact not found: org.eclipse.update.feature,com.aptana.feature,3.3.0.1350601913-BP7P8IBeaqBuJCM6s1DC44EXt-dS. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.aptana.feature_3.3.0.1350601913-BP7P8IBeaqBuJCM6s1DC44EXt-dS.jar Artifact not found: org.eclipse.update.feature,com.aptana.php.feature,3.3.0.201210181636-7J7E-7IOTVbd_UIT. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/com.aptana.php.feature_3.3.0.201210181636-7J7E-7IOTVbd_UIT.jar Artifact not found: org.eclipse.update.feature,org.radrails.rails,3.3.0.201210181635-7e-7Q7f5CZXYCHUY. http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/features/org.radrails.rails_3.3.0.201210181635-7e-7Q7f5CZXYCHUY.jar {code}
| 13 |
train
|
TISTUD-2590
|
Progress view appears on the right instead of at the bottom in simple Studio perspective
|
When in simple Studio perspective, clicking on the progress indicator in the status bar opens Progress view to the right of the editor area, instead of below the editor area like the extended Studio perspective has. We should set the placeholder for the views in the simple perspective.
| 5 |
train
|
TISTUD-2591
|
Webserver core plugin starting too slowly
|
After updating from Studio 2.1.2 to the latest 3.0.0 RC, I saw the following exception in the log after restart: {code} !ENTRY org.eclipse.osgi 2 0 2012-10-20 18:30:17.474 !MESSAGE While loading class "com.aptana.webserver.core.IServerManager", thread "Thread[Worker-13,5,main]" timed out waiting (5001ms) for thread "Thread[Worker-10,5,main]" to finish starting bundle "com.aptana.webserver.core_3.0.0.1347887896 [400]". To avoid deadlock, thread "Thread[Worker-13,5,main]" is proceeding but "com.aptana.webserver.core.IServerManager" may not be fully initialized. !STACK 0 org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/com.aptana.webserver.core_3.0.0.1347887896.jar" by thread "Worker-10". org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.acs.core.ACSCorePlugin$ACCSInitializer.run(ACSCorePlugin.java:170) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException ... 16 more Root exception: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1087) org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:297) org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:463) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) java.lang.ClassLoader.loadClass(ClassLoader.java:247) com.appcelerator.titanium.acs.core.ACSCorePlugin$ACCSInitializer.run(ACSCorePlugin.java:170) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 5 |
train
|
TISTUD-2592
|
Creating a Node.ACS project with a name that's already published produces error
|
Steps to reproduce: 1. Create a Node.ACS project; 2. Create a Node.ACS method in the project; 3. Deploy the app; 4. Delete the project; 5. Repeat Step 1. This produces an error popup shown in the screenshot and the following entry in the Studio log: {code} !SUBENTRY 1 com.aptana.projects 4 0 2012-10-20 19:34:42.524 !MESSAGE !STACK 0 java.lang.reflect.InvocationTargetException com.appcelerator.titanium.acs.internal.ui.wizards.NewNodeACSProjectWizard.createNewProject(NewNodeACSProjectWizard.java:187) com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326) com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: org.eclipse.core.commands.ExecutionException: ... 6 more Root exception: org.eclipse.core.commands.ExecutionException: com.appcelerator.titanium.acs.internal.ui.wizards.NewNodeACSProjectWizard.createNewProject(NewNodeACSProjectWizard.java:187) com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326) com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code}
| 8 |
train
|
TISTUD-2593
|
Unused NLS messages in the log after starting Studio
|
Seeing the following in the log on Linux: {code} SESSION 2012-10-20 20:42:16.068 ----------------------------------------------- eclipse.buildId=3.0.0.201210200240 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.102 !MESSAGE NLS unused message: <<<<<<< in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: ACCSStartup_Install_Nettle_Job in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: ACCSStartup_Login_ACCS_Task in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: in: com.appcelerator.titanium.acs.internal.ui.messages !ENTRY org.eclipse.osgi 2 1 2012-10-20 20:42:37.111 !MESSAGE NLS unused message: >>>>>>> in: com.appcelerator.titanium.acs.internal.ui.messages {code} Look like a merge conflict that wasn't resolved.
| 3 |
train
|
TISTUD-2594
|
After Update, An exception occurred in the script. Error name: Type Error
|
After updating to the latest version, I get the following error from the dashboard: "An exception occurred in the script. Error name: Type Error. Error description: Object doesn't support this property or method. Error number: -2146827850. Error message: Object doesn't support this property or method" Log file shows: {code} !ENTRY com.aptana.portal.ui 4 0 2012-10-21 10:17:58.740 !MESSAGE (Build 2.1.2.201208301612) [ERROR] wrong number of arguments !STACK 0 java.lang.IllegalArgumentException: wrong number of arguments sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) com.aptana.portal.ui.dispatch.actionControllers.AbstractActionController.invokeAction(AbstractActionController.java:101) com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.dispatch(DispatcherBrowserFunction.java:137) com.aptana.portal.ui.dispatch.browserFunctions.DispatcherBrowserFunction.function(DispatcherBrowserFunction.java:121) com.aptana.portal.ui.internal.BrowserWrapper$2.function(BrowserWrapper.java:51) org.eclipse.swt.browser.WebSite.Invoke(WebSite.java:773) org.eclipse.swt.browser.WebSite$7.method6(WebSite.java:129) org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119) org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) com.aptana.git.ui.GitUIPlugin$GitInstallationValidatorJob.runInUIThread(GitUIPlugin.java:181) org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code}
| 8 |
train
|
TISTUD-2599
|
Remove "Aptana" from header of Titanium update stream index pages
|
The Titanium Studio update streams have "Aptana" in the header of the page leading to confusion. It should be replaced with "Appcelerator" * http://preview.appcelerator.com/appcelerator/studio/standalone/update/stable/ * http://preview.appcelerator.com/appcelerator/studio/standalone/update/rc/ * http://preview.appcelerator.com/appcelerator/studio/standalone/update/beta/ * http://preview.appcelerator.com/appcelerator/studio/standalone/update/nightly/
| 8 |
train
|
TISTUD-2600
|
Add more space above "Enable Cloud" checkbox
|
This seems more an issue on Windows, but the text and the checkbox in the "Enable Cloud" section of the new project wizard are extremely close. There should be some vertical space there.
| 2 |
train
|
TISTUD-2602
|
Indent the checkbox for the new CLI in the preference page
|
The rest of the checkboxes align with the fields. This label and checkbox should sit underneath the path field
| 2 |
train
|
TISTUD-2603
|
Only display the "Install JDT" link when making an Android module
|
When creating a new Android module, if you do not have the JDT tools installed, Studio will ask you to install them. However, it should only display this link _when_ you have selected the Android radio button. I think I would also put it on the same link as the "Configure SDKs" link, perhaps separated by a pipe (|)
| 3 |
train
|
TISTUD-2604
|
Windows requirements check for JDK keeps on asking to install JDK
|
(from Ingo) I'm noticing some weird behavior where I do the JDK and Android install, and then it acts as if it didn't work-still showing me the '?' Over the android and re-prompting to download the JDK. Once I restart, it goes away.
| 5 |
train
|
TISTUD-2605
|
Titanium Updates on Linux: the installation is shown to be successful although it failed
|
This issue is specific on Ubuntu 12.04. If the user updates (Help > Titanium Updates) CLI, Alloy, and ACS, none of the updates are recognized as being installed, and the user is still prompted for updates, even after studio restart. Steps to Reproduce: 1. Help > Check for Titanium Updates and take all updates (CLI, Alloy, ACS). 2. Check again. Actual Result: Updates are still available, though they were already installed. Expected Result: No updates available, they were already installed.
| 8 |
train
|
TISTUD-2606
|
Studio: "Computing SDK Info" problem appears in Windows 7 on restarting Studio
|
Steps To Reproduce: 1. Update studio to latest 3.0 version. 2. Now after accepting all prompts restart studio. Actual: "Computing SDK Info" or 'o while seeking ' exception appears. kindly refer Screenshot and log file. Expected: No error should appear.
| 3 |
train
|
TISTUD-2607
|
Alloy: "java.lang.reflect.InvocationTargetException" internal error appears on windows 7
|
Steps To Reproduce: 1. On 3.0 latest version studio, try creating Alloy Default Project. Actual: "java.lang.reflect.InvocationTargetException" internal error appears on windows 7. Kindly refer screenshot and logs. Expected: No error must appear.
| 5 |
train
|
TISTUD-2612
|
Clicking Titanium Update toast while 'titanium' cli is being installed in Terminal hangs Studio
|
I started up Titanium Studio with Node.JS installed. On startup, it began installing 'titanium' CLI automatically in a Terminal view (off to the right, rather than along to bottom right like a console). While it was running, the Titanium SDK Update toast popped up. I clicked it. It hangs the IDE for around a minute. It looks like it's frozen for good, but I think it may continue once the installs are done in the Terminal (though that stops updating too).
| 5 |
train
|
TISTUD-2614
|
Node.ACS: Unpublish Node.ACS Service does not remove service from production
|
Node.ACS: Unpublish Node.ACS Service does not remove service from production. Log: {code} !ENTRY com.aptana.core 1 0 2012-10-22 15:31:51.779 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "unpublish" "Node.ACS" "-v" "0.1.0" "--no-banner" "--no-colors" Working directory: /Users/dhyde/Desktop/TISTUD-RC/workspace/Node.ACS 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-EeKGAL/Render, Apple_Ubiquity_Message=/tmp/launch-SW45KT/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-9CZqFn/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/Node.ACS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-0sLjqp/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. Publish > Deploy App. 3. Publish > Unpublish Node.ACS Service. 4. Publish > View Node.ACS Service or reenter weblink to service. Actual Result: Link is still there, app is still in production. Expected Result: Should be unable to view app service or enter website, link should be dead.
| 3 |
train
|
TISTUD-2615
|
Node ACS success URL says "OK"
|
After publishing a Node.ACS to the server I get a confirmation which normally has the URL where the service is located. Instead I get an OK link that does not lead anywhere. This is a regression as this functionality worked in 3.0.0. Steps to reproduce: 1. Create a Node.acs service (attached to a project or on its own) 2. Publish it to the servers. Expected result: The confirmation should give you the url the service is located at. Actual result: See Screenshot.
| 3 |
train
|
TISTUD-2616
|
Studio Dashboard: "default" and "Default Project" does not give clear information about Alloy and Project unless description is read.
|
Steps To Reproduce: 1. On dashboard on studio 3.0, navigate to Develop tab. 2. Notice "default" and "Default Project" & "two-tabbed" and "Tabbed Application" names. Actual: User does not get clear information from names that one is alloy project and another one is Titanium project unless he reads the description below. Expected: Naming convention or icon corresponding must suggest type of Project.
| 8 |
train
|
TISTUD-2620
|
Mobile Web: After successful packaging of mobile web project , the alert goes away very quickly and hence user sometimes doesn't know that packaging has done.
|
This defect is specific to Ubuntu 12.04. Steps to reproduce: 1.Launch Titanium Studio. 2. Create a titanium project. 3.Create a mobile web module. 4.Package that module in the project. 5. After packaging the module , package the mobile web project and save it to a desired location. 6.Observe the notification for "successful packaging" Actual Result: The duration for successful packaging prompt for mobile web project is too short to relise the user that the process has been completed.
| 5 |
train
|
TISTUD-2621
|
About box shows "%product.name" instead of correct text for non-English versions of Studio
|
If a user is _not_ using English as the default language, they will see an issue whereby Studio is not properly replacing the About Box text and the names in the menu. h3. Steps to reproduce: # Edit your Studio configuration file (TitaniumStudio.ini, see http://docs.appcelerator.com/titanium/2.1/index.html#!/guide/Adding_Command-Line_Options) # add the option -nl pt_PT, i.e.:\\ {code} -startup ../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.1.101.v20120109-1504 -nl pt_PT --launcher.XXMaxPermSize 256m {code} # Save the file # Start Studio. You will notice a few odd things, as shown in the screenshots ## The menu bar says %productName ## The %productName menu also has some missing replacements ## The help menu shows "Aptana" not "Titanium" ## The about box is wrong h3. Workaround Instead of using -nl pt_PT above, use -nl en
| 8 |
train
|
TISTUD-2622
|
If About Box text is not properly replaced, Studio reports build # as "null"
|
If a user is _not_ using English as the default language, they will see an issue whereby Studio is not properly replacing the About Box text and the names in the menu. It then reports the build as "null" in the log file. h3. Steps to reproduce: # Edit your Studio configuration file (TitaniumStudio.ini, see http://docs.appcelerator.com/titanium/2.1/index.html#!/guide/Adding_Command-Line_Options) # add the option -nl pt_PT, i.e.:\\ {code} -startup ../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.1.101.v20120109-1504 -nl pt_PT --launcher.XXMaxPermSize 256m {code} # Save the file # Start Studio. You will notice a few odd things ## The menu bar says %productName ## The log file will have things like (Build null) ## You won't be prompted for the newest versions of the SDK--you'll get 1.7.5 as the latest. Sample log file: {code}!ENTRY com.aptana.core 1 0 2012-10-23 06:13:05.830 !MESSAGE (Build null) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/bin/git" "symbolic-ref" "-q" "HEAD" Working directory: /Users/ingo/Documents/Projects/Aptana/KitchenSinkOld Environment: null {code} h3. Workaround Instead of using -nl pt_PT above, use -nl en
| 5 |
train
|
TISTUD-2625
|
Node.ACS: space in project name causes Errors running builder 'Studio Unified Builder' on project java.lang.IllegalArgumentException
|
Creating Node.ACS project fails with: Error: {code} Errors occurred during the build. Errors running builder 'Studio Unified Builder' on project 'Node.ACS Project 1044'. java.lang.IllegalArgumentException {code} log: {code} !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.526 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/local/bin/acs" "new" "Node.ACS Project 1044" "--no-banner" "--no-colors" Working directory: /Users/dhyde/Desktop/TISTUD-RC/workspace 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-EeKGAL/Render, Apple_Ubiquity_Message=/tmp/launch-SW45KT/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, COM_GOOGLE_CHROME_FRAMEWORK_SERVICE_PROCESS/USERS/DHYDE/LIBRARY/APPLICATION_SUPPORT/GOOGLE/CHROME_SOCKET=/tmp/launch-9CZqFn/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, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-0sLjqp/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.aptana.core 1 0 2012-10-23 10:44:30.850 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Searching for git in PATH locations: /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 !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.851 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/bin/git" "--version" Working directory: null Environment: null !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.894 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Found executable on PATH: /usr/bin/git !ENTRY com.aptana.core 1 0 2012-10-23 10:44:30.895 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process: Process: "/usr/bin/git" "rev-parse" "--git-dir" Working directory: /Users/dhyde/Desktop/TISTUD-RC/workspace/Node.ACS Project 1044 Environment: null !ENTRY com.aptana.editor.common 1 0 2012-10-23 10:44:31.235 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.editor.common/debug/presentation Initiating presentation reconciling for region at offset 0, length 590 in document of length 590 !ENTRY com.aptana.portal.ui 1 0 2012-10-23 10:44:31.284 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.portal.ui/debug/startpage Notifying the portal with: if (typeof(eventsDispatcher) !== undefined) eventsDispatcher.notify('{"event":"recentFiles","eventType":"changed","data":""}'); !ENTRY com.aptana.core 1 0 2012-10-23 10:44:31.300 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/firefox Check location /Users/dhyde/Library/Application Support/Firefox/ for default profile !ENTRY com.aptana.core 1 0 2012-10-23 10:44:31.303 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/firefox Profiles found: /Users/dhyde/Library/Application Support/Firefox/Profiles/kc9gfhqn.default !ENTRY com.aptana.core 1 0 2012-10-23 10:44:31.303 !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/firefox Default profile was found at /Users/dhyde/Library/Application Support/Firefox/Profiles/kc9gfhqn.default !ENTRY org.eclipse.core.resources 4 2 2012-10-23 10:44:31.322 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.IllegalArgumentException java.net.URI.create(URI.java:841) java.net.URI.resolve(URI.java:1027) com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.determineMainFileURI(ACSCompileParticipant.java:211) com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.buildFile(ACSCompileParticipant.java:88) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:525) com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:436) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:413) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:307) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.net.URISyntaxException: Illegal character in path at index 10: ./Node.ACS Project 1044.js java.net.URI$Parser.fail(URI.java:2810) java.net.URI$Parser.checkChars(URI.java:2983) java.net.URI$Parser.parseHierarchical(URI.java:3067) java.net.URI$Parser.parse(URI.java:3025) java.net.URI.<init>(URI.java:577) java.net.URI.create(URI.java:839) ... 21 more !ENTRY org.eclipse.core.resources 4 75 2012-10-23 10:44:31.345 !MESSAGE Errors occurred during the build. !SUBENTRY 1 com.aptana.buildpath.core 4 75 2012-10-23 10:44:31.345 !MESSAGE Errors running builder 'Studio Unified Builder' on project 'Node.ACS Project 1044'. !STACK 0 java.lang.IllegalArgumentException java.net.URI.create(URI.java:841) java.net.URI.resolve(URI.java:1027) com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.determineMainFileURI(ACSCompileParticipant.java:211) com.appcelerator.titanium.acs.internal.core.ACSCompileParticipant.buildFile(ACSCompileParticipant.java:88) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.core.build.UnifiedBuilder.buildFile(UnifiedBuilder.java:525) com.aptana.core.build.UnifiedBuilder.doBuildFiles(UnifiedBuilder.java:436) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:413) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:307) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.net.URISyntaxException: Illegal character in path at index 10: ./Node.ACS Project 1044.js java.net.URI$Parser.fail(URI.java:2810) java.net.URI$Parser.checkChars(URI.java:2983) java.net.URI$Parser.parseHierarchical(URI.java:3067) java.net.URI$Parser.parse(URI.java:3025) java.net.URI.<init>(URI.java:577) java.net.URI.create(URI.java:839) ... 21 more {code} Steps to Reproduce: 1. Create Node.ACS project. Actual Result: Fail. Expected Result: Success.
| 5 |
train
|
TISTUD-2626
|
Dashboard: Alloy templates should appear first in Templates section
|
Add a new section on the bottom, call it Alloy Templates, put the alloy templates there. The current UI is incomplete.
| 8 |
train
|
TISTUD-2629
|
TiStudio: node.ACS - Tail log is using -v to specify node.ACS app version instead of -a
|
Steps to reproduce: 1. In TiStudio, create a node.ACS project 2. Publish the project 3. Right-click on the project and go to Node.ACS > Tail Logs > 0.1.0 \\ \\ Actual: Terminal console would return the following: {code} acs logcat monkeyNode -v 0.1.0 0.9.24 {code} \\ \\ Expected: Instead of -v to specify app version, -a should be used instead: {code} $ acs logcat -h Function: Tail the log entries output from your app. If no appname provided it can run in project dir or with -d to specify a project dir. 'logcat -h' for more options. Usage: logcat [options] [appname] Options: -h, --help output usage information -a, --appversion <version> App version --interval <interval> Set refresh inteval for logcat {code} \\ \\ Note: To work around this, use *acs logcat -a <APP_VERSION>*
| 2 |
train
|
TISTUD-2630
|
Preferences: closing titanium preferences before android sdk list loads throws exception
|
Preferences: closing titanium preferences before android sdk list loads throws exception. Error: {code} An internal error has occurred. java.lang.NullPointerException {code} Steps to Reproduce: 1. Open Titanium Studio > Titanium preferences. 2. When android sdk is still loading in the sdk list, close preferences window. Actual Result: Error. Expected Result: Window closes without error.
| 5 |
train
|
TISTUD-2632
|
Editing and saving tiapp.xml while project is indexing hangs Studio
|
Importing KitchenSink, changing the sdk version, and saving the change in tiapp.xml while the project is indexing results in save failure. Studio hangs during this scenario. Core exceptions in log, out of sync. Could be related to TISTUD-2490. Steps to Reproduce: 1. Import KitchenSink from the samples. 2. change the sdk version in tiapp.xml and save. Actual Result: Fail to save. Expected Result: Save.
| 8 |
train
|
TISTUD-2633
|
Studio: Ubuntu- Node permission dialogs for acs and alloy install are transparent.
|
While testing the dev preview on Linux, I was prompted for permission to install acs, CLI, and alloy. Each had a window in a window with a transparent background. See images attached. Steps to reproduce: 1) Install the dev preview studio version 2) If not prompted, click "check for titanium updates" Result: Window appears for each permission request with transparent background. Expected: Beautiful dialogs
| 5 |
train
|
TISTUD-2634
|
Studio: Ubuntu- npm install displays some odd characters during install
|
While testing the dev preview, during the npm installs, the dialog displays many odd things that seem to correlate to the console output you would see when running from the command-line. During one of the installs, as the attached image shows, some odd characters are displayed. Steps to reproduce: 1) Install studio dev preview version 2) Check for titanium updates 3) Grant permission for install 4) watch progress Result: Odd characters shown Expected: No odd characters.
| 5 |
train
|
TISTUD-2636
|
Windows 7 Installer takes 10 seconds to load
|
Running titaniumstudio.exe installer takes 10 seconds to launch with no ui action.
| 5 |
train
|
TISTUD-2643
|
Android Distribution Wizard: android sdk preferences not respected
|
Android Distribution Wizard: android sdk preferences not respected, lists other android sdk. The android sdk preferences are correct, and the run configuration menu for packaging is correct, but the package > distribute android wizard lists the wrong android sdk. This is a regression. Does not occur in Studio 2.1.2. Steps to Reproduce: 1. Set Android SDK in preferences. 2. Clear existing distribution run configurations. 3. Packaging > Android Distribution. Actual Result: Wizard lists different android sdk than in the preferences, or what would appear if a new distribution run config were created. Expected Result: Android Publishing wizard android sdk should match preferences and new distribution run config entry.
| 5 |
train
|
TISTUD-2644
|
Node.JS: node module commands in empty /usr/bin/ folders are falsely detected by studio
|
Node.JS: node module commands in empty /usr/bin/ folders are falsely detected by studio. Manifests as null pointer exception when creating alloy project, etc. Note that npm is usually installed in /usr/local/bin Log: {code} !ENTRY com.aptana.core 1 0 2012-10-24 17:30:12.917\ !MESSAGE (Build 3.0.0.201210220122) [INFO] com.aptana.core/debug/shell Running process:\ Process: "/usr/bin/alloy" "new" "/Users/gtavridis/Documents/Titanium Studio Workspace/testapp5" "default"\ Working directory: null\ Environment: \{ANALYTICS_SOURCE=studio, APTANA_VERSION=3.0.0.1346448223, Apple_PubSub_Socket_Render=/tmp/launch-pwIDrd/Render, Apple_Ubiquity_Message=/tmp/launch-iPVDau/Apple_Ubiquity_Message, COMMAND_MODE=unix2003, DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer, DISPLAY=/tmp/launch-Kdr69A/org.x:0, HOME=/Users/gtavridis, JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home, LANG=en_US.UTF-8, LOGNAME=gtavridis, PATH=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin, PWD=/Applications/Titanium_Studio/TitaniumStudio.app/Contents/MacOS, SHELL=/bin/bash, SHLVL=1, SSH_AUTH_SOCK=/tmp/launch-D3IT5p/Listeners, TMPDIR=/var/folders/6g/7gkd364s4bd3_rq7891qgt000000gp/T/, USER=gtavridis, __CF_USER_TEXT_ENCODING=0x1F6:0:0, com.apple.java.jvmMode=client, com.apple.java.jvmTask=JNI\}\ \ !ENTRY com.aptana.projects 2 0 2012-10-24 17:30:40.252\ !MESSAGE Internal error: \ !STACK 1\ org.eclipse.core.runtime.CoreException: \ com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:253)\ org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)\ org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)\ com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304)\ org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)\ Caused by: java.lang.reflect.InvocationTargetException\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:310)\ com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249)\ ... 4 more\ Caused by: org.eclipse.core.runtime.CoreException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:344)\ com.appcelerator.titanium.mobile.ui.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:118)\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:306)\ ... 5 more\ Caused by: java.io.IOException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ java.lang.ProcessBuilder.start(ProcessBuilder.java:460)\ com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327)\ com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322)\ com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273)\ com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235)\ com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:202)\ com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:108)\ com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$AlloyTemplate.apply(AlloyTemplateInstaller.java:79)\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341)\ ... 7 more\ Caused by: java.io.IOException: error=13, Permission denied\ java.lang.UNIXProcess.forkAndExec(Native Method)\ java.lang.UNIXProcess.<init>(UNIXProcess.java:53)\ java.lang.ProcessImpl.start(ProcessImpl.java:91)\ java.lang.ProcessBuilder.start(ProcessBuilder.java:453)\ ... 15 more\ !SUBENTRY 1 com.aptana.projects 4 0 2012-10-24 17:30:40.255\ !MESSAGE \ !STACK 0\ java.lang.reflect.InvocationTargetException\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:310)\ com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249)\ org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)\ org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)\ com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304)\ org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)\ Caused by: org.eclipse.core.runtime.CoreException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:344)\ com.appcelerator.titanium.mobile.ui.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:118)\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:306)\ ... 5 more\ Caused by: java.io.IOException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ java.lang.ProcessBuilder.start(ProcessBuilder.java:460)\ com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327)\ com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322)\ com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273)\ com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235)\ com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:202)\ com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:108)\ com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$AlloyTemplate.apply(AlloyTemplateInstaller.java:79)\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341)\ ... 7 more\ Caused by: java.io.IOException: error=13, Permission denied\ java.lang.UNIXProcess.forkAndExec(Native Method)\ java.lang.UNIXProcess.<init>(UNIXProcess.java:53)\ java.lang.ProcessImpl.start(ProcessImpl.java:91)\ java.lang.ProcessBuilder.start(ProcessBuilder.java:453)\ ... 15 more\ Root exception:\ org.eclipse.core.runtime.CoreException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:344)\ com.appcelerator.titanium.mobile.ui.wizard.NewMobileProjectWizard.finalizeProjectCreation(NewMobileProjectWizard.java:118)\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.createNewProject(BasicNewTitaniumProjectWizard.java:306)\ com.aptana.projects.wizards.AbstractNewProjectWizard$1$1.run(AbstractNewProjectWizard.java:249)\ org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)\ org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)\ com.aptana.projects.wizards.AbstractNewProjectWizard$1.run(AbstractNewProjectWizard.java:304)\ org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)\ Caused by: java.io.IOException: Cannot run program "/usr/bin/alloy": error=13, Permission denied\ java.lang.ProcessBuilder.start(ProcessBuilder.java:460)\ com.aptana.core.util.ProcessUtil.startProcess(ProcessUtil.java:327)\ com.aptana.core.util.ProcessUtil.doRun(ProcessUtil.java:322)\ com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:273)\ com.aptana.core.util.ProcessUtil.run(ProcessUtil.java:235)\ com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:202)\ com.aptana.core.util.ProcessUtil.runInBackground(ProcessUtil.java:108)\ com.appcelerator.titanium.alloy.internal.ui.AlloyTemplateInstaller$AlloyTemplate.apply(AlloyTemplateInstaller.java:79)\ com.appcelerator.titanium.ui.wizard.BasicNewTitaniumProjectWizard.finalizeProjectCreation(BasicNewTitaniumProjectWizard.java:341)\ ... 7 more\ Caused by: java.io.IOException: error=13, Permission denied\ java.lang.UNIXProcess.forkAndExec(Native Method)\ java.lang.UNIXProcess.<init>(UNIXProcess.java:53)\ java.lang.ProcessImpl.start(ProcessImpl.java:91)\ java.lang.ProcessBuilder.start(ProcessBuilder.java:453)\ ... 15 more\ {code} Steps to Reproduce: 1. Create an empty folder in the following locations: "/usr/bin/alloy" "/usr/bin/npm" "/usr/bin/acs" "/usr/bin/titanium" 2. Try to run studio, create these projects, check for titanium updates, or enable the cli. Actual Result: Fail with permission error. Expected Result: Studio should ignore these false files and run existing npm packages.
| 3 |
train
|
TISTUD-2645
|
JS Content assist is only looking up members of Window for global namespace
|
When we lookup globals for Content Assist we explicitly look for members of Window. This is wrong, because we also need to look up members of it's supertype Global.
| 5 |
train
|
TISTUD-2646
|
JS Content Assist doesn't contain ECMAScript 5 types/properties
|
There are no entries for things like JSON.parse, JSON.stringify, Date.now, etc in our metadata. We need to add metadata for the new items added in ECMAScript 5. See http://kangax.github.com/es5-compat-table/ and http://www.ecma-international.org/ecma-262/5.1
| 20 |
train
|
TISTUD-2647
|
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 |
train
|
TISTUD-2650
|
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 |
train
|
TISTUD-2653
|
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 |
train
|
TISTUD-2654
|
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 |
train
|
TISTUD-2666
|
Content overlay - icon, description etc for Denso turbo brand
| null | 8 |
train
|
TISTUD-2676
|
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 |
train
|
TISTUD-2677
|
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 |
train
|
TISTUD-2678
|
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 |
train
|
TISTUD-2679
|
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 |
train
|
TISTUD-2688
|
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 |
train
|
TISTUD-2689
|
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 |
train
|
TISTUD-2694
|
Adopt AppDirect call with more module information
|
We want to utilize more information from the AppDirect call: -Module url -publish date -developer name -description -overview
| 5 |
train
|
TISTUD-2695
|
Adopt AppDirect call to compare version numbers correctly
|
We want to utilize the formatted version information from the AppDirect call The new format would be: Multiple versions: [{"name":"Admob module","productType":"MODULE","status":"ACTIVE","url":""," imageUrl":"","version": {"ios": "1.3","android: "2.0.1"} ] Single version for all platforms: [{"name":"Admob module","productType":"MODULE","status":"ACTIVE","url":""," imageUrl":"","version":"1.3"]
| 5 |
train
|
TISTUD-2696
|
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 |
train
|
TISTUD-2698
|
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 |
train
|
TISTUD-2699
|
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 |
train
|
TISTUD-2713
|
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 |
train
|
TISTUD-2714
|
Change the wizard image in Update wizard to look like an installer image
| null | 8 |
train
|
TISTUD-2715
|
Add user id field to the password sudo page in Update wizard
| null | 3 |
train
|
TISTUD-2716
|
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 |
train
|
TISTUD-2717
|
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 com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.build(IOSNodeJSCommandsHelper.java:142) com.appcelerator.titanium.mobile.cli.nodejs.IOSNodeJSCommandsHelper.installOnDevice(IOSNodeJSCommandsHelper.java:112) com.appcelerator.titanium.mobile.cli.IOSCommandsHelper.runOnDevice(IOSCommandsHelper.java:136) com.appcelerator.titanium.mobile.cli.nodejs.NodeTitaniumSDKCommandsHandler.run(NodeTitaniumSDKCommandsHandler.java:443) com.appcelerator.titanium.mobile.ui.iphone.launch.IOSDebugOnDeviceLaunchConfigurationDelegate.launch(IOSDebugOnDeviceLaunchConfigurationDelegate.java:47) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 2 |
train
|
TISTUD-2718
|
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 |
train
|
TISTUD-2720
|
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 |
train
|
TISTUD-2726
|
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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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 java.io.File.<init>(Unknown Source) com.appcelerator.titanium.mobile.SDKBuildPathContributor.getBuildPathEntries(SDKBuildPathContributor.java:38) com.aptana.buildpath.core.BuildPathManager.getDynamicBuildPaths(BuildPathManager.java:273) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:181) com.aptana.buildpath.core.BuildPathManager.getBuildPaths(BuildPathManager.java:252) com.aptana.buildpath.core.BuildPathIndexContributor.getFiles(BuildPathIndexContributor.java:47) com.aptana.core.build.UnifiedBuilder.getContributedFiles(UnifiedBuilder.java:362) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:298) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:153) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) 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.resourc...
| 5 |
train
|
TISTUD-2730
|
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 |
train
|
TISTUD-2733
|
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 |
train
|
TISTUD-2735
|
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 |
train
|
TISTUD-2739
|
Have a separate update site for Node.ACS feature
|
We want the base Titanium Studio continue to include Node.ACS feature, but have a separate update site defined for Node.ACS so it could update on its own without updating the whole Studio. We should also verify it will still work when later on we update Studio overall.
| 3 |
train
|
TISTUD-2741
|
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 |
train
|
TISTUD-2743
|
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 com.aptana.ui.wizards.WizardFolderImportPage.validate(WizardFolderImportPage.java:387) com.aptana.ui.wizards.WizardFolderImportPage$InputModifyListener.modifyText(WizardFolderImportPage.java:787) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058) org.eclipse.swt.widgets.Text.wmCommandChild(Text.java:2610) org.eclipse.swt.widgets.Control.WM_COMMAND(Control.java:4669) org.eclipse.swt.widgets.Control.windowProc(Control.java:4531) org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2425) org.eclipse.swt.widgets.Text.callWindowProc(Text.java:255) org.eclipse.swt.widgets.Control.windowProc(Control.java:4623) org.eclipse.swt.widgets.Text.windowProc(Text.java:2254) org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) org.eclipse.swt.internal.win32.OS.SetWindowTextW(Native Method) org.eclipse.swt.internal.win32.OS.SetWindowText(OS.java:3446) org.eclipse.swt.widgets.Text.setText(Text.java:1977) com.aptana.ui.wizards.WizardFolderImportPage.setProjectName(WizardFolderImportPage.java:483) com.aptana.ui.wizards.WizardFolderImportPage.createControl(WizardFolderImportPage.java:240) org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) org.eclipse.jface.window.Window.create(Window.java:431) org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) org.eclipse.jface.window.Window.open(Window.java:790) com.aptana.projects.actions.PromoteToProjectHandler.execute(PromoteToProjectHandler.java:59) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) 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 |
train
|
TISTUD-2744
|
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 |
train
|
TISTUD-2746
|
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 |
train
|
TISTUD-2748
|
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 |
train
|
TISTUD-2750
|
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 |
train
|
TISTUD-2752
|
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 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.