Hi Thomas,
I'm revoking my comments and my "-1" ... :-(
+) the maven-jcoverage-plugin is in my repo and is used suddenly used by
maven-1.1
+) maven-1.0.2 seems to ignore the default target defined in the
project.xml but maven-1.1 issues a deprecation warning
+) I'm also not able to reproduce the PMD issues either
As a side note - I accidentally setup maven-1.0.2 and maven-1.1 to use
the same local repository and it seems that causes me some problems
(e.g. unable to generate a valid idea project file on the one box but
not on the other). I will need to cleanly separate those instances
before making statements such as "the build is broken" - AFAIK there is
no way to nail down the plugin dependencies so the build can fail on a
box unexpectedly. One more reason to push M2 ...
PS: Having said that I'm pretty sure that a maven-1.1 user with a clean
repository is unable to build the site so I would recommed not to use
the maven-jcoverage-plugin
Thomas Vandahl wrote:
Siegfried Goeschl wrote:
Hi Thomas,
sorry if I sound like a complete a**hole but I *hate* build scripts
printing warnings and deprecation. The warning is the bug you chase
next week and the deprecation is the broken build in two months time
... :-(
Yes, I have to admit that parts of my spinal chord were thinking in
that direction... Anyway, we are talking about a maven-plugin that has
been around for years and will not stop to be around just because it
may be obsolete. After all, it's not the plugin we vote about but the
artifact.
Since today is my Open Source Day I' will have a look at the PMD
issue you don't have ...
Just a side comment: I would not spent too much effort removing *all*
PMD warnings. Some of them are plain silly. Once more: I see no
warnings in the PMD report at the site. Does your PMD-plugin do
different things than mine?
Siegfried Goeschl wrote:
2) are you using maven-1.1 or maven-1.0.2 - maven-1.1 complains
about the default goal defined in maven.xml
The build was done using maven 1.0.2. This version needs the default
goal in maven.xml. So you are telling me that I should break my build
to remove a warning in yours?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
