Created sample mobile module app with 8.3.1.GA Ti SDK.
Tried to package the module.
Expected:
Module should be packaged without any errors.
Actual:
Throwing the below error
2020-04-07T07:14:28.008Z | DEBUG | [PLUGIN-LOAD] 0ms
/Users/pc270889/.appcelerator/install/7.1.2/package/appc.js
2020-04-07T07:14:28.078Z | DEBUG | [PLUGIN-LOAD] 67ms
/Users/pc270889/.appcelerator/install/7.1.2/package/node_modules/appc-cli-titanium/appc.js
2020-04-07T07:14:28.078Z | DEBUG | run plugin:
/Users/pc270889/.appcelerator/install/7.1.2/package/node_modules/appc-cli-titanium
2020-04-07T07:14:28.081Z | DEBUG | [PLUGIN-LOAD] 1ms
/Users/pc270889/.appcelerator/install/7.1.2/package/node_modules/arrow/appc.js
2020-04-07T07:14:28.108Z | DEBUG | run plugin:
/Users/pc270889/.appcelerator/install/7.1.2/package/node_modules/arrow
2020-04-07T07:14:28.137Z | TRACE | plugin "arrow" failed its "when"
function check, skipping...
2020-04-07T07:14:28.138Z | TRACE | loading plugin "titanium" for
command "run" CLI options via function
2020-04-07T07:14:28.139Z | TRACE | loading plugin "titanium" for
command "run" CLI options via array
2020-04-07T07:14:28.141Z | TRACE | executing command "run" with the
following plugins:
["titanium"]
2020-04-07T07:14:28.143Z | TRACE | session already loaded in
opts.session
2020-04-07T07:14:28.144Z | DEBUG | Titanium Downloads Last Checked:
1586240964935
2020-04-07T07:14:29.078Z | TRACE | getInstalledTiSdkInfo {
sdkPath: '/Users/pc270889/Library/Application Support/Titanium',
activeSDK: '8.3.1.GA'
}
2020-04-07T07:14:29.078Z | DEBUG | active sdk info {
sdkPath: '/Users/pc270889/Library/Application Support/Titanium',
activeSDK: '8.3.1.GA'
}
2020-04-07T07:14:32.902Z | DEBUG | to download
{"modules":[{"id":"hyperloop","name":"Hyperloop","description":"Gain
complete access to native APIs in your Titanium mobile
applications.","guid":"99a136cd-4e51-40da-bcdb-d514f5895fb5","version":"1.2.8","url":"https://downloads.platform.axway.com/modules/hyperloop-1.2.8.zip","min_mobilesdk_version":"5.4.0","oses":["linux","win32","osx"],"platforms":["iphone","android"],"required":true,"partner":null,"versions":[{"platforms":["iphone","android","windows"],"sdk_versions":">=6.0.0
<7.0.0","version":"2.2.3","url":"https://downloads.platform.axway.com/modules/hyperloop-2.2.3.zip"}]},{"id":"ti.cloudpush","name":"ti.cloudpush","description":"Enables
Mobile Backend Services Push Notifications for Android
applications.","guid":"2d542783-c83c-4597-bd61-1073aa16ece2","oses":["linux","win32","osx"],"platforms":["android"],"required":true,"partner":null,"versions":[{"platforms":["android"],"sdk_versions":">=7.5.0
<8.0.0","version":"6.0.0","url":"https://downloads.platform.axway.com/modules/ti.cloudpush-android-6.0.0.zip"},{"platforms":["android"],"sdk_versions":">=7.0.0
<7.5.0","version":"5.2.1","url":"https://downloads.platform.axway.com/modules/ti.cloudpush-android-5.2.1.zip"}]},{"id":"com.appcelerator.aca","name":"Appcelerator
Crash Analytics","description":"Enables Appcelerator Crash Analytics.
Appcelerator Crash Analytics allows you to identify and troubleshoot
crashes in your mobile
applications.","guid":"ec713280-46fb-46ad-b9af-4435dfca143b","oses":["linux","win32","osx"],"platforms":["iphone","android"],"required":true,"partner":"aca","download":true,"versions":[{"platforms":["iphone","android"],"sdk_versions":">=9.0.0","version":"2.0.0","url":"https://downloads.platform.axway.com/modules/com.appcelerator.aca-2.0.0.zip"},{"platforms":["iphone","android"],"sdk_versions":">=8.1.1 <9.0.0","version":"1.4.3","url":"https://downloads.platform.axway.com/modules/com.appcelerator.aca-1.4.3.zip"},{"platforms":["iphone","android"],"sdk_versions":">=8.0.0 <8.1.1","version":"1.3.0","url":"https://downloads.platform.axway.com/modules/com.appcelerator.aca-1.3.0.zip"}]}],"components":[]}
2020-04-07T07:14:32.907Z | DEBUG | Module Found com.appcelerator.aca
iphone 1.4.3
2020-04-07T07:14:32.907Z | DEBUG | Module Found com.appcelerator.aca
android 1.4.3
2020-04-07T07:14:32.908Z | DEBUG | com.appcelerator.aca iphone Latest
Version 1.4.3
2020-04-07T07:14:32.908Z | DEBUG | com.appcelerator.aca android
Latest Version 1.4.3
2020-04-07T07:14:32.940Z | TRACE | No project alloy hook; skipping
update to 1.0.1
4/7/2020, 12:44:34 PM
Operating System
Name = Mac OS X
Version = 10.14.6
Architecture = 64bit
# CPUs = 8
Memory = 17179869184
Node.js
Node.js Version = 12.14.0
npm Version = 6.13.4
Titanium CLI
CLI Version = 5.2.2
Titanium SDK
SDK Version = 8.3.1.GA
SDK Path = /Users/pc270889/Library/Application Support/Titanium/mobilesdk/osx/8.3.1.GA
Target Platform = android
Command
/usr/local/bin/node /Users/pc270889/.appcelerator/install/7.1.2/package/node_modules/titanium/lib/titanium.js build --platform android --project-dir /Users/pc270889/Documents/Arun/kofaxModuleWorkspace/samplemodule/android --build-only --log-level trace --no-colors --no-progress-bars --no-prompt --no-banner --prompt-type socket-bundle --prompt-port 49898 --config-file /var/folders/wj/xt_k91vj6xb8g84bj4lswjtc0000gn/T/build-1586243668144.json --no-banner --project-dir /Users/pc270889/Documents/Arun/kofaxModuleWorkspace/samplemodule/android
Update the android:minSdkVersion in the tiapp.xml or custom AndroidManifest to at least 19:
[ERROR] : The minimum supported SDK API version must be 19 or newer,
but is currently set to 16
<android>
<manifest>
<uses-sdk android:minSdkVersion="19" android:targetSdkVersion="25" />
</manifest>
</android>
I have a somewhat similar gradle and spring webflux config up as described in Why spring webflux is choosing jetty by default and then failing?
But our goal is to have in memory Amazon dynamo db + spring webflux on netty (and NOT jetty) for our unit testing ( we already have production dynamo db with spring webfux on netty ). I am able to run unit tests using in-memory dynamo db but as soon as I enable springboot webflux, it starts complaining :
Caused by: java.lang.NoClassDefFoundError: org/eclipse/jetty/servlet/ServletHolder
at org.springframework.boot.web.embedded.jetty.JettyReactiveWebServerFactory.createJettyServer(JettyReactiveWebServerFactory.java:176) ~[spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE]
at org.springframework.boot.web.embedded.jetty.JettyReactiveWebServerFactory.getWebServer(JettyReactiveWebServerFactory.java:106) ~[spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE]
at org.springframework.boot.web.reactive.context.ReactiveWebServerApplicationContext$ServerManager.<init>(ReactiveWebServerApplicationContext.java:202) ~[spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE]
at org.springframework.boot.web.reactive.context.ReactiveWebServerApplicationContext$ServerManager.get(ReactiveWebServerApplicationContext.java:221) ~[spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE]
at org.springframework.boot.web.reactive.context.ReactiveWebServerApplicationContext.createWebServer(ReactiveWebServerApplicationContext.java:90) ~[spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE]
at org.springframework.boot.web.reactive.context.ReactiveWebServerApplicationContext.onRefresh(ReactiveWebServerApplicationContext.java:79) ~[spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE]
... 62 common frames omitted
Caused by: java.lang.ClassNotFoundException: org.eclipse.jetty.servlet.ServletHolder
I have tried following in my build.gradle :
configurations {
// exclude Reactor Jetty /Tomcat
compile.exclude group: 'org.springframework.boot',module: 'spring-boot-starter-jetty'
testcompile.exclude group: 'org.springframework.boot',module: 'spring-boot-starter-jetty'
//compile.exclude group: 'javax.servlet' , module: 'servlet-api' //<--tried servlet jar exclusion also
}
.....
testCompile ('com.amazonaws:DynamoDBLocal:1.11.477')
....//event tried this ( and is probably wrong)
testCompile("org.springframework.boot:spring-boot-starter-test:$springBootVersion") {
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-jetty' //by both name and group
exclude group: 'org.springframework.boot', module: 'spring-boot-starter-tomcat'
}
I checked dependency graph :
\--- com.amazonaws:DynamoDBLocal:1.11.477
+--- org.antlr:antlr4-runtime:4.7.2
+--- commons-cli:commons-cli:1.2
+--- org.apache.commons:commons-lang3:3.8.1
+--- com.almworks.sqlite4java:libsqlite4java-linux-i386:1.0.392
| \--- com.almworks.sqlite4java:sqlite4java:1.0.392
+--- com.almworks.sqlite4java:libsqlite4java-linux-amd64:1.0.392
| \--- com.almworks.sqlite4java:sqlite4java:1.0.392
+--- com.almworks.sqlite4java:sqlite4java-win32-x64:1.0.392
| \--- com.almworks.sqlite4java:sqlite4java:1.0.392
+--- com.almworks.sqlite4java:sqlite4java-win32-x86:1.0.392
| \--- com.almworks.sqlite4java:sqlite4java:1.0.392
+--- com.almworks.sqlite4java:libsqlite4java-osx:1.0.392
| \--- com.almworks.sqlite4java:sqlite4java:1.0.392
+--- com.amazonaws:aws-java-sdk-core:1.11.477 (*)
+--- com.amazonaws:aws-java-sdk-dynamodb:1.11.477 (*)
+--- org.apache.logging.log4j:log4j-api:2.6.2 -> 2.11.2
+--- org.apache.logging.log4j:log4j-core:2.6.2 -> 2.11.2
| \--- org.apache.logging.log4j:log4j-api:2.11.2
+--- org.eclipse.jetty:jetty-client:8.1.12.v20130726 -> 9.4.18.v20190429
| +--- org.eclipse.jetty:jetty-http:9.4.18.v20190429
| | +--- org.eclipse.jetty:jetty-util:9.4.18.v20190429
| | \--- org.eclipse.jetty:jetty-io:9.4.18.v20190429
| | \--- org.eclipse.jetty:jetty-util:9.4.18.v20190429
| \--- org.eclipse.jetty:jetty-io:9.4.18.v20190429 (*)
+--- org.eclipse.jetty:jetty-server:8.1.12.v20130726 -> 9.4.18.v20190429
| +--- javax.servlet:javax.servlet-api:3.1.0 -> 4.0.1
| +--- org.eclipse.jetty:jetty-http:9.4.18.v20190429 (*)
| \--- org.eclipse.jetty:jetty-io:9.4.18.v20190429 (*)
+--- org.mockito:mockito-core:1.10.19 -> 2.23.4
| +--- net.bytebuddy:byte-buddy:1.9.3 -> 1.9.12
So what I need is to force webflux to have Netty as server. I think it is getting overridden by dynamodb dependency or some jar transitivity.
I ran into this exact same issue. The problem is that the DynamoDBLocal library transitively references Jetty. With both Jetty and Netty on the classpath, Webflux thinks it should start up using Jetty instead of Netty. I was able to solve this by following what is detailed in the Spring Boot docs here: https://docs.spring.io/spring-boot/docs/current/reference/html/howto-embedded-web-servers.html#howto-configure-webserver
Specifically this part:
As a last resort, you can also declare your own WebServerFactory component, which will override the one provided by Spring Boot.
More concretely, you can add this to your test configuration (or your entire app configuration if you want to specifically tell everything to always use Netty):
#Bean
public ReactiveWebServerFactory reactiveWebServerFactory() {
return new NettyReactiveWebServerFactory();
}
Same issue here. I suspect that some internal condition forces the Tomcat instead of Netty, but I couldn't figure out.
I solved the issue combining this three changes:
Added org.springframework.boot:spring-boot-starter-reactory-netty dependecy
Added a NettyReactiveWebServerFactory bean (Thanks to Evan Lennick!)
Added spring.main.web-appplication-type=reactive to application.properties
I hope this could help!
This issue has already been resolved in Spring Boot 2.2.9 version:
https://github.com/spring-projects/spring-boot/issues/22275
I use JsDusk
Version : JSDuck 5.3.4 (Ruby 1.8.7)
OS: Linux ( CentOS 6 )
I want to exclude some directories, but it doesn't work.
--exclude="/Doc/Project1/application/,/Doc/Project1/docs/,/Doc/Project1/docUtil/"
Actually it should works. Here is the jsDuck Code .
I start jsDuck in a script with the command below.
find /Doc/Project1/ -name '*.js' | xargs jsduck --output=/Doc/DocSrc/jsdoc --exclude=/Doc/Project1/application/ext,/Doc/Project1/application/,/Project1/docs,/Doc/Project1/docUtil,/Doc/Project1/framework,/jawaDoc/Project1/info
The commit you're referring to is included to JSDuck 6.0 beta, but you're using 5.3.4.
You can install the beta with:
$ gem install jsduck --prerelease
I am migrating an Ember rc7 project to Ember 1.0.0. I have this unusual error:
Ember.State has been moved into a plugin: https://github.com/emberjs/ember-states
I have the error only if I use a combination of Ember.js 1.0.0 in combination with Ember data 0.13. If I include the extra ember-states lib, then everything works fine.
What is the reason of this change ? Why do I need an additional lib ?
If I use Ember.js 1.0.0 in combination with Ember data 1.0.0 beta.1, then this error does not occur.
I hope somebody can explain why this additional lib seems to be needed in some cases ?
Marc
According to this pull request Ember itself does not use Ember.State internally anymore, and as of this Ember Data commit Ember Data did not depend on the Ember.State implementation (a new/better way to handle internal state in Ember Data was used instead).
Since neither library has a dependency for Ember.State they moved it to its own package, which can be included manually if you still require it.
Github repository for Ember.State can be found here
Using this table you can see that when using Ember Data 0.13 and Ember 1.0.0, Ember Data 0.13 tries to use Ember.State, but Ember 1.0.0 does not provide it and causes your error.
+-------------------------+------------------+----------------------+
| Library | Uses Ember.State | Provides Ember.State |
+-------------------------+------------------+----------------------+
| Ember rc7 | no | yes |
| Ember 1.0.0 | no | no |
| Ember Data 0.13 | yes | no |
| Ember Data 1.0.0 beta 1 | no | no |
+-------------------------+------------------+----------------------+
I want to upgrade the ocsigen to 2.1 in my freebsd box.
$pkg_info | grep -i ocsigen
ocsigen-1.1.0_1 Web programming framework for OCaml
$cat /usr/ports/www/ocsigen/Makefile | grep -i version
POPORTVERSION= 2.1
$sudo pormaster ocsigen
...
===> Building for ocaml-tyxml-2.1
gmagmake: *** no rule to create “files/META.in” needed by “files/META”。 Stop
StoStop in /usr/ports/textproc/ocaml-tyxml.
...
===>>> You can restart from the point of failure with this command line
porportmaster <flags> www/ocsigen textproc/ocaml-tyxml
Maybe it is a simple error, but i cannot fix it by myself.
Sincerely!
You should now use OPAM, the "standard" tool for managing source distributions of OCaml packages. OPAM is available here:
http://opam.ocamlpro.com/