I am new in sencha and this my first App. I tried to create an App in sencha touch through following command
sencha -sdk /home/tanmay/amit_mob/adt-bundle-linux-x86-20140702/sdk generate app MyApp /home/tanmay/amit_mob/myapp
But I get an error
[ERR] Unable to locate supported Framework.
Please ensure this command was executed from a supported framework
directory or that a framework directory was specified via the -sdk switch.
For example:
sencha -sdk /path/to/framework-dir generate app AppName path/to/app
[ERR] com.sencha.exceptions.ExState: Not a framework directory : /home/tanmay/amit_mob/sdk/tools
at com.sencha.cli.AbstractCommand$Property.set(AbstractCommand.java:406)
at com.sencha.cli.AbstractCommand.processConfigParam(AbstractCommand.java:527)
at com.sencha.cli.AbstractCommand.configure(AbstractCommand.java:114)
at com.sencha.command.Sencha.main(Sencha.java:128)
Caused by: Not a framework directory : /home/tanmay/amit_mob/sdk/tools
at com.sencha.command.Sencha.setSdkPath(Sencha.java:361)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.sencha.cli.AbstractCommand$Property.set(AbstractCommand.java:394)
at com.sencha.cli.AbstractCommand.processConfigParam(AbstractCommand.java:527)
at com.sencha.cli.AbstractCommand.configure(AbstractCommand.java:114)
at com.sencha.command.Sencha.main(Sencha.java:128)
Please help me.
I forget to download sencha touch.If you face this problem then download sencha touch from http://www.sencha.com/products/touch/download/
and extract in any folder.
tanmay#tanmay-desk:~/amit_mob$ sencha -sdk /home/tanmay/mobile_app/touch-2.4.2 generate app MyApp /home/tanmay/amit_mob
and run above command.Change your directory please...
Hi follow the documentation
Command prompt / Terminal enter the below comments:
$ sencha -sdk /Users/dev2/Documents/Source/Sencha/touch-2.4.2 generate app MySampleApp /Users/dev2/Documents/Source/Sencha\ -\ Apps
Thanks
Not specifically for the scenario AGM had, Just in case for somebody else has this issue:
Check the 2 paths, sdk and app directroy, if they have spaces double quote the path like this:
Sencha -sdk "C:\Program Files\Sencha\Cmd\6.5.3.6" xxxxxxxxxx
Related
I have a Java web application I am developing in IntelliJ and deploying using Apache Tomcat. I have some run configurations defined that are shared between everyone on the team. These run configurations are defined to deploy an exploded war artifact into a local tomcat. Other team members are able to deploy and run just fine, but I get the following error:
Artifact Gradle : project : project.war (exploded): Error during artifact deployment. See server log for details.
Artifact Gradle : project : project.war (exploded): com.intellij.javaee.oss.admin.jmx.JmxAdminException: com.intellij.execution.ExecutionException: /IdeaProjects/project/build/libs/exploded/project.war not found for the web module.
It seems that IntelliJ doesn't want to create the exploded/project.war directories. If I create those directories manually I don't get that error message, but none of the WAR contents get placed into the directory.
I thought that it could be a permission error so I even tried giving my project directory 777 just to try to eliminate possible problems.
Has anyone ever run into this problem?
I am running MacOS 10.12, and have been able to deploy in the past, but this problem just started.
Thanks
Update
The IntelliJ log doesn't really show any additional errors, just the full StackTrace for the errors above.
2017-11-02 11:20:52,896 [3777157] INFO - erver.JavaeeServerInstanceImpl - com.intellij.execution.ExecutionException: <redacted>/build/libs/exploded/myproject.war not found for the web module.
com.intellij.javaee.oss.admin.jmx.JmxAdminException: com.intellij.execution.ExecutionException: <redacted>/build/libs/exploded/myproject.war not found for the web module.
at org.jetbrains.idea.tomcat.admin.TomcatAdminLocalServerImpl$DeployStep.perform(TomcatAdminLocalServerImpl.java:277)
at org.jetbrains.idea.tomcat.admin.TomcatAdminLocalServerImpl.doDeploy(TomcatAdminLocalServerImpl.java:125)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase$4.doPerform(JavaeeJmxAdminServerBase.java:120)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase$JmxOperation.perform(JavaeeJmxAdminServerBase.java:243)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase.doStartDeploy(JavaeeJmxAdminServerBase.java:135)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase$2.setDeploymentStatus(JavaeeJmxAdminServerBase.java:90)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase$DeploymentModelOperation.doSetDeploymentStatus(JavaeeJmxAdminServerBase.java:270)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase$3.doPerform(JavaeeJmxAdminServerBase.java:100)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase$JmxOperation.perform(JavaeeJmxAdminServerBase.java:243)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase.doStartDeployWithUndeploy(JavaeeJmxAdminServerBase.java:107)
at com.intellij.javaee.oss.admin.jmx.JavaeeJmxAdminServerBase.startDeploy(JavaeeJmxAdminServerBase.java:74)
at org.jetbrains.idea.tomcat.admin.TomcatAdminServerBase.startDeploy(TomcatAdminServerBase.java:115)
at org.jetbrains.idea.tomcat.admin.TomcatAdminLocalServerImpl.startDeploy(TomcatAdminLocalServerImpl.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.remoteServer.agent.impl.ThreadInvocationHandler.a(ThreadInvocationHandler.java:56)
at com.intellij.remoteServer.agent.impl.ThreadInvocationHandler.a(ThreadInvocationHandler.java:100)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.intellij.util.concurrency.BoundedTaskExecutor$2.run(BoundedTaskExecutor.java:212)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.intellij.execution.ExecutionException: <redacted>/build/libs/exploded/myproject.war not found for the web module.
at org.jetbrains.idea.tomcat.admin.TomcatAdminLocalServerImpl.addApplicationContext(TomcatAdminLocalServerImpl.java:217)
at org.jetbrains.idea.tomcat.admin.TomcatAdminLocalServerImpl$4.doPerform(TomcatAdminLocalServerImpl.java:121)
at org.jetbrains.idea.tomcat.admin.TomcatAdminLocalServerImpl$DeployStep.perform(TomcatAdminLocalServerImpl.java:274)
... 24 more
Before Intellij 2019.2 :
Under Gradle Settings, you have to make sure you don't have checked 'Delegate IDE build/run actions to gradle'
Since Intellij 2019.2 :
Settings is now under 'Build, Execution, Deployment > Build Tools > Gradle'.
You have to select Build and run using : Intellij IDEA
An issue has been opened on jetbrains bug tracker.
I have just installed Gradle 2.11 on a Windows 7 machine and when I run gradle -v I get a failure message. Gradle is in the path and the dll is present.
$ gradle -v --stacktrace
FAILURE: Build failed with an exception.
* What went wrong:
Failed to load native library 'native-platform.dll' for Windows 7 amd64.
* Try:
Run with --info or --debug option to get more log output.
* Exception is:
net.rubygrapefruit.platform.NativeException: Failed to load native library 'nati ve-platform.dll' for Windows 7 amd64.
at net.rubygrapefruit.platform.internal.NativeLibraryLoader.load(NativeL ibraryLoader.java:49)
at net.rubygrapefruit.platform.Native.init(Native.java:55)
at org.gradle.internal.nativeintegration.services.NativeServices.initial ize(NativeServices.java:74)
at org.gradle.internal.nativeintegration.services.NativeServices.initial ize(NativeServices.java:60)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute( CommandLineActionFactory.java:203)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute( CommandLineActionFactory.java:169)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionRep ortingAction.java:33)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionRep ortingAction.java:22)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBoots trap.java:54)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.j ava:35)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
Caused by: java.io.IOException: The system cannot find the path specified
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:1012)
at net.rubygrapefruit.platform.internal.NativeLibraryLocator.find(Native LibraryLocator.java:39)
at net.rubygrapefruit.platform.internal.NativeLibraryLoader.load(NativeL ibraryLoader.java:41)
... 16 more
This is cause by Windows configuration, probably through group policy. The file native-platform.dll is extracted from one of the JAR files, and probably placed in folder in the user home directory, such as c:\Users\%USERNAME%\Local Settings\Temp. For malware protection, loading of DLL's and execution of programs from TMP directories may be disabled.
I have a problem with the same symptoms, and I have been able to work around it in some cases by setting TEMP and TMP environment variables to point outside the user directory, such as c:\tmp. That has not been a universal solution and did not work for gradle. The location to which Gradle extracts DLL's can be overwritten by setting the GRADLE_OPTS to point to the desired location. This may work for you:
C:\ mkdir C:\tmp
C:\ set GRADLE_OPTS="-Dorg.gradle.native.dir=/tmp"
In adition, you have to put the set sentence in the gradle.bat located in the ../gradle-2.11/bin folder.
Example:
#rem Add default JVM options here. You can also use JAVA_OPTS and GRADLE_OPTS to pass JVM options to this script.
set DEFAULT_JVM_OPTS=
set DIRNAME=%~dp0
if "%DIRNAME%" == "" set DIRNAME=.
set APP_BASE_NAME=%~n0
set APP_HOME=%DIRNAME%..
#rem agregado por marcgaso
set GRADLE_OPTS="-Dorg.gradle.native.dir=/tmp"
**strong text**
Further to user6823564 solution above, I also came across this issue after cleaning my temporary files.
The cause is a missing native folder. Beats me why Gradle just doesn't restore it like any other bit of missing temporary/cached data.
Answer:
md %GRADLE_USER_HOME%\native
Which is the default location. Or use the setting given by user6823564 and Marcos... using either
set GRADLE_OPTS="-Dorg.gradle.native.dir=%GRADLE_USER_HOME%\native"
or using
%GRADLE_USER_HOME%\gradle.properties
good luck.
1.Open the projects gradle.properties file in android studio
2.Added this line at end of file org.gradle.jvmargs=-Xmx1024m & Save the file
3.Close & reopen the project
And you just need to restart the android studio and your system. This is getting just because you have no enough free space in ROM
I have a simple hybrid App for Android phones. I have a skin folder created for Android tablets. I create an HTML file under the android.tablet but if this HTML file name match the same name of the HTML file under common folder then Eclipse shows a pop up error message that says:
'Building Workspace' has encountered a problem
Errors occurred during the build.
Java.Lang.NullPointerException
I have Eclipse Kepler SR1 64bits on OS X I get same error in Eclipse Juno on Win7.
This is the exception:
Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
org.eclipse.core.runtime.CoreException: java.lang.NullPointerException
at com.worklight.studio.plugin.utils.PluginUtils.toCoreException(PluginUtils.java:138)
at com.worklight.studio.plugin.builders.PreviewResourceDeltaVisitor.visit(PreviewResourceDeltaVisitor.java:112)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at com.worklight.studio.plugin.builders.WorklightProjectBuilder.incrementalBuild(WorklightProjectBuilder.java:73)
at com.worklight.studio.plugin.builders.WorklightProjectBuilder.build(WorklightProjectBuilder.java:61)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.NullPointerException
at com.worklight.studio.plugin.builders.PreviewResourceDeltaVisitor.visit(PreviewResourceDeltaVisitor.java:78)
... 19 more
I cannot confirm this using Worklight 6.1.0:
Created new project and application, "test"
Added the Android environment
Add a skin to the Android environment, "android.skin"
Copied common\index.html to android.skin\
No pop-up
Changed the HTML a bit
Run As > Run on Worklight Server
No pop-up
Suggestions:
Try with a new workspace
Close Eclipse and follow these instructions to delete the wlBuildResources folder
I have installed the Cloudbees SDK on my Ubuntu 12.04 system following this doc. When I run bees help I get the following message :
Exception in thread "main" java.lang.NoClassDefFoundError:
com/cloudbees/sdk/boot/Launcher Caused by:
java.lang.ClassNotFoundException: com.cloudbees.sdk.boot.Launcher at
java.net.URLClassLoader$1.run(URLClassLoader.java:217) at
java.security.AccessController.doPrivileged(Native Method) at
java.net.URLClassLoader.findClass(URLClassLoader.java:205) at
java.lang.ClassLoader.loadClass(ClassLoader.java:321) at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at
java.lang.ClassLoader.loadClass(ClassLoader.java:266) Could not find
the main class: com.cloudbees.sdk.boot.Launcher. Program will exit.
It's maybe useful to note that I alredy installed an older version of the Cloudbees SDK and I started by uninstalling it by removing the installation folder and the .bees folder in my home directory.
It sounds like your bees command may be trying to launch with jars from an incorrect location. Make sure that your BEES_HOME environment variable is pointing at the same directory where there bees command/script you are running comes from.
I'm new to Cloudbees and having some difficulties getting my app deployed.
My app works in my local when using bees run. It also works when I placed it in another tomcat as Tomcat\webapps\ROOT.
In case it matters, I've added a lib:
C:\Java\cloudbees-sdk-1.3.1\biblenav\webapp\WEB-INF\lib\urlrewritefilter-4.0.3.jar
My war file is 635 KB and I'm using the free account.
I've tried to deploy using bees deploy from C:\Java\cloudbees-sdk-1.3.1\biblenav\
and I've tried to deploy the war file from the bees root dir. Both times I get the error below. I've no idea what to do about it. Can anyone help? Thanks!
C:\Java\cloudbees-sdk-1.3.1>bees app:deploy -a angelwarrior/biblenav ./biblenav/webapp/biblenav.war
Deploying application angelwarrior/biblenav (environment: ): .\biblenav\webapp\biblenav.war
........................uploaded 25%
........................uploaded 50%
........................uploaded 75%
........................upload completed
deploying application to server(s)...
Apr 25, 2013 11:25:23 PM com.cloudbees.api.BeesClient applicationDeployArchive
SEVERE: Invalid application deployment response: angelwarrior/biblenav
com.cloudbees.api.BeesClientException: Server.InternalError - java.lang.IllegalArgumentException: Platform error - {{invalid_local_plugin_dir,"/etc/genapp/plugins.d/jar"},
[{genapp_plugin,validate_plugin_dir,1},
{genapp_plugin,new,1},
{genapp_deploy,resolve_plugin,2},
{genapp_deploy,apply_stages,2},
{genapp_deploy,handle_task,1},
{e2_task,dispatch_handle_task,1},
{e2_service,dispatch_info,2},
{gen_server,handle_msg,5}]}
at com.cloudbees.api.BeesClient.readResponse(BeesClient.java:1121)
at com.cloudbees.api.BeesClient.applicationDeployArchive(BeesClient.java:638)
at com.cloudbees.sdk.commands.app.ApplicationDeploy.execute(ApplicationDeploy.java:322)
at com.cloudbees.sdk.commands.Command.run(Command.java:167)
at com.cloudbees.sdk.commands.Command.run(Command.java:80)
at com.cloudbees.sdk.Bees.run(Bees.java:117)
at com.cloudbees.sdk.Bees.main(Bees.java:308)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.cloudbees.sdk.boot.Launcher.main(Launcher.java:35)
That's an unfortunately obfuscated error message, but based on on the details, it looks like you attempted to deploy the app at some point using a "-t jar" flag. This sets your runtime stack to "jar", which isn't a known stack...which led to this downstream error.
You can see a list of valid stack names to use with that -t STACK flag in the CloudBees ClickStack docs.
In your case, it sounds like you'd like to run the deployed app package with Tomcat, so you probably want one of the following commands:
For Tomcat 6:
bees app:deploy -t tomcat -a APPID WAR_FILE
For Tomcat 7:
bees app:deploy -t tomcat7 -a APPID WAR_FILE
For JBoss 7:
bees app:deploy -t jboss -a APPID WAR_FILE
Note: once you set the stack with -t, it is sticky, so you don't need to specify on subsequent deployments.
This was a confusing error for you to see, so we'll also look at cleaning up that error to be more clear.