January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3583: -------------------------------------- Thanks! The upstream issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=478175) is fixed in Mars.2 SR2 so should be available in JBT 4.3.1.CR1. > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3575: -------------------------------------- [~mhusnain] please add a link to the corresponding TOOLSDOC and then it's OK to resolve this one as a duplicate. > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Misha Ali > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21512?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21512: -------------------------------------- Assignee: Koen Aers [~koen.aers] please review. > 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.Alpha1 > > > 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)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on LOCUS-50: ---------------------------------------- Have to wait for [~pleacu] to come back I'm afraid, but we'll get that done too. Thanks Nick > Locus bundle for jsonschema2pojo has corrupted Export-Package statement > ----------------------------------------------------------------------- > > Key: LOCUS-50 > URL: https://issues.jboss.org/browse/LOCUS-50 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Lars Heinemann > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.6.0 > > > see https://gist.github.com/lhein/47405c1fcb9dc2a7138e > Bundle: > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710 > When trying to resolve classes from this bundle it fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21512?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21512: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > 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 > Priority: Optional > Fix For: 4.4.0.Alpha1 > > > 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)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21377: ------------------------------------- {quote}Or, are you saying "no one needs this, so it should be optional... maybe we add a new Central connector instead?" (as I'd originally offered){quote} my feeling exactly. http://www.google.com/trends/explore#q=%2Fm%2F05cntt%2C%20%2Fm%2F01w6k2&d... > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21489) Explorer: Deployment view does not update properly if creating new deployment and it has to wait on a build

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21489?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21489: --------------------------------------- cc @fbricon > Explorer: Deployment view does not update properly if creating new deployment and it has to wait on a build > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21489 > URL: https://issues.jboss.org/browse/JBIDE-21489 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Create a new deployment in a project and note the content of the tree or the tabs does not reflect the same info as you would see in the web console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21377: ------------------------------------ Based on the initial problem statement in this JIRA: "There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. This would require adding it to the TP and adding a dependency from a JBT feature to it." So, that's why. JBT Central Community feature is the JBT equivalent of the JBDS Core Feature. It's the thing that chances are, everyone will install regardless of what their particular focus in development w/ JBT might be. If you would like to shoehorn this into being a default install part of JBT via a DIFFERENT feature, I'm happy to move the requirement to THAT feature instead. Where would you put it? Or, are you saying "no one needs this, so it should be optional... maybe we add a new Central connector instead?" (as I'd originally offered) > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on LOCUS-50: --------------------------------- Thanks for testing this stuff and finding problems. Next step: throw me a PR to fix it! :D For the jaxb stuff, please attach to https://issues.jboss.org/browse/LOCUS-49 For jsonschema2pojo, please attach here. > Locus bundle for jsonschema2pojo has corrupted Export-Package statement > ----------------------------------------------------------------------- > > Key: LOCUS-50 > URL: https://issues.jboss.org/browse/LOCUS-50 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Lars Heinemann > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.6.0 > > > see https://gist.github.com/lhein/47405c1fcb9dc2a7138e > Bundle: > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710 > When trying to resolve classes from this bundle it fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-548) JBDS IS 9 update site page links users to JBT IS update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-548?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-548: ----------------------------- Summary: JBDS IS 9 update site page links users to JBT IS update site (was: JBDS IS 8 and 9 contain old versions of Teiid Designer) > JBDS IS 9 update site page links users to JBT IS update site > ------------------------------------------------------------ > > Key: JBTIS-548 > URL: https://issues.jboss.org/browse/JBTIS-548 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > > On https://devstudio.jboss.com/9.0/stable/updates/integration-stack/ there's a link to http://download.jboss.org/jbosstools/mars/stable/updates/integration-stack/ but that's JBTIS, not JBDSIS. > Similar problem on https://devstudio.jboss.com/9.0/stable/updates/integration-stack/earlyacc... linking to http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... . > Aside: > Should the /8.0/ site contain the same (or newer!) version of Teiid Designer than the /9.0/ site? > I see this, and it confuses me: > !teiiddes903-in-mars-904-in-luna.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016