pombreda / maven-android-plugin Goto Github PK

Need a way to sign with a different keystore than the debug keystore.

What version of maven-android-plugin are you using?
2.0.0-SNAPSHOT as of 2009-06-07.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

What steps will reproduce the problem?
1. Download and install Android SDK 1.5
2. Try using it with maven-android-plugin
3.

What is the expected output? What do you see instead?
It should work.

It doesn't, because Android SDK directory structure has changed from 1.1 to
1.5.

What version of maven-android-plugin are you using?
2.0.0-SNAPSHOT as of 2009-06-07.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

Write front page with links to for example GettingStarted

What steps will reproduce the problem?

1. Create a Maven/Android project
2. Use android:dex

What is the expected output?

I was hoping that classes.dex did not include the contents of every compile
dependency, just the classes in the current project.

What do you see instead?

All the classes in the compile dependencies are included in classes.dex.

What version of maven-android-plugin are you using?

2.0.0.

What are the complete output lines of "mvn -version" on your machine?

mvn android:dex ...

Please provide any additional information below.

Between this and issue 31, I'm really just hoping that the android:dex
plugin can be a little more generic.  It seems like it's targeted for use
with a complete application, whereas I'm just trying to convert some
library classes to dex so they can be bundled in a "plugin" that's run on
the Android platform.  Obviously, I don't need all of the dependency
classes to accomplish that.

This should be a simple change, and could be done in one of two ways:
either a boolean that turns off copying the compile classpath classes to
android-classes or, when copying compile classpath classes, check to see if
the artifact has "provided" scope.  If so, exclude them.

What steps will reproduce the problem?
1. Download the samples 2.0.0-alpha4
2. Set up environment variables according to 
http://code.google.com/p/maven-android-plugin/wiki/GettingStarted
3. cd apidemos-15
4. Update the poms to use maven-android-plugin 2.0.0-alpha5-SNAPSHOT.
5. mvn install


What is the expected output?
It should build and install the samples. Then it should install the apk files 
to ~/.m2/repository/...

What do you see instead?
When it tries to install the apidemos-15-platformtest apk to ~/.m2/repository, 
it fails. The problem is that <packaging>android:apk:platformTest</packaging> 
contains a ":", which is not valid for filenames in Windows.

[INFO] [install:install]
[INFO] Installing 
C:\java\maven-android-plugin-samples\apidemos-15\apidemos-15-platformtests\targe
t\apidemos-15-platformtests-2.0.0-alpha4.apk to C:\Documents and 
Settings\Administrator\.m2\repository\com\jayway\maven\plugins\android\generatio
n2\samples\apidemos-15\apidemos-15-platformtests\2.0.0-alpha4\apidemos-15-platfo
rmtests-2.0.0-alpha4.android:apk:platformTest
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error installing artifact: The filename, directory name, or volume label 
syntax is incorrect


What version of maven-android-plugin are you using?
2.0.0-alpha5-SNAPSHOT

What is the output of "mvn -version" on your machine?
Maven version: 2.0.9
Java version: 1.6.0_14
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Try releasing everything with maven.
2.
3.

What is the expected output? What do you see instead?
It should just work.
The samples can't be released at the same time as the plugin, because they
require it to be built first. Having the plugin and samples directories in
the same git repo (but still subdirectories, and no root pom) doesn't work
either.


What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Be a new user.
2. Try to figure out how to set up an Android application project.
3.

What is the expected output?
It should be very easy.

What do you see instead?
I have to read through the long GettingStarted page, understand how to create 
my pom.xml, and understand the directory layout.

What version of maven-android-plugin are you using?
2.0.0-alpha4

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"


Please use labels and text to provide additional information.

Create a new goal named "mavenize", which can take an existing project 
directory and:
 * create a pom.xml
 * restructure the directory to fit the desired layout

It should take a config parameter "layout", which tells the goal how to 
structure the directory. For example (some ideas):
 * -Dandroid.layout=eclipse means to make the directory structure compatible with Eclipse.
 * -Dandroid.layout=idea means to make the directory structure compatible with IntelliJ IDEA.
 * -Dandroid.layout=maven means to make a fully mavenized directory structure, which obeys all Maven conventions, but probably isn't compatible with Eclipse.

It should try to figure out the groupId and artifactId based on package name 
and any existing code, such as the main launcher Activity in 
AndroidManifest.xml.

What steps will reproduce the problem?

1. My manifest XML looks like this:

<?xml version="1.0" encoding="utf-8"?>
<manifest
    xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.jimandlisa.myapp"
    android:versionCode="1"
    android:versionName="1.0"
    android:debuggable="true">
    <application android:icon="@drawable/icon"
android:label="@string/app_name">
        <activity android:name="MyApp" android:label="@string/app_name">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
        <activity android:name=".EditPreferences" />
    </application>
    <uses-sdk android:minSdkVersion="4" />
</manifest>

There is no mention of instrumentation.

None of the classes in MyApp descend from the Android test base class, or
depend on any classes that are test classes.

2. I run mvn clean install.

3. The build fails with:

[INFO] [android:internal-pre-integration-test {execution: 
default-internal-pre-integration-test}]
[INFO] C:\android-sdk-windows-1.6_r1/tools/adb [install, -r, 
C:\MyApp\target\MyApp-1.0.0-SNAPSHOT.apk]
        pkg: /data/local/tmp/MyApp-1.0.0-SNAPSHOT.apk

Success

[ERROR] 436 KB/s (118743 bytes in 0.265s)
[INFO] [android:internal-integration-test {execution: 
default-internal-integration-test}]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] No value for xpath: manifest//instrumentation/@android:name
[INFO] ------------------------------------------------------------------------

[INFO] Trace
org.apache.commons.jxpath.JXPathNotFoundException: No value for xpath:
manifest//instrumentation/@android:name
        at
org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getValue(JXPathContextRe
ferenceIm
pl.java:356)
        at
org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getValue(JXPathContextRe
ferenceIm
etc.

4. The problem is that the plugin for some reason thinks the app has
instrumentation, but it doesn't. Then when it tries to get the
instrumentation name, it dies because there isn't one.

5. Adding <enableIntegrationTest>false</enableIntegrationTest> to the POM
works around the problem.

What version of maven-android-plugin are you using?
2.2.0, but 2.2.1 does it as well.

What are the complete output lines of "mvn -version" on your machine?
C:\>mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
Java version: 1.6.0_15
Java home: C:\Program Files\Java\jdk1.6.0_15\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please provide any additional information below.
I can't cut it down to a smaller test case, and this is a complex
multi-project setup, but I'm willing to give you the source to help track
this down if you're willing to try to set up the whole config.

What steps will reproduce the problem?
1. Build project "project_A" with type "apk"
2. Build project "project_B" with type "apk" that includes project
"project_A" as "apksource" type dependency

What is the expected output?
A final assembled project_B.apk includes "assets" files from project_B and
project_A. 

What do you see instead?
A final assembled project_B.apk DOES NOT include "assets" files from
project_B. Only "assets" files from project_A are included in project_B.apk.

What version of maven-android-plugin are you using?
2.2.1

What are the complete output lines of "mvn -version" on your machine?
E:\>mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 16:16:01-0300)
Java version: 1.6.0_06
Java home: C:\java\jdk1.6.0_06\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please provide any additional information below.

Assets should be combined in a similar fashion how resources get combined
in target\generated-sources\combined-resources\res catalog.

There are some notes in Issue 18.

Use http://code.google.com/p/onejar-maven-plugin/wiki/DeployerInstructions
as template, because it's mostly the same.

Add site, source:jar, javadoc:jar to release configuration in pom.xml.

What steps will reproduce the problem?
1. Create a Maven project with jar packaging
2. Run android:dx on the project

What is the expected output?

I'm expecting android:dx to simply create classes.dex.  It does, but...

What do you see instead?

The android:dx mojo will attempt to attach an artifact named
groupId:artifactId:version:jar.  If the project is already using jar
packaging, Maven complains about a duplicate artifact being attached.

What version of maven-android-plugin are you using?

2.0.0.

What are the complete output lines of "mvn -version" on your machine?

maven android:dex -Dandroid.sdk.path=... -Dandroid.sdk.platform=1.5

Please provide any additional information below.

The reason I want to do this is because my project relates to creating
plugins (not Maven plugins, but generic plugins, sort of like OSGi bundles)
that run on Android.  I _only_ want to run dx and package up classes.dex
into my plugin file.  The project used to create these plugins has jar
packaging since other projects may need to depend on it.

Ideally, what I'd like to see is a simple boolean parameter to android:dx
that turns on or off DexMojo's default artifact attach behavior.

What steps will reproduce the problem?
1. Verified my configuration by compiling the maven-android-plugin samples
2. Added the add-on maps as shown in the "Add-Ons" wiki
3. Compiled an Android project (known to be working on device) with the Maps 
add-on

What is the expected output?
Compilation success.

What do you see instead?

D:\Workspace\Android Workspace\Parking>mvn install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building HelloMaps
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] [android:generate-sources {execution: default-generate-sources}]
[INFO] ANDROID-904-002: Found aidl files: Count = 0
[INFO] C:\android-sdk-windows-1.5_r2\platforms\android-1.5/tools/aapt [package,
-m, -J, D:\Workspace\Android Workspace\Parking\target\generated-sources\r, -M, D
:\Workspace\Android Workspace\Parking\AndroidManifest.xml, -S, D:\Workspace\Andr
oid Workspace\Parking\res, -A, D:\Workspace\Android Workspace\Parking\assets, -I
, C:\android-sdk-windows-1.5_r2\platforms\android-1.5\android.jar]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory D:\Workspace\Android Workspace\Parkin
g\src\main\resources
Downloading: http://repo1.maven.org/maven2/android/android/1.5_r2/android-1.5_r2
.pom
[INFO] Unable to find resource 'android:android:pom:1.5_r2' in repository centra
l (http://repo1.maven.org/maven2)
Downloading: http://repo1.maven.org/maven2/add-ons/maps/3/maps-3.pom
[INFO] Unable to find resource 'add-ons:maps:pom:3' in repository central (http:
//repo1.maven.org/maven2)
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 2 source files to D:\Workspace\Android Workspace\Parking\target
\classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
D:\Workspace\Android Workspace\Parking\src\com\mobileappx\park\activity\ParkCarA
ctivity.java:[170,30] cannot access com.google.map.MapPoint
class file for com.google.map.MapPoint not found
                                        mMapController.setCenter(new GeoPoint(la
titude, longitude));


[INFO] --------------------------------------------------------------------

What version of maven-android-plugin are you using?
2.1.0

What are the complete output lines of "mvn -version" on your machine?
D:\Workspace\Android Workspace\Parking>mvn --version
Apache Maven 2.2.0 (r788681; 2009-06-26 08:04:01-0500)
Java version: 1.6.0_13
Java home: C:\Program Files\Java\jdk1.6.0_13\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows vista" version: "6.1" arch: "amd64" Family: "windows"

Please provide any additional information below.

Need a way to sign any separate apk file.

What version of maven-android-plugin are you using?
2.0.0-SNAPSHOT as of 2009-06-07.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

When I build and run my Android-specific unit tests, I get the output below.

The number of "Can't dispatch DDM chunk" messages varies. Sometimes there
are none. Sometimes there are several.

It always says "[ERROR] NN KB/s (MMMMM bytes in XXX ms)".

Yet the tests build and run successfully.

I modified one of the tests to throw an exception to see if the tests
really are running, and the expected exception was thrown and the test
failed, so it appears that despite the error messages, all is well. But
it's bothersome.

Any idea what causes these errors?

[INFO] Building jar:
C:\devjim\projects\trunk\MyApp\Android\MyAppAndroidTests\target\MyAppAndroidTest
s-1.0.0-SNAPSHOT-javadoc.jar
[INFO] [android:internal-pre-integration-test {execution:
default-internal-pre-integration-test}]
[INFO] C:\devjim\tools\android-2.0/tools/adb [install, -r,
C:\devjim\projects\trunk\MyApp\Android\MyAppAndroid\target\MyAppAndroid-1.0.0-SN
APSHOT.apk]
        pkg: /data/local/tmp/MyAppAndroid-1.0.0-SNAPSHOT.apk

Success

[ERROR] 300 KB/s (120227 bytes in 0.390s)
[INFO] C:\devjim\tools\android-2.0/tools/adb [install, -r,
C:\devjim\projects\trunk\MyApp\Android\MyAppAndroidTests\target\MyAppAndroidTest
s-1.0.0-SNAPSHOT.apk]
DDM dispatch reg wait timeout

Can't dispatch DDM chunk 52454151: no handler defined

        pkg: /data/local/tmp/MyAppAndroidTests-1.0.0-SNAPSHOT.apk

Success

[ERROR] 93 KB/s (114744 bytes in 1.203s)
[INFO] [android:internal-integration-test {execution:
default-internal-integration-test}]
[INFO] C:\devjim\tools\android-2.0/tools/adb [shell, am, instrument, -w,
com.jimandlisa.MyApp.android.tests/android.test.InstrumentationTestRunner]

com.jimandlisa.MyApp.android.tests.DataAccessorAndroidTest:..

com.jimandlisa.MyApp.android.tests.PreferenceUtilsAndroidTest:..

com.jimandlisa.MyApp.android.tests.TimeManagerAndroidTest:..

Test results for InstrumentationTestRunner=......

Time: 38.444

OK (6 tests)

What steps will reproduce the problem?
1. Create a project that has maven dependencies.
2. Have at least one of those dependencies use resources in META-INF
3. Build the .apk as usual using maven-android-plugin.

What is the expected output?
Files in the 3rd party .jar's META-INF should be copied to the .apk META-INF.

What do you see instead?
Files are not copied.

What version of maven-android-plugin are you using?


What is the output of "mvn -version" on your machine?
OS name: "linux" version: "2.6.28-13-generic" arch: "i386" Family: "unix"

Please use labels and text to provide additional information.

I'm not sure if this is an issue with maven-android-plugin or with android
itself, but I thought I'd check in here since this project is much easier
to get involved with :)

What steps will reproduce the problem?
1.create android project in eclipse
2.remove gen default.properties
3.move src java; mkdir src; cd src; mkdir main; move java src\main;
4.copy pom.xml from samples project and adapt on project
5. mvn install

What is the expected output?
success

What do you see instead?
build error

[INFO] C:\home\android-sdk-windows-1.5_r2\platforms\android-1.5/tools/dx
[--dex, --output=C:\home\workspace\my-android\target\classes.dex,
C:\home\workspace\my-android\target\android-classes]
[ERROR] warning: Ignoring InnerClasses attribute for an anonymous inner
class that doesn't come with an associated EnclosingMethod attribute. (This cl
ass was probably produced by a broken compiler.)
[ERROR]
[ERROR] trouble processing:
[ERROR] class name (Queens) does not match path (bprolog/plc/Queens.class)
[ERROR] ...while parsing bprolog/plc/Queens.class
[ERROR] ...while processing bprolog/plc/Queens.class
[ERROR] warning: Ignoring InnerClasses attribute for an anonymous inner
class that doesn't come with an associated EnclosingMethod attribute. (This cl
ass was probably produced by a broken compiler.)
[ERROR] warning: Ignoring InnerClasses attribute for an anonymous inner
class that doesn't come with an associated EnclosingMethod attribute. (This cl
ass was probably produced by a broken compiler.)
...
BUILD ERROR
...
Embedded error: ANDROID-040-001: Could not execute: Command = cmd.exe /X /C
"C:\home\android-sdk-windows-1.5_r2\platforms\android-1.5\tools
\dx --dex --output=C:\home\workspace\my-android\target\classes.dex
C:\home\workspace\my-android\target\android-class
es", Result = 3


What version of maven-android-plugin are you using?
2.0.0-alpha6

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_07
OS name: "windows 2003" version: "5.2" arch: "x86" Family: "windows"

Please provide any additional information below.

Would be more fun developing if mojo configuration was in annotations than
trapped inside code comments.

With several projects I've tried to build, I get something similar to the 
error pasted below. I understand the error, but don't know the best way to 
solve it. I don't see why dex can't just supply an argument to discard the 
classes?

I've also tried listing every possible conflicting dependency as "provided" 
but with no luck. I've attached a pom that generates the error.


===============
[ERROR]
[ERROR] trouble processing 
"javax/xml/datatype/DatatypeConfigurationException.class":
[ERROR]
[ERROR] Attempt to include a core VM class in something other than a core 
library.
[ERROR] It is likely that you have attempted to include the core library 
from a desktop
[ERROR] virtual machine into an application, which will most assuredly not 
work. If
[ERROR] you really intend to build a core library -- which is only 
appropriate as
[ERROR] part of creating a full virtual machine binary, as opposed to 
compiling an
[ERROR] application -- then use the "--core-library" option to suppress 
this error
[ERROR] message. If you go ahead and use "--core-library" but are in fact 
building
[ERROR] an application, then please be aware that your build will still 
fail at some
[ERROR] point; you will simply be denied the pleasure of reading this 
helpful error
[ERROR] message.
[ERROR] 1 error; aborting
[INFO] --------------------------------------------------------------------
----
[ERROR] BUILD ERROR
[INFO] --------------------------------------------------------------------
----
[INFO]

Embedded error: ANDROID-040-001: Could not execute: Command = cmd.exe /X /C 
"C:\android-sdk-windows\platforms\android-1.5\tools\dx --dex --
output=c:\Users\Ben\workspace\DroidFlix\target\classes.dex 
c:\Users\Ben\workspace\DroidFlix\target\android-classes", Result = 1

trunk should not be part of the m2repo urls.

What steps will reproduce the problem?
1. Create an Android project to use as common sources from.
2. Create another Android project which depends on the first project 
(<type>apksources</type>)...You don't have to even use anything from the 
common project, just include it in this project's pom file.
3. Add an image that is just an overlay to the second projects drawable 
folder.
4. Build the common project
5. Build the 2nd project

What is the expected output?
A successful build

What do you see instead?
[ERROR] aapt: error: *** Resource file 'action_button.png' exists only in 
an overlay

What version of maven-android-plugin are you using?
2.2

What are the complete output lines of "mvn -version" on your machine?
Apache Maven 2.2.0 (r788681; 2009-06-26 08:04:01-0500)
Java version: 1.6.0_11
Java home: C:\Program Files\Java\jdk1.6.0_11\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows"

Please provide any additional information below.
If I remove the overlay image action_button.png, the build works.  The 
project builds fine in Eclipse.

Can we look at the "uses-sdk" tag in AndroidManifest.xml, and from that 
understand what the value should be for android.sdk.platform, if the user 
has not set it?

Then they would really only need to configure one thing in one place:
1. android.sdk.path in pom.xml
2. platform a.k.a. uses-sdk in AndroidManifest.xml

The mapping would look like this with a normal Android SDK 1.5 from Google:

Android SDK 1.0 = 1
Android SDK 1.1 = 2
Android SDK 1.5 = 3


What version of maven-android-plugin are you using?
2.0.0-alpha3

I've just tried running install.sh from maven-android-plugin-samples, and 
it requires maven-android-plugin/2.1.1-SNAPSHOT.
Could you either make the necessary pom's reference a repo with snapshot 
builds or downgrade requirements of the MAE plugin?
I believe getting samples and howtos to run with as little hassle as 
possible is key to adoption.

To run a specific goal in maven-android-plugin from command line, you have
to type a long command, for example "mvn
com.jayway.maven.plugins.android.generation2:maven-android-plugin:deploy".

It would be nice to be able to just type "mvn android:deploy".


What version of maven-android-plugin are you using?
2.0.0-SNAPSHOT as of 2009-06-07.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

What steps will reproduce the problem?
1. Build a maven project.
2.
3.

What is the expected output? What do you see instead?
When aapt is executed maven says:

[INFO] null/tools/aapt [package, -m, -J, 
C:\java\appstore\trunk\client\android\app\target\generated-sources\r, -M, 
C:\java\appstore\trunk\client\android\app\AndroidManifest.xml, -S, 
C:\java\appstore\trunk\client\android\app\res, -I, c:\Documents and 
Settings\Albin\.m2\repository\android\android\1.1_r1\android-1.1_r1.jar]

I have the ANDROID_HOME variable set correctly, but the plugin apparently 
ignores it.


What version of maven-android-plugin are you using?
2.0.0-alpha1

What is the output of "mvn -version" on your machine?
Maven version: 2.0.9
Java version: 1.6.0_11
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please provide any additional information below.

Write GettingStarted wiki page

Parameter names and expressions need to be consistent and easily
understandable.

What steps will reproduce the problem?
1. Mavenize the HelloAndroid Eclipse project using the attached pom. I went
for <sourceDirectory>src</sourceDirectory>
2. Enable Maven dependency management
3. Choose "Run as ... Maven install"

What is the expected output?
Build successful.

What do you see instead?
Three problems arise: 

1. Eclipse complains that "/HelloAndroid?/gen already exists but is not a
source folder. Convert to a source folder or rename it." I made
target/generated-sources/r a source folder, deactivated the android
preprocessor in Properties/Builders and the compile warnings went away. The
gen folder however is still there, and it is recreated automatically if I
try to delete it.
Maybe 

2.Maven complains about the following duplicate attachments: [WARNING]
Duplicate artifact attachment detected. (project:
org.example:maven-hello-android:apk:1.0.0-SNAPSHOT; illegal attachment:
org.example:maven-hello-android:jar:1.0.0-SNAPSHOT)
[ERROR] 

Your build attempted to attach multiple artifacts with the same classifier
to the main project.

Mojo responsible for second attachment
attempt:com.jayway.maven.plugins.android.generation2:maven-android-plugin:2.0.0:
apk

Reported for project:
Group-Id: org.example
Artifact-Id: maven-hello-android
Version: 1.0.0-SNAPSHOT
From file: C:\Dokumente und
Einstellungen\Dietrich\workspace\HelloAndroid\pom.xml


Artifact attachment:

Group-Id: org.example
Artifact-Id: maven-hello-android
Version: 1.0.0-SNAPSHOT
Type: jar
Scope: null

3. The maven-android-plugin compiles to a folder android-classes, but
m2eclipse configures eclipse to look in target/classes. Strangely that does
not seem to cause obvious errors, but it is hardly right.

What version of maven-android-plugin are you using?
2.0.0

What are the complete output lines of "mvn -version" on your machine?
C:\Programme\Windows Resource Kits\Tools>mvn -version
Maven version: 2.0.9
Java version: 1.6.0_13
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Release 2.0.0-alpha1 including site, source:jar, javadoc:jar

First - congratulations for the nice plugin !

I'm missing a feature which is not quite used if you don't work with several 
devices (emulators, phones) - the possibility to specify the target device 
for adb.
For example at command line it looks like: adb -s emulator-5554 shell.

It would be nice if this could be specified as a system property.

What steps will reproduce the problem?
1. In the pom, change the outputDirectory used for the maven builds to bin 
(this is the default 
folder for ant builds and eclipse so the minimal overhead for a multi build 
environment).
2. Run the command mvn:apk or any command that depends on it (such as mvn 
install).

What is the expected output?
I expect the command passed to apkbuilder to use the outputDirectory setting in 
the pom, not 
the default setting (target).

What do you see instead?
The following output is printed to the shell:
[INFO] ~/android-home/tools/apkbuilder 
[~/code/android-project/target/mds-android-
0.2.0.apk, -z, ~/code/android-project/target/mds-android-0.2.0.ap_, -f, 
~/code/android-
project/target/classes.dex, -rf, ~/code/android-project/target/classes]
[ERROR] ~/code/android-project/target/classes does not exist!

What version of maven-android-plugin are you using?
2.2.1


What are the complete output lines of "mvn -version" on your machine?
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_15
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.6.2" arch: "x86_64" Family: "mac"


Please provide any additional information below.
This is working fine when the output directory is unchanged so it's a low 
priority issue.

What steps will reproduce the problem?
1. Build a project using the Android Maven plugin.
2. Look for an error message of the form:
[ERROR] Using keystore: <your Android metadata parent
directory>\.android\debug.keystore
3. Note that the build continues past that error message, and succeeds.

What is the expected output?

If it really is an error, the build should fail. If it isn't an error, it
shouldn't be reported as an error. Perhaps it should be a warning?

What do you see instead?

An error message that appears to not actually be an error.

What version of maven-android-plugin are you using?

2.2.0

What are the complete output lines of "mvn -version" on your machine?

Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
Java version: 1.6.0_15
Java home: C:\devjim\tools\java\jdk1.6.0_15\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

What steps will reproduce the problem?
1. Create a maven project with "apk" packaging

What is the expected output?
A generated .apksources file does not contain .svn files

What do you see instead?
A generated .apksources file contains .svn files

What version of maven-android-plugin are you using?
2.2.1

What are the complete output lines of "mvn -version" on your machine?
E:\>mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 16:16:01-0300)
Java version: 1.6.0_06
Java home: C:\java\jdk1.6.0_06\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please provide any additional information below.
--

What steps will reproduce the problem?
1. Configure project with dependency
2. Run mvn android:deploy
3. Execute code relying on class

What is the expected output?
Normal execution

What do you see instead?
I'm getting a NoClassDefFoundError. The class in question is
javax.servlet.http.Coookie. If I browse through the android-classes
directory, I do see this class present.

What version of maven-android-plugin are you using?
2.0.0-rc1

What is the output of "mvn -version" on your machine?
Maven version: 2.0.9
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-13-generic" arch: "i386" Family: "unix"


Please provide any additional information below.
I am building a project off of the Bayeux cometd library.

What steps will reproduce the problem?

1. Create a Maven Android project as per usual.
2. Configure the maven-android-plugin to use either 1.6 or 2.0 of the Android 
SDK.
3. Configure the POM to use Android jar version 1.6 or 2.0.
4. Set the version of the plugin to 2.1.0 or 2.2.0.

What is the expected output?

[INFO] BUILD SUCCESSFUL

What do you see instead?

[ERROR] java.util.zip.ZipException: duplicate entry: AndroidManifest.xml
[INFO] ----
[ERROR] BUILD ERROR


What version of maven-android-plugin are you using?

I tried versions 2.1.0 and 2.2.0 and they both failed. Version 2.0.0 does work 
(thanks for writing 
this plugin!).

What are the complete output lines of "mvn -version" on your machine?

Maven version: 2.0.9
Java version: 1.6.0_15
OS name: "mac os x" version: "10.6.1" arch: "x86_64" Family: "mac"

I've also tried this with Maven 2.2.1 with the same outcomes.

Please provide any additional information below.

The problem is definitely the version of plugin used. Simply switching from 
2.2.0 to 2.0.0 back to 
2.2.0 I can turn on/off the success/fail of the build.

It would be nice to be able to start and stop an emulator from the
maven-android-plugin. Then it could be automatically started/stopped
before/after the platform tests.

What version of maven-android-plugin are you using?
2.0.0-SNAPSHOT as of 2009-06-07.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

Rather than recommending users copy the sample template and edit it, we 
could create an archetype for maven-android-plugin.  

Really the archetype can probably even create the base android project, if 
we want to go that far (or it can just create the pom and any other maven 
specific setup, and can still recommend users create android proj 
separately). 

What steps will reproduce the problem?
1.adding ksoap2 dependency in POM
2.initializing new SoapObject in source code
3.Debug android project using Eclipse IDE

What is the expected output?
Application should start. No log errors.

What do you see instead?
Log error: org.ksoap2.serialization.SoapObject referenced from method
rs.belex.belexdroid.Init.onCreate

What version of maven-android-plugin are you using?
2.2.2

What are the complete output lines of "mvn -version" on your machine?
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_17
Java home: C:\Program Files\Java\jdk1.6.0_17\jre
Default locale: sr, platform encoding: Cp1250
OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"

Please provide any additional information below.
If I add jar to my project from Google project ksoap2-android:
ksoap2-android-assembly-2.3-jar-with-dependencies.jar instead of maven
dependency for ksoap2, application starts normally. My guess is that some
reference error is related to maven library while using dependency for
ksoap2-android.

What steps will reproduce the problem?
1. Get an apk to your hard drive somehow, for example by building one of 
the samples: See wiki page Samples.
2. Make sure the maven-android-plugin is in your local ~/.m2/repository, 
for example by building one of the samples in step 1, which will cause it 
to get downloaded. (When the synk to Maven Central is complete, this step 
would not be needed.)
3. Go to a directory with no pom.xml in it.
4. Try running the android:undeploy-file goal, like this:

mvn com.jayway.maven.plugins.android.generation2:maven-android-
plugin:2.0.0-alpha3:undeploy-file -Dfile=maven-android-plugin-
samples/apidemos-15/apidemos-15-platformtests/target/apidemos-15-
platformtests-2.0.0-alpha3.apk

What is the expected output? What do you see instead?
The plugin should look inside the apk and try undeploying it from a 
connected device.

Instead, I get this:

[INFO] Scanning for projects...
[INFO] --------------------------------------------------------------------
----
[INFO] Building Maven Default Project
[INFO]    task-segment: 
[com.jayway.maven.plugins.android.generation2:maven-android-plugin:2.0.0-
alpha3:undeploy-file] (aggregator-style)
[INFO] --------------------------------------------------------------------
----
[INFO] [android:undeploy-file]
[INFO] --------------------------------------------------------------------
----
[ERROR] FATAL ERROR
[INFO] --------------------------------------------------------------------
----
[INFO] null
[INFO] --------------------------------------------------------------------
----
[INFO] Trace
java.lang.NullPointerException
        at 
com.jayway.maven.plugins.android.AbstractAndroidMojo.extractPackageNameFrom
Apk(AbstractAndroidMojo.java:274)
        at 
com.jayway.maven.plugins.android.AbstractAndroidMojo.undeployApk(AbstractAn
droidMojo.java:218)
        at 
com.jayway.maven.plugins.android.AbstractAndroidMojo.undeployApk(AbstractAn
droidMojo.java:205)
        at 
com.jayway.maven.plugins.android.standalonemojos.UndeployFileMojo.execute(U
ndeployFileMojo.java:41)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag
er.java:453)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif
ecycleExecutor.java:559)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(D
efaultLifecycleExecutor.java:513)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife
cycleExecutor.java:483)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai
lures(DefaultLifecycleExecutor.java:331)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def
aultLifecycleExecutor.java:228)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl
eExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at 
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] --------------------------------------------------------------------
----
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Jun 18 21:30:20 CEST 2009
[INFO] Final Memory: 14M/133M
[INFO] --------------------------------------------------------------------
----


What version of maven-android-plugin are you using?
2.0.0-alpha3

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"


Please use labels and text to provide additional information.

The problem is that in AbstractAndroidMojo, the config parameter "sdk" is 
only set to a non-null value if there is a pom.xml with an <sdk/> tag in 
the plugin configuration. Right now, we get this NPE when trying to read 
from the config parameter field we thought would refer to an Sdk 
configuration object.

What steps will reproduce the problem?
1. Use the Eclipse Android plugin to create an Eclipse Android project and
an Eclipse Android test project.
2. Create POMs for the two projects and configure the Android maven plugin
for both projects.
3. Build the projects with maven and run the unit tests with maven.

What is the expected output?

The tests should run from maven the same as they run from Eclipse.

What do you see instead?

The tests run fine in Eclipse, but they fail in maven with errors as follows:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running com.sample.tests.ExampleTest
org.apache.maven.surefire.booter.SurefireExecutionException:
com.sample.tests.ExampleTest; nested exception is
java.lang.RuntimeException: Stub!; nested exception is
org.apache.maven.surefire.testset.TestSetFailedException:
com.sample.tests.ExampleTest; nested exception is
java.lang.RuntimeException: Stub!
org.apache.maven.surefire.testset.TestSetFailedException:
com.sample.tests.ExampleTest; nested exception is
java.lang.RuntimeException: Stub!
java.lang.RuntimeException: Stub!
        at junit.framework.TestSuite.<init>(TestSuite.java:7)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
        at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorI
mpl.java:
39)
        at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorA
ccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at
org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject(JUnitTestSet.ja
va:151)
        at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:197)
        at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(Abstra
ctDirectoryTestSuite.java:140)
        at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirec
toryTestSuite.java:127)
        at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBoote
r.java:345)
        at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

What version of maven-android-plugin are you using?

2.2.0

What are the complete output lines of "mvn -version" on your machine?

Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
Java version: 1.6.0_15
Java home: C:\devjim\tools\java\jdk1.6.0_15\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please provide any additional information below.

The Samples are cited across the wiki and should be nice and simple to
build. I could only get them to build by replacing all version occurrences
of <version>2.1.1-SNAPSHOT</version> with <version>2.1.0</version>

In order to encourage adoption and ease introduction the samples should be
based upon a stable tag so that users first experience is as painless as
possible as there is no guarantee the users previous experience in maven2. 

What steps will reproduce the problem?
1. Do not set <sdk><path> value in pom.xml
2. Run "mvn package -Dandroid.sdk.path=C:/java/android-sdk-windows-1.6_r1"

What is the expected output?
C:/java/android-sdk-windows-1.6_r1 should be taken as <sdk><path> value.

What do you see instead?
[ERROR] FATAL ERROR
[INFO] Please provide a proper Android SDK directory path as configuration
parameter <sdk><path>...</path></sdk> in the plugin <configuration/>. As an
 alternative, you may add the parameter to commandline: -Dandroid.sdk.path=...

What version of maven-android-plugin are you using?
2.1.0

What are the complete output lines of "mvn -version" on your machine?
Apache Maven 2.2.1 (r801777; 2009-08-06 16:16:01-0300)
Java version: 1.6.0_06
Java home: C:\java\jdk1.6.0_06\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please provide any additional information below.

Release 1.0.1 including source:jar and javadoc:jar

What steps will reproduce the problem?
1. mvn install
2. mvn deploy
3.

What is the expected output?
Should deploy the built apk to device.

What do you see instead?
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'android'.
[INFO] --------------------------------------------------------------------
----
[INFO] Building My Project Name
[INFO]    task-segment: [android:deploy]
[INFO] --------------------------------------------------------------------
----
[INFO] [android:deploy]
[INFO] --------------------------------------------------------------------
----
[INFO] BUILD SUCCESSFUL
[INFO] --------------------------------------------------------------------
----
[INFO] Total time: 5 seconds
[INFO] Finished at: Tue Jun 23 10:30:57 CEST 2009
[INFO] Final Memory: 14M/133M
[INFO] --------------------------------------------------------------------
----


What version of maven-android-plugin are you using?
2.0.0-alpha6-SNAPSHOT

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-13-generic" arch: "i386" Family: "unix"


Please use labels and text to provide additional information.

Other software might put R.java and java files generated from aidl files,
into src/main/java, which is the wrong place to keep dynamically generated
source code. Currently, maven-android-plugin works around that fact by
deleting conflicting files.

We should see if there is a way to not have to delete those files, and
still work correctly.


What version of maven-android-plugin are you using?
2.0.0-SNAPSHOT as of 2009-06-07.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

What steps will reproduce the problem?
1. Follow the steps on
http://code.google.com/p/maven-android-plugin/wiki/GettingStarted and
http://code.google.com/p/maven-android-plugin/wiki/Samples
2. Run mvn install in apidemos-15
3. Build fails with the message that an import could not be found


What is the expected output?
Build should succeed

What do you see instead?
[INFO] C:\programme\android-sdk-windows-1.5_r2\platforms\android-1.5/tools/aapt
[package, -m, -J,
G:\jayway-maven-android-plugin-samples\apidemos-15\apidemos-15
-app\target\generated-sources\r, -M,
G:\jayway-maven-android-plugin-samples\apid
emos-15\apidemos-15-app\AndroidManifest.xml, -S,
G:\jayway-maven-android-plugin-
samples\apidemos-15\apidemos-15-app\res, -A,
G:\jayway-maven-android-plugin-samp
les\apidemos-15\apidemos-15-app\assets, -I,
C:\programme\android-sdk-windows-1.5
_r2\platforms\android-1.5\android.jar]
[ERROR] libpng warning: Ignoring attempt to set cHRM RGB triangle with zero
area

[ERROR]
G:\jayway-maven-android-plugin-samples\apidemos-15\apidemos-15-app\src\m
ain\java\com\example\android\apis\app\IRemoteService.aidl:19: couldn't find
impo
rt for class com.example.android.apis.app.IRemoteServiceCallback

What version of maven-android-plugin are you using?
2.0.0

What is the output of "mvn -version" on your machine?
2.0.9

Please provide any additional information below.
It seems the IRemoteServiceCallback is indeed missing, there is neither an
aidl nor a java file com\example\android\apis\app\IRemoteServiceCallback in
the sample code

I was able to convert my eclipse-generated HelloAndroid sample to a maven
project, though. I used the attached pom.

What steps will reproduce the problem?
1. Don't have an Android SDK installed and environment variable set up.
2. Want to use maven-android-plugin on an automated system, for example
continuous integration server such as Hudson http://hudson.dev.java.net
with minimal preinstallation of tools like Android SDK.
3.

What is the expected output? What do you see instead?
Maven-android-plugin should try downloading an Android SDK from a Maven
repo automatically if no ANDROID_SDK environment variable is set. It doesn't.

What version of maven-android-plugin are you using?
2.0.0-SNAPSHOT as of 2009-06-07.

What is the output of "mvn -version" on your machine?
Maven version: 2.0.10
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-11-generic" arch: "i386" Family: "unix"

Set up synchronization to maven central, so that users won't have to add
our maven repo to their configuraion.

http://maven.apache.org/guides/mini/guide-central-repository-upload.html

What steps will reproduce the problem?
1. run 'mvn help:describe -
Dplugin=com.jayway.maven.plugins.android.generation2:maven-android-plugin -
Ddetail'

What is the expected output?
 - a correct report of the plugin's goals and goal arguments

What do you see instead?
 - the report is complete, but all goals and their arguments are being 
reported as 'deprecated', which is not true.

What version of maven-android-plugin are you using?
 - 2.2.0

What are the complete output lines of "mvn -version" on your machine?

Apache Maven 2.2.1 (rdebian-1)
Java version: 1.6.0_0
Java home: /usr/lib/jvm/java-6-openjdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.31-14-generic" arch: "i386" Family: "unix"

What steps will reproduce the problem?
1. Set up your development environment according to GettingStarted, without 
setting PATH.
2. Build and run through the Samples.
3.

What is the expected output?
It should work.

What do you see instead?
[INFO] [android:platformTest]
[INFO] adb [shell, am, instrument, -w, 
com.example.android.apis.tests/android.test.InstrumentationTestRunner]
[ERROR] 'adb' is not recognized as an internal or external command,
[ERROR] operable program or batch file.
[ERROR]
[ERROR] 'adb' is not recognized as an internal or external command,operable 
program or batch file.
[INFO] --------------------------------------------------------------------
----
[ERROR] BUILD FAILURE
[INFO] --------------------------------------------------------------------
----

What version of maven-android-plugin are you using?
2.0.0-alpha4

What is the output of "mvn -version" on your machine?
Maven version: 2.0.9
Java version: 1.6.0_14
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Please use labels and text to provide additional information.