May 2016 - jbosstools-issues - Jboss List Archives

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

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-22430: ------------------------------------- Summary: 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.Alpha2 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). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22243: -------------------------------- Story Points: 5 > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha3 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22243: -------------------------------- Sprint: devex #115 May 2016 > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha3 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22429) Client library: Upgrade to latest openshift-restclient-java

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22429: ---------------------------------------- Summary: Client library: Upgrade to latest openshift-restclient-java Key: JBIDE-22429 URL: https://issues.jboss.org/browse/JBIDE-22429 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.4.0.Alpha3 Reporter: Andre Dietisheim We need to let the tooling use the latest openshift-restclient-java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22429) Client library: Upgrade to latest openshift-restclient-java

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22429?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22429: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 > Client library: Upgrade to latest openshift-restclient-java > ----------------------------------------------------------- > > Key: JBIDE-22429 > URL: https://issues.jboss.org/browse/JBIDE-22429 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Andre Dietisheim > Fix For: 4.4.0.Alpha3 > > > We need to let the tooling use the latest openshift-restclient-java -- 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.0.Alpha3 (was: 4.4.x) Story Points: 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.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] (JBIDE-22304) Server Editor: Pod deployment path is not shown

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22304: -------------------------------- Sprint: devex #115 May 2016 > Server Editor: Pod deployment path is not shown > ----------------------------------------------- > > Key: JBIDE-22304 > URL: https://issues.jboss.org/browse/JBIDE-22304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > Fix For: 4.4.0.Alpha3 > > > In Server Adapter wizard is not shown Pod deployment path. Widget supposed to display the path is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21302: -------------------------------- Sprint: devex #0 January 2016, devex #1 February 2016, devex #2 February 2016, devex #115 May 2016 (was: devex #0 January 2016, devex #1 February 2016, devex #2 February 2016) > Removing user from credentials framework while not authenticated to secure storage should not work > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21302 > URL: https://issues.jboss.org/browse/JBIDE-21302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.x > > > Removing credentials (which are stored in secure storage) using > CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage". -- 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: Neon.1 (4.6) Oxygen (4.7) > 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: Neon.1 (4.6), 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] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21302: -------------------------------- Story Points: 2 > Removing user from credentials framework while not authenticated to secure storage should not work > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21302 > URL: https://issues.jboss.org/browse/JBIDE-21302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.x > > > Removing credentials (which are stored in secure storage) using > CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage". -- 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