If you check how the source plugin is working now, that's it. When the javadoc plugin is able to generate a JAR, that will do it to and it will be on by default for releases.
Basically, we call the goal in the "package" phase, and it registers itself with the project, so that when install/deploy are called it knows to install and deploy it as well. We need to work on it some more (currently, it calls source every time and just does nothing on a SNAPSHOT - this all needs to be configurable). But it works. Cheers, Brett On 6/25/05, Mike Perham <[EMAIL PROTECTED]> wrote: > Obviously Maven is designed with the one project = one artifact rule. > How would one deal with javadoc archives for instance? I have a bunch > of source that I want to pack into a jar but I also want to generate the > javadoc into a versioned zip file for separate distribution from the > code but I want it all to be generated from a single project. > Conceptually how should this be handled? > > mike > > --------------------------------------------------------------------- > 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]
