[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1441) Product builds result in smaller executables than Uber builds -- verify this is correct

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBDS-1441:
-------------------------------------

>>  plugins 
>>      ESB 

included

>>      SpringIDE sources 
>>      apache comons sources 

not required

>>      portlet.ui 

included

>>      jBPM convert 

included

>> features
>>   esb 
included
>>      jbpm3 (including org.jbpm.gd.jpdl.feature and jbpm common) 
included
>>      jbpm convert 
included
>>      usage 
Not required to avoid direct deps/
>>      org.teiid.datatools.connectivity.feature 
included
>>   doc/sources from JDT, Help, 
included
>> Equinox, p2, 
not needed
>>ECF, 
docs fo ECF should be included into target platform first
>> Debug, 
not sure what that means
>> JPT, 
included 
>> PDE, 
not required
>> CVS, 
included
>> JUnit 
plugins are included
>>newer version of RSE (should be using 3.2.1 instead of 3.2.0?) 
included

> Product builds result in smaller executables than Uber builds -- verify this is correct
> ---------------------------------------------------------------------------------------
>
>                 Key: JBDS-1441
>                 URL: https://issues.jboss.org/browse/JBDS-1441
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: Build, installer
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>             Fix For: 4.0.0.CR1
>
>
> Latest Beta2 product build:
> http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4.0_stable_branch.product/builds/nightly/4.0.0.Beta2/201012030614/
>         jbdevstudio-win32-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 330.21 MB
> 	jbdevstudio-linux-gtk-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 330.16 MB
> 	jbdevstudio-linux-gtk-x86_64-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 334.26 MB
> 	jbdevstudio-macosx-carbon-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 332.93 MB
> 	jbdevstudio-macosx-cocoa-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 333.05 MB
>  	jbdevstudio-eap-win32-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 622.68 MB
> 	jbdevstudio-eap-linux-gtk-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 622.7 MB
> 	jbdevstudio-eap-linux-gtk-x86_64-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 626.74 MB
> 	jbdevstudio-eap-macosx-carbon-4.0.0.v201012030614R-H32-Beta2.jar
>     md5 | filesize: 625.46 MB
> 	jbdevstudio-eap-macosx-cocoa-4.0.0.v201012030614R-H32-Beta2.jar
> Latest Beta 2 uber build: 
> http://reports.qa.atl.jboss.com/binaries/RHDS/builds/nightly/4.0.0.Beta2/201012030520/
> 	jbdevstudio-win32-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 416.05 MB
> 	jbdevstudio-linux-gtk-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 415.75 MB
> 	jbdevstudio-linux-gtk-x86_64-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 419.87 MB
> 	jbdevstudio-macosx-carbon-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 418.31 MB
> 	jbdevstudio-macosx-cocoa-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 418.54 MB
> 	jbdevstudio-eap-win32-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 708.61 MB
> 	jbdevstudio-eap-linux-gtk-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 708.33 MB
> 	jbdevstudio-eap-linux-gtk-x86_64-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 712.35 MB
> 	jbdevstudio-eap-macosx-carbon-4.0.0.v201012030520R-H26-Beta2.jar
>     md5 | filesize: 710.81 MB
> 	jbdevstudio-eap-macosx-cocoa-4.0.0.v201012030520R-H26-Beta2.jar
> So, why is the product build 330-334M and 622-626M, while the uber build is 415-419M and 708-712M ? is this difference the loss of things we don't need in the TP, or loss of things we SHOULD have in there?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira