April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21441: ---------------------------------------- Updated PR for Neon: https://github.com/jbosstools/jbosstools-target-platforms/pull/204 > Consume m2e Easymport integration from upstream > ----------------------------------------------- > > Key: JBIDE-21441 > URL: https://issues.jboss.org/browse/JBIDE-21441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, playground, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport. > That would require to get a recent version of m2e in TP. > *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 1.7.0 > *License and owner:* EPL, m2e project (Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160... > *Include Sources:* No > *Affected JBoss Tools components:* playground, maven > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > + org.eclipse.m2e.importer > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21441: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/204 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/193) > Consume m2e Easymport integration from upstream > ----------------------------------------------- > > Key: JBIDE-21441 > URL: https://issues.jboss.org/browse/JBIDE-21441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, playground, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport. > That would require to get a recent version of m2e in TP. > *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 1.7.0 > *License and owner:* EPL, m2e project (Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160... > *Include Sources:* No > *Affected JBoss Tools components:* playground, maven > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > + org.eclipse.m2e.importer > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21478) New Server adapter using same build config and server is ignored

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21478?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21478. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > New Server adapter using same build config and server is ignored > ---------------------------------------------------------------- > > Key: JBIDE-21478 > URL: https://issues.jboss.org/browse/JBIDE-21478 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created. > I would expect one of following: > a) An existing server adapter will be updated according to the latest details filled in server adapter wizard > b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21940) Deploying specific docker images doesn't always result in a deployment on openshift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21940?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21940. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Deploying specific docker images doesn't always result in a deployment on openshift > ----------------------------------------------------------------------------------- > > Key: JBIDE-21940 > URL: https://issues.jboss.org/browse/JBIDE-21940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21970) Allow user to turn on/off showing console when output changes

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21970?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21970. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Allow user to turn on/off showing console when output changes > ------------------------------------------------------------- > > Key: JBIDE-21970 > URL: https://issues.jboss.org/browse/JBIDE-21970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3698) Installer - We should document (rel notes) the versions of the installable components that we support

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3698?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3698: ----------------------------------- There is one more thing I forgot to mention here - as of this version, if an older than required version is found, the installer will not let you proceed until you have dealt with it on your own. Plus in this release you are very much stuck with what the installer detects (you can't choose if you want to use the detected version or install anew). Thus if an old version is detected, you have to quit the installer, uninstall the software in question and start the installer again. Might be worth noting in the docs :) > Installer - We should document (rel notes) the versions of the installable components that we support > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-3698 > URL: https://issues.jboss.org/browse/JBDS-3698 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > It's good that the installer will allow users to have/retain their own installed components, and verify that the installed versions are supported, but we should provide the users with a documented list of the ranges of supported versions. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21713) Eclipse freeze when trying to reconnect to an existing connection

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21713?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21713. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Eclipse freeze when trying to reconnect to an existing connection > ----------------------------------------------------------------- > > Key: JBIDE-21713 > URL: https://issues.jboss.org/browse/JBIDE-21713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: connection, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > On nightly build of OpenShift tooling when I am trying to reconnect to an existing connection, whole IDE freeze. E.g. after restart of eclipse and token to server has not been stored in secure storage, I am prompted to enter token when trying to do anything with an existing OS3 connection and upon entering a token and hitting Finish button, IDE freeze and after a while its not responding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22253) Update to SWTBot 2.4.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22253?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22253: ----------------------------------- Description: *Reason:* SWTBot 2.4.0 comes with several fixes (about menus) and other that JBT/JBDS can probably take advantage of *Project page/sources:* http://eclipse.org/swtbot *Version:* 2.4.0 *License and owner:* EPL, Eclipse.org *Original p2 repo:* http://download.eclipse.org/technology/swtbot/releases/2.4.0 *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.4.0/ *Include Sources:* No *Affected JBoss Tools components:* tests *Include in JBDS:* No *Type of dependency:* testing *List of bundles added/removed:* {code} {code} If applicable: *non-p2 repository:* ... *non-p2 ids:* ... was: *Reason:* SWTBot 2.4.0 comes with several fixes (about menus) and other that JBT/JBDS can probably take advantage of *Project page/sources:* http://eclipse.org/swtbot *Version:* 2.4.0 *License and owner:* EPL, Eclipse.org *Original p2 repo:* http://download.eclipse.org/technology/swtbot/releases/2.4.0 *JBoss mirror:* *Include Sources:* No *Affected JBoss Tools components:* tests *Include in JBDS:* No *Type of dependency:* testing *List of bundles added/removed:* {code} {code} If applicable: *non-p2 repository:* ... *non-p2 ids:* ... > Update to SWTBot 2.4.0 > ---------------------- > > Key: JBIDE-22253 > URL: https://issues.jboss.org/browse/JBIDE-22253 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa, target-platform > Affects Versions: 4.3.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > *Reason:* SWTBot 2.4.0 comes with several fixes (about menus) and other that JBT/JBDS can probably take advantage of > *Project page/sources:* http://eclipse.org/swtbot > *Version:* 2.4.0 > *License and owner:* EPL, Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/swtbot/releases/2.4.0 > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.4.0/ > *Include Sources:* No > *Affected JBoss Tools components:* tests > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21168) Fix test failures in master

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21168?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21168. --------------------------------- > Fix test failures in master > --------------------------- > > Key: JBIDE-21168 > URL: https://issues.jboss.org/browse/JBIDE-21168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > In master [jenkins|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/...] currently reports test errors: > {code} > Tests in error: > NewApplicationWizardModelTest.getParametersShouldReturnAParameterMapWhenTemplateIsNotNull:121->givenTheTemplateHasParameters:131 NoSuchMethod > NewApplicationWizardModelTest.setTemplateShouldCopyParametersAndLabels:72->givenTheTemplateHasParameters:131 NoSuchMethod > NewApplicationWizardModelTest.resetParameterShouldSetTheOriginalValue:97 NoSuchMethod > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21706) Server adapter wizard: pod deployment path is always default (/opt/app-root/src)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21706?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21706. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Server adapter wizard: pod deployment path is always default (/opt/app-root/src) > -------------------------------------------------------------------------------- > > Key: JBIDE-21706 > URL: https://issues.jboss.org/browse/JBIDE-21706 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 April 2016