You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dan Adams <da...@ifactory.com> on 2006/05/03 20:31:18 UTC
[m2] help creating site with multiple modules
I have a project that has multiple modules to it and would like to
produce a site that ties the modules together. Can anyone point me to a
good example of how do to things like easily provide a consistent header
to all the sub-module sites?
--
Dan Adams
Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] help creating site with multiple modules
Posted by Mikael Andersson <ma...@gmail.com>.
Ok,
don't know about that I'm afraid.
Personally I maintain a site.xml for each module, which isn't to much of a
problem for me since I have different navigations setup, but it would be
nice if things were inherited though (like banners, skin and links).
- Micke
On 03/05/06, Dan Adams <da...@ifactory.com> wrote:
>
> Thanks. But how do you use a common site.xml with the child modules, for
> instance? I don't want to have to copy and paste it and then maintain it
> in 5 different modules.
>
> On Wed, 2006-05-03 at 19:48 +0100, Mikael Andersson wrote:
> > Hi
> >
> > When using the current version of the site plugin and running site:site
> on
> > the root/parent module, the site plugin will process the child modules
> as
> > well.
> > When deploying the site the child modules site will be but in the parent
> > modules site directory under the name of the artifactId.
> > Ex:
> >
> > project setup:
> > parent-module/
> > child-module1
> > child-module2
> >
> > deployed site:
> > parent/
> > [child-module1-artifactid]/
> > [child-module2-artifactid]/
> >
> > So it is known how to hyperlink to the child modules from the parent
> module.
> > But it isn't possible to properly test it without deploying the site,
> > because the location the sites are in the children's taget directories.
> >
> > With the next release of the site plugin there seems to be a ${modules}
> > expression which will generate navigation to the children, but I haven't
> > tested this yet. It is probably worthwhile for you to add the apache
> plugin
> > snapshot repository to your configuration and set the version of the
> site
> > plugin to 2.0-SNAPSHOT (and run a mvn -U ) which will (probably) give
> you
> > the ${modules} feature (not sure about this since I haven't tested it
> yet
> > myself).
> >
> > Hope this helps a little
> > - Micke
> >
> > On 03/05/06, Dan Adams <da...@ifactory.com> wrote:
> > >
> > > I have a project that has multiple modules to it and would like to
> > > produce a site that ties the modules together. Can anyone point me to
> a
> > > good example of how do to things like easily provide a consistent
> header
> > > to all the sub-module sites?
> > >
> > > --
> > > Dan Adams
> > > Software Engineer
> > > Interactive Factory
> > > 617.235.5857
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> --
> Dan Adams
> Software Engineer
> Interactive Factory
> 617.235.5857
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] help creating site with multiple modules
Posted by Dan Adams <da...@ifactory.com>.
Thanks. But how do you use a common site.xml with the child modules, for
instance? I don't want to have to copy and paste it and then maintain it
in 5 different modules.
On Wed, 2006-05-03 at 19:48 +0100, Mikael Andersson wrote:
> Hi
>
> When using the current version of the site plugin and running site:site on
> the root/parent module, the site plugin will process the child modules as
> well.
> When deploying the site the child modules site will be but in the parent
> modules site directory under the name of the artifactId.
> Ex:
>
> project setup:
> parent-module/
> child-module1
> child-module2
>
> deployed site:
> parent/
> [child-module1-artifactid]/
> [child-module2-artifactid]/
>
> So it is known how to hyperlink to the child modules from the parent module.
> But it isn't possible to properly test it without deploying the site,
> because the location the sites are in the children's taget directories.
>
> With the next release of the site plugin there seems to be a ${modules}
> expression which will generate navigation to the children, but I haven't
> tested this yet. It is probably worthwhile for you to add the apache plugin
> snapshot repository to your configuration and set the version of the site
> plugin to 2.0-SNAPSHOT (and run a mvn -U ) which will (probably) give you
> the ${modules} feature (not sure about this since I haven't tested it yet
> myself).
>
> Hope this helps a little
> - Micke
>
> On 03/05/06, Dan Adams <da...@ifactory.com> wrote:
> >
> > I have a project that has multiple modules to it and would like to
> > produce a site that ties the modules together. Can anyone point me to a
> > good example of how do to things like easily provide a consistent header
> > to all the sub-module sites?
> >
> > --
> > Dan Adams
> > Software Engineer
> > Interactive Factory
> > 617.235.5857
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
--
Dan Adams
Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] help creating site with multiple modules
Posted by Mikael Andersson <ma...@gmail.com>.
Hi
When using the current version of the site plugin and running site:site on
the root/parent module, the site plugin will process the child modules as
well.
When deploying the site the child modules site will be but in the parent
modules site directory under the name of the artifactId.
Ex:
project setup:
parent-module/
child-module1
child-module2
deployed site:
parent/
[child-module1-artifactid]/
[child-module2-artifactid]/
So it is known how to hyperlink to the child modules from the parent module.
But it isn't possible to properly test it without deploying the site,
because the location the sites are in the children's taget directories.
With the next release of the site plugin there seems to be a ${modules}
expression which will generate navigation to the children, but I haven't
tested this yet. It is probably worthwhile for you to add the apache plugin
snapshot repository to your configuration and set the version of the site
plugin to 2.0-SNAPSHOT (and run a mvn -U ) which will (probably) give you
the ${modules} feature (not sure about this since I haven't tested it yet
myself).
Hope this helps a little
- Micke
On 03/05/06, Dan Adams <da...@ifactory.com> wrote:
>
> I have a project that has multiple modules to it and would like to
> produce a site that ties the modules together. Can anyone point me to a
> good example of how do to things like easily provide a consistent header
> to all the sub-module sites?
>
> --
> Dan Adams
> Software Engineer
> Interactive Factory
> 617.235.5857
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>