at the moment I have asked on the maven users list if theres a way to
make use of the same config from the build and reporting sections.  I
have currently copied the config across,  I'll open a jira to remind
me to check back and see if it's possible to share the config, and if
so, go back and fix it up.

On Thu, Aug 12, 2010 at 1:23 PM, ant elder <[email protected]> wrote:
> I guess then it needs something like the same javadoc plugin config as
> is in the <reporting> section also in the release profile <plugins>
> section. I don't know if there is a way to avoid having to duplicate
> all the config.
>
>   ...ant
>
> On Thu, Aug 12, 2010 at 1:09 PM, kelvin goodson
> <[email protected]> wrote:
>> You can create the javadoc with either mvn:site or
>> mvn:javadoc:javadoc.  If I recall correctly I had understod from the
>> documentation that if you configured a reporting serction containing
>> javadoc plugin config, then that was aimed at the mvn:site command,
>> but javadoc plugin configuration under the the build element was aimed
>> at the mvn javadoc:javadoc  comand.  I believe I ran both variants of
>> the mvn command with the current reporting configuration and could see
>> that the javadoc plugin configuration under the reporting section
>> seemed to influence both commands.
>>
>> Kelvin.
>>
>> On Thu, Aug 12, 2010 at 1:02 PM, ant elder <[email protected]> wrote:
>>> On Thu, Aug 12, 2010 at 10:42 AM, kelvin goodson
>>> <[email protected]> wrote:
>>>> I did a bit of work experimenting with javadoc a while back, but never
>>>> got as far as understanding how to configure the release profile to
>>>> include javadoc in the release distro.  Does anyone have any clues
>>>> before I go dig around?
>>>>
>>>> Kelvin.
>>>>
>>>
>>> I guess the plugin need to be added/configured in the release profile
>>> of the top level pom.xml. What is the process or mvn command for
>>> creating the Javadoc at the moment?
>>>
>>>   ...ant
>>>
>>
>

Reply via email to