Thanks!
-Lukas
Anders Hammar wrote:
I'm pretty sure you're close to pissing some people off. "why hasn't this
been fixed yet" and "When is it going to be fixed" is not the right wording
for open source projects where you're not shipping in anything yourself.
Creating jiras and providing patches (with test cases) is the way to go.
/Anders
On Wed, May 19, 2010 at 19:05, Tim Fulmer<[email protected]> wrote:
Hello,
Yesterday we noticed an error when running mvn site to generate cobertura
reports to track down some coverage issues. Turns out this was caused by a
snapshot update mandated by the special way Maven handles plugin
versioning.
Things got even more special when trying to specify a version of
org.apache.maven.plugins:maven-project-info-reports-plugin. Turns out
plugin management doesn't work for reporting. The version specified in
plugin management is ignored in reporting and the current version is used.
Even though the current documentation on configuring reporting shows a
plugin management configuration. The solution was to spam a version
configuration across 20 some odd POM files. I'm sure we missed a few.
This isn't the first time we've been bitten by Maven's special plugin
versioning and dependency management. Other's have ongoing issues with
this
as well. My question is why hasn't this been fixed yet? Why is plugin
management the one place where Maven's own versioning and dependency
management practices are completely ignored in favor of something that's
obviously broken? When is it going to be fixed?
-- Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
