-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Fox wrote:
Therefore I think that
the pluginManagement in Super-Pom caused some
trouble and confusion that you might not be aware of.
It should use the version even if you invoke directly from the command
line, if not, that's a separate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
On Fri, Jul 24, 2009 at 4:36 PM, Joerg Hohwillerjo...@j-hohwiller.de wrote:
Hi there,
I read the documentation of javadoc-plugin about goal aggregate.
Then I called
mvn javadoc:aggregate and maven failed saying that the goal
Therefore I think that
the pluginManagement in Super-Pom caused some
trouble and confusion that you might not be aware of.
It should use the version even if you invoke directly from the command
line, if not, that's a separate bug.
On Fri, Jul 24, 2009 at 4:36 PM, Joerg Hohwillerjo...@j-hohwiller.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I read the documentation of javadoc-plugin about goal aggregate.
Then I called
mvn javadoc:aggregate and maven failed saying that the goal aggregate does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I read the documentation of javadoc-plugin about goal aggregate.
Then I called
mvn javadoc:aggregate and maven failed saying that the goal aggregate does not
exist.
mvn -U javadoc:aggregate, same result.
Website wrong?
Aha... think...