May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20338) Investigate adding filesystem deployment integration tests against running servers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20338?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20338: -------------------------------- Story Points: 8 > Investigate adding filesystem deployment integration tests against running servers > ---------------------------------------------------------------------------------- > > Key: JBIDE-20338 > URL: https://issues.jboss.org/browse/JBIDE-20338 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha3 > > > See JBIDE-15250 for more background. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-196) Opening a volume in Docker explorer silently fails [EBZ#493863]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-196?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-196: ------------------------------ Story Points: 4 > Opening a volume in Docker explorer silently fails [EBZ#493863] > --------------------------------------------------------------- > > Key: ERT-196 > URL: https://issues.jboss.org/browse/ERT-196 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) M5 > > > When displaying containers, Docker explorer allows Show in explorer on volumes but the folder/file may not be a local one. Command should enabled on the existence of the local resource. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22430) LiveReload needs to update to newer Jetty

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22430?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22430: ------------------------------- Description: If needed in a future version of Neon, LiveReload should be updated to use the same version of Jetty in Neon (eg. from 9.3.5 -> 9.3.6) was: With move to M7, livereload build fails: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereloa... It has to be updated to use newer version of Jetty. in TP (9.3.6). > LiveReload needs to update to newer Jetty > ----------------------------------------- > > Key: JBIDE-22430 > URL: https://issues.jboss.org/browse/JBIDE-22430 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, livereload, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > > If needed in a future version of Neon, LiveReload should be updated to use the same version of Jetty in Neon (eg. from 9.3.5 -> 9.3.6) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-183) Bad error message when running a Docker Image build on a Docker file when no Docker connections [EBZ#493210]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-183?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-183: ------------------------------ Story Points: 1 > Bad error message when running a Docker Image build on a Docker file when no Docker connections [EBZ#493210] > ------------------------------------------------------------------------------------------------------------ > > Key: ERT-183 > URL: https://issues.jboss.org/browse/ERT-183 > 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) > > > Created attachment 261544 > Capture > When we run a Docker Image build on a Docker file but our workspace has no existing Docker connections, the dialog displays a strange (bad I18N processing) error message (see attached image) -- 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: ------------------------------ Sprint: devex #115 May 2016 > 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.0.Alpha3 > > > 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] (ERT-196) Opening a volume in Docker explorer silently fails [EBZ#493863]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-196?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-196: ------------------------------ Fix Version/s: Neon (4.6) M5 > Opening a volume in Docker explorer silently fails [EBZ#493863] > --------------------------------------------------------------- > > Key: ERT-196 > URL: https://issues.jboss.org/browse/ERT-196 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) M5 > > > When displaying containers, Docker explorer allows Show in explorer on volumes but the folder/file may not be a local one. Command should enabled on the existence of the local resource. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-164) Improve connection detection in connection wizard [EBZ#475892]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-164?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-164: ------------------------------ Fix Version/s: (was: Neon.1 (4.6)) > Improve connection detection in connection wizard [EBZ#475892] > -------------------------------------------------------------- > > Key: ERT-164 > URL: https://issues.jboss.org/browse/ERT-164 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Oxygen (4.7) > > > The wizard should not block the UI when opening (especially when connection settings are found but no Docker daemon is available) > Also, in case of connection test failure, an error dialog with the root cause would be interesting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-202) Can't tune docker timeout [EBZ#494131]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-202?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-202: ------------------------------ Fix Version/s: Neon.1 (4.6) > Can't tune docker timeout [EBZ#494131] > -------------------------------------- > > Key: ERT-202 > URL: https://issues.jboss.org/browse/ERT-202 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22283) reveng *.java emitter does not escape java keyword 'return' as variable name

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22283?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-22283: ------------------------------ Sprint: devex #115 May 2016 > reveng *.java emitter does not escape java keyword 'return' as variable name > ---------------------------------------------------------------------------- > > Key: JBIDE-22283 > URL: https://issues.jboss.org/browse/JBIDE-22283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.x > Environment: Eclipse Mars > Reporter: Darryl Miles > Assignee: Koen Aers > Fix For: 4.4.0.Alpha2 > > > reveng *.java emitter does not escape java keyword 'return' as variable name > <table name="oc_return_history"> > <foreign-key constraint-name="FK_oc_return_history__return_id" foreign-table="oc_return"> > <column-ref local-column="return_id" foreign-column="return_id"/> >  > <many-to-one property="return"/> > </foreign-key> > </table> > The expected output would be: > private Return _return; > but actual output is: > private Return return; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3739: ------------------------------ Story Points: 1 > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, platform-installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.x > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- 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