Add parameter to lifecycleParticipant

Following on #422 

It adds the ability to use parameters in the pom to customize the way the lifecycleParticipant deals with dependencies in the libs folder of the apklib/aar

This is now complete.
I thought recalled other code that parsed the plugin config in the pom.

If so, that would be an immediate consumer.

But just on general OO principles it is better to have the config
consumption in its own class. Much easier to understand wtf is going on.

In
src/main/java/com/jayway/maven/plugins/android/phase_prebuild/ClasspathModifierLifecycleParticipant.java:

> @@ -151,6 +176,28 @@ else if ( type.equals( AndroidExtension.APKLIB ) && includeLibsJarsForApklib )
>          log.debug( "ClasspathModifierLifecycleParticipant#afterProjectsRead - finish" );
>      }
>
> +    protected String getPluginId()
> +    {
> +        return "android-maven-plugin";
> +    }
> +
> +    protected Xpp3Dom getMojoConfiguration( Plugin plugin )

Do we really want to make a Helper class for something that will only be
used in a LifecycleParticipant? I don't think we'll have another
Participant and if we do we might want to extract that at that moment no?

—
Reply to this email directly or view it on GitHub
<https://github.com/jayway/maven-android-plugin/pull/445/files#r17180495>.