July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17615) When runtime download asks to reenter credentials, it will not accept them even if valid

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17615?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17615: --------------------------------------- I wanted to try the use case I previously mentioned: 1. User starts the runtime download dialog, enters correct credentials, moves to license 2. User changes his password on jboss.org 3. User carries on in the dialog to actually start the download - now he will probably be asked to correct his credentials But for that I need to change my password at jboss.org, which currently doesn't work for me - reported here: ORG-3476 So I will revisit this later. > When runtime download asks to reenter credentials, it will not accept them even if valid > ---------------------------------------------------------------------------------------- > > Key: JBIDE-17615 > URL: https://issues.jboss.org/browse/JBIDE-17615 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2c B130 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > > I was playing around JBIDE-17601 - that JIRA is about the bug that JBoss.org credentials were not validated when you went through new archetype from central -> Download & Install. So you could enter anything and it would let you carry on. But once the real download is about to start, you will get a popup to enter the credentials again (since the downloader needs the correct password). Even if you now enter the correct credentials, it will ask you 2 more times and then fail on Incorrect password. > Yes, this will be less likely to happen once JBIDE-17601 is fixed. But I suppose that the popup is in place exactly for the situation when the password needs to be corrected, so it should work, right? > There may still be a valid use case to hit this issue (although a very rare case): > 1. User starts the runtime download dialog, enters correct credentials, moves to license > 2. User changes his password on jboss.org > 3. User carries on in the dialog to actually start the download - now he will probably be asked to correct his credentials > So in my opinion, if we already have a mechanism to ask for credentials again, then it should work. If you say this is not needed, then why even allow the popup? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22699) BrowserUtilTest.testCreateBrowser failure

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22699?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22699: -------------------------------- Sprint: (was: devex #117 July 2016) > BrowserUtilTest.testCreateBrowser failure > ----------------------------------------- > > Key: JBIDE-22699 > URL: https://issues.jboss.org/browse/JBIDE-22699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22699) BrowserUtilTest.testCreateBrowser failure

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22699?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22699: -------------------------------- Sprint: devex #118 July 2017 > BrowserUtilTest.testCreateBrowser failure > ----------------------------------------- > > Key: JBIDE-22699 > URL: https://issues.jboss.org/browse/JBIDE-22699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Import wizard: Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22079: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.x) > Import wizard: Error when import a project already existing in workspace > ------------------------------------------------------------------------ > > Key: JBIDE-22079 > URL: https://issues.jboss.org/browse/JBIDE-22079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: import-error.png > > > When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear). > Error: > {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts. > One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again. > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Import wizard: Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22079: ------------------------------------------ merged into master > Import wizard: Error when import a project already existing in workspace > ------------------------------------------------------------------------ > > Key: JBIDE-22079 > URL: https://issues.jboss.org/browse/JBIDE-22079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: import-error.png > > > When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear). > Error: > {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts. > One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again. > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22362: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.x) > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.AM3 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22680: ---------------------------------------- Thanks [~rawagner] . Do you think you could create jobs for all components? > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > Fix For: 4.4.x > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22672. --------------------------------- Closing. > PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.AM1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-784) Include New SAP Tooling and SAP Data Layer for Mars branch

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-784?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-784. ----------------------------------- I'm closing this issue since it was handled in a different way > Include New SAP Tooling and SAP Data Layer for Mars branch > ---------------------------------------------------------- > > Key: JBTIS-784 > URL: https://issues.jboss.org/browse/JBTIS-784 > Project: JBoss Tools Integration Stack > Issue Type: Component Upgrade > Components: distribution, Fuse IDE > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > I don't know how to process exactly. > Do I modify the URl here? https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > There is currently no new Tag. > We need to pick the 6.3.0-SNAPSHOT for SAP Data Layer from this update site: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... > The SAP Tooling should be retrieved from http://download.jboss.org/jbosstools/mars/integration/updates/integration... > Where do I need to modify something to be able to test it? > When teher will be a release, I will need to update again the file? or there some automatic mechanism possible? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-794) Deprecate ModeShape for 9.0.1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-794?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-794. ----------------------------------- Verified with JBDS-IS 9.0.1.CR2 > Deprecate ModeShape for 9.0.1 > ----------------------------- > > Key: JBTIS-794 > URL: https://issues.jboss.org/browse/JBTIS-794 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, modeshape > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.1.Final, 9.0.1.GA > > Attachments: modeshape_deprecated_1.png, modeshape_deprecated_2.png > > > Deprecate ModeShape - update labels. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016