[jbosstools-issues] [JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

[Denis Golovin (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Golovin updated JBIDE-14610:
----------------------------------

    Description: 
We have several types of objects which names should be presented in site stucture:
# Project: jbosstools
# Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
# Subproject: core, soatools
# Module: base, javaee, central, freemarker and etc.
# Distribution Type: updates|builds
# Bits Type: stable|development|nightly
# Targeted Eclipse: indigo|juno|kepler
# You name it ...

Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
# aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
# jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
# jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits


  was:

We have several types of objects which names should be presented in URL:
# Project Name: jbosstools
# Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
# Subproject Name: core, soatools
# Distribution Type: updates|builds
# Bits Type: stable|development|nightly
# Targeted Eclipse: indigo|juno|kepler
# You name it ...

Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
# aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
# jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
# jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits



    
> Design http://download.jboss.org/jbosstools structure
> -----------------------------------------------------
>
>                 Key: JBIDE-14610
>                 URL: https://issues.jboss.org/browse/JBIDE-14610
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, updatesite
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>
> We have several types of objects which names should be presented in site stucture:
> # Project: jbosstools
> # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
> # Subproject: core, soatools
> # Module: base, javaee, central, freemarker and etc.
> # Distribution Type: updates|builds
> # Bits Type: stable|development|nightly
> # Targeted Eclipse: indigo|juno|kepler
> # You name it ...
> Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
> # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
> # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
> # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits

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