maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Hansel (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSITE-548) site:deploy -> folder structure is different when artifactId=module's directory
Date Tue, 01 Feb 2011 10:54:22 GMT

    [ http://jira.codehaus.org/browse/MSITE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253693#action_253693
] 

Stefan Hansel commented on MSITE-548:
-------------------------------------

Ok, checked again - it indeed only happens with maven3.0.1 + 3.0.2 .
Who whould be responsible for such a bug-report? Is this the core of Maven http://jira.codehaus.org/browse/MNG
?

As you say 'non-standard project layout' - I thought that a flat multimodule project is completely
valid (at least officially documented in the sonartype docs) and the best way to cope with
eclipse, as it only knows a flat project structure anyway?

One other question: I already tried to manipulate/tweak the distributionManagement.site.url
(but of course don't want to use absolute paths there).

I hoped that 
{code}
  <distributionManagement>
    <site>
      <url>${project.parent.distributionManagement.site.url}/subdir</url>
    </site>
  </distributionManagement>
{code}
would help in the submodule, but I only get errors and it looks like the variable is not resolved.
Any suggestions?



> site:deploy -> folder structure is different when artifactId=module's directory
> -------------------------------------------------------------------------------
>
>                 Key: MSITE-548
>                 URL: http://jira.codehaus.org/browse/MSITE-548
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0-beta-3
>         Environment: windows
>            Reporter: Stefan Hansel
>         Attachments: artifact-id-testcase.zip
>
>
> There is a multimodule flat project structure:
> root
> module1
> module2
> module1 has an artifactID of 'module1'  (same as directory name)
> modulu2 has an artifactID of 'module-2' (different to directory name)
> After a 'mvn site-deploy' the generated report has the folder structure:
> /root
> /root/module-2
> /module1
> So based on the artifactID the submodules are created as a child of the root - or not.
> This is at least inconsistent and should be changed to be handled always the same - independent
of the artifactID.
> This is also important for other plugins (i.e. the dashboard plugin).
> They seem to have some hardcoded directory structure (preferring submodules as childs
of the root report). 
> Due to this bug (see http://jira.codehaus.org/browse/MOJO-1630) the links between reports
there still don't work as long as artifactID=module's directory. 
> Attached you will find a testcase (based on maven3, but can also be used with maven2
when the version of the site-plugin is changed).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message