December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-16286: ---------------------------------- Assignee: (was: Viacheslav Kabanovich) > CDI builder (not import, workspace rebuild) is very slow in wildfly > ------------------------------------------------------------------- > > Key: JBIDE-16286 > URL: https://issues.jboss.org/browse/JBIDE-16286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, maven > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Priority: Critical > Labels: performance > Fix For: 4.5.0.AM1 > > Attachments: VisualVM 1.3.2 _083.png, cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png > > > When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me. > Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me. > [^cdi-builder.ogv] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-15622: ---------------------------------- Assignee: Dmitrii Bocharov (was: Alexey Kazakov) > Automatically open/send report when log has error > ------------------------------------------------- > > Key: JBIDE-15622 > URL: https://issues.jboss.org/browse/JBIDE-15622 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Dmitrii Bocharov > Labels: f2f2014 > Fix For: 4.5.0.AM1 > > Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.bmml, ReportError1.png, ResultPage.bmml, ResultPage.png > > > Step 1: > !ReportError1.png! > Step 2: > !ReportBugStep3.png! > !ReportBugStep3SourceView.png! > Step 3: > !ReportBugStep2.png! > Result Page: > !ResultPage.png! > *Where to:* > 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug > 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace > 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions > 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report? > 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)? > *Feature list:* > 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously) > 2. Check Exception Stack-trace for duplicate > 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc) > 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator > 5. User should be able to see all the data he is going to send (see tab "Source View") > 6. Show communication errors > 7. Return link to created JIRA > 8. Inform user about the general/common process of bug reporting (see Work-flow) > 9. Option to attach log file > 10. Option to attach screen-shot > *Preconditions:* > 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user. > 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project. > *Work-flow:* > 1. User decides/agrees to report the problem (see list Where to) > 2. Report Problem dialog appears, user fills up the form > 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary. > 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions) > 4. User gets link to created issue and short description of what will happen next. (features 7. 8.) > 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools). > *Primary Description:* > JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error. > As it's probably not possible to send the error report without asking users, it should show the "Report problem" page. > NetBeans does that and has reported an actual quality benefit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16144) Editing files outside the workspace and served by Live Reload fails in Windows

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16144?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-16144: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Editing files outside the workspace and served by Live Reload fails in Windows > ------------------------------------------------------------------------------ > > Key: JBIDE-16144 > URL: https://issues.jboss.org/browse/JBIDE-16144 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.1.CR1 > Environment: Windows 7 - 64b, JDK 1.7.0_45 x86 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.5.0.AM1 > > > * In workspace preferences > General > Workspace > enable "Refresh using native hooks or polling" > * Import https://github.com/jbosstools/jbosstools-documentation/tree/master/whatsnew as a project > * Right-click on an html file, open with > Web Browser via Live Reload > * Open the text file in a text editor (sublime text for me),change something, save -> browser reloads eventually > * Make a second change : file can't be saved "Access denied" > * Wait 1 minute, try again, it works. > * repeat, fail ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15622: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > Automatically open/send report when log has error > ------------------------------------------------- > > Key: JBIDE-15622 > URL: https://issues.jboss.org/browse/JBIDE-15622 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Alexey Kazakov > Labels: f2f2014 > Fix For: 4.5.0.AM1 > > Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.bmml, ReportError1.png, ResultPage.bmml, ResultPage.png > > > Step 1: > !ReportError1.png! > Step 2: > !ReportBugStep3.png! > !ReportBugStep3SourceView.png! > Step 3: > !ReportBugStep2.png! > Result Page: > !ResultPage.png! > *Where to:* > 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug > 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace > 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions > 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report? > 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)? > *Feature list:* > 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously) > 2. Check Exception Stack-trace for duplicate > 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc) > 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator > 5. User should be able to see all the data he is going to send (see tab "Source View") > 6. Show communication errors > 7. Return link to created JIRA > 8. Inform user about the general/common process of bug reporting (see Work-flow) > 9. Option to attach log file > 10. Option to attach screen-shot > *Preconditions:* > 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user. > 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project. > *Work-flow:* > 1. User decides/agrees to report the problem (see list Where to) > 2. Report Problem dialog appears, user fills up the form > 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary. > 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions) > 4. User gets link to created issue and short description of what will happen next. (features 7. 8.) > 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools). > *Primary Description:* > JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error. > As it's probably not possible to send the error report without asking users, it should show the "Report problem" page. > NetBeans does that and has reported an actual quality benefit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15519) Clean UI and Core dependencies

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15519?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15519: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Clean UI and Core dependencies > ------------------------------ > > Key: JBIDE-15519 > URL: https://issues.jboss.org/browse/JBIDE-15519 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.5.0.AM1 > > > Move all *.ui.* dependencies from livereload.core to livereload.ui -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15480) Keep data for ICategoryProvider in KB model

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15480?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15480: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > Keep data for ICategoryProvider in KB model > ------------------------------------------- > > Key: JBIDE-15480 > URL: https://issues.jboss.org/browse/JBIDE-15480 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: common > Reporter: Viacheslav Kabanovich > Assignee: Alexey Kazakov > Fix For: 4.5.0.AM1 > > > Interface ICategoryProvider was created to sort attributes in Property View by categories and by priority. Currently, there is just one implementation for JQuery, but it was designed to have more implementations for other HTML 5 libraries. The first experience showed that this approach is resulting in repeating attribute data that otherwise could be encapsulated in KB model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15464) Create Datasource Dialog/Wizard should let preview changes in affected resources

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15464?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15464: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > Create Datasource Dialog/Wizard should let preview changes in affected resources > -------------------------------------------------------------------------------- > > Key: JBIDE-15464 > URL: https://issues.jboss.org/browse/JBIDE-15464 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common > Affects Versions: 4.1.1.Alpha2 > Reporter: Denis Golovin > Assignee: Alexey Kazakov > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15391) Investigate having ports UI add relevant command line args to server startup

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15391: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.2.x) > Investigate having ports UI add relevant command line args to server startup > ---------------------------------------------------------------------------- > > Key: JBIDE-15391 > URL: https://issues.jboss.org/browse/JBIDE-15391 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: Screenshot 2015-01-19 17.31.23.png > > > Subject seems pretty complete; forum post contains more information. Investigate how feasible it is for the editor sections to add relevant command line arguments to override standalone.xml's defaults. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15391) Investigate having ports UI add relevant command line args to server startup

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15391?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-15391: ------------------------------------ [~rob.stryker] can you check if this is still relevant > Investigate having ports UI add relevant command line args to server startup > ---------------------------------------------------------------------------- > > Key: JBIDE-15391 > URL: https://issues.jboss.org/browse/JBIDE-15391 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: Screenshot 2015-01-19 17.31.23.png > > > Subject seems pretty complete; forum post contains more information. Investigate how feasible it is for the editor sections to add relevant command line arguments to override standalone.xml's defaults. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15174) Improved work with datatools connection profiles for various projects using hibernate/jpa

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15174?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-15174: ---------------------------------- Assignee: Koen Aers > Improved work with datatools connection profiles for various projects using hibernate/jpa > ----------------------------------------------------------------------------------------- > > Key: JBIDE-15174 > URL: https://issues.jboss.org/browse/JBIDE-15174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.1.0.Beta2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.5.0.AM1 > > > When working with JPA projects or examples from Central it's necessary to create JPA connection profile. I assume I already have some kind of configuration - either hibernate configuration, or connection directly defined in persistence.xml or defined data source. Still hibernate tooling and eclipse.datatools is complaining that it needs to define connection profile. You have to create a connection configuration again for connection profile to have working tooling. It leads to multiple configurations or you have to reconfigure a project to use eclipse.datatools connection profiles. > What I would like to see is some mechanism howto easily create connection profiles: > * the seamless way would be some support for our examples to generate connection profiles when they are imported (or at least to help with that) > * and some support for hibernate configuration, persistence.xml and ds when creating connection profiles. > Both features might need some eclipse.datatools contributions. But currently these two worlds (hibernate/jpa tooling and datatools are not very well integrated each other). -- 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 December 2016