May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24390) Items hidden by filter are excluded from installation

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24390?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24390: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.4.Final) > Items hidden by filter are excluded from installation > ----------------------------------------------------- > > Key: JBIDE-24390 > URL: https://issues.jboss.org/browse/JBIDE-24390 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.4.Final > Reporter: Lukáš Valach > Priority: Minor > Fix For: 4.5.0.AM2 > > > Items which are hidden by filter won't be installed even if they are selected. > For example: > # Open Red Hat Central > # Click "Select All" > # Type into "Find" field "angular" > # The only one item are now displayed and button "Install/Update (1)" shows that only one item are selected to be installed which isn't true. All items are still selected though only one of them are shown. > # Click "Install/Update (1)" then you will see that only Angular is going to be installed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-23814. -------------------------------------- Resolution: Done > Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error > ----------------------------------------------------------------- > > Key: JBIDE-23814 > URL: https://issues.jboss.org/browse/JBIDE-23814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.GA > Build id: GA-v20161125-1418-B55 > Build date: 20161125-1418 > JBoss Openshift UI Plugin > Version: 3.3.1.v20161125-0956 > OpenShift > openshift v3.3.1.3 > Reporter: Siamak Sadeghianfar > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final > > Attachments: jbds-error.png, jboss-eap70-openshift.png > > > When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error: > {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory > OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23814: ------------------------------------------ I cannot replicate this. Resolving. Please feel free to reopen if you face it again. > Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error > ----------------------------------------------------------------- > > Key: JBIDE-23814 > URL: https://issues.jboss.org/browse/JBIDE-23814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.GA > Build id: GA-v20161125-1418-B55 > Build date: 20161125-1418 > JBoss Openshift UI Plugin > Version: 3.3.1.v20161125-0956 > OpenShift > openshift v3.3.1.3 > Reporter: Siamak Sadeghianfar > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final > > Attachments: jbds-error.png, jboss-eap70-openshift.png > > > When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error: > {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory > OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24241) Server adapter not working when created from replication controller fallback

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24241?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24241. ------------------------------ Verified in Devstudio 10.4.0.GA-v20170511-1748-B62. Closing. > Server adapter not working when created from replication controller fallback > ---------------------------------------------------------------------------- > > Key: JBIDE-24241 > URL: https://issues.jboss.org/browse/JBIDE-24241 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: replication-controller-not-found.png > > > When no service nor deployment config is available, it is possible to create a server adapter using replication controllers. A server adapter created this way errors on start with the following message: > {noformat} > An internal error occurred during: "Starting nodejs-1 (ReplicationController) at OpenShift 3 (192.168.42.24)". > deploymentconfigs "nodejs" not found deploymentconfigs "nodejs" not found > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23584) Integration tests global refactoring: org.jboss.tools.hibernate.ui.bot.test

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23584?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23584: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.4.Final) > Integration tests global refactoring: org.jboss.tools.hibernate.ui.bot.test > --------------------------------------------------------------------------- > > Key: JBIDE-23584 > URL: https://issues.jboss.org/browse/JBIDE-23584 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: hibernate, integration, integration_tests > Fix For: 4.5.0.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.hibernate.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24135: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Clean up old vscode builds and establish file retention / cleanup policy > ------------------------------------------------------------------------ > > Key: JBIDE-24135 > URL: https://issues.jboss.org/browse/JBIDE-24135 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Fix For: 4.5.0.AM1 > > > Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts. > * java-server 1.0.x > * java-server 0.1.x > * jdt-language-server 0.1 older than 4 weeks ago > Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as: > /neon/snapshots/vscode > /neon/integration/vscode > etc. > Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created. > Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24135: ------------------------------------ Is this still a concern? I see a lot of builds in http://download.jboss.org/jbosstools/static/vscode/ but not as many or as frequent as I might have expected - are we only doing releases every 2 weeks now? Can any of these be deleted ? cc: [~fbricon] [~gercan] > Clean up old vscode builds and establish file retention / cleanup policy > ------------------------------------------------------------------------ > > Key: JBIDE-24135 > URL: https://issues.jboss.org/browse/JBIDE-24135 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Fix For: 4.5.0.AM1 > > > Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts. > * java-server 1.0.x > * java-server 0.1.x > * jdt-language-server 0.1 older than 4 weeks ago > Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as: > /neon/snapshots/vscode > /neon/integration/vscode > etc. > Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created. > Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23575) Integration tests global refactoring: org.jboss.tools.central.ui.bot.test

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23575?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23575: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.4.Final) > Integration tests global refactoring: org.jboss.tools.central.ui.bot.test > ------------------------------------------------------------------------- > > Key: JBIDE-23575 > URL: https://issues.jboss.org/browse/JBIDE-23575 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: central, integration, integration_tests > Fix For: 4.5.0.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.central.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Pushing Image into Openshift registry fails

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23771: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Pushing Image into Openshift registry fails > ------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24229) Configure sonar build for jbosstools-openshift

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24229?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov resolved JBIDE-24229. -------------------------------------- Resolution: Done > Configure sonar build for jbosstools-openshift > ---------------------------------------------- > > Key: JBIDE-24229 > URL: https://issues.jboss.org/browse/JBIDE-24229 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.4.AM1 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > > We need to add sonar build for master with saving reports to sonarqube (mode should analysis, not preview). > Also we need to add code coverage be provided to sonar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 2017