June 2017 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-510) Create automated routine for checking plugin version compliance of plugins in Central Plugin Index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-510?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-510. --------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Out of Date > Create automated routine for checking plugin version compliance of plugins in Central Plugin Index > -------------------------------------------------------------------------------------------------- > > Key: FORGE-510 > URL: https://issues.jboss.org/browse/FORGE-510 > Project: Forge > Issue Type: Sub-task > Components: Plugin Repository > Affects Versions: 1.0.6.Final > Reporter: Ivan St. Ivanov > > Create a routine, executed by the build server, that checks a predefined set of Forge plugins for version consistency with Forge core. In order to satisfy this check, for each major version of the core there should be at least one plugin branch or tag that specifies the same major version. If the check fails, the plugin author should receive an email asking them to fix the inconcistency. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2754) Upgrade eGit to 4.7.1.201706071930-r

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2754?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2754. ---------------------------------- Resolution: Done > Upgrade eGit to 4.7.1.201706071930-r > ------------------------------------ > > Key: FORGE-2754 > URL: https://issues.jboss.org/browse/FORGE-2754 > Project: Forge > Issue Type: Component Upgrade > Components: Git > 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)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2754) Upgrade eGit to 4.7.1.201706071930-r

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2754: -------------------------------------- Summary: Upgrade eGit to 4.7.1.201706071930-r Key: FORGE-2754 URL: https://issues.jboss.org/browse/FORGE-2754 Project: Forge Issue Type: Component Upgrade Components: Git 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)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2749) Subfolders and files are copied to the destination folder but under same origin folder

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2749?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2749. ---------------------------------- Resolution: Won't Do You need to use the following syntax instead: {{cp -r ../../scripts/front/modified/. src/main/resources/static/}} (notice the {{/.}} in the end of the source folder) > Subfolders and files are copied to the destination folder but under same origin folder > -------------------------------------------------------------------------------------- > > Key: FORGE-2749 > URL: https://issues.jboss.org/browse/FORGE-2749 > Project: Forge > Issue Type: Enhancement > Reporter: Charles Moulliard > > When I run this command within the Forge shell > {code} > cp -r ../../scripts/front/modified src/main/resources/static/ > {code} > the folder "modified" is also copied to the destination while in fact we want to copy the files and subfolders under the "origin" folder > {code} > demo/cdfront/src/main/resources/static > demo/cdfront/src/main/resources/static/modified > demo/cdfront/src/main/resources/static/modified/app.html > demo/cdfront/src/main/resources/static/modified/fonts > .... > {code} > Is there a trick to copy all the files + subfolders under the folder "modified" only ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2753) Use Target Location Root in New Project wizard does not work appropriately

by Clement Escoffier (JIRA)

[ https://issues.jboss.org/browse/FORGE-2753?page=com.atlassian.jira.plugin... ] Clement Escoffier commented on FORGE-2753: ------------------------------------------ Fix confirmed! > Use Target Location Root in New Project wizard does not work appropriately > -------------------------------------------------------------------------- > > Key: FORGE-2753 > URL: https://issues.jboss.org/browse/FORGE-2753 > Project: Forge > Issue Type: Bug > Components: Projects > Affects Versions: 3.7.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.7.1.Final > > > When --use-target-location-root is specified, the project is not created. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2753) Use Target Location Root in New Project wizard does not work appropriately

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2753?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2753. ---------------------------------- Resolution: Done > Use Target Location Root in New Project wizard does not work appropriately > -------------------------------------------------------------------------- > > Key: FORGE-2753 > URL: https://issues.jboss.org/browse/FORGE-2753 > Project: Forge > Issue Type: Bug > Components: Projects > Affects Versions: 3.7.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.7.1.Final > > > When --use-target-location-root is specified, the project is not created. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2753) Use Target Location Root in New Project wizard does not work appropriately

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2753: -------------------------------------- Summary: Use Target Location Root in New Project wizard does not work appropriately Key: FORGE-2753 URL: https://issues.jboss.org/browse/FORGE-2753 Project: Forge Issue Type: Bug Components: Projects Affects Versions: 3.7.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.7.1.Final When --use-target-location-root is specified, the project is not created. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2753) Use Target Location Root in New Project wizard does not work appropriately

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2753?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2753: ----------------------------------- Forum Reference: https://github.com/cescoffier/vertx-forge-addon/issues/21 > Use Target Location Root in New Project wizard does not work appropriately > -------------------------------------------------------------------------- > > Key: FORGE-2753 > URL: https://issues.jboss.org/browse/FORGE-2753 > Project: Forge > Issue Type: Bug > Components: Projects > Affects Versions: 3.7.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.7.1.Final > > > When --use-target-location-root is specified, the project is not created. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[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: ------------------------------------- [~gastaldi] an example of being able to modify the value of inputs would be to automatically set the generator to use the Spring Boot one when on a Spring Boot project and requesting REST endpoint generation from entities. CommandExecutionListener wouldn't let me do that since I can't access the inputs from UICommand. > 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)

6 years, 10 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 commented on FORGE-2752: ---------------------------------------- [~claprun], what are the use cases for those examples? A feature that may help you is that Forge allows you to listen to command execution by implementing a CommandExecutionListener: https://github.com/forge/core/blob/master/ui/api/src/main/java/org/jboss/... > 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)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2017