[jbosstools-issues] [JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062917#comment-13062917 ] 

Mickael Istria commented on JBIDE-19715:
----------------------------------------

Branding and references are part of the generate-repository-facade mojo, which is not related to fullSite.

The create-full-site mojo doesn't produce anything that isn't in the buildinfo.json. I'd be in favour of getting rid of it, and put metadata and zips directly in the repository/ folder, instead of maintaining an overhead hierarchy besides of the repostory..
I checked Mojos and scripts and the only references to fullSite are only in unused or useless mojos, and in comments in rsync.sh. It seems to be used only in CI job configuration, where we could publish repository/ as easily.

> Get rid of "fullSite", stick with "repository"
> ----------------------------------------------
>
>                 Key: JBIDE-19715
>                 URL: https://issues.jboss.org/browse/JBIDE-19715
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Mickael Istria
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)