February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19336) When JBT and Central both contain the same IU but different versions, p2-director installation fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19336 at 2/20/15 9:40 AM: ------------------------------------------------------------- Yes. It does. Yes. I think what happened is that the Central site was rebuilt by the 4.3.mars job (hence the low number - B3) but the master job is still sourcing from the same site, Alpha1 instead of Alpha2. But my point is that having the same IUs in two different sites leads to duplicate content and the potential for install conflicts. Having just fixed the p2 director install tests, I found a bigger hidden problem. was (Author: nickboldt): Yes. It does. Yes. I think what happened is that the Central site was rebuilt by the 4.3.mars job (hence the low number - B3) but the master job is still sourcing from the same site, Alpha1 instead of Alpha2. > When JBT and Central both contain the same IU but different versions, p2-director installation fails > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19336) When JBT and Central both contain the same IU but different versions, p2-director installation fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19336: ------------------------------------ Yes. It does. Yes. I think what happened is that the Central site was rebuilt by the 4.3.mars job (hence the low number - B3) but the master job is still sourcing from the same site, Alpha1 instead of Alpha2. > When JBT and Central both contain the same IU but different versions, p2-director installation fails > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19336) When JBT and Central both contain the same IU but different versions, p2-director installation fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19336: ------------------------------- Fix Version/s: 4.3.0.Alpha2 > When JBT and Central both contain the same IU but different versions, p2-director installation fails > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3273: ----------------------------------- FYI, I was planning on performing only 1 big request, fetching back all 290+ quickstart data, so I can cache the result locally for a period of time (page session), and then perform all the filtering locally as well. Caching the json payload allows us to go offline and work against local git repos. > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19336) When JBT and Central both contain the same IU but different versions, p2-director installation fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19336: ------------------------------- Affects Version/s: 4.3.0.Alpha1 > When JBT and Central both contain the same IU but different versions, p2-director installation fails > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19336) When JBT and Central both contain the same IU but different versions, p2-director installation fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19336: ------------------------------- Component/s: build > When JBT and Central both contain the same IU but different versions, p2-director installation fails > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19223) Revise support status in support matrix doc

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19223?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19223. ------------------------------ Resolution: Done > Revise support status in support matrix doc > ------------------------------------------- > > Key: JBIDE-19223 > URL: https://issues.jboss.org/browse/JBIDE-19223 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.2.Final > > > This doc contains a column called "Supported?": > https://developer.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec... > All of the version since JBDS/RHDS 1 say they are supported. This is not true. > It seems that currently what is supported is JBDS 6 and up. But this needs verification. Do we need that column at all? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19223) Revise support status in support matrix doc

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19223?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19223: ------------------------------- Fix Version/s: 4.2.2.Final > Revise support status in support matrix doc > ------------------------------------------- > > Key: JBIDE-19223 > URL: https://issues.jboss.org/browse/JBIDE-19223 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.2.Final > > > This doc contains a column called "Supported?": > https://developer.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec... > All of the version since JBDS/RHDS 1 say they are supported. This is not true. > It seems that currently what is supported is JBDS 6 and up. But this needs verification. Do we need that column at all? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3162) Change "jboss-eap" to "JBoss Enterprise Application Platform"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3162?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3162: ------------------------------------------- "As I've already said, it would seem very strange to have JBoss EAP, JBoss EWP, JBoss AS, JBoss JPP, and JBoss Fuse Service Works. It would be more reasonable to lobby that FSW simply become an approved abbreviation." Please start that lobbying - until the result of the lobbying is known we use the approved abbreviation. > Change "jboss-eap" to "JBoss Enterprise Application Platform" > ------------------------------------------------------------- > > Key: JBDS-3162 > URL: https://issues.jboss.org/browse/JBDS-3162 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: runtime-detection, server, ui/branding > Reporter: Burr Sutter > Assignee: Rob Stryker > Labels: f2f2014 > Fix For: 9.0.0.Alpha2 > > Attachments: JBDS-3162.suggested.png, JBDS-3162.suggested2.png > > > When installing JBDS+EAP (same installer), the default name under the Servers tab is "jboss-eap". This is a request to have that default server name changed to "JBoss Enterprise Application Platform". > And the default runtime name to "JBoss EAP Runtime". > http://www.screencast.com/t/POpKcyHjhtlP > http://www.screencast.com/t/LZdFW0rJu0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3273: ----------------------------------- That pretty much sound like what I need. My only concern is if you need to import 2 quickstarts that are not modules under a root parent. quickstart_id(s) could be a collection type > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2015