October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26334) Launcher wizard: improve user experience

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26334?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26334. --------------------------------- Closing, launcher wizard is improved. Verified in: Red Hat Developer Studio Version: 12.9.0.GA Build id: GA-v20180928-1629-B3448 Build date: 20180928-1629 > Launcher wizard: improve user experience > ---------------------------------------- > > Key: JBIDE-26334 > URL: https://issues.jboss.org/browse/JBIDE-26334 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: launcher_wizard > Fix For: 4.9.0.Final > > Attachments: error-markers-for-missing-info.png, location-missing-decoration.png, maven-artifact-elements.png, mission-infos.png, new-wizard-page.png > > > The launcher wizard that we implemented in 4.9.AM3 works but it lacks explanations that would help a novice user. > Suggested improvements: > * A novice user has no idea what a mission is all about. We should maybe add an explanatory label that tells the user what he's picking with a mission. And then we should explain what the mission that he has chose will provide. > !mission-infos.png! > * A novice user has no idea what the maven artifact elements are for. > !maven-artifact-elements.png! > * Generally speaking it is preferable to decorate missing input fields with a "*" than to mark them as errors (as one can see in most web forms). OpenShift tooling does this as a rule of thumb. > !error-markers-for-missing-info.png! > * Location is not decorated with an "required value" (or error) marker > !location-missing-decoration.png! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26380) Pod log: does not work if oc is configured at the connection level

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26380?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26380. --------------------------------- Closing, no error dialog is shown. Verified in: Red Hat Developer Studio Version: 12.9.0.GA Build id: GA-v20180928-1629-B3448 Build date: 20180928-1629 > Pod log: does not work if oc is configured at the connection level > ------------------------------------------------------------------ > > Key: JBIDE-26380 > URL: https://issues.jboss.org/browse/JBIDE-26380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM3 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Major > Labels: connection, oc_binary, pod_log > Fix For: 4.9.0.Final > > Attachments: screenshot-1.png > > > ASSERT: no oc configured at the workspace level > ASSERT: oc is configured at the connection level > ASSERT: have a pod running > ASSERT: execute the pod log command > EXPECTED: pod log is shown > Instead, a dialog is shown claiming there is an issue with the oc client -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26335) Add server adapter for WildFly 14

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26335?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26335. --------------------------------- WF14 can be downloaded and basic operations are working(start/stop/restart, deploy, hotdeploy, debug). Verified in: Red Hat Developer Studio Version: 12.9.0.GA Build id: GA-v20180928-1629-B3448 Build date: 20180928-1629 > Add server adapter for WildFly 14 > --------------------------------- > > Key: JBIDE-26335 > URL: https://issues.jboss.org/browse/JBIDE-26335 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.9.0.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Major > Fix For: 4.9.0.Final > > > Wildfly 14 was released. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26296) Remove JBoss from maven.apt feature.properties

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26296?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26296. --------------------------------- PR is merged, closing. > Remove JBoss from maven.apt feature.properties > ---------------------------------------------- > > Key: JBIDE-26296 > URL: https://issues.jboss.org/browse/JBIDE-26296 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Major > Fix For: 4.9.0.AM2 > > > In JBDS-4709 Nick removed all mentions of "JBoss by Red Hat" in feature.properties but there was just one occurrence left: > https://github.com/jbosstools/m2e-apt/blob/master/org.jboss.tools.maven.a... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26379) Launcher: should be moved from base to central

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26379?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26379. --------------------------------- Closing, PRs are merged. > Launcher: should be moved from base to central > ---------------------------------------------- > > Key: JBIDE-26379 > URL: https://issues.jboss.org/browse/JBIDE-26379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common > Affects Versions: 4.9.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: launcher_wizard > Fix For: 4.9.0.Final > > > as discussed in https://github.com/jbosstools/jbosstools-base/pull/631#issuecomment-42109... > {quote} > This should all live in central, and it shouldn't really be added to the common.all feature if we intend to simply move it later. > Give it it's own feature, add it to the master list of features added to the project, and then later move it to the central repo. > I personally believe a rename-and-move is just fine even before a Final. Keeping it where it is through a final actually is what's harder to change. Then it becomes a sort of API that the common.all feature contains this launcher, and later it won't. > {quote} > we should move the launcher from jbosstools-base to jbosstools-central -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26283. --------------------------------- Closing, see previous comments. > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Major > Labels: releasework > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26147) Incremental publish not working with WF13, WF12 and WF11

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26147. --------------------------------- Closing, rejected. > Incremental publish not working with WF13, WF12 and WF11 > -------------------------------------------------------- > > Key: JBIDE-26147 > URL: https://issues.jboss.org/browse/JBIDE-26147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Major > Fix For: 4.9.0.Final > > Attachments: helloworld-rs.zip > > > Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context. > This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0. > Then this code is commented out, the application is incrementally published but the error persists -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh

by Rob Stryker (Jira)

[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-26311: ------------------------------------- I'm still not able to replicate this. > EAP 7.1 fails to stop when connected over ssh > --------------------------------------------- > > Key: JBIDE-26311 > URL: https://issues.jboss.org/browse/JBIDE-26311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Major > Labels: regression > Fix For: 4.9.0.Final > > Attachments: JBIDE-26311.local.ogv > > > I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says: > Server Red Hat JBoss EAP 7.1 ssh failed to stop. > An exception stack trace is not available. > It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works. > I'm pretty sure this worked last time (previous milestone). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26416) AM3 download pages missing update site URLs

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26416?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-26416 at 10/3/18 3:29 PM: ------------------------------------------------------------- Actually, it's more pervasive than that. http://tools.jboss.org/downloads/jbosstools/photon/4.6.0.AM3.html (no URL) Could be that the URL isn't defined, but could be a bug in the non-Final pages. TODO: make sure 4.6.0.Final URL is either a pointer to the actual site, or is missing the URL since we're replacing /photon/stable/updates/ w/ the 4.9 bits. was (Author: nickboldt): Actually, it's more pervasive than that. http://tools.jboss.org/downloads/jbosstools/photon/4.6.0.AM3.html (no URL) Could be that the URL isn't defined, but could be a bug in the non-Final pages. > AM3 download pages missing update site URLs > ------------------------------------------- > > Key: JBIDE-26416 > URL: https://issues.jboss.org/browse/JBIDE-26416 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Rob Stryker > Assignee: Nick Boldt > Priority: Major > Fix For: 4.9.0.Final > > > See http://tools.jboss.org/downloads/jbosstools/2018-09/4.9.0.AM3.html > Note that there is no update site URL. > See http://tools.jboss.org/downloads/jbosstools/2018-09/4.9.x.Nightly.html > Note that an update site URL *is* present. > TODO: fix am3.html to include a link to the update site > TODO: make sure 4.9.0.Final (when released) also has a linked update site. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26416) AM3 download pages missing update site URLs

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26416?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26416: ------------------------------- Sprint: devex #156 October 2018 > AM3 download pages missing update site URLs > ------------------------------------------- > > Key: JBIDE-26416 > URL: https://issues.jboss.org/browse/JBIDE-26416 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Rob Stryker > Assignee: Nick Boldt > Priority: Major > Fix For: 4.9.0.Final > > > See http://tools.jboss.org/downloads/jbosstools/2018-09/4.9.0.AM3.html > Note that there is no update site URL. > See http://tools.jboss.org/downloads/jbosstools/2018-09/4.9.x.Nightly.html > Note that an update site URL *is* present. > TODO: fix am3.html to include a link to the update site > TODO: make sure 4.9.0.Final (when released) also has a linked update site. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 October 2018