February 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-682) ShellPrompt has fixed set of PromptTypes, should be extensible

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-682?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-682: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > ShellPrompt has fixed set of PromptTypes, should be extensible > -------------------------------------------------------------- > > Key: FORGE-682 > URL: https://issues.jboss.org/browse/FORGE-682 > Project: Forge > Issue Type: Enhancement > Components: Shell > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > Fix For: 2.0.0.Alpha2 > > > If a plugin wants to prompt the user to supply some settings it'll use: > {code:title=ShellPrompt} > String promptCommon(String message, PromptType type); > {code} > PromptType is what the prompt would use to validate the user input against. Unfortunately PromptType is an enum so there's no way for a plugin to provide it's own prompt type. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-535) Support gradle as a build tool

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-535?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-535: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Support gradle as a build tool > ------------------------------ > > Key: FORGE-535 > URL: https://issues.jboss.org/browse/FORGE-535 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > Much like the current Maven support. It would be nice if Forge could be used to manipulate Gradle projects. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-379) Add user profiles

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-379?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-379: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Add user profiles > ----------------- > > Key: FORGE-379 > URL: https://issues.jboss.org/browse/FORGE-379 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 1.0.0.Beta3 > Reporter: Pete Muir > Fix For: 2.0.0.Alpha2 > > > At the moment Forge assumes that every user needs the same level of hand-holding. This means that advanced users are shortchanged (as they want more control) and newbies can get lost. Introducing a number of user profiles (e.g. newbie, intermediate, god) could help here. For example, if in newbie mode, the faces plugin wouldn't ask if you wanted to change from jar -> war packaging, assuming that the person does... -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-736) Properties file Resource Addon - Potential implementation / backing library

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-736?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-736: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Properties file Resource Addon - Potential implementation / backing library > --------------------------------------------------------------------------- > > Key: FORGE-736 > URL: https://issues.jboss.org/browse/FORGE-736 > Project: Forge > Issue Type: Story > Components: Resources API > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > This "OWNER" library looks like something that might make a nice foundation for a properties file F2 addon. > Doesn't look like its in central or any reliable repo, though. But if its good enough, we could help that along. > http://lviggiano.github.com/owner/ -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-770: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version > ------------------------------------------------------------------------------------------- > > Key: FORGE-770 > URL: https://issues.jboss.org/browse/FORGE-770 > Project: Forge > Issue Type: Story > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.) > {code} > (A) -> (B, v1) > -> Service 1 > (B, v2) > -> Service 1v2 > -> Service 2v1 > {code} > A should receive only the instance of Service 1 from (B, v1) -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-734) AnnotationTarget should be renamed to AnnotationCapable

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-734?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-734: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > AnnotationTarget should be renamed to AnnotationCapable > ------------------------------------------------------- > > Key: FORGE-734 > URL: https://issues.jboss.org/browse/FORGE-734 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.0.0.Alpha2 > > > In order to keep the API consistent, I propose that the interface > {code}org.jboss.forge.parser.java.AnnotationTarget{code} > should be renamed to > {code}org.jboss.forge.parser.java.AnnotationCapable{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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-707) Forge 2 should support non-CDI addons / service registration via ServiceLoader

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-707?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-707: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Forge 2 should support non-CDI addons / service registration via ServiceLoader > ------------------------------------------------------------------------------ > > Key: FORGE-707 > URL: https://issues.jboss.org/browse/FORGE-707 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-757) Forge tests should delete the created folders

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-757?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-757: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Forge tests should delete the created folders > --------------------------------------------- > > Key: FORGE-757 > URL: https://issues.jboss.org/browse/FORGE-757 > Project: Forge > Issue Type: Bug > Components: Test Harness > Affects Versions: 1.2.0.Final > Reporter: George Gastaldi > Fix For: 1.2.2.Final, 2.0.0.Alpha2 > > > After running tests, Forge isn't removing the created temp folders inside the /tmp folder. That leads to insufficient disk space after some time if these files are not deleted. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-688) Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-688?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-688: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet > ----------------------------------------------------------------------- > > Key: FORGE-688 > URL: https://issues.jboss.org/browse/FORGE-688 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Affects Versions: 1.1.0.Final > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.0.0.Alpha2 > > > It would be nice if we have a JavaEE6Facet, which installs the jboss bom. > Even though the BaseJavaEEFacet abstract class already does that, this behavior would not be possible if a custom Facet is created extending a specific subclass of BaseFacet and requiring the JavaEE6. > The more elegant solution would be to add: > {code:java} > @RequiresFacet(JavaEE6Facet.class) > {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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-689) Shell should report "People who used this command also used the following commands: X Y Z"

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-689?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-689: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Shell should report "People who used this command also used the following commands: X Y Z" > ------------------------------------------------------------------------------------------ > > Key: FORGE-689 > URL: https://issues.jboss.org/browse/FORGE-689 > Project: Forge > Issue Type: Feature Request > Components: Shell > Affects Versions: 1.1.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > This should probably not be tied to the shell, but use analytics tracking data to report on which commands generally follow which and expose an API that can be used to implement this feature in the shell, IDE, or any UI. -- 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

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013