]
Max Rydahl Andersen updated JBIDE-14610:
----------------------------------------
Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015)
Design
http://download.jboss.org/jbosstools structure
-----------------------------------------------------
Key: JBIDE-14610
URL:
https://issues.jboss.org/browse/JBIDE-14610
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build, updatesite
Affects Versions: 4.1.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.3.0.Beta1
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