May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21608: ----------------------------------- Assignee: (was: Xavier Coulon) Dimitry, please look into this one > "Show In -> Web Browser via Live Reload" on EJB module should be disabled > ------------------------------------------------------------------------- > > Key: JBIDE-21608 > URL: https://issues.jboss.org/browse/JBIDE-21608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Fix For: 4.4.x > > > This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. > Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. > So for Livereload, there are these two items that should be disabled on an ejb module: > Show in -> Web Browser via Livereload > Show in -> Web Browser on External device -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21608: -------------------------------- Sprint: devex #115 May 2016 > "Show In -> Web Browser via Live Reload" on EJB module should be disabled > ------------------------------------------------------------------------- > > Key: JBIDE-21608 > URL: https://issues.jboss.org/browse/JBIDE-21608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Fix For: 4.4.x > > > This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. > Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. > So for Livereload, there are these two items that should be disabled on an ejb module: > Show in -> Web Browser via Livereload > Show in -> Web Browser on External device -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3739: ------------------------------------- This is still happening, testing in JBDS build id: Alpha1-v20160520-1027-B5398. Now there is no exception but docker connection gets disabled (icon of docker connection become grey from blue) and it is not even possible to get it enabled (there is a tool item for it). Still user has to remove connection and restart CDK to get working CDK docker connection. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, platform-installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.x > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21517) Disable livereload quick access option for modules on stopped server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21517?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21517: -------------------------------- Sprint: devex #115 May 2016 > Disable livereload quick access option for modules on stopped server > -------------------------------------------------------------------- > > Key: JBIDE-21517 > URL: https://issues.jboss.org/browse/JBIDE-21517 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.x > > > Since the 'show in web browser via livereload' quick access will fail in the end. Plus context menu option on modules is already disabled when the server is not running. It might be nicer to have both options disabled in this instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21517) Disable livereload quick access option for modules on stopped server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21517?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21517: -------------------------------- Story Points: 3 (was: 1) > Disable livereload quick access option for modules on stopped server > -------------------------------------------------------------------- > > Key: JBIDE-21517 > URL: https://issues.jboss.org/browse/JBIDE-21517 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.x > > > Since the 'show in web browser via livereload' quick access will fail in the end. Plus context menu option on modules is already disabled when the server is not running. It might be nicer to have both options disabled in this instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21512) Enable hibernate-search by default (set hibernate.search.autoregister_listeners to true)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21512?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21512: -------------------------------- Story Points: 2 > Enable hibernate-search by default (set hibernate.search.autoregister_listeners to true) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21512 > URL: https://issues.jboss.org/browse/JBIDE-21512 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.x > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Optional > Fix For: 4.4.0.Alpha3 > > > The _hibernate.search.autoregister_listeners_ property was set to _false _by default in [ConfigurationFactory] (https://github.com/jbosstools/jbosstools-hibernate/blob/12928b28d3769b266...), if not set to true by use in xml configuration. > The reason is descibed in the comments some lines above. I also linked the appropriate JIRAs. > The idea is to set this property to _true _, because in order to use the curently being created [hibernate-search plugin] (https://github.com/bdshadow/org.jboss.tools.hibernate.search) the user has to set it to true in the configuration, while this property isn't obligatory by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21512) Enable hibernate-search by default (set hibernate.search.autoregister_listeners to true)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21512?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21512: -------------------------------- Sprint: devex #115 May 2016 > Enable hibernate-search by default (set hibernate.search.autoregister_listeners to true) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21512 > URL: https://issues.jboss.org/browse/JBIDE-21512 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.x > Reporter: Dmitry Bocharov > Assignee: Koen Aers > Priority: Optional > Fix For: 4.4.0.Alpha3 > > > The _hibernate.search.autoregister_listeners_ property was set to _false _by default in [ConfigurationFactory] (https://github.com/jbosstools/jbosstools-hibernate/blob/12928b28d3769b266...), if not set to true by use in xml configuration. > The reason is descibed in the comments some lines above. I also linked the appropriate JIRAs. > The idea is to set this property to _true _, because in order to use the curently being created [hibernate-search plugin] (https://github.com/bdshadow/org.jboss.tools.hibernate.search) the user has to set it to true in the configuration, while this property isn't obligatory by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-718) JBTIS Target Platform - Mars - move Fuse and DV dependencies to released

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-718: -------------------------------- Summary: JBTIS Target Platform - Mars - move Fuse and DV dependencies to released Key: JBTIS-718 URL: https://issues.jboss.org/browse/JBTIS-718 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.3.1.Final-TP Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.3.2.Final-TP *Reason:* Move Fuse Tooling and DV dependencies to released *Project page/sources:* *Version:* 4.3.2-SNAPSHOT *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* JBTIS/JBDSIS *Include in JBDS:* Yes (JBDSIS) *Type of dependency:* distribution *List of bundles added/removed:* {code} {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19738: -------------------------------- Story Points: 6 > Failed runtime download offers no error message > ----------------------------------------------- > > Key: JBIDE-19738 > URL: https://issues.jboss.org/browse/JBIDE-19738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.0.Alpha3 > > > While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19738: -------------------------------- Sprint: devex #115 May 2016 > Failed runtime download offers no error message > ----------------------------------------------- > > Key: JBIDE-19738 > URL: https://issues.jboss.org/browse/JBIDE-19738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.0.Alpha3 > > > While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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