September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26813) use latest openshift client 8.0.1

by André Dietisheim (Jira)

André Dietisheim created JBIDE-26813: ---------------------------------------- Summary: use latest openshift client 8.0.1 Key: JBIDE-26813 URL: https://issues.jboss.org/browse/JBIDE-26813 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.12.0.Final Reporter: André Dietisheim -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-753) [GTK] Make "Print Selection" work [EBZ#299550]

by Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-753: --------------------------------------- Summary: [GTK] Make "Print Selection" work [EBZ#299550] Key: ERT-753 URL: https://issues.jboss.org/browse/ERT-753 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot Since gtk bug http://bugzilla.gnome.org/show_bug.cgi?id=344519 has now been fixed, we should use this feature in the GTK print dialog. We need to show the "Selection" radio by default when the dialog is opened, and then we need to set and get the value of the radio before and after the PrintDialog is opened. I believe the new radio will show up if you set gtk_print_unix_dialog_set_support_selection(true) Then, if the scope in our PrinterData is set to PrinterData.SELECTION, we need to set (and get) GTK_PRINT_PAGES_SELECTION in the gtk_print_settings_print_pages field of the gtk_print_settings struct. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26808) Assure that npm on the machines uses internal Nexus NPM registry

by Maneesh Mehra (Jira)

[ https://issues.jboss.org/browse/JBIDE-26808?page=com.atlassian.jira.plugi... ] Maneesh Mehra commented on JBIDE-26808: --------------------------------------- This is great. Can these profiles be dynamically applied to build jobs too that run on build systems depending on whether they run within the enterprise's trusted network or outside ? Reason I am asking this is because some teams are doing upstream development and have build systems that are located on both trusted and public systems. Its a challenge to them to identify which repo to use, based on where the build job is running. In any case, would you mind updating the Google doc with these instructions for benefit of all developers ? I am sure developers will be mindful of switching ti an appropriate profile based on where they are connected. Also overall, what is the ETA for closure on this issue ? Thx in advance. > Assure that npm on the machines uses internal Nexus NPM registry > ----------------------------------------------------------------- > > Key: JBIDE-26808 > URL: https://issues.jboss.org/browse/JBIDE-26808 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jan Richter > Priority: Major > Fix For: 4.13.0.Final > > > According to [1] we need to take actions at projects using npm. > [1]: https://docs.google.com/document/d/1dn1gQFaJ_Q0IOeRAnFAsBMgVRnwA8ieLQV-AG... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26764) Migrate Installer - Standalone integration tests into job DSL

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26764?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26764: ---------------------------------- Summary: Migrate Installer - Standalone integration tests into job DSL (was: Migrate Installer integration tests into job DSL) > Migrate Installer - Standalone integration tests into job DSL > ------------------------------------------------------------- > > Key: JBIDE-26764 > URL: https://issues.jboss.org/browse/JBIDE-26764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.13.0.AM1 > > > Rewrite QE integration tests into job DSL and place them under dev-platform/cci-config repo -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26758) examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26758?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26758: ------------------------------------ Description: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml, current artifact ids are: * For dist: {color:#DE350B}quickstarts-dist{color} * For wicket-ear: {color:#DE350B}wildfly-wicket-ear-parent{color} * For helloworld-classfiletransformer: {color:#DE350B}helloworld-classfiletransformers{color} was: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml, current artifact ids are: * For dist: quickstarts-dist * For wicket-ear: wildfly-wicket-ear-parent * For helloworld-classfiletransformer: helloworld-classfiletransformers > examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-26758 > URL: https://issues.jboss.org/browse/JBIDE-26758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.12.0.Final > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: > * dist > * wicket-ear > * helloworld-classfiletransformer > h2. *Error messages:* > "There is no project with name jboss-dist" > "There is no project with name jboss-wicket-ear" > "There is no project with name jboss-helloworld-classfiletransformer" > h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml, current artifact ids are: > * For dist: {color:#DE350B}quickstarts-dist{color} > * For wicket-ear: {color:#DE350B}wildfly-wicket-ear-parent{color} > * For helloworld-classfiletransformer: {color:#DE350B}helloworld-classfiletransformers{color} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26758) examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26758?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26758: ------------------------------------ Description: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml, current artifact ids are: * For dist: quickstarts-dist * For wicket-ear: wildfly-wicket-ear-parent * For helloworld-classfiletransformer: helloworld-classfiletransformers was: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml: * quickstarts-dist * wildfly-wicket-ear-parent * helloworld-classfiletransformers > examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-26758 > URL: https://issues.jboss.org/browse/JBIDE-26758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.12.0.Final > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: > * dist > * wicket-ear > * helloworld-classfiletransformer > h2. *Error messages:* > "There is no project with name jboss-dist" > "There is no project with name jboss-wicket-ear" > "There is no project with name jboss-helloworld-classfiletransformer" > h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml, current artifact ids are: > * For dist: quickstarts-dist > * For wicket-ear: wildfly-wicket-ear-parent > * For helloworld-classfiletransformer: helloworld-classfiletransformers -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26758) examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26758?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26758: ------------------------------------ Description: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml * quickstarts-dist * wildfly-wicket-ear-parent * helloworld-classfiletransformers was: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml > examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-26758 > URL: https://issues.jboss.org/browse/JBIDE-26758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.12.0.Final > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: > * dist > * wicket-ear > * helloworld-classfiletransformer > h2. *Error messages:* > "There is no project with name jboss-dist" > "There is no project with name jboss-wicket-ear" > "There is no project with name jboss-helloworld-classfiletransformer" > h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml > * quickstarts-dist > * wildfly-wicket-ear-parent > * helloworld-classfiletransformers -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26758) examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26758?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26758: ------------------------------------ Description: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml: * quickstarts-dist * wildfly-wicket-ear-parent * helloworld-classfiletransformers was: h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: * dist * wicket-ear * helloworld-classfiletransformer h2. *Error messages:* "There is no project with name jboss-dist" "There is no project with name jboss-wicket-ear" "There is no project with name jboss-helloworld-classfiletransformer" h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml * quickstarts-dist * wildfly-wicket-ear-parent * helloworld-classfiletransformers > examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-26758 > URL: https://issues.jboss.org/browse/JBIDE-26758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.12.0.Final > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: > * dist > * wicket-ear > * helloworld-classfiletransformer > h2. *Error messages:* > "There is no project with name jboss-dist" > "There is no project with name jboss-wicket-ear" > "There is no project with name jboss-helloworld-classfiletransformer" > h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml: > * quickstarts-dist > * wildfly-wicket-ear-parent > * helloworld-classfiletransformers -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26811) Fix common compress to 1.19

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26811?page=com.atlassian.jira.plugi... ] André Dietisheim closed JBIDE-26811. ------------------------------------ nothing for QE to verify. Closing. > Fix common compress to 1.19 > --------------------------- > > Key: JBIDE-26811 > URL: https://issues.jboss.org/browse/JBIDE-26811 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26812) Add support for WildFly 18

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26812?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-26812: ------------------------------------- Assignee: Jeff MAURY > Add support for WildFly 18 > -------------------------- > > Key: JBIDE-26812 > URL: https://issues.jboss.org/browse/JBIDE-26812 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.13.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > > WildFly 18 will be out in the middle of September. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 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 September 2019