[
https://issues.jboss.org/browse/JBDS-3092?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-3092:
-------------------------------------------
There is something weird/wrong if the installer provisions from the TP site and then
result in a bigger installer isn't there ?
or is it because we include it blindly into the installer without filtering it before
actually putting it in the installer?
couldn't we "mirror" the updatesite with includeAllDependencies=true into
the installer ?
no need for multiple poms/categories for that is there?
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-upd... ?
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)