You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Tom Bollwitt <tl...@mersoft.com> on 2009/07/01 14:51:43 UTC
Re: Using parent POMs effectively
We created a maven site skin and then added a site.xml in the project
that is used for our parent "super pom".
All our projects eventually inherit from this "global" super pom so
the site.xml is also inherited.
If you need info on creating a skin then check here...
http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html
example site.xml....
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/DECORATION/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/DECORATION/1.0.0 http://maven.apache.org/xsd/decoration-1.0.0.xsd
">
<skin>
<groupId>com.mersoft</groupId>
<artifactId>maven-mersoft-skin</artifactId>
<version>0.0.1</version>
</skin>
...
<body>
...
</body>
</project>
I hope this helps.
Regards,
Tom Bollwitt
SYSTEMS ENGINEER
Mersoft
9300 W. 110th St.
Building 55, Suite 350
Overland Park, KS 66210
913-871-6200
tlbollwitt@mersoft.com
On Jun 30, 2009, at 10:45 AM, J.T.Halliley@flagstar.com wrote:
> I've created a parent POM, in which to house a few common
> dependencies,
> but mostly to set up how a site is built:
>
> * CheckStyle rules,
> * JavaDoc stylesheet,
> * JXR stylesheet,
> * site stylesheet.
>
> But the latter site.css is not being picked up: It lives in
> src/site/resources/css/site.css
> under the parent project. If I put site.css under the child
> project, it
> is copied to
> target/site/css just fine.
>
> Should I be able to put such resources under the parent POM's project?
> I've even tried specifying the following in the parent POM:
>
> <reporting>
> <plugins>
> <!-- Site -->
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <configuration>
> <stylesheet>
> ${env.FSB_PROJECTS_HOME}/fsb-master-pom/src/site/resources/css/
> site.css
> </stylesheet>
> </configuration>
> </plugin>
> ...
>
> It'd be nice to specify such things once in the parent project to be
> used
> by all child projects.
>
> Ideas?
>
> Tom
> j.t.halliley@flagstar.com
>
> <P>
> This e-mail may contain data that is confidential, proprietary or
> non-public personal information, as that term is defined in the
> Gramm-Leach-Bliley Act (collectively, Confidential Information). The
> Confidential Information is disclosed conditioned upon your
> agreement that you will treat it confidentially and in accordance
> with applicable law, ensure that such data isn't used or disclosed
> except for the limited purpose for which it's being provided and
> will notify and cooperate with us regarding any requested or
> unauthorized disclosure or use of any Confidential Information.
> By accepting and reviewing the Confidential information, you agree
> to indemnify us against any losses or expenses, including attorney's
> fees that we may incur as a result of any unauthorized use or
> disclosure of this data due to your acts or omissions. If a party
> other than the intended recipient receives this e-mail, he or she is
> requested to instantly notify us of the erroneous delivery and
> return to us all data so delivered.
> </P>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Using parent POMs effectively
Posted by J....@flagstar.com.
Yes, I agree that a skin would produce the desired results; maybe I
shouldn't avoid that solution ;-)
My question simply put is this: Should the site plugin inherit resources
from a parent POM or not? It seems that other plugins (e.g., CheckStyle,
JXR, etc.) do inherit same quite nicely. Is this a bug in the site
plugin?
Thanks,
Tom
j.t.halliley@flagstar.com
From:
Tom Bollwitt <tl...@mersoft.com>
To:
"Maven Users List" <us...@maven.apache.org>
Date:
07/01/2009 08:52 AM
Subject:
Re: Using parent POMs effectively
We created a maven site skin and then added a site.xml in the project
that is used for our parent "super pom".
All our projects eventually inherit from this "global" super pom so
the site.xml is also inherited.
If you need info on creating a skin then check here...
http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html
example site.xml....
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/DECORATION/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://maven.apache.org/DECORATION/1.0.0
http://maven.apache.org/xsd/decoration-1.0.0.xsd
">
<skin>
<groupId>com.mersoft</groupId>
<artifactId>maven-mersoft-skin</artifactId>
<version>0.0.1</version>
</skin>
...
<body>
...
</body>
</project>
I hope this helps.
Regards,
Tom Bollwitt
SYSTEMS ENGINEER
Mersoft
9300 W. 110th St.
Building 55, Suite 350
Overland Park, KS 66210
913-871-6200
tlbollwitt@mersoft.com
On Jun 30, 2009, at 10:45 AM, J.T.Halliley@flagstar.com wrote:
> I've created a parent POM, in which to house a few common
> dependencies,
> but mostly to set up how a site is built:
>
> * CheckStyle rules,
> * JavaDoc stylesheet,
> * JXR stylesheet,
> * site stylesheet.
>
> But the latter site.css is not being picked up: It lives in
> src/site/resources/css/site.css
> under the parent project. If I put site.css under the child
> project, it
> is copied to
> target/site/css just fine.
>
> Should I be able to put such resources under the parent POM's project?
> I've even tried specifying the following in the parent POM:
>
> <reporting>
> <plugins>
> <!-- Site -->
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <configuration>
> <stylesheet>
> ${env.FSB_PROJECTS_HOME}/fsb-master-pom/src/site/resources/css/
> site.css
> </stylesheet>
> </configuration>
> </plugin>
> ...
>
> It'd be nice to specify such things once in the parent project to be
> used
> by all child projects.
>
> Ideas?
>
> Tom
> j.t.halliley@flagstar.com
>
> <P>
> This e-mail may contain data that is confidential, proprietary or
> non-public personal information, as that term is defined in the
> Gramm-Leach-Bliley Act (collectively, Confidential Information). The
> Confidential Information is disclosed conditioned upon your
> agreement that you will treat it confidentially and in accordance
> with applicable law, ensure that such data isn't used or disclosed
> except for the limited purpose for which it's being provided and
> will notify and cooperate with us regarding any requested or
> unauthorized disclosure or use of any Confidential Information.
> By accepting and reviewing the Confidential information, you agree
> to indemnify us against any losses or expenses, including attorney's
> fees that we may incur as a result of any unauthorized use or
> disclosure of this data due to your acts or omissions. If a party
> other than the intended recipient receives this e-mail, he or she is
> requested to instantly notify us of the erroneous delivery and
> return to us all data so delivered.
> </P>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org