[
https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi...
]
Denis Golovin updated JBIDE-14610:
----------------------------------
Description:
[~dgolovin] said:
{quote}
It is time to cleanup
download.jboss.org and develop structure that would easy to
understand and navigate, what we have now looks like .... lets say politely - confusing.
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
{quote}
was:
[~dgolovin] said:
{quote}
It is time to cleanup
download.jboss.org and develop structure that would easy to
understand and navigate, what we have now looks like .... lets say politely - confusing.
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
{quote}
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
[~dgolovin] said:
{quote}
It is time to cleanup
download.jboss.org and develop structure that would easy to
understand and navigate, what we have now looks like .... lets say politely - confusing.
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
{quote}
--
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