September 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-136) Angular scaffolding should use promises when fetching data from multiple resources

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-136?page=com.atlassian.jira.... ] Vineet Reynolds commented on FORGEPLUGINS-136: ---------------------------------------------- This would require using AngularJS 1.2. Resources as Promises was committed to AngularJS master [in this PR|https://github.com/angular/angular.js/pull/2060]. > Angular scaffolding should use promises when fetching data from multiple resources > ---------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-136 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-136 > Project: Forge Plugins > Issue Type: Enhancement > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Certain varieties of AngularJS controllers generated by the scaffold fetch data from multiple ngResources. Since the fetches are performed in an asynchronous manner, some of the values are not available to the controller and the model. This results in the view being in an unstable state for an indeterminate amount of time. > The generated scaffold should use promises to establish a 'barrier' that must be passed before the view is made available for editing to users. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-136) Angular scaffolding should use promises when fetching data from multiple resources

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-136: -------------------------------------------- Summary: Angular scaffolding should use promises when fetching data from multiple resources Key: FORGEPLUGINS-136 URL: https://issues.jboss.org/browse/FORGEPLUGINS-136 Project: Forge Plugins Issue Type: Enhancement Components: AngularJS Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds Certain varieties of AngularJS controllers generated by the scaffold fetch data from multiple ngResources. Since the fetches are performed in an asynchronous manner, some of the values are not available to the controller and the model. This results in the view being in an unstable state for an indeterminate amount of time. The generated scaffold should use promises to establish a 'barrier' that must be passed before the view is made available for editing to users. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1227) Facet classloading problem

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1227?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1227: ----------------------------------- Fix Version/s: 1.x Future > Facet classloading problem > -------------------------- > > Key: FORGE-1227 > URL: https://issues.jboss.org/browse/FORGE-1227 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 1.4.1.Final > Reporter: Lennart Jörelid > Fix For: 1.x Future > > > I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line > > {code:java} > final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class); > {code} > > if you use the "forge install-plugin", compared to if you download the repository 'manually' using Git and execute "forge source-plugin" on the repository. > > In the latter of these cases, the statement above is executed correctly and the plugin works well. In the former of these cases, however, the statement above throws an exception as shown below. I interpret this exception as something indicating that one of the Facets in the statement above is not present ... but since I cannot provoke this state when building the plugin locally (as is typical for debugging), I am at a loss to finding the cause. Is the statement above fundamentally wrong? Or should something be preceeding it to secure that the given Facets are present? > > {code} > java.util.NoSuchElementException > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:184) > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:124) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:64) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:52) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:229) > at org.jboss.forge.maven.facets.MavenContainer.lookup(MavenContainer.java:214) > at org.jboss.forge.maven.facets.MavenContainer.getBuildingRequest(MavenContainer.java:86) > at org.jboss.forge.maven.facets.MavenContainer.getRequest(MavenContainer.java:68) > at org.jboss.forge.maven.facets.MavenContainer$Proxy$_$$_WeldClientProxy.getRequest(MavenContainer$Proxy$_$$_WeldClientProxy.java) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:90) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338) > at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394) > at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172) > at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64) > at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186) > at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178) > at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146) > at se.jguru.nazgul.forge.factory.api.AbstractNewNazgulFrameworkProjectPlugin.makeNazgulStyleProjectStructure(AbstractNewNazgulFrameworkProjectPlugin.java:253) > ... > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1227) Facet classloading problem

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1227?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1227: ----------------------------------- Component/s: Build Tools - Maven > Facet classloading problem > -------------------------- > > Key: FORGE-1227 > URL: https://issues.jboss.org/browse/FORGE-1227 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 1.4.1.Final > Reporter: Lennart Jörelid > > I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line > > {code:java} > final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class); > {code} > > if you use the "forge install-plugin", compared to if you download the repository 'manually' using Git and execute "forge source-plugin" on the repository. > > In the latter of these cases, the statement above is executed correctly and the plugin works well. In the former of these cases, however, the statement above throws an exception as shown below. I interpret this exception as something indicating that one of the Facets in the statement above is not present ... but since I cannot provoke this state when building the plugin locally (as is typical for debugging), I am at a loss to finding the cause. Is the statement above fundamentally wrong? Or should something be preceeding it to secure that the given Facets are present? > > {code} > java.util.NoSuchElementException > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:184) > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:124) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:64) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:52) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:229) > at org.jboss.forge.maven.facets.MavenContainer.lookup(MavenContainer.java:214) > at org.jboss.forge.maven.facets.MavenContainer.getBuildingRequest(MavenContainer.java:86) > at org.jboss.forge.maven.facets.MavenContainer.getRequest(MavenContainer.java:68) > at org.jboss.forge.maven.facets.MavenContainer$Proxy$_$$_WeldClientProxy.getRequest(MavenContainer$Proxy$_$$_WeldClientProxy.java) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:90) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338) > at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394) > at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172) > at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64) > at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186) > at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178) > at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146) > at se.jguru.nazgul.forge.factory.api.AbstractNewNazgulFrameworkProjectPlugin.makeNazgulStyleProjectStructure(AbstractNewNazgulFrameworkProjectPlugin.java:253) > ... > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1226) API to manipulate JavaDoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1226?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1226: ----------------------------------- Summary: API to manipulate JavaDoc (was: api to manipulate javadoc) > API to manipulate JavaDoc > ------------------------- > > Key: FORGE-1226 > URL: https://issues.jboss.org/browse/FORGE-1226 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha12 > Reporter: Michael Schwartz > Priority: Minor > Fix For: 2.x Future > > > I would like to manipulate - namely read, insert and modify javadoc at class-, field- and method-level. > The underlying AST library supports this however forge does not currently. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1227) Facet classloading problem

by Lennart Jörelid (JIRA)

Lennart Jörelid created FORGE-1227: -------------------------------------- Summary: Facet classloading problem Key: FORGE-1227 URL: https://issues.jboss.org/browse/FORGE-1227 Project: Forge Issue Type: Bug Affects Versions: 1.4.1.Final Reporter: Lennart Jörelid I am a bit puzzled about a Forge behaviour I can not seem to understand. There seems to be a difference in the line {code:java} final Project topReactor = projectFactory.createProject(rootDirectory,DependencyFacet.class, MetadataFacet.class, MavenPluginFacet.class); {code} if you use the "forge install-plugin", compared to if you download the repository 'manually' using Git and execute "forge source-plugin" on the repository. In the latter of these cases, the statement above is executed correctly and the plugin works well. In the former of these cases, however, the statement above throws an exception as shown below. I interpret this exception as something indicating that one of the Facets in the statement above is not present ... but since I cannot provoke this state when building the plugin locally (as is typical for debugging), I am at a loss to finding the cause. Is the statement above fundamentally wrong? Or should something be preceeding it to secure that the given Facets are present? {code} java.util.NoSuchElementException at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:184) at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:124) at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:64) at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:52) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:229) at org.jboss.forge.maven.facets.MavenContainer.lookup(MavenContainer.java:214) at org.jboss.forge.maven.facets.MavenContainer.getBuildingRequest(MavenContainer.java:86) at org.jboss.forge.maven.facets.MavenContainer.getRequest(MavenContainer.java:68) at org.jboss.forge.maven.facets.MavenContainer$Proxy$_$$_WeldClientProxy.getRequest(MavenContainer$Proxy$_$$_WeldClientProxy.java) at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:90) at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338) at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394) at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172) at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64) at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153) at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208) at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186) at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178) at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146) at se.jguru.nazgul.forge.factory.api.AbstractNewNazgulFrameworkProjectPlugin.makeNazgulStyleProjectStructure(AbstractNewNazgulFrameworkProjectPlugin.java:253) ... {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1226) api to manipulate javadoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1226?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1226: ---------------------------------------- This is something we wanted for a long time. Wanna take a shot at it? Pull-Requests are more than welcomed ;) > api to manipulate javadoc > ------------------------- > > Key: FORGE-1226 > URL: https://issues.jboss.org/browse/FORGE-1226 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha12 > Reporter: Michael Schwartz > Priority: Minor > Fix For: 2.x Future > > > I would like to manipulate - namely read, insert and modify javadoc at class-, field- and method-level. > The underlying AST library supports this however forge does not currently. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1226) api to manipulate javadoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1226?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1226: ----------------------------------- Component/s: Parsers / File Manipulation (was: Resources API) > api to manipulate javadoc > ------------------------- > > Key: FORGE-1226 > URL: https://issues.jboss.org/browse/FORGE-1226 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha12 > Reporter: Michael Schwartz > Priority: Minor > > I would like to manipulate - namely read, insert and modify javadoc at class-, field- and method-level. > The underlying AST library supports this however forge does not currently. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1226) api to manipulate javadoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1226?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1226: ----------------------------------- Fix Version/s: 2.x Future > api to manipulate javadoc > ------------------------- > > Key: FORGE-1226 > URL: https://issues.jboss.org/browse/FORGE-1226 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha12 > Reporter: Michael Schwartz > Priority: Minor > Fix For: 2.x Future > > > I would like to manipulate - namely read, insert and modify javadoc at class-, field- and method-level. > The underlying AST library supports this however forge does not currently. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1226) api to manipulate javadoc

by Michael Schwartz (JIRA)

Michael Schwartz created FORGE-1226: --------------------------------------- Summary: api to manipulate javadoc Key: FORGE-1226 URL: https://issues.jboss.org/browse/FORGE-1226 Project: Forge Issue Type: Feature Request Components: Resources API Affects Versions: 2.0.0.Alpha12 Reporter: Michael Schwartz Priority: Minor I would like to manipulate - namely read, insert and modify javadoc at class-, field- and method-level. The underlying AST library supports this however forge does not currently. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2013