>
> Probably the same way as in 6cd539b. Now, that was just passing a
> classpathref= to an existing plugin. Writing a new plugin, you may
> have to figure out what the plugin needs to /do/ with the classpathref,
> but the maven-antrun-plugin source must contain the answer somewhere.
>
I looked into the maven-antrun-plugin. The relevant part is here
<https://github.com/apache/maven-antrun-plugin/blob/8e5b3c613e96c20881347ec16813864a2d8ef0bb/src/main/java/org/apache/maven/plugins/antrun/AntRunMojo.java#L364>.
It adds the classpaths as a reference to an instance of an Ant Project. The
documentation
<https://ant.apache.org/manual/api/org/apache/tools/ant/Project.html#addReference(java.lang.String,java.lang.Object)>
for which is not very illuminating. After that, it just executes the tasks
on the Ant Project. I'll keep digging further to find something useful. I
also found https://issues.apache.org/jira/browse/MANTRUN-200 and
https://issues.apache.org/jira/browse/MNG-6275. I think these might be
relevant to the problem as well. I have also pushed the changes. I suspect
I might be doing something wrong in the integration itself which might be a
cause of this.
Regards,
Kartik.