[jbosstools-issues] [JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Tue Aug 20 04:10:27 EDT 2013


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

Max Rydahl Andersen commented on JBIDE-15340:
---------------------------------------------

No, none of these associate sites are needed to be referenced by locus; none of the component on the locus should have dependencies *outside* of very basic org.eclipse stuff. if tycho, a user or whatever needs some other dependency (like org.osgi.core.whatever) then that is something the build/user/other updatesite decides where it comes from.

Locus is like a lowest component site that is *only* use at build time for other builds to get from. Yes, it needs its own dependencies during build time - that does not mean it should be part of associate sites.

This rule about not having associate sites applies equally well to any of our sub-component builds - they are *not* supposed to have *any* external references - it is the build, the aggregating updatesite etc. that gets to decide how it is assembled. 

We've had plenty of discussions and scenarioes where this have been a problem (i.e. testing and combining updatesites becomes very tricky if a site refers to multiple eclipse release trains).

Associate sites are 99.9% only relevant for end-user updatesites - like JBT, JBTIS or complete separate updatesite sites (even in JBTIS case it would be better if it didn't linked back to JBT so it could be combined with any release of JBT - but that is something we do right now since no better solution).

We have to stop mingling up enduser and internal build sites needs/requirements.


                
> Remove site references from Locus site
> --------------------------------------
>
>                 Key: JBIDE-15340
>                 URL: https://issues.jboss.org/browse/JBIDE-15340
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: locus
>            Reporter: Rob Cernich
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 1.1.0-LOCUS
>
>         Attachments: 15340_locus110CI-full-install.png
>
>
> The Locus p2 repo/update site should not include references to other update sites.  Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/

--
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


More information about the jbosstools-issues mailing list