[
https://issues.jboss.org/browse/JBDS-3375?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-3375:
--------------------------------------
Frankly, I do not think that this is an issue (since we also assume that the update-site
zip can be used to have a local mirror on another network). So I don't think it's
worth any effort and not worth adding any additional complexity to the build.
I find it accurate to have update-site zip matching the update-site thus I'd be in
favour of rejecting this issue.
JBDS target platform zip contains both packed and unpacked artifacts
--------------------------------------------------------------------
Key: JBDS-3375
URL:
https://issues.jboss.org/browse/JBDS-3375
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: build, target-platform, updatesite
Affects Versions: 9.0.0.Alpha2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Minor
Fix For: 9.0.0.Alpha2
I've got two approaches now for including the JBDS target platform into the JBDS
update site.
a) mirror the TP site - size on disk is 328M and the increase in size to JBDS update site
is about 200M
b) wget the TP zip and unpack - size on disk after unzipping is 458M
So... not sure which approach is more efficient given the zip is a single file to
download, but it's 130M (more than 1/3rd) larger.
If we can remove the packed (or unpacked) artifacts from the zip, we'd certainly win.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)