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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBDS-3532:
--------------------------------------

Yes, it's a change we completed around Beta2 to have deploy steps in the pom: JBIDE-18772
The difficulty is that we aren't just using the Maven deploy plugin (because we don't change versions between milestones and risk to cross streams if we rely on regular Maven deploy without it), but we're using a combination of mojos that perform the deploy steps. So there is no easy command-line to run those steps from Maven AFAIK.

A possible workaround is to build/rebuild and republish installer just after we run "mvn deploy" on the p2 repo.

> Installer and updatesite-core zip contain different timestamps for JBDS product IU
> ----------------------------------------------------------------------------------
>
>                 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
>             Fix For: 9.0.0.GA
>
>
> The updatesite 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)