August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22972) Properties: Add Queue To Events to improve performance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22972?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22972: ------------------------------------- Labels: openshift_v3 properties (was: properties) > Properties: Add Queue To Events to improve performance > ------------------------------------------------------ > > Key: JBIDE-22972 > URL: https://issues.jboss.org/browse/JBIDE-22972 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Jeff Cantrill > Labels: openshift_v3, properties > Fix For: 4.4.x > > > There are concerns that unlike other openshift resources, the number of events can be large and we should limit the number we display to 50 > https://github.com/jbosstools/jbosstools-openshift/pull/1278#issuecomment... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22915) Deploy Docker Image: Replication controller is not created for some images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22915: ------------------------------------- Fix Version/s: 4.4.1.Final > Deploy Docker Image: Replication controller is not created for some images > -------------------------------------------------------------------------- > > Key: JBIDE-22915 > URL: https://issues.jboss.org/browse/JBIDE-22915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.Final > > > When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1") -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22912: ------------------------------------- Priority: Minor (was: Major) > Deploy Docker Wizard: Inappropriate project combo size > ------------------------------------------------------ > > Key: JBIDE-22912 > URL: https://issues.jboss.org/browse/JBIDE-22912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Environment: Fedora 24, GTK 3 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > Attachments: project_combo.png > > > In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good. > !project_combo.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22912: ------------------------------------- Fix Version/s: 4.4.x > Deploy Docker Wizard: Inappropriate project combo size > ------------------------------------------------------ > > Key: JBIDE-22912 > URL: https://issues.jboss.org/browse/JBIDE-22912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Environment: Fedora 24, GTK 3 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > Attachments: project_combo.png > > > In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good. > !project_combo.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22972) Properties: Add Queue To Events to improve performance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22972?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22972: ------------------------------------- Fix Version/s: 4.4.x > Properties: Add Queue To Events to improve performance > ------------------------------------------------------ > > Key: JBIDE-22972 > URL: https://issues.jboss.org/browse/JBIDE-22972 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Jeff Cantrill > Fix For: 4.4.x > > > There are concerns that unlike other openshift resources, the number of events can be large and we should limit the number we display to 50 > https://github.com/jbosstools/jbosstools-openshift/pull/1278#issuecomment... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22971) Unable to install JRebel

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22971?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22971. ------------------------------ Resolution: Rejected It looks like it was one time outage on JRebel side. > Unable to install JRebel > ------------------------ > > Key: JBIDE-22971 > URL: https://issues.jboss.org/browse/JBIDE-22971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.1.AM3 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.4.x > > > {noformat}An error occurred while collecting items to be installed > session context was:(profile=devstudio, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/plugins/org.zeroturnar.... > connect timed out > Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/plugins/org.zeroturnar.... > connect timed out > Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/features/org.zeroturna.... > connect timed out > Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/plugins/org.zeroturnar.... > connect timed out > Unable to read repository at http://update.zeroturnaround.com/update-site-jboss/features/org.zeroturna.... > connect timed out{noformat} > This seems like problem on zeroturnaround.com side (even www.zeroturnaround.com is very slow to load today). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22911) Exception below RenameMethodParticipant$RenameMethodSearcher.outOfSynch (thrown in Thread.getStackTrace)

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22911?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22911: ----------------------------------------------- The fix in pull request does not stop at an out-fo-sync file, but adds a warning if the file's content (taken from Eclipse cache or file on disk, whatever is available) has a match to replace; and continues to iterate over other resources. Irrelevant out-of-sync files will not influence refactoring in any way. > Exception below RenameMethodParticipant$RenameMethodSearcher.outOfSynch (thrown in Thread.getStackTrace) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22911 > URL: https://issues.jboss.org/browse/JBIDE-22911 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > java.lang.Exception: HIDDEN > at java.lang.Thread.getStackTrace(null:-1) > at org.jboss.tools.jsf.ui.el.refactoring.RenameMethodParticipant$RenameMethodSearcher.outOfSynch(RenameMethodParticipant.java:145) > at org.jboss.tools.jst.web.kb.refactoring.RefactorSearcher.scanProject(RefactorSearcher.java:148) > at org.jboss.tools.jst.web.kb.refactoring.RefactorSearcher.scanProject(RefactorSearcher.java:108) > at org.jboss.tools.jst.web.kb.refactoring.RefactorSearcher.findELReferences(RefactorSearcher.java:166) > at org.jboss.tools.jsf.ui.el.refactoring.RenameMethodParticipant.checkConditions(RenameMethodParticipant.java:58) > at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:257) > at org.eclipse.ltk.core.refactoring.Refactoring.checkAllConditions(Refactoring.java:162) > at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:80) > at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) > at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5409) > at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Bundles: > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 | > | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v20160516-2131 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 | > | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.7.0.v20160419-0705 | > | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.7.200.v20140625-1835 | > | org.jboss.tools.jsf.ui | 3.7.1.Final-v20160330-2256-B84 | 3.8.0.Final-v20160610-0126-B1 | > | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 | > Operating Systems: > | Linux | 3.19.0 | 4.2.0 | > | MacOSX | 10.11.4 | 10.11.4 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5730baa5e4b0ba8b6a...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4023) set up docker/jenkins instance on wonka to do CI builds of RPM

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4023: -------------------------------- Summary: set up docker/jenkins instance on wonka to do CI builds of RPM Key: JBDS-4023 URL: https://issues.jboss.org/browse/JBDS-4023 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: build, rpm Affects Versions: 10.1.0.GA Reporter: Nick Boldt Assignee: Nick Boldt To enable building the RPM via CI builds, in response to new devstudio builds, need a Jenkins server on which we can run rpmbuild and mock. I have root access to wonka and it has TONS of space, so that seems a viable place to host this until we can get eng-ops to support Fedora24 or RHEL7 w/ EPEL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23048) remove test JIRAs created in issues.stage.jboss.org

by Nick Boldt (JIRA)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23048) remove test JIRAs created in issues.stage.jboss.org

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23048: ---------------------------------- Summary: remove test JIRAs created in issues.stage.jboss.org Key: JBIDE-23048 URL: https://issues.jboss.org/browse/JBIDE-23048 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Affects Versions: 4.4.1.Final Reporter: Nick Boldt While testing the new job, I created some jobs in issues.stage, but can't log in to delete them. So... might need to create a new python task to do the cleanup. Meanwhile, opened https://engineering.redhat.com/rt/Ticket/Display.html?id=417531 to report the outage to eng-ops. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 August 2016