Develop Reference

TACO Java Dependencies

I have a Cordova project created using Visual Studio 2015's Tools for Apache Cordova. We're trying to create a plugin that uses an external library, and that library depends on various things such as Google's location services. I've found that they go in a .gradle file, but have no idea how to get them in that file using TACO. I can do it manually, but VS regenerates the .gradle file every time the project's built.
I'm new to TACO, so it may be I'm missing something.

Very common problem when starting out with Cordova Plugins. I've struggled with this in the past. Start by reading this. You need to add some entries to your plugin.xml file. In that file you should have a section for each platform you support. You should also not be modifying the platform/android/build.gradle file directly. Make a separate one which will eventually get it's contents appended to your platform/android/build.gradle using <framework>.
<platform name="android">
</platform>
In platforms add something similar to match your features:
Permissions docs
<config-file target="AndroidManifest.xml" parent="/*">
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
....
</config-file>
External Libs docs
<framework src="src/android/build.gradle" custom="true" type="gradleReference" />
<source-file src="lib/android/sample-android-sdk/sample.jar" custom="true" target-dir="lib" />

Generate multiple APK's with same code base using ANT

I am trying to generate multiple apk with same code using ANT and have followed many posts to get it done. But i am unable to build the project successfully.
Let me start with my first problem. I have a main project which has two library projects, something like
Main Project ---> Library Project(isLibrary) ---> Google Play Services (isLibrary)
When i am trying to update those projects, each and every time getting a message like
It seems that there are sub-projects. If you want to update them
please use the --subprojects parameter.
So, from the above message it looks like am failing at early step of the build process.
Then i have added the following snippet prior to
<target
name="-package-resources" >
<!-- only package resources if *not* a library project -->
<echo message="Current Package name: ${app.custompackagename}" />
<do-only-if-not-library elseText="Library project: do not package resources..." >
<aapt
androidjar="${project.target.android.jar}"
apkfolder="${out.absolute.dir}"
assets="${asset.absolute.dir}"
buildType="${build.target}"
command="package"
debug="${build.is.packaging.debug}"
executable="${aapt}"
ignoreAssets="${aapt.ignore.assets}"
libraryPackagesRefid="project.library.packages"
libraryRFileRefid="project.library.bin.r.file.path"
libraryResFolderPathRefid="project.library.res.folder.path"
manifest="${out.manifest.abs.file}"
manifestpackage="${app.custompackagename}"
nocrunch="${build.packaging.nocrunch}"
previousBuildType="${build.last.target}"
resourcefilename="${resource.package.file.name}"
resourcefilter="${aapt.resource.filter}"
versioncode="${version.code}"
versionname="${version.name}" >
<res path="${out.res.absolute.dir}" />
<res path="${resource.absolute.dir}" />
<!-- <nocompress /> forces no compression on any files in assets or res/raw -->
<!-- <nocompress extension="xml" /> forces no compression on specific file extensions in assets and res/raw -->
</aapt>
</do-only-if-not-library>
</target>
then i have executed the following command from command line
ant debug -Dpackage.manifest.name=com.example.test
and here are my logs
BUILD FAILED
D:\Vijay\Android\android-sdk_r06-windows\android-sdk_r06-windows\android-sdk-win
dows\tools\ant\build.xml:571: Failed to resolve library path: D:\Vijay\Android\G
itHub\project\library

Android/PhoneGap: Using third-party libraries in plugin-development

I'm working on a PhoneGap/Cordova plugin that's supposed to provide a socket for sending and receiving OSC messages (Open Sound Control). For that purpose I'd like to use JavaOSC but I'm uncertain about how to include the library into my project.
I'm using Android Studio and I've basically followed this tutorial to set up my project. First I placed the raw JavaOSC class-files in the same directory as my OSCPlugin.class and placed the import declarations at the to of my OSCPlugin.class:
import com.illposed.osc;
That didn't work.
As a next step I tried to add the library from maven within the project's module settings. I was able to download the jar files from maven and install put them into /platforms/android/libs. Within the settings for the module 'android' I can see that 'Android API 17' is supposed to be used as SDK, including cordova-3.1.0 and com.illposed.osc:javaosc-core:0.2 - both activated. I can see the cordova-3.1.0.jar as well as javaosc-core-0.2.jar, containing com.illposed.osc in the navigator within Android Studio.
However, when trying to compile my project I get:
Gradle: cannot find symbol class osc
triggered from within OSCPlugin.class that contains the above mentioned import declaration
I have very little experience with Java and even less with Android development. But I'd be interested in solving this riddle and get started. I have searched the Java docs but the problem doesn't merely lie within Java but rather within the structure of the Android project.
I'd be thankful if someone could shed some light on this issue. Any hint's highly appreciated!

For one of my Phonegap projects I needed the Apache Commons Net, trying to follow these steps:
...
<source-file src="src/android/xxx.jar" target-dir="libs" framework="true" />
<source-file src="src/android/MyPlugin.java" target-dir="src/com/mypackage" />
...
unfortunately, without success. The trick was to embed the third-party library in another plugin (following the very plugin structure). Having the org.apache.commons.net as a top level directory:
org.apache.commons.net
+src
+android(this is where the .jar is located)
+www (empty, not referencing any .js)
+plugin.xml
For brevity, plugin.xml as follows:
<?xml version="1.0" encoding="UTF-8"?>
<plugin xmlns="http://www.phonegap.com/ns/plugins/1.0"
id="org.apache.commons.net"
version="0.1.0">
<name>org.apache.commons.net</name>
<description>org.apache.commons.net</description>
<license>Apache License, Version 2.0</license>
<keywords>org.apache.commons.net</keywords>
<!-- android -->
<platform name="android">
<config-file target="res/xml/config.xml" parent="/*">
<feature name="org.apache.commons.net">
<param name="android-package" value="org.apache.commons.net"/>
</feature>
</config-file>
<source-file src="src/android/commons-net-2.2.jar" target-dir="libs" framework="true" />
</platform>
</plugin>
Assuming the org.apache.commons.net directory is located in your local git repo, adding it to your project is as trivial as:
phonegap local plugin add /path/to/your/org.apache.commons.net

To add external library, basically all you have to do is copy the jar to the /libs folder.
Here you have a bad import in your source.
import is used to import a class by specifying the package name followed by the class name and here you only specify the class name, so the error "cannot find symbol class osc" you are having is because there is no class osc.
You should use either
import com.illposed.osc.*; if you want to import all classes from the package
or add an import for each class from the package that you are going to use.
And if you want make the plugin installable using the CLI or phonegap build, you also have to update plugin.xml to add the copy of the jar file.
ps in case you don't know, you won't be able to use classes from com.illposed.osc.ui as they are using swing and designed for the jvm and not android.

Android 4: Failed resolving class from org.simalliance.openmobileapi package

I'm working on application which make use of the org.simalliance.openmobileapi API to use the Secure element communication.
The application is Native that is the main Activity call a JNI library to operate. The JNI library use the JNI Method to call functions of the org.simalliance.openmobileapi package.
The API level is 8 as write in the mainfest:
<uses-sdk android:minSdkVersion="8" android:targetSdkVersion="8"/>
The application work fine with Android 2.3.6 but when i try to launch the application from Android 4.0.4 or later the application can't find the SEService class of the org.simalliance.openmobileapi. Useful log are:
09-20 11:00:48.509: I/dalvikvm(1104): Failed resolving Lpkg/wrapper/SecureChannel; interface 203 'Lorg/simalliance/openmobileapi/SEService$CallBack;'
09-20 11:00:48.509: W/dalvikvm(1104): Link of class 'Lpkg/wrapper/SecureChannel;' failed
01-01 22:08:33.460: I/dalvikvm(10881): java.lang.NoClassDefFoundError: org.simalliance.openmobileapi.SEService$1
The class SecureChannel is a Java class that is called by the JNI to operate over the Secure Element and is contained in a jar that is "dexed" at compiling time with the rest of the project.
The package org.simalliance.openmobileapi.jar is contained in the /system/framework folder in both version of Android:
On Android 2.3.6
-rw-r--r-- root root 29148 2012-11-15 11:24 org.simalliance.openmobileapi.jar
On Android 4.0.4
-rw-r--r-- root root 313 2012-06-11 15:49 org.simalliance.openmobileapi.jar
-rw-r--r-- root root 24864 2012-06-11 15:49 org.simalliance.openmobileapi.odex
The only difference i see is the odex file in the Android 4.0.4 OS.
Is there a way to include the classpath or the reference to a package contained in the /system/framework folder ?

I've found a clean solution to this problem.
Instead of saying to the compiler that you want to compile the library into your application, just say that the library is provided for your application and everything will works fine.
In my case I use Gradle with Android studio.
So I just extract the .jar file from the downloaded add-on in my SDK path:
sdk\add-ons\addon-open_mobile_api-giesecke_devrient_gmbh-18\libs
And placed it in my application libs folder.
Then in my build.gradle file I replaced :
dependencies {
compile files('libs/org.simalliance.openmobileapi.jar')
}
with this :
dependencies {
provided files('libs/org.simalliance.openmobileapi.jar')
}
And now everything works just fine.

Here is my configure in Android Studio
in app/build.gradle
dependencies {
compile fileTree(include: ['*.jar'], exclude: ['org.simalliance.openmobileapi.jar'], dir: 'libs')
provided files('libs/org.simalliance.openmobileapi.jar')
}
in AndroidManifest.xml ,turning it true or false depends on you
<uses-library
android:name="org.simalliance.openmobileapi"
android:required="false" />
and in /system/framwork/, "org.simalliance.openmobileapi.jar" is required or an exception will throw up.

I solved the problem putting on src/ folder of my project the source contained in this package:
http://code.google.com/p/seek-for-android/downloads/detail?name=MSC%20Smartcard%20Service%203.0.tar.gz&can=2&q=
More precisely the source in the package com.mobilesecuritycard.openmobileapi.jar which is the new version of the seek-for-android library made to replace the old package org.simalliance.openmobileapi.jar.
I had to rename all the reference to the package from com.mobilesecuritycard to org.simalliance because the SecureChannel class was written with the old package so the old package name must be used.

In android manifest don't forget add:
<application
android:name=....
android:icon="#drawable/icon"
android:label="#string/app_name"
android:allowBackup = "true" >
<!-- support USIM -->
<uses-library
android:name="org.simalliance.openmobileapi"
android:required="false"/>

Cross linking java doc between separate projects

I'm having trouble getting javadoc to reference another project's API.
There's a strict hirearchy between the projects (a "common" project referenced by an "app" project).
Both projects build just fine, so there's no issue with classes and packages not actually existing.
My understanding is that javadoc doesn't have a sort of buildpath in the same way that Java does, but uses links to other javadoc websites instead. There's some pretty logical reasons for this in terms of being able to generate HTML cross references.
My attempt to make this goes as follows:
I've built the javadoc for the common project
I threw that on a webserver on my intranet
I added a link to the api (on my intranet) to the javadoc ant task in the app project.
I attempted to build the app project
Javadoc still spits out error messages of the form:
[javadoc] C:\Users\couling\workspace\app\src\com\blahblah\app\AppMain.java:14: package com.blahblah.common.foo does not exist
[javadoc] import com.blahblah.common.foo.Bar
[javadoc] ^
The resulting javadoc has no cross links between the projects.
The ant tasks for the two projects are as follows:
Common:
<javadoc
access="protected"
author="true"
classpath="."
destdir="out/doc/docs"
nodeprecated="false"
nodeprecatedlist="false"
noindex="false"
nonavbar="false"
notree="false"
packagenames="*"
source="1.6"
sourcepath="src"
splitindex="true"
use="true"
version="true">
<link href="http://download.oracle.com/javase/6/docs/api/" />
</javadoc>
App:
<javadoc
access="protected"
author="true"
classpath="."
destdir="out/doc/docs"
nodeprecated="false"
nodeprecatedlist="false"
noindex="false"
nonavbar="false"
notree="false"
packagenames="com.blahblah.app.*"
source="1.6"
sourcepath="src"
splitindex="true"
use="true"
version="true">
<link href="http://intranet.blahblah.com/api/common/docs/" />
<link href="http://download.oracle.com/javase/6/docs/api/" />
</javadoc>
Any thoughts on what I need to do to get app to reference common?

The <link> element (or the -link option for command line javadoc) only help with generating the links - but Javadoc stops at an earlier point, it can't really work with your app classes if they reference unknown (common) classes.
In this respect, Javadoc works just like Javac - you must somehow point it to the classes to be used, i.e. they must be in the class path. You can use a <classpath> element to point to the jar file or class directory, or a <sourcepath> element, to point to the sources (do this if you need to inherit some comments from them).
This is not needed for linking to the standard API, since it is already included in the compiler.
Note that linking in this way requires Javadoc to download the package-list from this URL - you can instead point to a local directory which contains this package-list file.