Using <version>x.y.z</version> does not necessarily mean you're going to get x.y.z.
If you absolutely must only get version 2.2, and nothing newer/older is acceptable, then you should use [2.2] to lock down the version. Wayne On 8/20/07, Michael Meyer <[EMAIL PROTECTED]> wrote: > L. J. schrieb: > > However, even I put the maven-javadoc-plugin version number 2.2 in the > > pom.xml as below, maven 2.0.6 still uses 2.3. > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-javadoc-plugin</artifactId> > > <version>2.2</version> > > > > What would be the best way/workaround, any suggestion? > > Using version 2.2 of the javadoc plugin is the workaround that I'm using for > the following bug: http://jira.codehaus.org/browse/MJAVADOC-135. > Are you sure that adding this to your pom doesn't work? > > <reporting> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-javadoc-plugin</artifactId> > <version>2.2</version> > </plugin> > </plugins> > </reporting> > > Cheers, michael > > --------------------------------------------------------------------- > 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]
