[MASSEMBLY-310] improve site inclusion handling in assemblies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.2-beta-2
• Component/s: site
• Environment: Maven 2.0.9, Win XP SP2
• Assignee: Unassigned
• Reporter: Michael Osipov
• Created: 14/Apr/08 13:15
• Updated: 27/Dec/15 20:50
• Resolved: 27/Dec/15 20:50

Description

The current state of including the site into an assembly is extremely bad.

There is <includeSiteDirectory> but this suits only for a single module project.
if you do have a multimodule project, try so assemble all subsites into the parent sie module, you have to struggle with fileset or modulesets or both.

I was able to solve this for me with:

<moduleSet>
    <sources>
        <includeModuleDirectory>false</includeModuleDirectory>
        <fileSets>
            <fileSet>
                <outputDirectory>site/${artifactId}</outputDirectory>
                <directory>target/site</directory>
            </fileSet>
        </fileSets>
    </sources>
</moduleSet>

This is a better way than using the regular fiesets but still an ugly solution since I needed several hours to accomplish that the way I wanted.
I am asking for a more profound and easier solution for this. It could be solved maybe with site:jar and usage of binaries and attachmentClassifer = site but this still seems quite inferior.

I propose something like this:

<moduleSet>
    <!-- your includes and excludes -->
    <sites>true</sites>
</moduleSet>

The in- and excludes would make it quite flexible. An much more easier approach without any flexibility would just be introduce a <includeSubModulesSiteDirectory>.