June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17496: ---------------------------------- Description: When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). It looks like there is a race condition. Several times when I tried to install Findbugs, I got: {quote} The following connectors are not available: FindBugs Proceed with the installation anyways? {quote} Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 !connector-error.png! Another time I got a different error. was: When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). It looks like there is a race condition. Several times when I tried to install Findbugs, I got: {quote} The following connectors are not available: FindBugs Proceed with the installation anyways? {quote} Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 Another time I got a different error. > Central installation fails if done right after Eclipse start > ------------------------------------------------------------ > > Key: JBIDE-17496 > URL: https://issues.jboss.org/browse/JBIDE-17496 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2a B106 > Reporter: Martin Malina > Attachments: connector-error.png > > > When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. > I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). > It looks like there is a race condition. > Several times when I tried to install Findbugs, I got: > {quote} > The following connectors are not available: FindBugs > Proceed with the installation anyways? > {quote} > Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 > !connector-error.png! > Another time I got a different error. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17496: ---------------------------------- Description: When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). It looks like there is a race condition. Several times when I tried to install Findbugs, I got: {quote} The following connectors are not available: FindBugs Proceed with the installation anyways? {quote} Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 !connector-error.png! If I proceed anyway, the install dialog is empty. Another time I got a different error. was: When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). It looks like there is a race condition. Several times when I tried to install Findbugs, I got: {quote} The following connectors are not available: FindBugs Proceed with the installation anyways? {quote} Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 !connector-error.png! Another time I got a different error. > Central installation fails if done right after Eclipse start > ------------------------------------------------------------ > > Key: JBIDE-17496 > URL: https://issues.jboss.org/browse/JBIDE-17496 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2a B106 > Reporter: Martin Malina > Attachments: connector-error.png > > > When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. > I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). > It looks like there is a race condition. > Several times when I tried to install Findbugs, I got: > {quote} > The following connectors are not available: FindBugs > Proceed with the installation anyways? > {quote} > Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 > !connector-error.png! > If I proceed anyway, the install dialog is empty. > Another time I got a different error. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17496: ---------------------------------- Attachment: connector-error.png > Central installation fails if done right after Eclipse start > ------------------------------------------------------------ > > Key: JBIDE-17496 > URL: https://issues.jboss.org/browse/JBIDE-17496 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2a B106 > Reporter: Martin Malina > Attachments: connector-error.png > > > When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. > I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). > It looks like there is a race condition. > Several times when I tried to install Findbugs, I got: > {quote} > The following connectors are not available: FindBugs > Proceed with the installation anyways? > {quote} > Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 > Another time I got a different error. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start

by Martin Malina (JIRA)

Martin Malina created JBIDE-17496: ------------------------------------- Summary: Central installation fails if done right after Eclipse start Key: JBIDE-17496 URL: https://issues.jboss.org/browse/JBIDE-17496 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.2.0.Beta2 Environment: JBDS 8.0.0.Beta2a B106 Reporter: Martin Malina When you try to install something from Central as soon as JBDS starts for the first time, you can get errors. I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached). It looks like there is a race condition. Several times when I tried to install Findbugs, I got: {quote} The following connectors are not available: FindBugs Proceed with the installation anyways? {quote} Followed by the Computing connector errors with NPEs familiar from JBIDE-17471 Another time I got a different error. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17469) Find proper way to check for allowed/supported runtime (no mo' strings please)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17469?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17469: ------------------------------------- ASTools is undergoing pressures on a bunch of sides. We have FuseIDE looking to use our tools, and asking us to push more API down into as.wtp.core and as.wtp.ui. On the other hand, we have consumers like you, who want to be able to depend on our interfaces and some constants without pulling in too many dependencies. Under issue right now is that some classes in as.ui may need to be pushed down to as.wtp.ui, but these classes depend on things like jbosstools-base/runtimes. I'll be looking to minimize the damage here, but, something needs to be done. > Find proper way to check for allowed/supported runtime (no mo' strings please) > ------------------------------------------------------------------------------ > > Key: JBIDE-17469 > URL: https://issues.jboss.org/browse/JBIDE-17469 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > JBIDE-17247 was fixed by using String comparison. There must be a more robust way to check for the appropriate runtime. > [~rob.stryker], please advise. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17494) Download Runtimes not validating credentials when launched from new server wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17494?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17494. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.2.0.Beta3 Resolution: Done pushed > Download Runtimes not validating credentials when launched from new server wizard > --------------------------------------------------------------------------------- > > Key: JBIDE-17494 > URL: https://issues.jboss.org/browse/JBIDE-17494 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > When entering the download-runtimes wizard via the hyperlink in a new runtime wizard, your credentials are not validated at all, and T&C are not shown. > This is due to the new runtime wizard being launched via a normal WizardDialog instead of via the enhancde TaskWizardDialog, which properly forwards calls to nextPressed to the fragment so it can do long-running tasks during the press of the 'next' button. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17494) Download Runtimes not validating credentials when launched from new server wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17494?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17494: ------------------------------------- The diff is as follows: - WizardDialog dialog = new WizardDialog(downloadAndInstallButton.getShell(), wizard); + WizardDialog dialog = new TaskWizardDialog(downloadAndInstallButton.getShell(), wizard); There is also a new import. > Download Runtimes not validating credentials when launched from new server wizard > --------------------------------------------------------------------------------- > > Key: JBIDE-17494 > URL: https://issues.jboss.org/browse/JBIDE-17494 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > > When entering the download-runtimes wizard via the hyperlink in a new runtime wizard, your credentials are not validated at all, and T&C are not shown. > This is due to the new runtime wizard being launched via a normal WizardDialog instead of via the enhancde TaskWizardDialog, which properly forwards calls to nextPressed to the fragment so it can do long-running tasks during the press of the 'next' button. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17495) Duplicate mylin central connector

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17495?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17495: ---------------------------------- Fix Version/s: 4.2.0.Beta2 > Duplicate mylin central connector > --------------------------------- > > Key: JBIDE-17495 > URL: https://issues.jboss.org/browse/JBIDE-17495 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Environment: JBT 4.2.0.Beta2a B113 > JBDS 8.0.0.Beta2a B106 > Reporter: Martin Malina > Fix For: 4.2.0.Beta2 > > > After I open the software tab in Central, I get this in the workspace log: > {code} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2014-06-02 10:34:17.612 > !MESSAGE Duplicate category id 'org.jboss.tools.central.discovery.a.web': declaring sources: org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_5476860046903147773.jar, org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_7457645340608527583.jar > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2014-06-02 10:34:17.612 > !MESSAGE Duplicate certification id 'com.jboss.jbds.discovery.certification.earlyaccess': declaring sources: org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_5476860046903147773.jar, org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_7457645340608527583.jar > {code} > This is copied from JBT, but similar thing happens with JBDS. > I didn't use any custom discovery properties, so Beta2a should be used. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17495) Duplicate mylin central connector

by Martin Malina (JIRA)

Martin Malina created JBIDE-17495: ------------------------------------- Summary: Duplicate mylin central connector Key: JBIDE-17495 URL: https://issues.jboss.org/browse/JBIDE-17495 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.2.0.Beta2 Environment: JBT 4.2.0.Beta2a B113 JBDS 8.0.0.Beta2a B106 Reporter: Martin Malina After I open the software tab in Central, I get this in the workspace log: {code} !ENTRY org.eclipse.mylyn.discovery.core 4 0 2014-06-02 10:34:17.612 !MESSAGE Duplicate category id 'org.jboss.tools.central.discovery.a.web': declaring sources: org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_5476860046903147773.jar, org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_7457645340608527583.jar !ENTRY org.eclipse.mylyn.discovery.core 4 0 2014-06-02 10:34:17.612 !MESSAGE Duplicate certification id 'com.jboss.jbds.discovery.certification.earlyaccess': declaring sources: org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_5476860046903147773.jar, org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_7457645340608527583.jar {code} This is copied from JBT, but similar thing happens with JBDS. I didn't use any custom discovery properties, so Beta2a should be used. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17494) Download Runtimes not validating credentials when launched from new server wizard

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-17494: ----------------------------------- Summary: Download Runtimes not validating credentials when launched from new server wizard Key: JBIDE-17494 URL: https://issues.jboss.org/browse/JBIDE-17494 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Beta2 Reporter: Rob Stryker When entering the download-runtimes wizard via the hyperlink in a new runtime wizard, your credentials are not validated at all, and T&C are not shown. This is due to the new runtime wizard being launched via a normal WizardDialog instead of via the enhancde TaskWizardDialog, which properly forwards calls to nextPressed to the fragment so it can do long-running tasks during the press of the 'next' button. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 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 June 2014