On Monday 23 June 2008 André Kelpe wrote: > In the company I work for we have a somewhat big maven2 setup which is > working quite good so far. We now wanted to organize our release process > in a more structured way (esp. release-poms) to avoid problems with > version ranges and I found the maven release plugin, which looks like it > can solve all our problems. Currently I am trying to set it correctly up, > but I always encounter a problem, which is that the release pom is not > correctly created. For all plugins that we use the version number in the > release-pom is set to "RELEASE" instead of the actual version number. > Here is an example: > > This is in the master pom: > [...] > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-javadoc-plugin</artifactId> > <executions> > <execution> > <id>attach-javadocs</id> > <goals> > <goal>jar</goal> > </goals> > </execution> > </executions> > </plugin> > [...] > > and this is what will end up in the release-pom > > <plugin> > <artifactId>maven-javadoc-plugin</artifactId> > <version>RELEASE</version> <-- this is the problem > <configuration> > <links> > <link>http://java.sun.com/javase/6/docs/api/</link> > </links> > <aggregate>true</aggregate> > </configuration> > </plugin>
You probably didn't define a version for the maven-javadoc-plugin in this projects pom or a parent pom, so maven (prior to 2.0.9) defaults to RELEASE. Just define the version of all plugins you are using (best in a <dependencyManagement> section), which is a best practice anyway. This should solve your problem. hth, - martin
signature.asc
Description: This is a digitally signed message part.
