October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-504: ----------------------------- Attachment: jbtis-disc-ea.png jbtis-disc.png > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBTIS-504: ------------------------------------ So, if I understand Paul's suggestion, we'll have a single non-selectable note in place of the warning messages for the first several/many messages informing the user that some selections are only available through early access. That's a much better solution! > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-504: ---------------------------------- Why not reuse the connector ID from the NA one as the connector ID for the first one that becomes available? Then it should disappear, along with its NA category. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBTIS-504: -------------------------------------- JBT looks good to me. JBDS message is a little bit long so it's cut. But anyway. It's much better now. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-504: ---------------------------------- This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !disc-jbtis.png|thumbnail! !disc-jbtis-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-504: ----------------------------- Attachment: disc-jbdsis.png disc-jbdsis-ea.png disc-jbtis-ea.png disc-jbtis.png > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20914) make jbds-dist-diff more user-friendly and scriptable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20914?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20914: ------------------------------------ {code} $➔ ./jbds-dist-diff.sh ~/tmp/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone.jar ~/tmp/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar [INFO] Install /home/nboldt/tmp/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone.jar into /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone real 1m57.235s user 2m37.254s sys 0m26.206s [INFO] Installed in /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.CR2-v20150925-1252-B116-installer-standalone [INFO] Install /home/nboldt/tmp/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone.jar into /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone real 1m56.286s user 2m33.083s sys 0m27.052s [INFO] Installed in /tmp/tmp.bStU70UhlX/jboss-devstudio-9.0.0.GA-v20151002-2235-B124-installer-standalone BUILD FAILED /home/nboldt/truu/jbdevstudio-qa/jbds-dist-diff/diff.xml:10: Unexpected differences were found or expected differences were not found Total time: 11 seconds real 0m11.890s user 0m16.530s sys 0m2.523s [INFO] Logs are in /tmp/tmp.bStU70UhlX: [INFO] * /tmp/tmp.bStU70UhlX/old_dir_file_list.log.txt [INFO] * /tmp/tmp.bStU70UhlX/new_dir_file_list.log.txt [INFO] * /tmp/tmp.bStU70UhlX/dist-diff.log.txt [INFO] * /tmp/tmp.bStU70UhlX/dist-diff-grepped-no-manifests.log.txt [INFO] * /tmp/tmp.bStU70UhlX/dist-diff-grepped-no-signatures.log.txt {code} -- PR: https://github.com/jbdevstudio/jbdevstudio-qa/pull/82 > make jbds-dist-diff more user-friendly and scriptable > ----------------------------------------------------- > > Key: JBIDE-20914 > URL: https://issues.jboss.org/browse/JBIDE-20914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR2, 4.4.0.Alpha1 > Reporter: Nick Boldt > > Did some digging into the https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/jbds-dist-diff tool and discovered that its doc is not entirely straightforward. > Also, it doesn't support headless JBDS installs, so it needs human bootstrapping. > I propose making it support headless installs so it's more easily scriptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20914) make jbds-dist-diff more user-friendly and scriptable

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20914: ---------------------------------- Summary: make jbds-dist-diff more user-friendly and scriptable Key: JBIDE-20914 URL: https://issues.jboss.org/browse/JBIDE-20914 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.0.CR2, 4.4.0.Alpha1 Reporter: Nick Boldt Did some digging into the https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/jbds-dist-diff tool and discovered that its doc is not entirely straightforward. Also, it doesn't support headless JBDS installs, so it needs human bootstrapping. I propose making it support headless installs so it's more easily scriptable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20677) Cannot finish Install dialog called from central in some scenarios

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20677?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20677: ---------------------------------- Component/s: upstream > Cannot finish Install dialog called from central in some scenarios > ------------------------------------------------------------------ > > Key: JBIDE-20677 > URL: https://issues.jboss.org/browse/JBIDE-20677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Affects Versions: 4.3.0.CR1 > Environment: Linux x86_64 gtk3 > Reporter: Denis Golovin > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: recording.mp4 > > > After pressing "Deselect All" and "Select All" buttons in Install dialog finish button is not available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20677) Cannot finish Install dialog called from central in some scenarios

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20677?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20677: --------------------------------------- This is an upstream issue. I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=479063. > Cannot finish Install dialog called from central in some scenarios > ------------------------------------------------------------------ > > Key: JBIDE-20677 > URL: https://issues.jboss.org/browse/JBIDE-20677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR1 > Environment: Linux x86_64 gtk3 > Reporter: Denis Golovin > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: recording.mp4 > > > After pressing "Deselect All" and "Select All" buttons in Install dialog finish button is not available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 October 2015