July 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1961) Incorrect default value for database in JPA:Setup when JBoss Enterprise Application Server is chosen

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1961: -------------------------------------- Summary: Incorrect default value for database in JPA:Setup when JBoss Enterprise Application Server is chosen Key: FORGE-1961 URL: https://issues.jboss.org/browse/FORGE-1961 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Java EE Affects Versions: 2.7.2.Final Reporter: Vineet Reynolds The default value for the database input field is HSQLDB instead of H2, when the application server is selected as JBoss EAP (the default). This results in an incorrect dialect being specified in the project's persistence.xml file. Apparently this appears to cause no problems, since the dialects might be similar, but this should still be fixed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1960) Support creation and management of Cordova projects

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1960?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1960: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/492 > Support creation and management of Cordova projects > --------------------------------------------------- > > Key: FORGE-1960 > URL: https://issues.jboss.org/browse/FORGE-1960 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Projects > Affects Versions: 2.7.2.Final > Reporter: Vineet Reynolds > > We should support creation of new Cordova projects in Forge. This is primarily to help with FORGEPLUGINS-113 and FORGEPLUGINS-166 so that projects with a different build system unlike Maven or Gradle can be supported by Forge. > We should also allow existing Cordova projects to be recognized as projects in Forge so that additional contextual commands maybe activated for the benefit of end-users. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1960) Support creation and management of Cordova projects

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1960?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1960: ----------------------------------- Component/s: Projects > Support creation and management of Cordova projects > --------------------------------------------------- > > Key: FORGE-1960 > URL: https://issues.jboss.org/browse/FORGE-1960 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Projects > Affects Versions: 2.7.2.Final > Reporter: Vineet Reynolds > > We should support creation of new Cordova projects in Forge. This is primarily to help with FORGEPLUGINS-113 and FORGEPLUGINS-166 so that projects with a different build system unlike Maven or Gradle can be supported by Forge. > We should also allow existing Cordova projects to be recognized as projects in Forge so that additional contextual commands maybe activated for the benefit of end-users. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1960) Support creation and management of Cordova projects

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1960: -------------------------------------- Summary: Support creation and management of Cordova projects Key: FORGE-1960 URL: https://issues.jboss.org/browse/FORGE-1960 Project: Forge Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.7.2.Final Reporter: Vineet Reynolds We should support creation of new Cordova projects in Forge. This is primarily to help with FORGEPLUGINS-113 and FORGEPLUGINS-166 so that projects with a different build system unlike Maven or Gradle can be supported by Forge. We should also allow existing Cordova projects to be recognized as projects in Forge so that additional contextual commands maybe activated for the benefit of end-users. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1959) Use current furnace version when installing addons from GIT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1959?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1959. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.7.3.Final (was: 2.x Future) Resolution: Done > Use current furnace version when installing addons from GIT > ----------------------------------------------------------- > > Key: FORGE-1959 > URL: https://issues.jboss.org/browse/FORGE-1959 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Addon Manager > Affects Versions: 2.7.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.7.3.Final > > > Forge should always attempt to build addons using the current Furnace version. > We should pass the {{version.furnace}} as a parameter to the addon build to allow this. Addons should use the {{<version.furnace>}} property in the pom.xml to define the forge version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1959) Use current furnace version when installing addons from GIT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1959?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1959: ----------------------------------- Description: Forge should always attempt to build addons using the current Furnace version. We should pass the {{version.furnace}} as a parameter to the addon build to allow this. Addons should use the {{<version.furnace>}} property in the pom.xml to define the forge version. was: Forge should always attempt to build addons using the current Furnace version. We should pass the {{version.furnace}} as a parameter to the addon build to allow this. Addons should use the <furnace.version> property in the pom.xml to define the forge version. > Use current furnace version when installing addons from GIT > ----------------------------------------------------------- > > Key: FORGE-1959 > URL: https://issues.jboss.org/browse/FORGE-1959 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Addon Manager > Affects Versions: 2.7.2.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Forge should always attempt to build addons using the current Furnace version. > We should pass the {{version.furnace}} as a parameter to the addon build to allow this. Addons should use the {{<version.furnace>}} property in the pom.xml to define the forge version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1959) Use current furnace version when installing addons from GIT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1959?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1959: ----------------------------------- Description: Forge should always attempt to build addons using the current Furnace version. We should pass the {{version.furnace}} as a parameter to the addon build to allow this. Addons should use the <furnace.version> property in the pom.xml to define the forge version. was: Forge should always attempt to build addons using the current Furnace version. We should pass the {{furnace.version}} as a parameter to the addon build to allow this. Addons should use the <furnace.version> property in the pom.xml to define the forge version. > Use current furnace version when installing addons from GIT > ----------------------------------------------------------- > > Key: FORGE-1959 > URL: https://issues.jboss.org/browse/FORGE-1959 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Addon Manager > Affects Versions: 2.7.2.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Forge should always attempt to build addons using the current Furnace version. > We should pass the {{version.furnace}} as a parameter to the addon build to allow this. Addons should use the <furnace.version> property in the pom.xml to define the forge version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1959) Use current furnace version when installing addons from GIT

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1959: -------------------------------------- Summary: Use current furnace version when installing addons from GIT Key: FORGE-1959 URL: https://issues.jboss.org/browse/FORGE-1959 Project: Forge Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Addon Manager Affects Versions: 2.7.2.Final Reporter: George Gastaldi Fix For: 2.x Future Forge should always attempt to build addons using the current Furnace version. We should pass the {{furnace.version}} as a parameter to the addon build to allow this. Addons should use the <furnace.version> property in the pom.xml to define the forge version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1953) Add command to list JVM system properties

by Mahmoud Ben Hassine (JIRA)

[ https://issues.jboss.org/browse/FORGE-1953?page=com.atlassian.jira.plugin... ] Mahmoud Ben Hassine commented on FORGE-1953: -------------------------------------------- Thank you for your support! I'm glad to contribute to forge :-) > Add command to list JVM system properties > ----------------------------------------- > > Key: FORGE-1953 > URL: https://issues.jboss.org/browse/FORGE-1953 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.7.2.Final > Reporter: Mahmoud Ben Hassine > Assignee: Mahmoud Ben Hassine > Priority: Minor > Fix For: 2.7.3.Final > > > It's always useful to have a list of system properties used to start forge's JVM. This feature request suggests a *_sysprops_* command that list all system properties. What do you think about it? > The command name can be changed. I have already implemented the command, if it is ok for you, i'll send a pull request. > Best regards, > Mahmoud -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1953) Add command to list JVM system properties

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1953?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1953. ---------------------------------- Fix Version/s: 2.7.3.Final Resolution: Done Done, thanks! > Add command to list JVM system properties > ----------------------------------------- > > Key: FORGE-1953 > URL: https://issues.jboss.org/browse/FORGE-1953 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.7.2.Final > Reporter: Mahmoud Ben Hassine > Assignee: Mahmoud Ben Hassine > Priority: Minor > Fix For: 2.7.3.Final > > > It's always useful to have a list of system properties used to start forge's JVM. This feature request suggests a *_sysprops_* command that list all system properties. What do you think about it? > The command name can be changed. I have already implemented the command, if it is ok for you, i'll send a pull request. > Best regards, > Mahmoud -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2014