September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25077) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [fusetools-extras]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25077?page=com.atlassian.jira.plugi... ] Lars Heinemann closed JBIDE-25077. ---------------------------------- Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [fusetools-extras] > -------------------------------------------------------------------------- > > Key: JBIDE-25077 > URL: https://issues.jboss.org/browse/JBIDE-25077 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [fusetools-extras]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25076) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [fusetools]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25076?page=com.atlassian.jira.plugi... ] Lars Heinemann closed JBIDE-25076. ---------------------------------- Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [fusetools] > ------------------------------------------------------------------- > > Key: JBIDE-25076 > URL: https://issues.jboss.org/browse/JBIDE-25076 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [fusetools]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25098) Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25098?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-25098: ------------------------------------ Summary: Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip (was: Provide a status preserving the stacktrace in org.eclipse.core.runtime.CoreException) > Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-25098 > URL: https://issues.jboss.org/browse/JBIDE-25098 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Fix For: 4.5.1.AM3 > > > in org.jboss.tools.runtime.core.util.internal.DownloadRuntimeOperationUtility.downloadAndUnzip(String, String, String, boolean, String, String, TaskModel, IProgressMonitor) > a status is directly returned instead of following the guidelines explained in the javadoc for CoreException.getStatus to recreate a Status which will preserve the stacktrace > {noformat} > IStatus org.eclipse.core.runtime.CoreException.getStatus() > Returns the status object for this exception. > IMPORTANT: > The result must NOT be used for logging, error reporting, or as a method return value, since that code pattern hides the original stack trace. Instead, create a new Status with your plug-in ID and this CoreException, and use that new status for error reporting or as a method return value. For example, instead of: > yourPlugin.getLog().log(exception.getStatus()); > > Use: IStatus result = new Status(exception.getStatus().getSeverity(), pluginId, message, exception); > yourPlugin.getLog().log(result); > > Returns:a status object > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25098) Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25098?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-25098: ------------------------------------ Fix Version/s: 4.5.1.AM3 > Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-25098 > URL: https://issues.jboss.org/browse/JBIDE-25098 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Fix For: 4.5.1.AM3 > > > in org.jboss.tools.runtime.core.util.internal.DownloadRuntimeOperationUtility.downloadAndUnzip(String, String, String, boolean, String, String, TaskModel, IProgressMonitor) > a status is directly returned instead of following the guidelines explained in the javadoc for CoreException.getStatus to recreate a Status which will preserve the stacktrace > {noformat} > IStatus org.eclipse.core.runtime.CoreException.getStatus() > Returns the status object for this exception. > IMPORTANT: > The result must NOT be used for logging, error reporting, or as a method return value, since that code pattern hides the original stack trace. Instead, create a new Status with your plug-in ID and this CoreException, and use that new status for error reporting or as a method return value. For example, instead of: > yourPlugin.getLog().log(exception.getStatus()); > > Use: IStatus result = new Status(exception.getStatus().getSeverity(), pluginId, message, exception); > yourPlugin.getLog().log(result); > > Returns:a status object > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25051) Deadlock after startup

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-25051: ------------------------------------------ [~rob.stryker] could you, please, take a look at it? > Deadlock after startup > ---------------------- > > Key: JBIDE-25051 > URL: https://issues.jboss.org/browse/JBIDE-25051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.Final > Reporter: Emond Papegaaij > Priority: Minor > Attachments: Screenshot_20170926_103927.png, eclipse-stackdump.txt > > > Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25051) Deadlock after startup

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ] Emond Papegaaij updated JBIDE-25051: ------------------------------------ Attachment: Screenshot_20170926_103927.png > Deadlock after startup > ---------------------- > > Key: JBIDE-25051 > URL: https://issues.jboss.org/browse/JBIDE-25051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.Final > Reporter: Emond Papegaaij > Priority: Minor > Attachments: Screenshot_20170926_103927.png, eclipse-stackdump.txt > > > Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25051) Deadlock after startup

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ] Emond Papegaaij commented on JBIDE-25051: ----------------------------------------- The issue at Eclipse is https://bugs.eclipse.org/bugs/show_bug.cgi?id=522468 What I mean with 'the workspace is shown', is that this happened directly after startup. The editor is open, including views like the package explorer, outline and console. I'm using eclipse 4.7.0. Unfortunately, I'm unable to create a dump of the exact configuration as Eclipse crashes when I try to copy the gigantic piece of text. I've attached a screenshot of the installed JBoss plugins. > Deadlock after startup > ---------------------- > > Key: JBIDE-25051 > URL: https://issues.jboss.org/browse/JBIDE-25051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.Final > Reporter: Emond Papegaaij > Priority: Minor > Attachments: Screenshot_20170926_103927.png, eclipse-stackdump.txt > > > Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25051) Deadlock after startup

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-25051: ------------------------------------------ [~papegaaij] could you please, link this Jira to an issue that you've created in Eclipse bugzilla. Also you say: "The workspace is shown", i can see only stackdump attached. Also what version of Eclipse and JBoss Tools do you use? > Deadlock after startup > ---------------------- > > Key: JBIDE-25051 > URL: https://issues.jboss.org/browse/JBIDE-25051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.Final > Reporter: Emond Papegaaij > Priority: Minor > Attachments: eclipse-stackdump.txt > > > Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4564) Configure slaves with c++ build tools

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4564?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4564: ------------------------------ Fix Version/s: 11.1.0.AM3 > Configure slaves with c++ build tools > ------------------------------------- > > Key: JBDS-4564 > URL: https://issues.jboss.org/browse/JBDS-4564 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.1.0.AM3 > > > JBDS-4520 requires c++ build tools on CI machines in order to run builds. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4482) Create 'About' dialog to show most relevant information about installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4482?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-4482 at 9/26/17 1:30 AM: -------------------------------------------------------------- [~crobson] We cannot change title colors, would it be OK to keep current implementation (see comments above)? Thanks! was (Author: dgolovin): [~crobson] We cannot change title colors, would it be OK to keep current emplementation (see comments obove)? Thanks! > Create 'About' dialog to show most relevant information about installer > ----------------------------------------------------------------------- > > Key: JBDS-4482 > URL: https://issues.jboss.org/browse/JBDS-4482 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 11.0.0.GA > Reporter: Denis Golovin > Assignee: Sudhir Verma > Labels: New_and_noteworthy, ui > Fix For: 11.x > > Attachments: RCUE_About_BG.png, RCUE_About_mockup.png, about-on-location.png, about-on-welcome.png, devsuite-about.png > > > Dialog should contain: > 1. Application logo, name and version > 2. Link to documentation > 3. Link to release notes > 4. Link to documentation how to report issues > Dialog can be requested trough context menu 'About' and should show modal dialog with content listed above > !devsuite-about.png! > Good Example is Atom editor About Page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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