maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-310) improve site inclusion handling in assemblies
Date Fri, 02 Nov 2012 10:31:13 GMT

     [ https://jira.codehaus.org/browse/MASSEMBLY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dennis Lundberg updated MASSEMBLY-310:
--------------------------------------

    Component/s: site
    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:

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

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:

{code:xml}
<moduleSet>
    <!-- your includes and excludes -->
    <sites>true</sites>
</moduleSet>
{code}

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

  was:
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:

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

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:

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

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

    
> improve site inclusion handling in assemblies
> ---------------------------------------------
>
>                 Key: MASSEMBLY-310
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-310
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: New Feature
>          Components: site
>    Affects Versions: 2.2-beta-2
>         Environment: Maven 2.0.9, Win XP SP2
>            Reporter: Michael Osipov
>
> 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:
> {code:xml}
> <moduleSet>
>     <sources>
>         <includeModuleDirectory>false</includeModuleDirectory>
>         <fileSets>
>             <fileSet>
>                 <outputDirectory>site/${artifactId}</outputDirectory>
>                 <directory>target/site</directory>
>             </fileSet>
>         </fileSets>
>     </sources>
> </moduleSet>
> {code}
> 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:
> {code:xml}
> <moduleSet>
>     <!-- your includes and excludes -->
>     <sites>true</sites>
> </moduleSet>
> {code}
> The in- and excludes would make it quite flexible. An much more easier approach without
any flexibility would just be introduce a <includeSubModulesSiteDirectory>.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message