Wrong .. the Android Maven Plugin is fully capable of creating aar files as
well as consuming them as a dependency (or transitive dependency). Problem is
that the pom created by Gradle does not specify the dependencies correctly.
Manfred
Robert Patrick wrote on 08.12.2014 08:40:
> The problem
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67438782
See http://jira.codehaus.org/browse/MNG-5738
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
GitHub user ChristianSchulte reopened a pull request:
https://github.com/apache/maven/pull/32
[MPIR-238] Addition of command line flag '--legacy-reactor-resolution'.
See http://jira.codehaus.org/browse/MPIR-238
This pull request will add a new command line flag
'--legacy-re
Github user ChristianSchulte closed the pull request at:
https://github.com/apache/maven/pull/32
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Yes, this definitely helps, Stephen. Thanks for your detailed and
well-written explanation. I appreciate it much.
Cheers,
Paul
On Wed, Dec 17, 2014 at 9:22 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> On Wednesday, December 17, 2014, Paul Benedict
> wrote:
>
> > Stephen, I
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/32
[MPIR-238] Addition of command line flag '--legacy-reactor-resolution'.
See http://jira.codehaus.org/browse/MPIR-238
This pull request will add a new command line flag
'--legacy-reac
Hi,
We solved 1 issue:
https://jira.codehaus.org/browse/MPLUGINTESTING-44
There are no issues left in JIRA
Staging repo:
https://repository.apache.org/content/repositories/maven-1106/
http://repository.apache.org/content/repositories/maven-1106/org/apache/maven/plugin-testing/maven-plugin-test
Sorry Igor, I see now I omitted a chunk of context.
The reason for the error is that this component :
com.android.support
support-v13
21.0.2
aar
has a dependency upon
com.android.support
support-v4
21.0.2
Am 2014-12-17 um 21:54 schrieb Karl Heinz Marbaise:
Hi Michael,
On 12/17/14 8:56 PM, Michael Osipov wrote:
Karl Heinz,
is this going to be hopefully the final release of the plugin?
Why ?
Burrying Ant support was overdue -- and why should we be able to
generate Ant build files from POMs at
Hi Michael,
On 12/17/14 8:56 PM, Michael Osipov wrote:
Karl Heinz,
is this going to be hopefully the final release of the plugin?
Why ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache
On 17 Dec 2014, at 20:55, Jason van Zyl wrote:
> +1 from Jason, Stephen, and Karl
+1 from me as well - outside of querying that strange tycho thing I had. 3.2.5
is looks sweet. Will be glad to not get dependency resolution locking!
--
Mark Derricutt
http://www.theoryinpractice.net
http://plus.
Am 2014-12-13 um 23:48 schrieb Michael Osipov:
Hi folks,
I have been working recently on Maven Project Info Reports Plugin and
fixed a bunch of issues. Those which are still open I requested
participants to respond whether the issues are still valid. If no one
responds, I will "won't fix" them.
Karl Heinz,
is this going to be hopefully the final release of the plugin?
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1 works with the Android Maven Plugin and a bunch of other projects.
Hervé BOUTEMY wrote on 17.12.2014 07:08:
> +1
>
> Regards,
>
> Hervé
>
> Le dimanche 14 décembre 2014 13:00:12 Jason van Zyl a écrit :
>> Hi,
>>
>> Time to release Maven 3.2.5!
>>
>> Here is a link to Jira with 22 issues r
On Wednesday, December 17, 2014, Paul Benedict wrote:
> Stephen, I don't feel strongly about it but I don't think there is another
> option. Unlike assembly:single which is used to create multiple
> distributions, this is about creating an artifact destined to be consumed
> as a dependency. Corre
Stephen, I don't feel strongly about it but I don't think there is another
option. Unlike assembly:single which is used to create multiple
distributions, this is about creating an artifact destined to be consumed
as a dependency. Correct me if wrong, but Maven artifact types are meant to
produce on
+1
Regards,
Hervé
Le dimanche 14 décembre 2014 13:00:12 Jason van Zyl a écrit :
> Hi,
>
> Time to release Maven 3.2.5!
>
> Here is a link to Jira with 22 issues resolved:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=20
> 819
>
> Staging repo:
> https://repositor
For JIRA there is an easier way to handle this: you rename the
version(s) in JIRA.
If 3.2.4 fails, rename it to 3.2.5.
Additionally if there are more future patch versions in JIRA, then
they need to be renamed first.
If 3.2.4 fails , and in JIRA we have 3.2.4, 3.2.5 and 3.2.6, then we
end up wit
GitHub user vlsi opened a pull request:
https://github.com/apache/maven-plugins/pull/40
Avoid overwrite of the destination file if the produced contents is the same
maven-remote-resource-plugin is used in Apache pom to add DEPENDENCIES, and
the resulting file is overwritten on each
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Hervé Boutemy, Kristian Rosenvold
I will promote the artifacts to the central repo and continue the release.
Kristian
2014-12-17 9:14 GMT+01:00 Kristian Rosenvold :
> +1
>
> 2014-12-16 1:30 GMT+01:00 Hervé BOUTE
+1
2014-12-16 1:30 GMT+01:00 Hervé BOUTEMY :
> +1
>
> Regards,
>
> Hervé
>
> Le samedi 13 décembre 2014 10:33:24 Kristian Rosenvold a écrit :
>> Hi,
>>
>> We solved 21 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20790&styleName=Htm
>> l&projectId=11126
>>
>> This release is
21 matches
Mail list logo
