March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1699) High CPU consumption on Windows and Linux

by Esteve Aviles (JIRA)

[ https://issues.jboss.org/browse/FORGE-1699?page=com.atlassian.jira.plugin... ] Esteve Aviles updated FORGE-1699: --------------------------------- Attachment: image.jpg Screenshot > High CPU consumption on Windows and Linux > ----------------------------------------- > > Key: FORGE-1699 > URL: https://issues.jboss.org/browse/FORGE-1699 > Project: Forge > Issue Type: Quality Risk > Components: UI - Shell > Affects Versions: 2.3.0.Final > Environment: Windows 7 32 bits 4 GB RAM > Linux Fedora 19 64bits 4 GB RAM > Reporter: Esteve Aviles > Attachments: image.jpg > > > CPU usage is very high when executing a command in Forge Shell. > I attach an image of CPU consumption. > Tried both Windows (at work) and Linux with the same result. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1699) High CPU consumption on Windows and Linux

by Esteve Aviles (JIRA)

Esteve Aviles created FORGE-1699: ------------------------------------ Summary: High CPU consumption on Windows and Linux Key: FORGE-1699 URL: https://issues.jboss.org/browse/FORGE-1699 Project: Forge Issue Type: Quality Risk Components: UI - Shell Affects Versions: 2.3.0.Final Environment: Windows 7 32 bits 4 GB RAM Linux Fedora 19 64bits 4 GB RAM Reporter: Esteve Aviles CPU usage is very high when executing a command in Forge Shell. I attach an image of CPU consumption. Tried both Windows (at work) and Linux with the same result. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1698) MavenJavaCompilerFacet should use user properties instead of declaring the compiler plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1698?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1698. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.3.1.Final (was: 2.x Future) Resolution: Done > MavenJavaCompilerFacet should use user properties instead of declaring the compiler plugin > ------------------------------------------------------------------------------------------ > > Key: FORGE-1698 > URL: https://issues.jboss.org/browse/FORGE-1698 > Project: Forge > Issue Type: Enhancement > Components: Build Tools - Maven > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Labels: Starter > Fix For: 2.3.1.Final > > > The current {{org.jboss.forge.addon.maven.projects.facets.MavenJavaCompilerFacet}} declares a compiler plugin with the parameters: > {code} > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.7</source> > <target>1.7</target> > <encoding>UTF-8</encoding> > </configuration> > </plugin> > {code} > As per http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html, this could be changed to: > {code} > <properties> > <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> > <maven.compiler.source>1.7</maven.compiler.source> > <maven.compiler.target>1.7</maven.compiler.target> > </properties> > {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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1698) MavenJavaCompilerFacet should use user properties instead of declaring the compiler plugin

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1698: -------------------------------------- Summary: MavenJavaCompilerFacet should use user properties instead of declaring the compiler plugin Key: FORGE-1698 URL: https://issues.jboss.org/browse/FORGE-1698 Project: Forge Issue Type: Enhancement Components: Build Tools - Maven Affects Versions: 2.3.0.Final Reporter: George Gastaldi Priority: Minor Fix For: 2.x Future The current {{org.jboss.forge.addon.maven.projects.facets.MavenJavaCompilerFacet}} declares a compiler plugin with the parameters: {code} <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>3.1</version> <configuration> <source>1.7</source> <target>1.7</target> <encoding>UTF-8</encoding> </configuration> </plugin> {code} As per http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html, this could be changed to: {code} <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <maven.compiler.source>1.7</maven.compiler.source> <maven.compiler.target>1.7</maven.compiler.target> </properties> {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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1674) Forge should add EJB 3.1 dependency

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1674?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1674. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.3.1.Final Resolution: Done > Forge should add EJB 3.1 dependency > ----------------------------------- > > Key: FORGE-1674 > URL: https://issues.jboss.org/browse/FORGE-1674 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.2.0.Final > Reporter: Ivan St. Ivanov > Assignee: George Gastaldi > Priority: Critical > Labels: Starter > Fix For: 2.3.1.Final > > Attachments: testcase.txt > > > When I install the EJB facet in a Java EE project and I choose version 3.1 of the EJB spec, Forge adds the following managed dependency: > javax.ejb:ejb-api:jar::3.0-alpha-1 > This is EJB 3.0, however, so I cannot have things like Singleton EJBs in my project. Adding this dependency would fix the issue: > org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar::1.0.1.Final > I have attached a [failing] test case. Just add it to org.jboss.forge.addon.javaee.ejb.EJBFacetTest and you can simulate the issue. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1684) Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1684?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1684. ---------------------------------- > Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API > ---------------------------------------------------------------------- > > Key: FORGE-1684 > URL: https://issues.jboss.org/browse/FORGE-1684 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.2.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.3.1.Final > > > The MetawidgetInspectorFacade was introduced in the Forge 1 scaffold-x API for use by other scaffolding providers that could use Metawidget only for inspecting classes and producing inspection results that could be enhanced and later using in templating. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1685) Move the utility classes from the scaffold-api project to a scaffold-spi project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1685?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1685. ---------------------------------- > Move the utility classes from the scaffold-api project to a scaffold-spi project > -------------------------------------------------------------------------------- > > Key: FORGE-1685 > URL: https://issues.jboss.org/browse/FORGE-1685 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 2.2.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.3.1.Final > > > Scaffold providers should not depend on the scaffold-api for accessing utility classes. The scaffold-spi project should house these classes so that they could be used in scaffold providers through a simple compile-time dependency. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1684) Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1684?page=com.atlassian.jira.plugin... ] Vineet Reynolds resolved FORGE-1684. ------------------------------------ Fix Version/s: 2.3.1.Final Resolution: Done Merged: https://github.com/forge/core/commit/a851adf63a070c7187380f2454a8fa51b89a... > Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API > ---------------------------------------------------------------------- > > Key: FORGE-1684 > URL: https://issues.jboss.org/browse/FORGE-1684 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.2.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.3.1.Final > > > The MetawidgetInspectorFacade was introduced in the Forge 1 scaffold-x API for use by other scaffolding providers that could use Metawidget only for inspecting classes and producing inspection results that could be enhanced and later using in templating. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1685) Move the utility classes from the scaffold-api project to a scaffold-spi project

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1685?page=com.atlassian.jira.plugin... ] Vineet Reynolds resolved FORGE-1685. ------------------------------------ Fix Version/s: 2.3.1.Final Resolution: Done Merged: https://github.com/forge/core/commit/f39b3e266e0b4ecd1d9cedd9d734a7dc161b... > Move the utility classes from the scaffold-api project to a scaffold-spi project > -------------------------------------------------------------------------------- > > Key: FORGE-1685 > URL: https://issues.jboss.org/browse/FORGE-1685 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 2.2.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.3.1.Final > > > Scaffold providers should not depend on the scaffold-api for accessing utility classes. The scaffold-spi project should house these classes so that they could be used in scaffold providers through a simple compile-time dependency. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1697) Add Highlighter for YAML

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1697?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1697: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.3.1.Final (was: 2.x Future) Resolution: Done > Add Highlighter for YAML > ------------------------ > > Key: FORGE-1697 > URL: https://issues.jboss.org/browse/FORGE-1697 > Project: Forge > Issue Type: Feature Request > Components: Text > Affects Versions: 2.3.0.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.3.1.Final > > -- 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

12 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014