May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21857: -------------------------------- Story Points: 5 > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Thomas Mäder > Priority: Blocker > Fix For: 4.4.x > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22071) JDBCMetaDataConfiguration should allow fetching of table names only

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22071?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-22071: ----------------------------------- I created a duplicate in the HBX JIRA > JDBCMetaDataConfiguration should allow fetching of table names only > ------------------------------------------------------------------- > > Key: JBIDE-22071 > URL: https://issues.jboss.org/browse/JBIDE-22071 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: hibernate > Environment: Hibernate Tools 4.3.1.Final ({{org.hibernate:hibernate-tools:4.3.1.Final}}) > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.4.0.Alpha2 > > > I have a MySQL DB containing 40 tables. When I call {{org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC()}} it takes a considerably amount of time (minutes) when all I need are the table names. It seems that this method reads the entire mapping structure for all tables. > This is where I am using it: https://github.com/forge/core/blob/master/database-tools/impl/src/main/ja.... > The {{HibernateToolsHelper}} class calls {{JDBCMetaDataConfiguration.readFromJDBC()}} here: https://github.com/forge/core/blob/master/database-tools/impl/src/main/ja... > Can we improve this class to return only the table names and avoid this extra amount of work? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-156) Docker host ip cannot be copied to clipboard from anywhere [EBZ#487035]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-156?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-156: ------------------------------ Story Points: 2 (was: 1) > Docker host ip cannot be copied to clipboard from anywhere [EBZ#487035] > ----------------------------------------------------------------------- > > Key: ERT-156 > URL: https://issues.jboss.org/browse/ERT-156 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > > It would be nice if you could copy the docker host ip from somewhere. > Currently when you create a docker connection to a docker host (using Docker Machine on Mac or similar), in Docker Explorer, you see the url next to the connection name. But there is no way to copy the ip. > Currently it's not listed in the connection properties in Properties view either. I think this would be the easiest place to get it - at least show it in the Properties view so it's ready for copying to clipboard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-154) Allow for specifying labels when running a container [EBZ#485913]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-154?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-154: ------------------------------ Story Points: 5 (was: 3) > Allow for specifying labels when running a container [EBZ#485913] > ----------------------------------------------------------------- > > Key: ERT-154 > URL: https://issues.jboss.org/browse/ERT-154 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Labels can be specified on the container when it is created. The wizard/launcher could also provide this feature in the UI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22274: ---------------------------------- Story Points: 5 > Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22274 > URL: https://issues.jboss.org/browse/JBIDE-22274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247 > Reporter: Radim Hopp > Fix For: 4.4.x > > > Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2" > Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged: > {noformat:title=Failed to open in Web Browser} > java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: error=20, Not a directory > at java.lang.UNIXProcess.forkAndExec(Native Method) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:248) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 5 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21559) Pod Log: should be able to select a container to show logs if pod contains more than 1 containers

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21559?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21559. --------------------------------- Verified in Red Hat Developer Studio with build id: Alpha1-v20160520-1027-B5398. > Pod Log: should be able to select a container to show logs if pod contains more than 1 containers > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21559 > URL: https://issues.jboss.org/browse/JBIDE-21559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: openshift_v3, pod_log > Fix For: 4.4.0.Alpha1 > > > The existing issue: > 1.EXEC: Deploy a pod which contains more than 1 containers > 2.EXEC: Expand the related service tree view in "OpenShift Explorer" > 3.EXEC: Right click above pod -> click "Pod Log..." > 4.ASSERT: Will meet some errors in "Console" window like "Error from server: a container name must be specified for pod logging-kibana-1-icxl2" > So, we need find a method for user to specify a container to show logs when the pod has more than 1 containers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-18) Support for Docker Compose [EBZ#479592]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-18?page=com.atlassian.jira.plugin.sys... ] Xavier Coulon updated ERT-18: ----------------------------- Fix Version/s: Oxygen (4.7) (was: Neon (4.6) RC1) > Support for Docker Compose [EBZ#479592] > --------------------------------------- > > Key: ERT-18 > URL: https://issues.jboss.org/browse/ERT-18 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Oxygen (4.7) > > > Would suggest to support Docker Compose support in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Story Points: 3 > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12637) Hibernate Tools generates @SequenceGenerator with not unique name

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12637?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-12637: ------------------------------ Story Points: (was: 8) > Hibernate Tools generates @SequenceGenerator with not unique name > ----------------------------------------------------------------- > > Key: JBIDE-12637 > URL: https://issues.jboss.org/browse/JBIDE-12637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Nicolas Bihan > Assignee: Koen Aers > Priority: Critical > Labels: SequenceGenerator, hibenate, hibernate-tools, jpa > Fix For: 4.4.x > > > When generating entities with EJB3 annotations with a strategy set to "sequence", Hibernate tools generates POJOs with non unique javax.persistence.SequenceGenerator name "generator". But according to the Java documentation : > bq. String name (Required) A unique generator name that can be referenced by one or more classes to be the generator for primary key values. > See [javadoc|http://docs.oracle.com/javaee/5/api/javax/persistence/SequenceGen...] > Exemple of generated code with 4.0.0 Alpha1: > {code} > @SequenceGenerator(name = "generator", sequenceName = "S_CLIENT") > @Id > @GeneratedValue(strategy = SEQUENCE, generator = "generator") > @Column(name = "CLIENT_ID", unique = true, nullable = false, precision = 22, scale = 0) > public long getClientId() { > return this.clientId; > } > {code} > [Source code|https://github.com/hibernate/hibernate-tools/blob/master/src/java/or...] can be seen here. > So looks like the //TODO comment is right and it should generate a unique name atribute. sequencename+"generator" would be a good name. > It would even be better if we could define this name in reveng.xml or/and in a DelegatingReverseEngineeringStrategy class. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12637) Hibernate Tools generates @SequenceGenerator with not unique name

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12637?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-12637: ------------------------------ Fix Version/s: 4.4.x (was: 4.4.0.Alpha3) > Hibernate Tools generates @SequenceGenerator with not unique name > ----------------------------------------------------------------- > > Key: JBIDE-12637 > URL: https://issues.jboss.org/browse/JBIDE-12637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Nicolas Bihan > Assignee: Koen Aers > Priority: Critical > Labels: SequenceGenerator, hibenate, hibernate-tools, jpa > Fix For: 4.4.x > > > When generating entities with EJB3 annotations with a strategy set to "sequence", Hibernate tools generates POJOs with non unique javax.persistence.SequenceGenerator name "generator". But according to the Java documentation : > bq. String name (Required) A unique generator name that can be referenced by one or more classes to be the generator for primary key values. > See [javadoc|http://docs.oracle.com/javaee/5/api/javax/persistence/SequenceGen...] > Exemple of generated code with 4.0.0 Alpha1: > {code} > @SequenceGenerator(name = "generator", sequenceName = "S_CLIENT") > @Id > @GeneratedValue(strategy = SEQUENCE, generator = "generator") > @Column(name = "CLIENT_ID", unique = true, nullable = false, precision = 22, scale = 0) > public long getClientId() { > return this.clientId; > } > {code} > [Source code|https://github.com/hibernate/hibernate-tools/blob/master/src/java/or...] can be seen here. > So looks like the //TODO comment is right and it should generate a unique name atribute. sequencename+"generator" would be a good name. > It would even be better if we could define this name in reveng.xml or/and in a DelegatingReverseEngineeringStrategy class. -- 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