August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18180) Hibernate Tools UI elements not loading images

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18180?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-18180. ------------------------------- Resolution: Done > Hibernate Tools UI elements not loading images > ---------------------------------------------- > > Key: JBIDE-18180 > URL: https://issues.jboss.org/browse/JBIDE-18180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599 (from nightly repo) > Reporter: Luke Maurer > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > Attachments: screenshot-1.png > > > Immediately upon switching to the Hibernate perspective, I get error dialogs and log messages saying “Unable to create resource URLImageDescriptor” with an URL. All elements in the Hibernate Configurations tab, including the toolbar buttons (reload, HQL editor, etc.) and the nodes in the configuration tree, appear as little red squares or as blank. Functionality seems unaffected (besides having to click through those dialogs …). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18180) Hibernate Tools UI elements not loading images

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18180?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-18180: ----------------------------------- This works as of build 602. The icons/ folder was not included in the binary build artefact. > Hibernate Tools UI elements not loading images > ---------------------------------------------- > > Key: JBIDE-18180 > URL: https://issues.jboss.org/browse/JBIDE-18180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599 (from nightly repo) > Reporter: Luke Maurer > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > Attachments: screenshot-1.png > > > Immediately upon switching to the Hibernate perspective, I get error dialogs and log messages saying “Unable to create resource URLImageDescriptor” with an URL. All elements in the Hibernate Configurations tab, including the toolbar buttons (reload, HQL editor, etc.) and the nodes in the configuration tree, appear as little red squares or as blank. Functionality seems unaffected (besides having to click through those dialogs …). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18105: ---------------------------------------- I'm writing a mojo doing that. In case I don't succeed to get something working well enough, we could still make the first shot manually. > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. > Currently the properties file looks like this: > https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-18105: -------------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. > Currently the properties file looks like this: > https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11150) No output/info after generation tables from entities into DB

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11150?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-11150: ------------------------------ Fix Version/s: 4.3.x (was: 4.2.0.CR1) Since this requires a change in Hibernate Tools Core, which is certainly not going to happen before GA, this is deferred to 4.3.x. > No output/info after generation tables from entities into DB > ------------------------------------------------------------ > > Key: JBIDE-11150 > URL: https://issues.jboss.org/browse/JBIDE-11150 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.3.0.Beta1 > Environment: jbdevstudio-product-universal-5.0.0.v201203010100M-H88-Beta1.jar, L64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.3.x > > > There is no output/message after JPA Tools -> Generate tables from entities when export to DB is enabled. It's not replacing database by default and it's not certain what's the status of export when there is no message, status, etc. There should be some info message in error log or some dialog providing user friendly report. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8849) JPA project revalidation after export to db

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8849?page=com.atlassian.jira.plugin... ] Koen Aers updated JBIDE-8849: ----------------------------- Fix Version/s: 4.3.x (was: 4.2.0.CR1) Punting this feature request to 4.3.x as this will certainly not happen before GA anymore. > JPA project revalidation after export to db > ------------------------------------------- > > Key: JBIDE-8849 > URL: https://issues.jboss.org/browse/JBIDE-8849 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate, upstream > Affects Versions: 3.2.1.M1 > Environment: JBDS 4.1.0 m1 H359 > Reporter: Jiri Peterka > Labels: jpa > Fix For: 4.3.x > > > 1. Create datasource and open it > 2. Let's have JPA Project referenced datasource from step above > 3. Create entity M with table name Z, you'll get Table "Z" cannot be resolved > 4. Project -> JPA Tools -> Generate Tables from Entities with "Check Export to database" selected > 5. Finish > After doing this project entity is not yet valid > It would be nice, if connection could be refreshed and code revalidated automatically after export to db (it could be also configurable if desired) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18162) For JBIDE 4.2.0.CR1: Code Freeze + Branch [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18162?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-18162. ------------------------------------------ Resolution: Done > For JBIDE 4.2.0.CR1: Code Freeze + Branch [BrowserSim] > ------------------------------------------------------ > > Key: JBIDE-18162 > URL: https://issues.jboss.org/browse/JBIDE-18162 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Mickael Istria > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [BrowserSim]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13210) Generate Hibernate/JPA Annotations is disabled in main menubar

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13210?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13210. ------------------------------- Resolution: Done > Generate Hibernate/JPA Annotations is disabled in main menubar > -------------------------------------------------------------- > > Key: JBIDE-13210 > URL: https://issues.jboss.org/browse/JBIDE-13210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.0.0.CR1 > Environment: JBDS 6.0.0.CR1b, L64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > Source -> Generate Hibernate/JPA is disabled (at least I didn't find any case when it's enabled). Operation works via context (on java file(s)) without problems. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18183) Enhancement to custom jmx provider UI

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18183?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18183: ------------------------------------- Linking issue > Enhancement to custom jmx provider UI > ------------------------------------- > > Key: JBIDE-18183 > URL: https://issues.jboss.org/browse/JBIDE-18183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Fix For: 4.2.0.CR1 > > > Currently, each JMX provider has a UI mapped to it, and the UI assumes only 1 icon for each provider. > Fuse Tools has several server types that behave identically, but require different icons. This could be worked around by declaring 4 or 5 different providers, and accompanying xml indicating different icons, but this is a lot of overhead and would make the code much more complex. > A simpler solution is to allow an image provider to be part of the extension point. The image provider could then pull the Image from the server type ui (declared in wtp's api). This would also instantiate fewer images by re-using those already instantiated for wtp.server. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18183) Enhancement to custom jmx provider UI

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18183?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18183: -------------------------------- Fix Version/s: 4.2.0.CR1 > Enhancement to custom jmx provider UI > ------------------------------------- > > Key: JBIDE-18183 > URL: https://issues.jboss.org/browse/JBIDE-18183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Fix For: 4.2.0.CR1 > > > Currently, each JMX provider has a UI mapped to it, and the UI assumes only 1 icon for each provider. > Fuse Tools has several server types that behave identically, but require different icons. This could be worked around by declaring 4 or 5 different providers, and accompanying xml indicating different icons, but this is a lot of overhead and would make the code much more complex. > A simpler solution is to allow an image provider to be part of the extension point. The image provider could then pull the Image from the server type ui (declared in wtp's api). This would also instantiate fewer images by re-using those already instantiated for wtp.server. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 August 2014