You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Graham Sanderson <Gr...@lombardi.com> on 2006/11/03 01:55:39 UTC

maven site

I may be missing something here, but we have a bunch of different
artifacts built using maven, and we'd like to be able to publish for
each major build of a product a site including all the javadoc, source
XRef and reports for all its dependent artifacts

 

Maven site even when used with an aggregate artifact does not seem to
produce (for example javadoc) results that can correctly link to each
other.

 

Is there an existing way to do this?

 

Thanks,

 

Graham Sanderson

Software Engineer
Lombardi Software, Inc.
gsanderson@lombardisoftware.com <ma...@lombardisoftware.com>


www.lombardisoftware.com <http://www.lombardisoftware.com> 

 


Re: maven site

Posted by franz see <fr...@gmail.com>.
Good day to you, Graham,

Wendy is right. Some released reporting plugins have aggregation bugs.
Although some of them have already been fixed, I'm not quite sure if they've
been released now. 

Btw, what are these reports you are talking about? You may want to take a
look at their jira and search whether there are known bugs about their
aggregation or multimodule feature, and whether those have been fixed
already. 

If they have been fixed and not yet released, you can opt to use their
snapshot versions for your development (that is till you intend to deploy).
But If you're about to deploy and these plugins have not yet been released,
you may "lock" (or branch) these plugins by changing their version (i.e
2.0-graham) and deploying these artifacts as well. 

Cheers, 
Franz


Wendy Smoak-3 wrote:
> 
> On 11/2/06, Graham Sanderson <Gr...@lombardi.com> wrote:
> 
>> I may be missing something here, but we have a bunch of different
>> artifacts built using maven, and we'd like to be able to publish for
>> each major build of a product a site including all the javadoc, source
>> XRef and reports for all its dependent artifacts
> 
> For all its dependencies?  Or for its child modules?
> 
>> Maven site even when used with an aggregate artifact does not seem to
>> produce (for example javadoc) results that can correctly link to each
>> other.
> 
> Also, what do you mean by 'linking to each other; (menu links, or ??)
> and where/how are you checking the links?
> 
> My guess is that not all reporting plugins know how to do aggregation
> yet.  It would help to see the pom configuration that isn't working.
> Even better, construct a simple example that demonstrates the problem.
>  (Check JIRA first, there may already be issues open for the
> individual plugins.)
> 
> -- 
> Wendy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/maven-site-tf2565197s177.html#a7194401
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: maven site

Posted by Wendy Smoak <ws...@gmail.com>.
On 11/2/06, Graham Sanderson <Gr...@lombardi.com> wrote:

> I may be missing something here, but we have a bunch of different
> artifacts built using maven, and we'd like to be able to publish for
> each major build of a product a site including all the javadoc, source
> XRef and reports for all its dependent artifacts

For all its dependencies?  Or for its child modules?

> Maven site even when used with an aggregate artifact does not seem to
> produce (for example javadoc) results that can correctly link to each
> other.

Also, what do you mean by 'linking to each other; (menu links, or ??)
and where/how are you checking the links?

My guess is that not all reporting plugins know how to do aggregation
yet.  It would help to see the pom configuration that isn't working.
Even better, construct a simple example that demonstrates the problem.
 (Check JIRA first, there may already be issues open for the
individual plugins.)

-- 
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org