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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-14610:
------------------------------------

Haven't seen any suggestions here as to how we could organize things better, only that it's apparently confusing. Complaining without suggesting a solution doesn't get you very far. :(

Note that recently we migrated all the target platforms from /updates/<eclipse version>/ to /targetplatforms/ so it's a bit more obvious what's what.

Thus:

http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kepler/ replaces http://download.jboss.org/jbosstools/updates/kepler/
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kepler/ replaces http://download.jboss.org/jbosstools/updates/kepler/extras/ (JBDS-2623)

Also looking at replacing builds/staging\{,.previous}/JOB_NAME with builds/ci/JOB_NAME/BUILD_ID, as per JBIDE-15482.
                
> 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: Denis Golovin
>            Priority: Blocker
>             Fix For: 4.2.0.Alpha1
>
>
> 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