[
http://jira.codehaus.org/browse/MNG-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4607.
----------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
This is bug in the metadata of the Android plugin which goes unnoticed in Maven
2. Without the mojo annotation {...@requiresdependencyresolution}}, a mojo must
not make any assumptions about the resolved artifacts. This has apparently been
already fixed on the plugin side in 2bfafb1c86c4415ec3ea91174bdc15742a7c4496.
> Regression: Maven Android Plugin dependency pull in fails under maven3alpha7
> ----------------------------------------------------------------------------
>
> Key: MNG-4607
> URL: http://jira.codehaus.org/browse/MNG-4607
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0-alpha-7
> Environment: Macosx, Maven 3 alpha 7 from apache, Maven 2.2.1 from
> macports
> Reporter: Manfred Moser
> Assignee: Benjamin Bentmann
>
> The maven android plugin is supposed to pull in external dependencies during
> its build to extract the class files and convert them to dx files. With maven
> 3 alpha 7 this does however not happen. With 2.2.1 it works fine.
> I have filed an issue on the plugin page
> http://code.google.com/p/maven-android-plugin/issues/detail?id=57
> I am also a committer on the plugin and willing to help. However I do not
> know where to start - with the maven android plugin and the config or
> dependencies of it, maven 3 itself or potentially somehow with the dependency
> plugin.
> What can I provide to give more details?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
