[jbosstools-issues] [JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-17536:
----------------------------------------

(Coming late in the discussion)
Independently of when we build, the initial installation issue [~mmalina] reported is happening because we change content directly on a public URL. As it is a staging/, I would be OK to just say "Yes, this kind of things can happen". If we want to fix this, [~nickboldt]'s suggestion about publishing to a specific directory seems to be the only working one. And having some composite*.xml at the public URL pointing to the 2 or 3 last builds wouldn't require any change for consumer.

About when to build and publish, here is what I suggest
* Build whenever something happens upstream
* Use p2diff to compare build output with staging
* In case p2diff spots a difference, publish; otherwise, do nothing and keep older build which is equivalent.


> JBoss Tools Core Nightly update site fails to install if a new build is published during install
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-17536
>                 URL: https://issues.jboss.org/browse/JBIDE-17536
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Martin Malina
>            Assignee: Nick Boldt
>             Fix For: 4.2.x
>
>
> When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this:
> {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code}
> This is because during your install, the old jars were replaced with the new jars, i.e. different filenames.
> I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table.
> Nick offered this alternative:
> install from a specific build folder instead of the "latest nightly"
> http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-04_06-40-59-B8878/all/repo/
> http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-04_09-46-40-B8879/all/repo/
> But obviously that's just a workaround, not a real solution.
> One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)