]
Nick Boldt commented on JBDS-2176:
----------------------------------
After much discussion the only remaining point of interest is the absence of rootfiles
(about.html, about_files/*) in the studio/ folder of the install.
IMHO this shouldn't be a blocker.
Audit differences between Tycho-built installer (.updatesite job) and
PDE-built installer (.product job)
--------------------------------------------------------------------------------------------------------
Key: JBDS-2176
URL:
https://issues.jboss.org/browse/JBDS-2176
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 5.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.CR1
Attachments: jbds2176_bundles.info.png, jbds2176_config.ini.png,
jbds2176_jbdevstudio.ini.png, jbds2176_orphans.png, lucene.png,
trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png,
trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png,
trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png,
trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png
Comparing the on-disk footprints for the two installers, I see some discrepancies.
!trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png!
Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j
Right: unpcked plugins
!trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png!
Left: javax.servlet 3.0; no org.apache.lucene
Right: no javax.servlet; org.apache.lucene 2.9.1
!trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png!
Left: org.eclipse.jetty
Right: no jetty
!trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png!
Left: org.eclipse.mylyn.commons.workbench, org.jdom
Right: no org.eclipse.mylyn.commons.workbench; no org.jdom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: