May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-423: ---------------------------------- Okay - I'll go back to a common connector ID between release/ EA. I'll go back to a common category ID as well (to avoid having two categories) and re-examine the origin error. The original error was not blocking installation - it just showed up in the error log. > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-418) Cannot install JBDS-IS from downloaded zip into JBDS when offline

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-418?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-418: ---------------------------------- [~dgolovin] - Hey Denis - I'm unsure what to do with this. I'd say having to specify jboss-devstudio-8.0.2.GA-updatesite-core.zip in full offline mode is reasonable. > Cannot install JBDS-IS from downloaded zip into JBDS when offline > ----------------------------------------------------------------- > > Key: JBTIS-418 > URL: https://issues.jboss.org/browse/JBTIS-418 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Affects Versions: 8.0.0.GA > Environment: Linux x86_64 Open JDK 7 > JBDS 8.0.0.GA-v20141020-1042-B317 > JBDS IS 8.0.0.GA > Reporter: Denis Golovin > Assignee: Paul Leacu > > While was testing possible solutions for including JBDS IS into JBDS Installer I realized that there something missing in JBDS or IS zip. Offfline installation into JBDS 8.0.0.GA fails with > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Data Virtualization Development (ModeShape, Teiid Designer) 8.0.0.201502201745 (com.jboss.devstudio.integration-stack.ds.feature.feature.group 8.0.0.201502201745) > Missing requirement: JBoss Data Virtualization Development (ModeShape, Teiid Designer) 8.0.0.201502201745 (com.jboss.devstudio.integration-stack.ds.feature.feature.group 8.0.0.201502201745) requires 'org.jboss.tools.usage.feature.feature.group 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19758) when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19758?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19758: ------------------------------- Fix Version/s: 4.2.3.Final > when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19758 > URL: https://issues.jboss.org/browse/JBIDE-19758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.3.Final > Reporter: Nick Boldt > Fix For: 4.2.3.Final > > > Seems somewhere between 4.2.x and 4.3.x we stopped moving /builds/staging/jbosstools-4.2.x.Final-* folders into /static/releases/ > Need to fix that (by hand) and ensure we don't forget to do this for any future 4.2.x releases (if any happen). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19758) when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19758?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19758: ---------------------------------- Assignee: Nick Boldt > when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19758 > URL: https://issues.jboss.org/browse/JBIDE-19758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.3.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.3.Final > > > Seems somewhere between 4.2.x and 4.3.x we stopped moving /builds/staging/jbosstools-4.2.x.Final-* folders into /static/releases/ > Need to fix that (by hand) and ensure we don't forget to do this for any future 4.2.x releases (if any happen). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16755) Confirmation pop-up when installing JRebel from Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16755?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-16755. ------------------------------ > Confirmation pop-up when installing JRebel from Central > ------------------------------------------------------- > > Key: JBIDE-16755 > URL: https://issues.jboss.org/browse/JBIDE-16755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery, upstream > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.3.0.Alpha2 > > Attachments: install-grinder-takes-forever.png, JBIDE-16755.jpeg, testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg > > > (Previously discussed in JBIDE-16269) > These builds are timing out: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19758) when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /static/releases for archiving

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19758?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19758: ------------------------------------ I've moved all the 4.2.0.Final - 4.2.3.Final build folders from /builds/staging/ to /builds/stable/: http://download.jboss.org/jbosstools/builds/stable/ > when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /static/releases for archiving > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19758 > URL: https://issues.jboss.org/browse/JBIDE-19758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.3.Final > Reporter: Nick Boldt > > Seems somewhere between 4.2.x and 4.3.x we stopped moving /builds/staging/jbosstools-4.2.x.Final-* folders into /static/releases/ > Need to fix that (by hand) and ensure we don't forget to do this for any future 4.2.x releases (if any happen). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19758) when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19758?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19758: ------------------------------- Summary: when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving (was: when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /static/releases for archiving) > when released, should move JBT 4.2.x.Final folders from /builds/staging/ into /builds/stable/ for archiving > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19758 > URL: https://issues.jboss.org/browse/JBIDE-19758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.3.Final > Reporter: Nick Boldt > > Seems somewhere between 4.2.x and 4.3.x we stopped moving /builds/staging/jbosstools-4.2.x.Final-* folders into /static/releases/ > Need to fix that (by hand) and ensure we don't forget to do this for any future 4.2.x releases (if any happen). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-423: ------------------------------------------- btw. since EA contains the released content (as it should) I really do not see the problem. If users want to install only supported content they unselect "early access". > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-423: ------------------------------------------- We do *not* want both selectable. Users that do not want to use early access content should not enable early access. We already have the case of same ID's in Core - angularjs exists in both released and early release options. This is how it is intended to work. I'll repeat that by doing this you've done now you are breaking proxy wizards. The connector ID's should not be different. Still not following why you have problems with the category ID's - I haven't seen that in our usage. > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-432) Cannot install JBoss Integration and SOA Development from non-earlyaccess site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-432?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-432. ------------------------------ Fix Version/s: 8.0.2.CR1 Resolution: Done Removed SOA from Eclipse Marketplace eligible tooling since SwitchYard is unavailable until 8.0.3. https://github.com/jbosstools/jbosstools-integration-stack/commit/b813b57... > Cannot install JBoss Integration and SOA Development from non-earlyaccess site > ------------------------------------------------------------------------------ > > Key: JBTIS-432 > URL: https://issues.jboss.org/browse/JBTIS-432 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.CR1 > Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.2.ER1 (without earlyaccess) > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 8.0.2.CR1 > > > Cannot install JBoss Integration and SOA Development from non-earlyaccess site, namely if you try to install com.jboss.devstudio.integration-stack.soa.feature. > Note that this is not a common use case since you have to uncheck 'Group items by category' during installation. > The problem is that this feature includes switchyard features which are available only on early access. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015