[jbosstools-issues] [JBoss JIRA] (JBDS-3092) Remove content in JBDS update site which is duplicated in the JBDS TP

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3092:
----------------------------------

OK, so then the only question is...

a) do we maintain two nearly-identical poms (one with includeAllDependencies=true, one with includeAllDependencies=false) and two nearly identical category.xml files (one with source features, one without), or 

b) use one pom + category.xml to build both sites, using some sort of custom scripting/repackaging?

> Remove content in JBDS update site which is duplicated in the JBDS TP
> ---------------------------------------------------------------------
>
>                 Key: JBDS-3092
>                 URL: https://issues.jboss.org/browse/JBDS-3092
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: target-platform, updatesite
>    Affects Versions: 8.0.0.Beta3
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> From Max:
> {quote}    Why is parts of TP included inside https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3-updatesite-core/ ?
>     why not *just* our plugins ? {quote}
> Ref: https://wiki.eclipse.org/Tycho/Packaging_Types#eclipse-repository
> Haha:   http://memegenerator.net/instance/52610169
> Reason for the extraneous inclusions is that this config param is set in the JBDS update site pom:          
> {code:title=https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/pom.xml#L29}
> <includeAllDependencies>true</includeAllDependencies>
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)