June 2017 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2752) Introduce extension points in the existing Java EE commands

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/FORGE-2752?page=com.atlassian.jira.plugin... ] Chris Laprun commented on FORGE-2752: ------------------------------------- Example of things that could also make it easier to reuse commands: - Make it easier to parse results (i.e. make it possible to know is a result is a success or failure) - Make it possible to modify the values of inputs of commands (for example to automatically provide values to inputs) when using a command transformer. > Introduce extension points in the existing Java EE commands > ----------------------------------------------------------- > > Key: FORGE-2752 > URL: https://issues.jboss.org/browse/FORGE-2752 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 3.7.0.Final > Reporter: George Gastaldi > Fix For: 3.x Future > > > JPA and REST commands are used in the Java EE addon but could perform differently when using another technology (like Spring Boot, for example). > Example: > JPA: In Spring Boot, there is no {{persistence.xml}}, but an {{application.properties}} file that contains the necessary information. > REST: Even though JAX-RS is not used, the generated REST endpoints would need extra annotations to perform correctly. This is accomplished now > Right now the JPASetupWizard for example delegates the action to a PersistenceOperations class directly. It would be nice if we could introduce some indirection (or even extract to a common addon) in the commands.execute() method. > One idea is to have a Command -> Facet -> Operations sequence, so other technologies (like Spring Boot) could reuse the same command by only implementing a different facet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-126) Format options not taken into account

by Luca Burgazzoli (JIRA)

[ https://issues.jboss.org/browse/ROASTER-126?page=com.atlassian.jira.plugi... ] Luca Burgazzoli commented on ROASTER-126: ----------------------------------------- As I set the FORMATTER_LINE_SPLIT to 120, should't the code split at the 120th char ? As far as I can see now it splits at the 80th. > Format options not taken into account > ------------------------------------- > > Key: ROASTER-126 > URL: https://issues.jboss.org/browse/ROASTER-126 > Project: Roaster > Issue Type: Bug > Components: Formatter > Affects Versions: 2.20.0.Final > Reporter: Luca Burgazzoli > Priority: Minor > > I'm doing some small experiments with Forge Roaster and I'm unable to get some formatting options taken into account. > My code and the result is here: https://gist.github.com/lburgazzoli/115377c3887972696f77db3a71fef85f > As you can notice, I configured some properties so that the code should wrap at column 120 and it should use spaces instead of tabs but my set-up is ignored and the resulting code is still formatted with some defaults. > I set the formatting properties with: > {code:java} > properties.put(DefaultCodeFormatterConstants.FORMATTER_LINE_SPLIT, "120") > properties.put(DefaultCodeFormatterConstants.FORMATTER_TAB_CHAR, "space") > properties.put(DefaultCodeFormatterConstants.FORMATTER_TAB_SIZE, "4") > {code} > The behaviour does not change if I use constants without the shaded package value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2752) Introduce extension points in the existing Java EE commands

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2752?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2752: ----------------------------------- Description: JPA and REST commands are used in the Java EE addon but could perform differently when using another technology (like Spring Boot, for example). Example: JPA: In Spring Boot, there is no {{persistence.xml}}, but an {{application.properties}} file that contains the necessary information. REST: Even though JAX-RS is not used, the generated REST endpoints would need extra annotations to perform correctly. This is accomplished now Right now the JPASetupWizard for example delegates the action to a PersistenceOperations class directly. It would be nice if we could introduce some indirection (or even extract to a common addon) in the commands.execute() method. One idea is to have a Command -> Facet -> Operations sequence, so other technologies (like Spring Boot) could reuse the same command by only implementing a different facet. was: JPA and REST commands are used in the Java EE addon but could perform differently when using another technology (like Spring Boot, for example). Example: JPA: In Spring Boot, there is no {{persistence.xml}}, but an {{application.properties}} file that contains the necessary information. REST: Even though JAX-RS is not used, the generated REST endpoints would need extra annotations to perform correctly. This is accomplished now Right now the JPASetupWizard for example delegates the action to a PersistenceOperations class directly. It would be nice if we could introduce some indirection (or even extract to a common addon) in the commands.execute() method. One idea is to have a Command -> Facet -> Operations, so other technologies (like Spring Boot) could reuse the same command by only implementing a different facet. > Introduce extension points in the existing Java EE commands > ----------------------------------------------------------- > > Key: FORGE-2752 > URL: https://issues.jboss.org/browse/FORGE-2752 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 3.7.0.Final > Reporter: George Gastaldi > Fix For: 3.x Future > > > JPA and REST commands are used in the Java EE addon but could perform differently when using another technology (like Spring Boot, for example). > Example: > JPA: In Spring Boot, there is no {{persistence.xml}}, but an {{application.properties}} file that contains the necessary information. > REST: Even though JAX-RS is not used, the generated REST endpoints would need extra annotations to perform correctly. This is accomplished now > Right now the JPASetupWizard for example delegates the action to a PersistenceOperations class directly. It would be nice if we could introduce some indirection (or even extract to a common addon) in the commands.execute() method. > One idea is to have a Command -> Facet -> Operations sequence, so other technologies (like Spring Boot) could reuse the same command by only implementing a different facet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2752) Introduce extension points in the existing Java EE commands

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2752: -------------------------------------- Summary: Introduce extension points in the existing Java EE commands Key: FORGE-2752 URL: https://issues.jboss.org/browse/FORGE-2752 Project: Forge Issue Type: Enhancement Components: Java EE Affects Versions: 3.7.0.Final Reporter: George Gastaldi Fix For: 3.x Future JPA and REST commands are used in the Java EE addon but could perform differently when using another technology (like Spring Boot, for example). Example: JPA: In Spring Boot, there is no {{persistence.xml}}, but an {{application.properties}} file that contains the necessary information. REST: Even though JAX-RS is not used, the generated REST endpoints would need extra annotations to perform correctly. This is accomplished now Right now the JPASetupWizard for example delegates the action to a PersistenceOperations class directly. It would be nice if we could introduce some indirection (or even extract to a common addon) in the commands.execute() method. One idea is to have a Command -> Facet -> Operations, so other technologies (like Spring Boot) could reuse the same command by only implementing a different facet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2751) Upgrade to Furnace 2.26.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2751?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2751. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.26.1.Final > ------------------------------- > > Key: FORGE-2751 > URL: https://issues.jboss.org/browse/FORGE-2751 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 3.7.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.7.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2750) Upgrade to Maven 3.5.0 and replace Aether with Maven Resolver

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2750?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2750. ---------------------------------- Resolution: Done > Upgrade to Maven 3.5.0 and replace Aether with Maven Resolver > ------------------------------------------------------------- > > Key: FORGE-2750 > URL: https://issues.jboss.org/browse/FORGE-2750 > Project: Forge > Issue Type: Component Upgrade > Components: Build Tools - Maven > Affects Versions: 3.7.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.7.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-131) NoSuchElementException when installing modules

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-131?page=com.atlassian.jira.plugi... ] George Gastaldi commented on FURNACE-131: ----------------------------------------- Is there a test case? Need more info to reproduce that > NoSuchElementException when installing modules > ---------------------------------------------- > > Key: FURNACE-131 > URL: https://issues.jboss.org/browse/FURNACE-131 > Project: Forge: Furnace > Issue Type: Bug > Affects Versions: 2.24.3.Final > Reporter: Ondrej Zizka > Attachments: ForgeException.txt > > > Got this in Windup: Full log attached. > Hardly reproducible. > Caused by: java.util.NoSuchElementException > at java.util.ArrayDeque.removeFirst(ArrayDeque.java:280) > at java.util.ArrayDeque.pop(ArrayDeque.java:517) > at org.jboss.forge.furnace.container.cdi.events.CrossContainerObserverMethod.pop(CrossContainerObserverMethod.java:141) > at org.jboss.forge.furnace.container.cdi.events.CrossContainerObserverMethod.handleEvent(CrossContainerObserverMethod.java:86) > at sun.reflect.GeneratedMethodAccessor4536.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78) > at org.jboss.weld.injection.MethodInvocationStrategy$DefaultMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:109) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:277) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:255) > at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:269) > at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:258) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:154) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:136) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:675) > at org.jboss.forge.furnace.container.cdi.events.EventManagerImpl.lambda$fireEvent$0(EventManagerImpl.java:42) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:70) > at org.jboss.forge.furnace.container.cdi.events.EventManagerImpl.fireEvent(EventManagerImpl.java:41) > ... 11 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2751) Upgrade to Furnace 2.26.1.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2751: -------------------------------------- Summary: Upgrade to Furnace 2.26.1.Final Key: FORGE-2751 URL: https://issues.jboss.org/browse/FORGE-2751 Project: Forge Issue Type: Component Upgrade Components: Furnace (Container) Affects Versions: 3.7.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.7.1.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2750) Upgrade to Maven 3.5.0 and replace Aether with Maven Resolver

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2750: -------------------------------------- Summary: Upgrade to Maven 3.5.0 and replace Aether with Maven Resolver Key: FORGE-2750 URL: https://issues.jboss.org/browse/FORGE-2750 Project: Forge Issue Type: Component Upgrade Components: Build Tools - Maven Affects Versions: 3.7.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.7.1.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-143) Upgrade to Maven 3.5.0 and replace Aether with Maven Resolver

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-143?page=com.atlassian.jira.plugi... ] George Gastaldi closed FURNACE-143. ----------------------------------- Resolution: Done > Upgrade to Maven 3.5.0 and replace Aether with Maven Resolver > ------------------------------------------------------------- > > Key: FURNACE-143 > URL: https://issues.jboss.org/browse/FURNACE-143 > Project: Forge: Furnace > Issue Type: Component Upgrade > Components: Maven > Affects Versions: 2.26.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.26.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2017