January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 Beta2: Update support page with fedora versions

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-708: ------------------------------- Sprint: 18-Jan >> 31-Jan 2016-JBDS/JBT (was: 01-Feb >> 14-Feb 2016-JBDS/JBT) > JBDS 9.1 Beta2: Update support page with fedora versions > -------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Attachments: screenshot_support.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 Beta2: Update support page with fedora versions

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-708: ------------------------------- Attachment: screenshot_support.png Updated support page. > JBDS 9.1 Beta2: Update support page with fedora versions > -------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Attachments: screenshot_support.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3576) Add products that JBDSIS is supported against to the CSP

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3576?page=com.atlassian.jira.plugin.... ] Misha Ali closed JBDS-3576. --------------------------- Resolution: Done Fixed here: https://access.redhat.com/articles/427493 > Add products that JBDSIS is supported against to the CSP > -------------------------------------------------------- > > Key: JBDS-3576 > URL: https://issues.jboss.org/browse/JBDS-3576 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 9.0.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > Labels: Support > Fix For: 9.1.0.Beta2 > > Attachments: Tooling_Support.png > > > On JBDSIS Supported configurations page [1], there is no mention of the products and the versions compatible. We should add which JBDSIS products are supported against which version of the tooling. i.e. JBDSIS 7.0.x only works with Fuse 6.1 and earlier. > We need a full list from JBDSIS team of tested and supported products. > [1] https://access.redhat.com/articles/1351903 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21441: ------------------------------------- Forgot to post that here : the snapshots can be accessed from http://download.eclipse.org/technology/m2e/snapshots/1.7.0/ now. > 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 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.x, 4.4.x > > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21559) Should can select a container to show logs when the pod contains more than 1 containers

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21559?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21559: ----------------------------------------------- [~fbricon], my guess for containers number is IPod.getImages().size() > Should can select a container to show logs when the pod contains more than 1 containers > --------------------------------------------------------------------------------------- > > Key: JBIDE-21559 > URL: https://issues.jboss.org/browse/JBIDE-21559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156 > Reporter: Chunyun Chen > Labels: openshift_v3 > > The existing issue: > 1.EXEC: Deploy a pod which contains more than 1 containers > 2.EXEC: Expand the related service tree view in "OpenShift Explorer" > 3.EXEC: Right click above pod -> click "Pod Log..." > 4.ASSERT: Will meet some errors in "Console" window like "Error from server: a container name must be specified for pod logging-kibana-1-icxl2" > So, we need find a method for user to specify a container to show logs when the pod has more than 1 containers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20986. --------------------------------- Resolution: Done Works with jboss-eap-7.0.0.ER4-maven-repository > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20986) JBoss EAP 7 Maven repository is not recognized

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20986?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20986: -------------------------------- Fix Version/s: 4.3.1.Beta2 4.4.0.Alpha1 (was: 4.3.x) (was: 4.4.x) > JBoss EAP 7 Maven repository is not recognized > ---------------------------------------------- > > Key: JBIDE-20986 > URL: https://issues.jboss.org/browse/JBIDE-20986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > - Unzip Maven repo from http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/ > - Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories... (point at unzipped maven DR11 repo dir) > - ASSERT the Maven repo should be recognized as an EAP repo > - FAILURE a "No new repository found" message is displayed > This is caused by the repository identifier looking for a com/sun/faces/jsf-impl" folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar files. > The check can be updated in the code, but the best solution is to leverage the .maven-repository marker file, that should be added at the root of the repository. See JBIDE-18323. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21521) Port Forwarding: Caching of checkbox for free port does not work properly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21521?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21521: ------------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Port Forwarding: Caching of checkbox for free port does not work properly > ------------------------------------------------------------------------- > > Key: JBIDE-21521 > URL: https://issues.jboss.org/browse/JBIDE-21521 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.CR1 > > > In JBIDE-21123 was fixed caching of the checkbox for usage of free ports in case of inactivity of port forwarding. But upon checking the checkbox to use free ports and start port forwarding, closing wizard and reopening port forwarding wizard, port forwarding is still active using free ports but the checkbox is unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21521) Port Forwarding: Caching of checkbox for free port does not work properly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21521?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21521: ------------------------------------------ [~scabanovich] thanks for the patch! I punt this to CR1 since this is imho not critical enough to justify a respin. > Port Forwarding: Caching of checkbox for free port does not work properly > ------------------------------------------------------------------------- > > Key: JBIDE-21521 > URL: https://issues.jboss.org/browse/JBIDE-21521 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.CR1 > > > In JBIDE-21123 was fixed caching of the checkbox for usage of free ports in case of inactivity of port forwarding. But upon checking the checkbox to use free ports and start port forwarding, closing wizard and reopening port forwarding wizard, port forwarding is still active using free ports but the checkbox is unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21457) Explorer: Show build in explorer deployment view if it any state other then complete

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21457: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Explorer: Show build in explorer deployment view if it any state other then complete > ------------------------------------------------------------------------------------ > > Key: JBIDE-21457 > URL: https://issues.jboss.org/browse/JBIDE-21457 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.CR1 > > > Display the build in the tree view when it is any non-terminated state ("Complete", "Failed", "Error", "Cancelled"). Expectation is builds should be visible in the tree for a short period of time and then disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016