search

pitate7777777 / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

Can't bind plugin execution to run in pre-integration-test before internal-pre-integration-test #415

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a plugin execution (any plugin) bound to pre-integration-test phase.
2. mvn verify
3. maven-android-plugin's internal-pre-integration-phase goal is run before 
plugin executions specified in the POM.

What is the expected output?
That the plugin executions specified in the POM are run before 
maven-android-plugin's internal ones.

What do you see instead?
Maven-android-plugin's built-in executions are run before the ones specified in 
the POM

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

What are the complete output lines of "mvn -version" on your machine?
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: /opt/jdk1.6.0_45/jre
Default locale: en_CA, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-34-generic", arch: "amd64", family: "unix"

Please provide any additional information below.
I'm trying to use maven-android-plugin in conjunction with Android-x86 
(www.android-x86.org). For this I've written a plugin (androidx86-maven-plugin) 
that will start and stop QEmu running an Android system image. My plugin will 
start and stop QEmu in the pre-integration-test and post-integration-test 
phases by default, respectively. Unfortunately, maven runs 
maven-android-plugin's "default-internal-pre-integration-test" execution before 
my plugin invocation, which results in the build failing because there's no 
device connected to ADB (my plugin sets up ADB as well).

Original issue reported on code.google.com by cein...@gmail.com on 20 Aug 2013 at 2:32

GoogleCodeExporter commented 9 years ago 
I've worked around the issue by cloning maven-android-plugin's components.xml 
and adding my goals to the lifecycle phases, but this is sub-optimal for now. 
:-(

Original comment by cein...@gmail.com on 20 Aug 2013 at 6:59

GoogleCodeExporter commented 9 years ago 
The android maven plugin already has a emulator start and stop goal. Why not 
use that? Also the order can not be changed .. Maven works that way that 
components.xml goes before config in the pom..

Original comment by mosa...@gmail.com on 18 Sep 2013 at 4:16