Yeah, I was mistaken. I'm working on clearing up the confusion, but
basically it got changed somewhere between 2.0.x branch and today in
trunk.
-john
On Mar 3, 2008, at 12:19 PM, Benjamin Bentmann wrote:
I'd like to know how many people are using ${plugin.artifacts} in
their plugins.
One
All I can say is, OOPS!
I wasn't completely aware of this, but the plugin-classloader
construction logic changed in the trunk of maven from 2.0.x. It seems
that during the course of these changes the plugin manager stopped
managing the PluginDescriptor's artifacts collection as closely.
I'd like to know how many people are using ${plugin.artifacts} in
their plugins.
One here, basically for a use-case similar to MANTRUN-41 on some in-house
plugin.
This would mean that all of a sudden things like maven-plugin-api and
maven-project will start appearing in the result of $
{plugin
I'd like to know how many people are using ${plugin.artifacts} in
their plugins.
I just came across a use case for plugin development, where the
developer needs access to the full dependency list for the plugin
using ${plugin.artifacts}. This is a problem because Maven currently
applies a
