April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-136) ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830]

by Nick Boldt (JIRA)

Nick Boldt created ERT-136: ------------------------------ Summary: ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830] Key: ERT-136 URL: https://issues.jboss.org/browse/ERT-136 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt An exception occurs when a JavaScript project has no Source Folder defined: java.lang.ArrayIndexOutOfBoundsException: 0 at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.validate(JavaScriptValidator.java:55) at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704) at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669) at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299) at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120) at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87) at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:117) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:105) at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219) at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178) at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-133) Not possible to toggle breakpoint in JSDT editor [EBZ#490281]

by Nick Boldt (JIRA)

Nick Boldt created ERT-133: ------------------------------ Summary: Not possible to toggle breakpoint in JSDT editor [EBZ#490281] Key: ERT-133 URL: https://issues.jboss.org/browse/ERT-133 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt It looks like after obsolete parser update with esprima based one it is not possible to toggle breakpoints in JSDT editor - "A valid location can not be found for the breakpoint" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-133) Not possible to toggle breakpoint in JSDT editor [EBZ#490281]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-133?page=com.atlassian.jira.plugin.sy... ] Nick Boldt resolved ERT-133. ---------------------------- Resolution: Done > Not possible to toggle breakpoint in JSDT editor [EBZ#490281] > ------------------------------------------------------------- > > Key: ERT-133 > URL: https://issues.jboss.org/browse/ERT-133 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: Debug, bzira > > It looks like after obsolete parser update with esprima based one it is not possible to toggle breakpoints in JSDT editor - "A valid location can not be found for the breakpoint" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-134) Make ReconcileWorkingCopyOperation to use new parser completely [EBZ#490714]

by Nick Boldt (JIRA)

Nick Boldt created ERT-134: ------------------------------ Summary: Make ReconcileWorkingCopyOperation to use new parser completely [EBZ#490714] Key: ERT-134 URL: https://issues.jboss.org/browse/ERT-134 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt The change https://git.eclipse.org/r/69179 has turned ReconcileWorkingCopyOperation to use ASTParser.newParser()/createAST(). But we still need to make it to use new parser completely. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-135) [contentassist] Some templates have multiple ${cursor} variables [EBZ#490800]

by Nick Boldt (JIRA)

Nick Boldt created ERT-135: ------------------------------ Summary: [contentassist] Some templates have multiple ${cursor} variables [EBZ#490800] Key: ERT-135 URL: https://issues.jboss.org/browse/ERT-135 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt Some templates fail the validation check because they have more than one ${cursor} variable. Simple fix: remove other ${cursor} variables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22170) Openshift 3 plugin should allow me to edit Routes

by Rafael Benevides (JIRA)

Rafael Benevides created JBIDE-22170: ---------------------------------------- Summary: Openshift 3 plugin should allow me to edit Routes Key: JBIDE-22170 URL: https://issues.jboss.org/browse/JBIDE-22170 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Rafael Benevides - As a developer I would like to edit existing openshift routes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12637?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-12637: ----------------------------------- Fix Version/s: (was: 4.0.x) (was: 4.1.x) > 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 > Affects Versions: 4.0.0.Alpha1 > Reporter: Nicolas Bihan > Assignee: Koen Aers > Priority: Blocker > Labels: SequenceGenerator, hibenate, hibernate-tools, jpa > > 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)

10 years

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12637?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-12637: ----------------------------------- Priority: Critical (was: Blocker) > 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 > Affects Versions: 4.0.0.Alpha1 > Reporter: Nicolas Bihan > Assignee: Koen Aers > Priority: Critical > Labels: SequenceGenerator, hibenate, hibernate-tools, jpa > > 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)

10 years

1
0
0 / 0

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

by Tamás Ábele (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12637?page=com.atlassian.jira.plugi... ] Tamás Ábele commented on JBIDE-12637: ------------------------------------- To provide a solution which can produce useable POJO-s is simple, so it's very surprising that after 4 years this blocking bug isn't fixed. I just simply modified the generateAnnIdGenerator() method in EntityPOJOClass to the following: {code:java} builder .resetAnnotation(importType("javax.persistence.GeneratedValue")) .addAttribute("strategy", staticImport("javax.persistence.GenerationType", "SEQUENCE")) .addQuotedAttribute("generator", clazz.getClassName()+"IdGenerator"); idResult.append(builder.getResult()); builder .resetAnnotation(importType("javax.persistence.SequenceGenerator")) .addQuotedAttribute("name", clazz.getClassName()+"IdGenerator") .addQuotedAttribute("sequenceName", properties.getProperty(org.hibernate.id.SequenceGenerator.SEQUENCE, null)); {code} > 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 > Affects Versions: 4.0.0.Alpha1 > Reporter: Nicolas Bihan > Assignee: Koen Aers > Priority: Blocker > Labels: SequenceGenerator, hibenate, hibernate-tools, jpa > Fix For: 4.0.x, 4.1.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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-659) JBTIS Target Platform - Neon

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-659?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-659: ----------------------------- Affects Version/s: 4.4.0.Alpha1-TP (was: 4.4.0.Alpha1) > JBTIS Target Platform - Neon > ---------------------------- > > Key: JBTIS-659 > URL: https://issues.jboss.org/browse/JBTIS-659 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Alpha1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > Add support for a Neon based JBTIS target platform. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016