June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19775) Warn user when he selects class for reveng.strategy that is not a subclass of org.hibernate.cfg.reveng.ReverseEngineeringStrategy

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19775?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19775: ------------------------------ Fix Version/s: 4.3.x > Warn user when he selects class for reveng.strategy that is not a subclass of org.hibernate.cfg.reveng.ReverseEngineeringStrategy > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19775 > URL: https://issues.jboss.org/browse/JBIDE-19775 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: hibernate > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.x > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19792) antlr packages and lib not exported in Hibernate Tools 4.0.1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19792?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19792: ----------------------------------- Hi Bastian, This is exactly what we want to avoid that people do: use the core Hibernate classes directly in the Eclipse tooling code. If you do that, you will lock yourself to one particular version of the Hibernate runtime while the tools should be as independent from the version as possible. This is why we have created a service provider plugin that exposes interfaces for all the Hibernate classes that are used in the tooling code together with service implementations for each included Hibernate version that implements all these interfaces using the proper core Hibernate classes. Surely this does explain the problem but doesn't solve it. One solution is to create an SPI interface for the classes that you need and implement this interface in the implementation plugins. However, these interfaces could change thoroughly in the next JBoss Tools releases as the SPI is probably too fine-grained right now and needs to be reworked towards something more coarse grained. A second possibility would be to mimic the Hibernate code in your plugin itself. To start with, that is probably the easiest solution. Cheers, Koen > antlr packages and lib not exported in Hibernate Tools 4.0.1 > ------------------------------------------------------------ > > Key: JBIDE-19792 > URL: https://issues.jboss.org/browse/JBIDE-19792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Final > Environment: Eclipse Luna SR2 > Reporter: Bastian Ulke > Assignee: Koen Aers > Attachments: B82_MANIFEST.MF, B95_MANIFEST.MF > > > I am currently working on an Eclipse-Plugin that is built on top of the > Hibernate Tools project. For example, I am using the following statements > to get the AST of a named query: > {code} > try { > HqlParser parser = HqlParser.getInstance(statementString); > parser.statement(); > } catch (RecognitionException | TokenStreamException e) { > e.printStackTrace(); > } > AST statementAst = parser.getAST(); > {code} > For this to work well with Hibernate Tools Version 4.0.0, I added bundle > org.hibernate.eclipse.libs as required bundle to my plug-in configuration > (which resolved to > org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far). > However, I now updated to Hiberate Tools 4.0.1 > (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The problem I > have now is that the following imports cannot be resolved: > import antlr.RecognitionException; > import antlr.TokenStreamException; > import antlr.collections.AST; > The problem seems to arise from the fact, that in the new version's > MANIFEST.MF, the antlr... packages are not exported and > lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath any > more (I reformatted both MANIFEST.MFs, that you can find attached, to allow > a convenient comparison). After manually adding the antlr-related entries > to the new version's MANIFEST.MF, my code works pretty well again. > I agree, that internal libraries should generally not be exported. However, > org.hibernate.hql.ast.HqlParser is exported -- so why not its prerequesites? > (By the way, I'd be fine with integrating another library into my project. > However, I tried to manally add antlr-2.7.6.jar as library to > my project, which solved the compilation error, but yields a > java.lang.ClassNotFoundException: antlr.LLkParser cannot be found by > org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3425) Disable Uninstaller generation for Mac OS X

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3425?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3425: -------------------------------- Summary: Disable Uninstaller generation for Mac OS X (was: Disable Unintsaller generation for Mac OS X) > Disable Uninstaller generation for Mac OS X > ------------------------------------------- > > Key: JBDS-3425 > URL: https://issues.jboss.org/browse/JBDS-3425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Uninstaller doesn't make sense for Mac platform, because it is literally just removing .app package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-646) Add info about installing Android SDK in Create Mobile Hybrid

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-646?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-646: ------------------------------------ Sounds like a good approach. > Add info about installing Android SDK in Create Mobile Hybrid > -------------------------------------------------------------- > > Key: TOOLSDOC-646 > URL: https://issues.jboss.org/browse/TOOLSDOC-646 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Priority: Minor > Fix For: 4.2.3.Final > > > Add data about installing Android SDK as a pre-requisite in the article (https://access.redhat.com/articles/1295913) > Also, add steps to add another emulator/change skin of existing one. > Discuss with [~mhusnain] where exactly to add these in the doc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-637) JBDS-IS 8.0.2 - Installation Guide: Add information about FTT Installation

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-637?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-637: ------------------------------------ Scoped. Looks easy, as expected. Instructions in this video: https://vimeo.com/119989261 Update and test shortly. > JBDS-IS 8.0.2 - Installation Guide: Add information about FTT Installation > -------------------------------------------------------------------------- > > Key: TOOLSDOC-637 > URL: https://issues.jboss.org/browse/TOOLSDOC-637 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Fuse Transformation Tooling [1] for Fuse 6.2 will be installed via JBDS-IS 8.0.2. Document how. > [1] https://github.com/fabric8io/data-mapper -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-646) Add info about installing Android SDK in Create Mobile Hybrid

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-646?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-646: ------------------------------------ This information does not replace the important information, which warns users about a separate issue. Prerequisites sounds good, but this information was in two articles. Which one did you mean, or is it both? > Add info about installing Android SDK in Create Mobile Hybrid > -------------------------------------------------------------- > > Key: TOOLSDOC-646 > URL: https://issues.jboss.org/browse/TOOLSDOC-646 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Priority: Minor > Fix For: 4.2.3.Final > > > Add data about installing Android SDK as a pre-requisite in the article (https://access.redhat.com/articles/1295913) > Also, add steps to add another emulator/change skin of existing one. > Discuss with [~mhusnain] where exactly to add these in the doc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-649) Adding the intros to the docs published in the community

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-649?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-649: ------------------------------------ I have a PR open currently for TOOLSDOC-645. Once that is resolved, I'll create a PR for this. > Adding the intros to the docs published in the community > -------------------------------------------------------- > > Key: TOOLSDOC-649 > URL: https://issues.jboss.org/browse/TOOLSDOC-649 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Reporter: Supriya Bharadwaj > Assignee: Misha Ali > > Add these introductions to the community versions of the doc -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-583) Add Section for OpenShift v3

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-583?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-583: ------------------------------------ After some discussion with the OpenShift writers, a tentative plan of action for the JBDS/JBT docs team is as follows: 1. Wait for the OS v3 GA to have a more or less stable version of the new product to work with. 2. Review the existing OS (v2) documentation and determine how much of it we can test and update for v3 (probably separate articles for v3 and marking the older ones for v2). I expect this may be a substantial amount of work, so may use the JBT OS article statistics to determine which OS articles are most used and work on those as a priority and save the rest for later). We can track this effort in this JIRA, most likely. 3. Work on the commitments for JBDS 9.0 when the devs are done with the corresponding dev JIRAs. This will likely be closer to the JBDS 9 GA. > Add Section for OpenShift v3 > ---------------------------- > > Key: TOOLSDOC-583 > URL: https://issues.jboss.org/browse/TOOLSDOC-583 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: User Guide > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > Add Section for OpenShift that is specific to architecture v3 which is based on Kubernetes and Docker. Should include similar section to what exists for v2 http://tools.jboss.org/documentation/howto/#developing-apps-for-the-cloud -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17686: ------------------------------------- This has been confirmed as a bug upstream. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19536: ----------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Infinite job loop when creating project > --------------------------------------- > > Key: JBIDE-19536 > URL: https://issues.jboss.org/browse/JBIDE-19536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > Attachments: cdi_jstack, jstack.out > > > Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974 > I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 June 2015