[ 
http://jira.codehaus.org/browse/MSITE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lukas Theussl closed MSITE-277.
-------------------------------

    Resolution: Not A Bug
      Assignee: Lukas Theussl

The deploy location is uniquely determined by distMngmnt.site.url, there is a 
default inheritance mechanism that is used consistently by the site plugin. If 
you want to avoid duplication, use a default directory layout. If you use a 
custom layout, don't complain that you have to adjust your build. ;)

> site:deploy possibility to choose directory tree when using sub-modules
> -----------------------------------------------------------------------
>
>                 Key: MSITE-277
>                 URL: http://jira.codehaus.org/browse/MSITE-277
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Improvement
>          Components: site:deploy, site:stage(-deploy)
>    Affects Versions: 2.0-beta-6
>            Reporter: Guimiot Isabelle
>            Assignee: Lukas Theussl
>            Priority: Minor
>
> I use Eclipse and my modules (root and submodules) are all at the same level 
> in the directory tree :
> [eclipse_workspace]/root
> [eclipse_workspace]/sub1
> [eclipse_workspace]/sub2
> Until the 2.0-beta-5 of the maven site plugin, when I deployed my site, I 
> obtained this tree :
> [publish]/root
> [publish]/root/sub1
> [publish]/root/sub2
> I installed the beta-6 version, and the default behaviour has changed, I now 
> have every module at the same level :
> [publish]/root
> [publish]/sub1
> [publish]/sub2
> So I just wondered if it was possible to have an option to choose whether we 
> prefer to publish the submodules inside the root directory, or at the same 
> level... ?
> thx
> Isabelle

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

        

Reply via email to