It's a huge pain in the butt - but you can't (yet). Plugin separation of
the classloaders has been on the cards for a long while, but when I
implemented it in pre-1.0 I found a large number of projects started
breaking because they had come to depend on plugin's dependencies being
present :)
I
Greetings.
Perhaps there is some document that tells me how to fix this problem,
and I haven't stumbled across it yet.
Here is the situation:
I'm the author of an enhancement (that was incorporated in the latest
release) to the javadoc plugin that produces a report on the javadoc
warning in the
Greetings.
Perhaps there is some document that tells me how to fix this problem,
and I haven't stumbled across it yet.
Here is the situation:
I submitted an enhancement (that was incorporated in the latest release)
to the javadoc plugin that produces a report on the javadoc warning in
the same
