May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher refresh view but collapse tree items to project level

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22361: -------------------------------- Fix Version/s: 4.4.0.Alpha2 Sprint: devex #114 May 2016 > OpenShift Explorer: Watcher refresh view but collapse tree items to project level > --------------------------------------------------------------------------------- > > Key: JBIDE-22361 > URL: https://issues.jboss.org/browse/JBIDE-22361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod in running state. Once watcher should update resources automatically, tree items are collapsed to project level (if service was visible, it is not anymore, only connection with its project). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3887) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3887?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3887: -------------------------------------- +1 for container tools. > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10 > --------------------------------------------------------- > > Key: JBDS-3887 > URL: https://issues.jboss.org/browse/JBDS-3887 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 10.0.0.Alpha2 > > > Include Docker & Vagrant tooling 2.0.0 in JBoss Tools 4.4 & DS 10... somehow. (Mechanism to be clarified below.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3887) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3887?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3887: ---------------------------------- [~akazakov] Thanks for your clarification. Docker is already in the "CoreTools" (Abridged) category for JBT. It's also in the GeneralTools category: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... I'll do the same for devstudio. Perhaps we should use the CloudTools category (currently includes Openshift and CDK features)? https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... Or a new one for ContainerTools? > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10 > --------------------------------------------------------- > > Key: JBDS-3887 > URL: https://issues.jboss.org/browse/JBDS-3887 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 10.0.0.Alpha2 > > > Include Docker & Vagrant tooling 2.0.0 in JBoss Tools 4.4 & DS 10... somehow. (Mechanism to be clarified below.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22360) Extract OAuth token from the New Connection wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22360?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22360: -------------------------------- Labels: new_and_noteworthy (was: ) > Extract OAuth token from the New Connection wizard > -------------------------------------------------- > > Key: JBIDE-22360 > URL: https://issues.jboss.org/browse/JBIDE-22360 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Minor > Labels: new_and_noteworthy, ux > Fix For: 4.4.0.Alpha2 > > > When creating a new connection in OAuth mode, the user can use an integrated browser to connect to Openshift and once connected, the page displays the token. We could extract the token from that page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22360) Extract OAuth token from the New Connection wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22360?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22360: -------------------------------- Labels: new_and_noteworthy ux (was: new_and_noteworthy) > Extract OAuth token from the New Connection wizard > -------------------------------------------------- > > Key: JBIDE-22360 > URL: https://issues.jboss.org/browse/JBIDE-22360 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Minor > Labels: new_and_noteworthy, ux > Fix For: 4.4.0.Alpha2 > > > When creating a new connection in OAuth mode, the user can use an integrated browser to connect to Openshift and once connected, the page displays the token. We could extract the token from that page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-654: -------------------------------------- Why do u want to blow up the size of the installer in that way? Sometimes less is more. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3884) Define the version of EAP that we embed with next major version of devstudio

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3884?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3884: --------------------------------- Fix Version/s: 10.x (was: 10.0.0.GA) > Define the version of EAP that we embed with next major version of devstudio > ---------------------------------------------------------------------------- > > Key: JBDS-3884 > URL: https://issues.jboss.org/browse/JBDS-3884 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: runtime > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Assignee: Todd Mancini > Fix For: 10.x > > > Should it continue to be EAP 6.x or the new EAP 7.0 ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3887) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3887?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3887: -------------------------------------- IMO Docker tooling should be a first class citizen in both devstudio and JBT. But Vagrant tooling is very optional. JBT: - Docker tooling should be in "JBoss Tools Abridged" category. Add to marketplace connector. - Vagrant tooling should bi included in some other update site category to be available as optional installs. Not sure what category to use. Devstudio: - Docker tooling should be installed OOTB. + BYOE category + marketplace. - Vagrant tooling should bi included in some other update site category to be available as optional installs. Not sure what category to use. > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10 > --------------------------------------------------------- > > Key: JBDS-3887 > URL: https://issues.jboss.org/browse/JBDS-3887 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 10.0.0.Alpha2 > > > Include Docker & Vagrant tooling 2.0.0 in JBoss Tools 4.4 & DS 10... somehow. (Mechanism to be clarified below.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22286) JavaModelException below EclipseJavaUtil.findType (thrown in Openable.generateInfos)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22286?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-22286. ------------------------------------ Resolution: Rejected > JavaModelException below EclipseJavaUtil.findType (thrown in Openable.generateInfos) > ------------------------------------------------------------------------------------ > > Key: JBIDE-22286 > URL: https://issues.jboss.org/browse/JBIDE-22286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Alexey Kazakov > Fix For: 4.4.0.Alpha2 > > > The following problem was reported via the automated error reporting: > Message: jboss-javaee-webapp does not exist > {noformat} > org.eclipse.jdt.core.JavaModelException: jboss-javaee-webapp does not exist > at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566) > at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1642) > at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2329) > at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2339) > at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1357) > at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1264) > at org.jboss.tools.common.util.EclipseJavaUtil.findType(EclipseJavaUtil.java:115) > at org.jboss.tools.common.java.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:157) > at org.jboss.tools.common.java.ParametedType.buildInheritance(ParametedType.java:259) > at org.jboss.tools.common.java.ParametedType.getInheritedTypes(ParametedType.java:308) > at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:400) > at org.jboss.tools.common.java.ParametedType.getAllTypes(ParametedType.java:388) > at org.jboss.tools.cdi.internal.core.impl.ProducerMethod.getAllTypes(ProducerMethod.java:112) > at org.jboss.tools.cdi.internal.core.impl.ProducerMethod.getLegalTypes(ProducerMethod.java:94) > at org.jboss.tools.cdi.internal.core.impl.CDICache.addBean(CDICache.java:319) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.addBean(CDIProject.java:1451) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1396) > at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1216) > at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:267) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > {noformat} > Bundles: > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.12.0.v20160317-0200 | > | org.eclipse.jdt.core | 3.11.0.xx-201603042130-e45 | 3.12.0.v20160315-2126 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jst.common.project.facet.core | 1.4.400.v201403261418 | 1.4.400.v201403261418 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 | > | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | > | org.jboss.tools.batch.core | 1.7.1.CR1-v20160129-2014-B69 | 1.7.1.Final-v20160330-2256-B84 | > | org.jboss.tools.cdi.core | 1.7.1.CR1-v20160129-2014-B69 | 1.8.0.Alpha1-v20160421-2020-B942 | > | org.jboss.tools.common | 3.7.1.CR1-v20160219-2136-B86 | 3.8.0.Alpha1-v20160426-0436-B918 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Alpha1-v20160426-0436-B918 | > | org.jboss.tools.jst.web | 3.7.1.CR1-v20160128-1907-B79 | 3.7.1.Final-v20160331-0256-B96 | > | org.jboss.tools.jst.web.kb | 3.7.1.CR1-v20160128-1907-B79 | 3.7.1.Final-v20160331-0256-B96 | > Operating Systems: > | Linux | 3.13.0 | 4.2.0 | > | MacOSX | 10.11.3 | 10.11.4 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56cb04afe4b0f02ab7...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22355) JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22355: ------------------------------- Summary: JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2 (was: Build qualifier still say Alpha2) > JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2 > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22355 > URL: https://issues.jboss.org/browse/JBIDE-22355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1. > All those should be moved to Alpha2 (they should be moved just when branching/releasing actually) -- 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 May 2016