[
https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-17536:
------------------------------------
Why? Because of a desire to be consistent w/ previous.
All the other nightly/<site-type>/<stream>/ folders are single AGGREGATE
releases -- a snapshot that's always the latest.
(site-type = 4 JBT update sites + JBTIS; stream = 4.1.kepler, 4.2.luna, 4.3.mars, master)
Why should JBT nightly core master be the exception? If we change one to being a
composite, we should change them all. Or else in 3 months you'll suddenly realize
we're being inconsistent and blame me for shitty architectural decisions. See
JBIDE-14610 for the most recent example of this.
http://download.jboss.org/jbosstools/updates/nightly-composite/core/master/ is rather of
verbose but if that makes you happy, cool. We can do that.
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.0.CR1
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-0...
http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0...
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)