[jbosstools-issues] [JBoss JIRA] (JBDS-3532) Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3532:
----------------------------------

Regarding this idea that deploy will REBUILD stuff:

{code}
+ cd /mnt/hudson_workspace/workspace/devstudio.product_9.0.mars/sources/product/results
+ M2_HOME=/qa/tools/opt/apache-maven-3.2.5/
+ /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -U -e -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/devstudio.product_9.0.mars/.repository -Djbosstools_site_stream=4.3.mars -B -U -fae -e -P hudson,eap,unified.target -DBUILD_ALIAS=GA
{code}

Nope, it only deploys from the results/ folder. It does NOT rebuild the update site or the installer. 

Check the log, and prove me wrong if you can. :D

> Installer and updatesite zip contain different timestamps for JBDS product IU (because rebuilt?)
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-3532
>                 URL: https://issues.jboss.org/browse/JBDS-3532
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: updatesite
>    Affects Versions: 9.0.0.CR2
>         Environment: jboss-devstudio-9.0.0.GA-v20150925-1252-B116-installer-standalone.jar
> jboss-devstudio-9.0.0.GA-v20150925-1252-B116-updatesite-core.zip
> downloaded from
> http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-9.0.0.CR2-build-product/
>            Reporter: Jan Richter
>            Assignee: Nick Boldt
>            Priority: Blocker
>              Labels: respin-a
>             Fix For: 9.0.0.GA
>
>
> The update site zip has a later timestamp than what you get from the installer but it is still the same build. 
> So you can basically update to the same build because of that.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)