Find my answers in your e-mail:

Le 19/09/2011 15:20, darakok a écrit :
This is part of my POM file where i specify the version of Android API jar
file to compile with.

<plugin>
                                        
<groupId>com.jayway.maven.plugins.android.generation2</groupId>
                                        
<artifactId>maven-android-plugin</artifactId>
                                        <version>2.9.0-beta-5</version>
                                        <configuration>
                                                <sdk>
                                                        <platform>8</platform>
                                                </sdk>
                                                
<deleteConflictingFiles>true</deleteConflictingFiles>

                                                
<resourceDirectory>${project.build.directory}/filtered-resources
                                                </resourceDirectory>
                                        </configuration>
                                        <extensions>true</extensions>
                                </plugin>
Ok, so If you change here to 11, it does not modify the classpath of the maven compiler plugin. It simply informs thet maven android plugin that you are targetting the level 11. The jar used by the maven compiler is defined in your dependencies.

I'm sure the correct Android jar file is used to compile my project because
it shows the jar file path in the console just before the error comes up.
Interestingly, that same jar file is reference in my project in eclipse and
Eclipse recognize the method that I have problem with when building with
maven.
Can't really know what's going on here since you have not posted your dependencies and since we don't know where Maven resolves your artifacts (if you installed the jars manually, you can put whatever version you want and therefore have an the wrong jar). Eclipse is of no use here because you can easily add jars through other means (add a jar, add a library container, etc...). Actually, if you have such external (to Maven) dependency , you should remove it because they are not portable from one IDE to another and mainly because this will not be reflected in your Maven build (probably indicates why you are having some issues in your build now).


--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818946.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Cheers,
Guillaume

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to