[ 
https://issues.apache.org/jira/browse/MSITE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MSITE-1012:
----------------------------------
    Description: As is seems with MSITE-1010 people assume that since we use 
the term "site repository" it behaves like a Maven repository in terms of 
structure. It does **not**. Let's get rid of that term and use "site" or "site 
deployment" only. No implications. With this, the parameter 
{{stagingRepositoryId}} in {{SiteStageDeployMojo}} will be ranamed to 
{{stagingSiteId}} to clean up confusion.  (was: As is seems with MSITE-1010 
people assume that since we use the term "site repository" it behaves like a 
Maven repository in terms of structure. It does **not**. Let's get rid of that 
term and use "site" or "site deployment" only. No implications.

With this the parameter {{stagingRepositoryId}} in {{SiteStageDeployMojo}} will 
be ranamed to {{stagingSiteId}} to clean up confusion.)

> Clean up notion that sites aren't deployed to repositories
> ----------------------------------------------------------
>
>                 Key: MSITE-1012
>                 URL: https://issues.apache.org/jira/browse/MSITE-1012
>             Project: Maven Site Plugin
>          Issue Type: Improvement
>          Components: inheritance, multi module, site:deploy
>    Affects Versions: 4.0.0-M15
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 4.0.0, 4.0.0-M16
>
>
> As is seems with MSITE-1010 people assume that since we use the term "site 
> repository" it behaves like a Maven repository in terms of structure. It does 
> **not**. Let's get rid of that term and use "site" or "site deployment" only. 
> No implications. With this, the parameter {{stagingRepositoryId}} in 
> {{SiteStageDeployMojo}} will be ranamed to {{stagingSiteId}} to clean up 
> confusion.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to