November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23536 at 11/25/16 12:00 PM: --------------------------------------------------------------- There's API to query default assignee based on a component https://issues.jboss.org/rest/api/2/component/12317750 -> https://docs.atlassian.com/jira/REST/6.4.9/#d2e4713 -> ... but for issues which are automatically closed when the commits are added, there's little need for this add-on. That said, N&N JIRAs *DO* need an owner/default assignee, so there's value for those. was (Author: nickboldt): There's API to query default assignee based on a component https://issues.jboss.org/rest/api/2/component/12317750 -> https://docs.atlassian.com/jira/REST/6.4.9/#d2e4713 -> ... but if the issue is automatically closed when the commits are added, there's little need for this add-on. > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, release, release-eng > Fix For: 4.4.3.AM1 > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23536: ------------------------------------ There's API to query default assignee based on a component https://issues.jboss.org/rest/api/2/component/12317750 -> https://docs.atlassian.com/jira/REST/6.4.9/#d2e4713 -> ... but if the issue is automatically closed when the commits are added, there's little need for this add-on. > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: build, release, release-eng > Fix For: 4.4.3.AM1 > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23536: ---------------------------------- Assignee: Nick Boldt > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, release, release-eng > Fix For: 4.4.3.AM1 > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21857 at 11/25/16 10:33 AM: --------------------------------------------------------------------- [~mlabuda] Hot code replace wont work in any case that changes the structure of classes. Adding/removing methods or changing their signatures wont work. For these kind of changes you need JRebel. Simpler cases where the class structure stays intact, like for instance changing the code within methods, should work was (Author: adietish): [~mlabuda] Hot code replace wont work in any case that changes the structure of classes. Adding/removing methods or changing their signatures wont work. For these kind of changes you need JRebel. Simpler cases where the class structure stays intact, like for instance changing the code within methods should work > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1 > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21857: ------------------------------------------ [~mlabuda] Hot code replace wont work in any case that changes the structure of classes. Adding/removing methods or changing their signatures wont work. For these kind of changes you need JRebel. Simpler cases where the class structure stays intact, like for instance changing the code within methods should work > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1 > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23488) NullPointerException in WizardDialogHelper.openWizard

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23488?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23488. --------------------------------- Closing. Cannot reproduce - no steps to reproduce bug are provided. I have set in AERI auto action to make this unresolved, if the problem persists in newer versions. > NullPointerException in WizardDialogHelper.openWizard > ----------------------------------------------------- > > Key: JBIDE-23488 > URL: https://issues.jboss.org/browse/JBIDE-23488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Automated Error Reporting Bot > Assignee: George Gastaldi > Fix For: 4.4.2.Final > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > java.lang.NullPointerException: null > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:103) > at org.jboss.tools.forge.ui.internal.ext.handlers.RunForgeCommandHandler.openWizard(RunForgeCommandHandler.java:85) > at org.jboss.tools.forge.ui.internal.ext.handlers.RunForgeCommandHandler.execute(RunForgeCommandHandler.java:72) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > Bundles: > | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 | > | org.eclipse.swt | 3.105.0.v20160519-0649 | 3.105.0.v20160603-0902 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 | > | org.jboss.tools.forge.ui.ext | 2.0.2.Final-v20160331-1851-B95 | 2.0.101.v20160607-1332 | > Operating Systems: > | Linux | 4.4.0 | 4.4.0 | > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.1.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/57a34e1fe4b084ea943... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23563) Replace/Add Che stack definitions with Red Hat ones

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23563?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-23563. -------------------------------- Release Notes Text: wrong project Resolution: Rejected > Replace/Add Che stack definitions with Red Hat ones > --------------------------------------------------- > > Key: JBIDE-23563 > URL: https://issues.jboss.org/browse/JBIDE-23563 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Gorkem Ercan > > Dharmit has created centos based stacks for us. Replace/augment the stacks that are coming from upstream project with the centos stacks on the almighty distribution. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23563) Replace/Add Che stack definitions with Red Hat ones

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-23563: ------------------------------------ Summary: Replace/Add Che stack definitions with Red Hat ones Key: JBIDE-23563 URL: https://issues.jboss.org/browse/JBIDE-23563 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Gorkem Ercan Dharmit has created centos based stacks for us. Replace/augment the stacks that are coming from upstream project with the centos stacks on the almighty distribution. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23517) Upgrade Forge Runtime to 3.4.0.Final

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23517?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23517. --------------------------------- Forge is updated. Verified in: Red Hat JBoss Developer Studio Version: 10.2.0.GA Build id: GA-v20161125-0600-B6545 Build date: 20161125-0600 > Upgrade Forge Runtime to 3.4.0.Final > ------------------------------------ > > Key: JBIDE-23517 > URL: https://issues.jboss.org/browse/JBIDE-23517 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.2.AM3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.2.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-459) Report docker-compose error when the process failed to start [EBZ#506262]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-459: --------------------------------------- Summary: Report docker-compose error when the process failed to start [EBZ#506262] Key: ERT-459 URL: https://issues.jboss.org/browse/ERT-459 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.2 (4.6) For now, the only thing that the user can see is an entry in the "Error Log" view, but with no details on what happened. Eg: "'docker-compose up' exited with code 1". We should display an error dialog with the real error, such as: "The Compose file './docker-compose.yml' is invalid because: services.app.links contains an invalid type, it should be an array" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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