Thank you, that did the trick.
Also, I've noticed that if you want to deploy the sources, but not the
javadocs, you can set the javadoc plugin's sourcepath to a bogus directory,
like so:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.2</version>
<configuration>
<sourcepath>${basedir}/meh</sourcepath>
</configuration>
</plugin>
On Thu, Oct 23, 2008 at 2:18 PM, Nick Stolwijk <[EMAIL PROTECTED]>wrote:
> Default the release plugin performs the phases deploy and site-deploy.
> By giving the command -Dgoals=deploy, you tell the release:perform to
> only deploy your application and not the generated site. Also, you can
> use the -DuseReleaseProfile=false, which will stop generating the
> sources and javadoc jar. See [1] for other options.
>
> [1] http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html
> Hth,
>
> Nick Stolwijk
> ~Java Developer~
>
> Iprofs BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> www.iprofs.nl
>
>
>
> On Thu, Oct 23, 2008 at 8:10 PM, Blake Martin <[EMAIL PROTECTED]>
> wrote:
> > I'm trying to perform a release of a legacy project, which isn't even
> close
> > to having functional Javadocs.
> >
> > The release plugin fails because the Javadoc goal fails. How can I skip
> > Javadoc generation?
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
