December 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3296: ---------------------------------- So to confirm, the bug is that Eclipse or JBDS assumes the install drive can be deduced from $\{user.home}, and therefore update fails in weird ways if user.home = c:\something and install dir is d:\something-else. Correct? Can this be reproduced w/ just Eclipse doing an update of an EPP product (eg., from Luna R to SR1)? Or is this strictly a JBDS product bug? Also, is this only for Windows, because of the way it maps / to c:/ (and therefore d:\ is not accessible from a linux-like path) ? > P2 reports several locations without repositories in case product installed on different device from user home directory > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3296 > URL: https://issues.jboss.org/browse/JBDS-3296 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Affects Versions: 8.0.0.GA, 8.0.1.GA > Reporter: Denis Golovin > Assignee: Nick Boldt > Attachments: fixed.png > > > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18869: ------------------------------------ I've created a Jenkins job to perform the mirroring from Eclipse to JBoss: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-requireme... By default it'll push to http://download.jboss.org/jbosstools/builds/staging/jbosstools-requiremen... But if you want to cut over a specific milestone into /updates/requirements/, you can pass in some value of version, such as 0.1.0-SNAPSHOT-201412181815, and end up with: http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... Then all we need to do is ensure that the JBT parent pom uses the correct mirror URL. Note that when we start rolling out the path changes in JBDS-3208, this job will need to be tweaked to publish to the new paths too. (cc: [~mickael_istria] [~gercan] [~maxandersen]) {quote}And am I blind or is there not a PR for the parent pom that is missing to define the thym repo ?{quote} Do you mean the first PR listed above? https://github.com/jbosstools/jbosstools-build/pull/161/files {quote}this is just for 4.3.0 not 4.2.0 ?{quote} We could backport this to 8.1 if we wanted. Depends on how many more Thym builds will be needed in the 8.x stream, I guess. > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3295) Product update fails on windows if installation folder and user home are on different devices

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3295?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3295: ------------------------------------- I put this steps as to workarounds field. It would let to stay on the same device and get jbdevstudio updated. Thanks :) > Product update fails on windows if installation folder and user home are on different devices > --------------------------------------------------------------------------------------------- > > Key: JBDS-3295 > URL: https://issues.jboss.org/browse/JBDS-3295 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: p2-product > Affects Versions: 8.0.1.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3295) Product update fails on windows if installation folder and user home are on different devices

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3295?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3295: -------------------------------- Workaround Description: Workaround 1: move installation to C:\ or wherever device user home folder is located Workaround 2: 1) Stop JBDS 2) Go to the directory where your product .exe exit, for example: D:\IDEs\jbdevstudio\studio 3) Copy jbdevstudio.exe and paste it in the same place with another name (i.e. jbdevstudio2.exe) 4) Start JBDS using the copied file (jbdevstudio2.exe) 5) The update will complete successfully and the product will be restarted using the same exe file 6) Stop JBDS again 7) Delete jbdevstudio2.exe 8) Start JBDS as usual and enjoy was:move installation to C:\ or wherever device user home folder is located > Product update fails on windows if installation folder and user home are on different devices > --------------------------------------------------------------------------------------------- > > Key: JBDS-3295 > URL: https://issues.jboss.org/browse/JBDS-3295 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: p2-product > Affects Versions: 8.0.1.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18984: ------------------------------- Description: Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. This would mean less target platform churning DURING a release, and speed up the way we do releases. Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: * one for JBT content (a subset of the JBT aggregate) and * one for 3rd party content (an adjunct to the Central site) This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself. was: Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. This would mean less target platform churning DURING a release, and speed up the way we do releases. Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: * one for JBT content (a subset of the JBT aggregate) and * one for 3rd party content (an adjunct to the Central site) This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someon i > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) > This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18984: ------------------------------- Description: Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. This would mean less target platform churning DURING a release, and speed up the way we do releases. Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: * one for JBT content (a subset of the JBT aggregate) and * one for 3rd party content (an adjunct to the Central site) This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someon i was: Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. This would mean less target platform churning DURING a release, and speed up the way we do releases. Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: * one for JBT content (a subset of the JBT aggregate) and * one for 3rd party content (an adjunct to the Central site) > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) > This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someon i -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18965) use Tycho 0.22 to build JBT 4.3/JBDS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18965?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18965: ---------------------------------- Assignee: Mickael Istria > use Tycho 0.22 to build JBT 4.3/JBDS 9 > -------------------------------------- > > Key: JBIDE-18965 > URL: https://issues.jboss.org/browse/JBIDE-18965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Tycho 0.22 is out; we should use it to build JBT 4.3/JBDS 9, and see what new fun goodies we can take advantage of, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18984: ------------------------------- Fix Version/s: 4.3.0.Alpha1 > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18984: ---------------------------------- Summary: Build Early Access site as an update site, not a TP Key: JBIDE-18984 URL: https://issues.jboss.org/browse/JBIDE-18984 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, target-platform, updatesite Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 Reporter: Nick Boldt Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. This would mean less target platform churning DURING a release, and speed up the way we do releases. Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: * one for JBT content (a subset of the JBT aggregate) and * one for 3rd party content (an adjunct to the Central site) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18984: ---------------------------------- Assignee: Nick Boldt > Build Early Access site as an update site, not a TP > ---------------------------------------------------- > > Key: JBIDE-18984 > URL: https://issues.jboss.org/browse/JBIDE-18984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite > Affects Versions: 4.2.1.Final, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central. > This would mean less target platform churning DURING a release, and speed up the way we do releases. > Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds: > * one for JBT content (a subset of the JBT aggregate) and > * one for 3rd party content (an adjunct to the Central site) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014