If there isn't one already, yes please.
On 16/10/2008, at 7:40 AM, jaxzin wrote:
I can confirm that downgrading to 2.0-beta-5 fixes my issue and the
module's
site is generated with it's site descriptor. Thanks Brett! Do you
need me
to open a JIRA ticket?
brettporter wrote:
Does it happen to work with 2.0-beta-5? I know 2.0-beta-6 regressed
in
this regard, but I thought it was fixed.
- Brett
On 16/10/2008, at 7:33 AM, jaxzin wrote:
No, it's ignoring the module's site descriptor (mymodule/src/site/
site.xml)
completely. We do take advantage of the site descriptor inheritance
and
that's working properly with inheriting the site descriptor from the
top-level project's parent (aka grandparent??) but again the
module's site
is using the top-level's site descriptor and ignoring the apt files
in the
module as well.
More concretely:
Top-level site.xml (src/site/site.xml):
<?xml version="1.0" encoding="ISO-8859-1"?>
<project>
<bannerLeft>
<name>${project.name}</name>
<href>${project.url}</href>
</bannerLeft>
<version position="left"/>
<body>
<menu name="Parent Test">
<item name="Introduction" href="index.html"/>
</menu>
<menu ref="modules"/>
</body>
</project>
Module's site.xml (mymodule/src/site/site.xml):
<?xml version="1.0" encoding="ISO-8859-1"?>
<project>
<bannerLeft>
<name>${project.name}</name>
<href>${project.url}</href>
</bannerLeft>
<version position="left"/>
<body>
<menu name="Overview">
<item name="Introduction" href="index.html"/>
<item name="Goals" href="plugin-info.html"/>
<item name="Usage" href="usage.html"/>
</menu>
</body>
</project>
If I run 'mvn site' from the top-level dir, then the file
"mymodule/target/site/index.html" has a menu 'Parent Test' and no
menu
'Overview'.
I've tested this with 2.0-beta-7 and 2.0-beta-6.
brettporter wrote:
No, but it's expected that it would be inherited and merged. Is
that
what you are seeing?
- Brett
On 16/10/2008, at 7:17 AM, jaxzin wrote:
I've deployed the site of a multi-module project and found that
the
sites for
the modules are using the site descriptor for the top-level
project
rather
than each modules site descriptor that I've defined. Is that the
expected
behavior?
--
View this message in context:
http://www.nabble.com/Module-site-descriptor-ignored-in-multi-module-project--tp20001464p20001464.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Module-site-descriptor-ignored-in-multi-module-project--tp20001464p20001779.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Module-site-descriptor-ignored-in-multi-module-project--tp20001464p20001932.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
