February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1552) Update homebrew to 1.4.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1552?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1552: -------------------------------------- Assignee: George Gastaldi > Update homebrew to 1.4.4.Final > ------------------------------ > > Key: FORGE-1552 > URL: https://issues.jboss.org/browse/FORGE-1552 > Project: Forge > Issue Type: Task > Reporter: George Gastaldi > Assignee: George Gastaldi > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1552) Update homebrew to 1.4.4.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1552: -------------------------------------- Summary: Update homebrew to 1.4.4.Final Key: FORGE-1552 URL: https://issues.jboss.org/browse/FORGE-1552 Project: Forge Issue Type: Task Reporter: George Gastaldi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1551) After executing faces-setup command, facesFacet isn't available on project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1551?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1551: ----------------------------------- Fix Version/s: 2.x Future > After executing faces-setup command, facesFacet isn't available on project > -------------------------------------------------------------------------- > > Key: FORGE-1551 > URL: https://issues.jboss.org/browse/FORGE-1551 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Affects Versions: 2.0.0.Final > Environment: Windows 7, JDK 1.7 > Reporter: Rudy De Busscher > Fix For: 2.x Future > > > Create an addon with following execute method > @Override > public Result execute(UIExecutionContext context) throws Exception { > Project project = getSelectedProject(context.getUIContext()); > Iterator<ProjectFacet> facets = project.getFacets().iterator(); > while (facets.hasNext()) { > System.out.println(facets.next()); > } > return Results.success("Testing addons."); > } > install the addon in Forge 2 (suppose it has the new command test-command) > when execute following commands in forge 2 > project-new --named demo --type war > faces-setup --facesVersion 2.2 > test-command > The facesFacet is not in the list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1551) After executing faces-setup command, facesFacet isn't available on project

by Rudy De Busscher (JIRA)

[ https://issues.jboss.org/browse/FORGE-1551?page=com.atlassian.jira.plugin... ] Rudy De Busscher commented on FORGE-1551: ----------------------------------------- using projectFactory.invalidateCaches() doesn't help. (suggestion of George in the forum) > After executing faces-setup command, facesFacet isn't available on project > -------------------------------------------------------------------------- > > Key: FORGE-1551 > URL: https://issues.jboss.org/browse/FORGE-1551 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Affects Versions: 2.0.0.Final > Environment: Windows 7, JDK 1.7 > Reporter: Rudy De Busscher > > Create an addon with following execute method > @Override > public Result execute(UIExecutionContext context) throws Exception { > Project project = getSelectedProject(context.getUIContext()); > Iterator<ProjectFacet> facets = project.getFacets().iterator(); > while (facets.hasNext()) { > System.out.println(facets.next()); > } > return Results.success("Testing addons."); > } > install the addon in Forge 2 (suppose it has the new command test-command) > when execute following commands in forge 2 > project-new --named demo --type war > faces-setup --facesVersion 2.2 > test-command > The facesFacet is not in the list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1551) After executing faces-setup command, facesFacet isn't available on project

by Rudy De Busscher (JIRA)

Rudy De Busscher created FORGE-1551: --------------------------------------- Summary: After executing faces-setup command, facesFacet isn't available on project Key: FORGE-1551 URL: https://issues.jboss.org/browse/FORGE-1551 Project: Forge Issue Type: Feature Request Components: Java EE APIs Affects Versions: 2.0.0.Final Environment: Windows 7, JDK 1.7 Reporter: Rudy De Busscher Create an addon with following execute method @Override public Result execute(UIExecutionContext context) throws Exception { Project project = getSelectedProject(context.getUIContext()); Iterator<ProjectFacet> facets = project.getFacets().iterator(); while (facets.hasNext()) { System.out.println(facets.next()); } return Results.success("Testing addons."); } install the addon in Forge 2 (suppose it has the new command test-command) when execute following commands in forge 2 project-new --named demo --type war faces-setup --facesVersion 2.2 test-command The facesFacet is not in the list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1548) Updated the Forge 2.0 plugin and now JBDS won't start

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/FORGE-1548?page=com.atlassian.jira.plugin... ] Koen Aers reassigned FORGE-1548: -------------------------------- Assignee: Koen Aers > Updated the Forge 2.0 plugin and now JBDS won't start > ----------------------------------------------------- > > Key: FORGE-1548 > URL: https://issues.jboss.org/browse/FORGE-1548 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.CR2, 2.0.0.Final > Environment: JBDS 7.1 Macbook Pro Maverick OS. > Reporter: Robb Greathouse > Assignee: Koen Aers > > After checking for updates on JBDS I approved the update of the Forge 2 plugin. > JBDS asked to to be restarted. Upon restarting it gave a progress window announcing Forge 2 starting. After 10 minutes it had not started. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1550) Set up a CI build server that is publicly visible and works.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1550?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1550: ----------------------------------- Priority: Critical (was: Major) > Set up a CI build server that is publicly visible and works. > ------------------------------------------------------------ > > Key: FORGE-1550 > URL: https://issues.jboss.org/browse/FORGE-1550 > Project: Forge > Issue Type: Task > Reporter: Lincoln Baxter III > Priority: Critical > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1550) Set up a CI build server that is publicly visible and works.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1550?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1550: ---------------------------------------- Some options include: - Cloudbees: http://www.cloudbees.com/ - Dedicated Jenkins instance (Eg: http://ci.hibernate.org/) > Set up a CI build server that is publicly visible and works. > ------------------------------------------------------------ > > Key: FORGE-1550 > URL: https://issues.jboss.org/browse/FORGE-1550 > Project: Forge > Issue Type: Task > Reporter: Lincoln Baxter III > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1550) Set up a CI build server that is publicly visible and works.

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1550: ----------------------------------------- Summary: Set up a CI build server that is publicly visible and works. Key: FORGE-1550 URL: https://issues.jboss.org/browse/FORGE-1550 Project: Forge Issue Type: Task Reporter: Lincoln Baxter III -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-997) "beans new-bean" command should better validate user input of restricted Java keywords

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-997?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-997: ---------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > "beans new-bean" command should better validate user input of restricted Java keywords > -------------------------------------------------------------------------------------- > > Key: FORGE-997 > URL: https://issues.jboss.org/browse/FORGE-997 > Project: Forge > Issue Type: Bug > Affects Versions: 1.3.2.Final > Environment: Eclipse Kepler + Jboss tools 4 > Reporter: Hubert Schumacher > Priority: Minor > Fix For: 2.x Future > > > forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014