May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19761) Hibernate Tools DelegatingReverseEngineeringStrategy not working

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19761?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19761: ----------------------------------- No worries, as I said we should do a better job informing the user when an improper class is selected. I have created JBIDE-19775. > Hibernate Tools DelegatingReverseEngineeringStrategy not working > ---------------------------------------------------------------- > > Key: JBIDE-19761 > URL: https://issues.jboss.org/browse/JBIDE-19761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: Eclipse Luna > Reporter: Luis Lima > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.3.Final, 4.3.0.Beta1 > > > I'm using the HibernateTools plugin (latest version) with Eclipse Luna and keep getting an error when trying to use my own reverse engineering implementation class. Every time I try to generate my classes I get this exception from Eclipse: > org.hibernate.console.HibernateConsoleRuntimeException: java.lang.IllegalAccessException: Class org.jboss.tools.hibernate.proxy.ServiceProxy can not access a member of class org.hibernate.cfg.reveng.ReverseEngineeringStrategyUtil with modifiers "private" java.lang.IllegalAccessException: Class org.jboss.tools.hibernate.proxy.ServiceProxy can not access a member of class org.hibernate.cfg.reveng.ReverseEngineeringStrategyUtil with modifiers "private" > Seems there's some incompatibility with ServiceProxy and the ReverseEngineeringStrategyUtil class as it seems to be trying to access a method that's no longer private. The stacktrace doesn't really provide any info other than this so hopefully this is a known issue and someone might be able to suggest how to fix it. > It's not related to my code since right now my ReverseEngineeringStrategy implementation is doing nothing ie: > @Override > public String tableToClassName(TableIdentifier tableIdentifier){ > return super.tableToClassName(tableIdentifier); > } > My libraries are 4.3 (4.3.1.CR1 more specifically) and I also have the console configuration set to that version. > Here's my maven dependency: > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-tools</artifactId> > <version>4.3.1.CR1</version> > </dependency> > And always get the error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

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

by Koen Aers (JIRA)

Koen Aers created JBIDE-19775: --------------------------------- Summary: Warn user when he selects class for reveng.strategy that is not a subclass of 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 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19733. ------------------------------------ Resolution: Done This was fixed upstream and the version of easymport included in 4.3.0 nightly build includes the change. > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19733: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19755: --------------------------------------------- I stand corrected. So I would add that info to the bugzilla, mark as critical and raise on wtp-dev as hot bug. > Implement ServerPort portion of wst.servertools API > --------------------------------------------------- > > Key: JBIDE-19755 > URL: https://issues.jboss.org/browse/JBIDE-19755 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it. > Unfortunately, I've been hit by an upstream bug that hinders my progress: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109 > To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19774) Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-19774: ---------------------------------------------- Summary: Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor Key: JBIDE-19774 URL: https://issues.jboss.org/browse/JBIDE-19774 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core Affects Versions: 4.3.0.Alpha2 Environment: Linux Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Priority: Critical Fix For: 4.3.0.Beta1 While testing new Central I notice that if Central was opened before visual editor, XulRunner engine is always used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19774) Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19774?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19774: ------------------------------------------- Steps to Reproduce: 1. Open Eclipse, close all editors, go to Visual Page Editor Preferences. 2. Set HTML5(webkit) as browser engine. Restart Eclipse(even if you already have HTML5 mode turned on). 3. Open Eclipse web browser(or open new Central based on HTML5). ERROR: XulRunner will be used as browser engine 4. Open HTML file with visual Editor. ERROR: XulRunner will be used as browser engine was: 1. Open Eclipse, close all editors, go to Visual Page Editor Preferences. 2. Set HTML5(webkit) as browser engine. Restart Eclipse. 3. Open Eclipse web browser(or open new Central based on HTML5). ERROR: XulRunner will be used as browser engine 4. Open HTML file with visual Editor. ERROR: XulRunner will be used as browser engine > Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19774 > URL: https://issues.jboss.org/browse/JBIDE-19774 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Linux > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > While testing new Central I notice that if Central was opened before visual editor, XulRunner engine is always used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19767) Workspace root and WebContent are detected as projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19767?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19767. ------------------------------------ Resolution: Done Marking as resolved as the part about WebContent should be resolved. The part about workspace root is actually included in the ability to select what to import ( JBIDE-19768 ) > Workspace root and WebContent are detected as projects > ------------------------------------------------------ > > Key: JBIDE-19767 > URL: https://issues.jboss.org/browse/JBIDE-19767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: dynamic-web-project.png > > > When I try to import Dynamic Web Project, two other folders are discovered as projects - the workspace root and the WebContent directory. The directory is also wrongly described as OSGI bundle. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19767) Workspace root and WebContent are detected as projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19767?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19767: ---------------------------------------- I believe the issue about WebContent was fixed upstream with http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/commit/?id=0fa2b9e24060... and is part of nightly builds. > Workspace root and WebContent are detected as projects > ------------------------------------------------------ > > Key: JBIDE-19767 > URL: https://issues.jboss.org/browse/JBIDE-19767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: dynamic-web-project.png > > > When I try to import Dynamic Web Project, two other folders are discovered as projects - the workspace root and the WebContent directory. The directory is also wrongly described as OSGI bundle. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19756: --------------------------------------------- a) I'm sorry but our snapshots very clearly know what the build is for so not sure why this should be a problem here. All our other artifacts has the right version number in it, why can this not have it ? b) I used sources because you used sources. if the right name is src then use that and I then think it should be the same for both jbosstools and devstudio. Shouldn't have a difference. > jbosstools-src.zip has incomplete/misleading version info in folder names/structure > ----------------------------------------------------------------------------------- > > Key: JBIDE-19756 > URL: https://issues.jboss.org/browse/JBIDE-19756 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: jbide19756.png > > > Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named: > <componentname>_<buildqualifier>_<sha1> > example: > jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad > A few issues with this: > a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ? > b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 2015