Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for the D8 compiler integration #787

Merged
merged 1 commit into from
May 6, 2019

Conversation

cfiehe
Copy link

@cfiehe cfiehe commented Apr 10, 2019

This commit fixes the D8 compiler integration. Because the D8 compiler options differ from those provided by the dex compiler, the <dex> tag cannot be used for D8 configuration. There is no way to set e.g. the minApi within the <dex> tag, because the DexMojo defines no corresponding parameter. This commit separates the two configurations and introduces a new <d8> tag for D8 compiler configuration.

If you want to use the D8 compiler, you can use the following plugin configuration in your pom:

<dexCompiler>d8</dexCompiler>
<d8>
    <minApi>26</minApi>
    ...
</d8>

Signed-off-by: Christoph Fiehe [email protected]

This commit fixes the D8 compiler integration. Because the D8 compiler options differ from those provided by the dex compiler, the <dex> tag cannot be used for D8 configuration. There is no way to set e.g. the minApi within the <dex> tag, because the DexMojo defines no corresponding parameter. This commit separates the two configurations and introduces a new <d8> tag for D8 compiler configuration.

If you want to use the D8 compiler, you can use the following plugin configuration in your pom:
<dexCompiler>d8</dexCompiler>
<d8>
    <minApi>26</minApi>
    ...
</d8>

Signed-off-by: Christoph Fiehe <[email protected]>
@mosabua
Copy link
Member

mosabua commented May 3, 2019

From what I can tell this is an incompatible change right? So users are forced to update their pom if they adopt this potentially new release of the plugin.

@mosabua
Copy link
Member

mosabua commented May 3, 2019

@william-ferguson-au what do you think... this seems a follow up to your PR https://github.com/simpligility/android-maven-plugin/pull/781/files

@cfiehe
Copy link
Author

cfiehe commented May 3, 2019

There are no changes necessary for all those users who migrate to a follow-up release containing this extension. If you do not specify the dexCompiler, dex gets used by default. The existing dex element is still valid, has the same configuration properties and refers to the same Mojo as before. The new d8 element is just a replacement.

@william-ferguson-au
Copy link
Contributor

Sorry @mosabua I'm too tired to reason this one through.

@mosabua mosabua merged commit a6549ff into simpligility:master May 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants