November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21141) OpenShift Application Wizard: Tags for application templates should be grey

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21141?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21141: -------------------------------- Priority: Minor (was: Major) > OpenShift Application Wizard: Tags for application templates should be grey > --------------------------------------------------------------------------- > > Key: JBIDE-21141 > URL: https://issues.jboss.org/browse/JBIDE-21141 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3 > > In New OpenShift application on first wizard page is tree of server application templates. Application templates of internal OSE 3 instance are currently shown together with tags in the same way. It would be nice if tags - the key words in parenthesis e.g. "(java, eap, jboss, xpaas)" - would be shown as styled text (gray) as less significant information. We should show difference between template name and tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21138) "Show In -> Web Browser" on EJB module does nothing.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21138?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21138: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > "Show In -> Web Browser" on EJB module does nothing. > ---------------------------------------------------- > > Key: JBIDE-21138 > URL: https://issues.jboss.org/browse/JBIDE-21138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151122-1948-B143 > Reporter: Radim Hopp > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > As title says... Selecting "Show In -> Web Browser" on EJB module does nothing. I would expect this option to be disabled, or web browser to be opened with 404 page. Instead of this, nothing happens. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21138) "Show In -> Web Browser" on EJB module does nothing.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21138?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21138: -------------------------------- Priority: Minor (was: Major) > "Show In -> Web Browser" on EJB module does nothing. > ---------------------------------------------------- > > Key: JBIDE-21138 > URL: https://issues.jboss.org/browse/JBIDE-21138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151122-1948-B143 > Reporter: Radim Hopp > Priority: Minor > > As title says... Selecting "Show In -> Web Browser" on EJB module does nothing. I would expect this option to be disabled, or web browser to be opened with 404 page. Instead of this, nothing happens. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21143) Triggering action on one connection refresh whole OpenShift Explorer view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21143?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21143: ---------------------------------- Labels: explorer (was: ) > Triggering action on one connection refresh whole OpenShift Explorer view > ------------------------------------------------------------------------- > > Key: JBIDE-21143 > URL: https://issues.jboss.org/browse/JBIDE-21143 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: explorer > > Actions such as deleting or creating a new project for an OpenShift connection (those which change content of OpenShift Explorer visually) causes refreshing all connection in OpenShift Explorer view - I have spotted it when I was creating a project for a connection of local OpenShift instance and while this project was being shown in OpenShift Explorer view under the connection, a connection to internal OSE instance had been refreshed too and loading tree item was shown underneath. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21143) Triggering action on one connection refresh whole OpenShift Explorer view

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21143: ------------------------------------- Summary: Triggering action on one connection refresh whole OpenShift Explorer view Key: JBIDE-21143 URL: https://issues.jboss.org/browse/JBIDE-21143 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda Actions such as deleting or creating a new project for an OpenShift connection (those which change content of OpenShift Explorer visually) causes refreshing all connection in OpenShift Explorer view - I have spotted it when I was creating a project for a connection of local OpenShift instance and while this project was being shown in OpenShift Explorer view under the connection, a connection to internal OSE instance had been refreshed too and loading tree item was shown underneath. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21142) could JBDS Discovery build depend on JDBS root pom?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21142: ---------------------------------- Summary: could JBDS Discovery build depend on JDBS root pom? Key: JBIDE-21142 URL: https://issues.jboss.org/browse/JBIDE-21142 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt {quote} creation of a JBDS/discovery parent pom? https://github.com/jbosstools/jbosstools-build/commit/5ce5c5aa9c6febd562d... and https://github.com/jbosstools/jbosstools-discovery/pull/279 try this: jbds disco depends on jbds prod root pom?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21142) could JBDS Discovery build depend on JDBS root pom?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21142?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21142: ---------------------------------- Assignee: Nick Boldt > could JBDS Discovery build depend on JDBS root pom? > --------------------------------------------------- > > Key: JBIDE-21142 > URL: https://issues.jboss.org/browse/JBIDE-21142 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > {quote} > creation of a JBDS/discovery parent pom? > https://github.com/jbosstools/jbosstools-build/commit/5ce5c5aa9c6febd562d... > and https://github.com/jbosstools/jbosstools-discovery/pull/279 > try this: jbds disco depends on jbds prod root pom?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21141) OpenShift Application Wizard: Tags for application templates should be grey

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21141?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21141: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > OpenShift Application Wizard: Tags for application templates should be grey > --------------------------------------------------------------------------- > > Key: JBIDE-21141 > URL: https://issues.jboss.org/browse/JBIDE-21141 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > In New OpenShift application on first wizard page is tree of server application templates. Application templates of internal OSE 3 instance are currently shown together with tags in the same way. It would be nice if tags - the key words in parenthesis e.g. "(java, eap, jboss, xpaas)" - would be shown as styled text (gray) as less significant information. We should show difference between template name and tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21141) OpenShift Application Wizard: Tags for application templates should be grey

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21141: ------------------------------------- Summary: OpenShift Application Wizard: Tags for application templates should be grey Key: JBIDE-21141 URL: https://issues.jboss.org/browse/JBIDE-21141 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda In New OpenShift application on first wizard page is tree of server application templates. Application templates of internal OSE 3 instance are currently shown together with tags in the same way. It would be nice if tags - the key words in parenthesis e.g. "(java, eap, jboss, xpaas)" - would be shown as styled text (gray) as less significant information. We should show difference between template name and tags. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21120) Why do we deploy TP zips to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21120?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21120. ------------------------------ Resolution: Done Closing. > Why do we deploy TP zips to Nexus snapshots repo? > ------------------------------------------------- > > Key: JBIDE-21120 > URL: https://issues.jboss.org/browse/JBIDE-21120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our TP update sites to the JBoss Nexus snapshots repo. > {code} > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > ... > {code} > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > So, why don't we set a custome deployment strategy (eg., akin to *maven.deploy.skip=true*) in the jbosstools-targetplatform & jbosstools-discovery root pom to prevent this waste of time/space? Then we can just deploy the .target files, not the zips. > This would certainly speed up builds, which currently take 30-60 mins per TP build. -- 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 November 2015