So in the end, I just separated my wrapper utility into a small maven
project upon which the plugin depends. I was hoping not to do it,
since it's basically two classes, but it's likely the right way to
handle it anyway. Thanks for the suggestions.
Incidentally, the plugin expression is b
I thought that was available under the parameter expression $
{plugin}, which returns the current plugin's PluginDescriptor
instance...from there, I thought there was an accessor method that
exposed the artifacts used to create that plugin's classpath...
Maybe I'm dreaming, or maybe it's cha
Hey,
I'm trying to use pluginArtifacts to include the current plugin's
jar as a classpath for an external call, as I have created a crazy but
necessary wrapper. When I go to find the plugin in pluginArtifacts, I
find that I cannot, and that pluginArtifacts is not populated on
MavenPro
