September 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2684) eclipse jpa-generate-entities-from-tables only allows mysql fabric driver

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2684?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-2684: -------------------------------------- Assignee: George Gastaldi > eclipse jpa-generate-entities-from-tables only allows mysql fabric driver > ------------------------------------------------------------------------- > > Key: FORGE-2684 > URL: https://issues.jboss.org/browse/FORGE-2684 > Project: Forge > Issue Type: Bug > Components: Database Tools > Affects Versions: 3.3.1.Final > Environment: Using forge from a windows command line I can successfully execute > {code:java} > jpa-generate-entities-from-tables --database-tables * --target-package ca.gerrymatte.health.model --hibernate-dialect org.hibernate.dialect.MySQL5InnoDBDialect --driver-class com.mysql.jdbc.Driver --driver-location D:/s/jclasses/drivers/mysql.jar --user-name root --user-password secret --jdbc-url jdbc:mysql://127.0.0.1/health ; > {code} > Using forge 3.3.1.Final included with Jboss Developer Studio 10.1.0.Final the dialog box that specifies which driver to use defaults to the mysql fabric driver. When I select the normal mysql driver and test the connection all is ok. > However when I click next the resulting screen shows the fabric driver is still being used and of course the connection fails to work. See the attached screen images. > Reporter: Gerry Matte > Assignee: George Gastaldi > Attachments: jpa-gen01.png, jpa-gen02.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2684) eclipse jpa-generate-entities-from-tables only allows mysql fabric driver

by Gerry Matte (JIRA)

Gerry Matte created FORGE-2684: ---------------------------------- Summary: eclipse jpa-generate-entities-from-tables only allows mysql fabric driver Key: FORGE-2684 URL: https://issues.jboss.org/browse/FORGE-2684 Project: Forge Issue Type: Bug Components: Database Tools Affects Versions: 3.3.1.Final Environment: Using forge from a windows command line I can successfully execute {code:java} jpa-generate-entities-from-tables --database-tables * --target-package ca.gerrymatte.health.model --hibernate-dialect org.hibernate.dialect.MySQL5InnoDBDialect --driver-class com.mysql.jdbc.Driver --driver-location D:/s/jclasses/drivers/mysql.jar --user-name root --user-password secret --jdbc-url jdbc:mysql://127.0.0.1/health ; {code} Using forge 3.3.1.Final included with Jboss Developer Studio 10.1.0.Final the dialog box that specifies which driver to use defaults to the mysql fabric driver. When I select the normal mysql driver and test the connection all is ok. However when I click next the resulting screen shows the fabric driver is still being used and of course the connection fails to work. See the attached screen images. Reporter: Gerry Matte Attachments: jpa-gen01.png, jpa-gen02.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-111) Spaces in generic types in ExtendableSource.setSuperType causes exception

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-111?page=com.atlassian.jira.plugi... ] George Gastaldi closed ROASTER-111. ----------------------------------- Fix Version/s: 2.19.1.Final Resolution: Done > Spaces in generic types in ExtendableSource.setSuperType causes exception > ------------------------------------------------------------------------- > > Key: ROASTER-111 > URL: https://issues.jboss.org/browse/ROASTER-111 > Project: Roaster > Issue Type: Bug > Components: API, Formatter > Affects Versions: 2.19.0.Final > Reporter: Steven Paligo > Fix For: 2.19.1.Final > > > Having a space in the generics of a super type causes an IllegalArgumentException. This is similar to ROASTER-107, but apparently that fix didn't correct this issue. > Code to reproduce: > {code:java} > final JavaClassSource myClass = Roaster.create(JavaClassSource.class); > myClass.setPackage("test"); > myClass.setPublic() > .setName("MyClass") > .setSuperType("test.MyClassParent<java.util.String, java.util.Object>"); > {code} > Exception: > {noformat} > Exception in thread "main" java.lang.IllegalArgumentException: Invalid identifier : > java< > at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:195) > at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202) > at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newName(AST.java:1965) > at org.jboss.forge.roaster.model.impl.ImportImpl.setName(ImportImpl.java:65) > at org.jboss.forge.roaster.model.impl.AbstractJavaSource.addImport(AbstractJavaSource.java:186) > at org.jboss.forge.roaster.model.impl.JavaClassImpl.setSuperType(JavaClassImpl.java:190) > at org.jboss.forge.roaster.model.impl.JavaClassImpl.setSuperType(JavaClassImpl.java:30) > ... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-111) Spaces in generic types in ExtendableSource.setSuperType causes exception

by Steven Paligo (JIRA)

Steven Paligo created ROASTER-111: ------------------------------------- Summary: Spaces in generic types in ExtendableSource.setSuperType causes exception Key: ROASTER-111 URL: https://issues.jboss.org/browse/ROASTER-111 Project: Roaster Issue Type: Bug Components: API, Formatter Affects Versions: 2.19.0.Final Reporter: Steven Paligo Having a space in the generics of a super type causes an IllegalArgumentException. This is similar to ROASTER-107, but apparently that fix didn't correct this issue. Code to reproduce: {code:java} final JavaClassSource myClass = Roaster.create(JavaClassSource.class); myClass.setPackage("test"); myClass.setPublic() .setName("MyClass") .setSuperType("test.MyClassParent<java.util.String, java.util.Object>"); {code} Exception: {noformat} Exception in thread "main" java.lang.IllegalArgumentException: Invalid identifier : > java< at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:195) at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202) at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newName(AST.java:1965) at org.jboss.forge.roaster.model.impl.ImportImpl.setName(ImportImpl.java:65) at org.jboss.forge.roaster.model.impl.AbstractJavaSource.addImport(AbstractJavaSource.java:186) at org.jboss.forge.roaster.model.impl.JavaClassImpl.setSuperType(JavaClassImpl.java:190) at org.jboss.forge.roaster.model.impl.JavaClassImpl.setSuperType(JavaClassImpl.java:30) ... {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2682) Enable project-new wizard to filter archetypes by group id and version

by James Netherton (JIRA)

[ https://issues.jboss.org/browse/FORGE-2682?page=com.atlassian.jira.plugin... ] James Netherton commented on FORGE-2682: ---------------------------------------- Yes, correct. I was thinking it'd nice to have some means of trimming down the list of stuff that gets displayed based on some sort of filter. > Enable project-new wizard to filter archetypes by group id and version > ---------------------------------------------------------------------- > > Key: FORGE-2682 > URL: https://issues.jboss.org/browse/FORGE-2682 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Reporter: James Netherton > > When creating a new project and selecting the 'from-archetype-catalog' option, it'd be nice if the archetype list could be filtered based on a Maven group id and / or version. E.g something like: > {code} > project-new --archetype-group-id=org.foo --archetype-version=1.0 > {code} > Then, when the list of available archetypes is displayed, they get filtered based on these parameters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2682) Enable project-new wizard to filter archetypes by group id and version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2682?page=com.atlassian.jira.plugin... ] George Gastaldi edited comment on FORGE-2682 at 9/20/16 5:56 PM: ----------------------------------------------------------------- Ah now that I see that this is meant for the "from-archetype-catalog" project type. It should be easier by iterating the existing registered archetype catalog factories. However I don't think that from-archetype-catalog has the {{archetype-group-id}} and {{archetype-version}} parameters? was (Author: gastaldi): Ah now that I see that this is meant for the "from-archetype-catalog" project type. It should be easier by iterating the existing registered archetype catalog factories. > Enable project-new wizard to filter archetypes by group id and version > ---------------------------------------------------------------------- > > Key: FORGE-2682 > URL: https://issues.jboss.org/browse/FORGE-2682 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Reporter: James Netherton > > When creating a new project and selecting the 'from-archetype-catalog' option, it'd be nice if the archetype list could be filtered based on a Maven group id and / or version. E.g something like: > {code} > project-new --archetype-group-id=org.foo --archetype-version=1.0 > {code} > Then, when the list of available archetypes is displayed, they get filtered based on these parameters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2682) Enable project-new wizard to filter archetypes by group id and version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2682?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2682: ---------------------------------------- Ah now that I see that this is meant for the "from-archetype-catalog" project type. It should be easier by iterating the existing registered archetype catalog factories. > Enable project-new wizard to filter archetypes by group id and version > ---------------------------------------------------------------------- > > Key: FORGE-2682 > URL: https://issues.jboss.org/browse/FORGE-2682 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Reporter: James Netherton > > When creating a new project and selecting the 'from-archetype-catalog' option, it'd be nice if the archetype list could be filtered based on a Maven group id and / or version. E.g something like: > {code} > project-new --archetype-group-id=org.foo --archetype-version=1.0 > {code} > Then, when the list of available archetypes is displayed, they get filtered based on these parameters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2682) Enable project-new wizard to filter archetypes by group id and version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2682?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2682: ---------------------------------------- This looks interesting from an UX point of view. Thinking on the technical aspects, that would mean downloading the archetype-catalog.xml from all the configured repositories. Thoughts? > Enable project-new wizard to filter archetypes by group id and version > ---------------------------------------------------------------------- > > Key: FORGE-2682 > URL: https://issues.jboss.org/browse/FORGE-2682 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Reporter: James Netherton > > When creating a new project and selecting the 'from-archetype-catalog' option, it'd be nice if the archetype list could be filtered based on a Maven group id and / or version. E.g something like: > {code} > project-new --archetype-group-id=org.foo --archetype-version=1.0 > {code} > Then, when the list of available archetypes is displayed, they get filtered based on these parameters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2683) Upgrade to Furnace 2.24.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2683?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2683. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.24.0.Final > ------------------------------- > > Key: FORGE-2683 > URL: https://issues.jboss.org/browse/FORGE-2683 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.3.2.Final > > > It features Weld 2.4.0.Final, which removes the dependency on guava -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2683) Upgrade to Furnace 2.24.0.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2683: -------------------------------------- Summary: Upgrade to Furnace 2.24.0.Final Key: FORGE-2683 URL: https://issues.jboss.org/browse/FORGE-2683 Project: Forge Issue Type: Component Upgrade Components: Furnace (Container) Affects Versions: 3.3.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.3.2.Final It features Weld 2.4.0.Final, which removes the dependency on guava -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2016