#6300 closed change (fixed)

Remove Maven and Ant support

Reported by: asmirnov Assignee:
Priority: P3 Milestone:
Module: Libadblockplus-Android Keywords:
Cc: Blocked By:
Blocking: #5139, #6000 Platform: Android
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

https://codereview.adblockplus.org/29677586/

Description

Background

We still support Maven and Ant as build tools (see pom.xml and build.xml).
They are deprecated nowadays and Android projects use Gradle.
Ant support has been removed from latest Android SDKs (see #5139).

However it's preferred to have AARs pushed in local maven repo after built by Gradle.

What to change

Remove Maven and Ant support, push AARS to local maven repo.

Change History (7)

comment:1 Changed 22 months ago by asmirnov

Since we have lot's of build variants (ARCH x BuildType) = 3 x 2 = 6 which ones should we push to maven repository?
Let's say it's debug build for ARM. Should we push AAR to repo? Should we push only 'abi_all' + Release only?

Also we have to add Maven module dependencies properly and it seems to be not trivial task as we have to map Gradle modules to Maven modules.

comment:2 Changed 22 months ago by asmirnov

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:4 Changed 22 months ago by asmirnov

  • Blocking 6000 added

comment:5 Changed 22 months ago by asmirnov

Discussed it with Diego.
According to #6205 we're going to publish artifacts in bintray (or any other external Maven repository).
So no push to local Maven repo is required.

comment:7 Changed 22 months ago by asmirnov

  • Resolution set to fixed
  • Status changed from reviewing to closed
Note: See TracTickets for help on using tickets.