May 2013 - forge-issues - Jboss List Archives

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-535?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-535: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.Alpha5 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-510) Create automated routine for checking plugin version compliance of plugins in Central Plugin Index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-510?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-510: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Create automated routine for checking plugin version compliance of plugins in Central Plugin Index > -------------------------------------------------------------------------------------------------- > > Key: FORGE-510 > URL: https://issues.jboss.org/browse/FORGE-510 > Project: Forge > Issue Type: Task > Components: Plugin Repository > Affects Versions: 1.0.6.Final > Reporter: Ivan St. Ivanov > Fix For: 2.0.0.Alpha5 > > > Create a routine, executed by the build server, that checks a predefined set of Forge plugins for version consistency with Forge core. In order to satisfy this check, for each major version of the core there should be at least one plugin branch or tag that specifies the same major version. If the check fails, the plugin author should receive an email asking them to fix the inconcistency. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-440: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > A pom.xml which contains comments loses all of them after Forge operates on it. > ------------------------------------------------------------------------------- > > Key: FORGE-440 > URL: https://issues.jboss.org/browse/FORGE-440 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.0.6.Final > Environment: HEAD > Reporter: Pete Muir > Fix For: 2.0.0.Alpha5 > > > Also looses formatting, but this is less of an 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-479) Implement @CommandScoped to enable Plugin - Facet communication

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-479?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-479: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Implement @CommandScoped to enable Plugin - Facet communication > --------------------------------------------------------------- > > Key: FORGE-479 > URL: https://issues.jboss.org/browse/FORGE-479 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.CR2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha5 > > > (05:04:44 PM) Lincoln: i want to implement @CommandScoped > (05:04:46 PM) Lincoln: that would be nice > (05:04:49 PM) Lincoln: and not hard to do actually > (05:05:00 PM) Lincoln: actually, is that there? > (05:05:13 PM) Paul Bakker: no > (05:05:17 PM) Paul Bakker: but good idea > (05:05:54 PM) Lincoln: easy to tie into the command execution lifecycle > (05:06:01 PM) Lincoln: would be nice to add extension points there as well > (05:06:04 PM) Lincoln: could be helpful for plugins > (05:06:09 PM) Lincoln: before/after command > (05:06:47 PM) Paul Bakker: yes should really do this, very helpful I think for plugin/facet communication > (05:07:03 PM) Lincoln: yeah that could be a recommended pattern actually > (05:07:11 PM) Lincoln: if it works well > (05:07:21 PM) Paul Bakker: yep -- 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, 10 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-734?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-734: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.Alpha5 > > > 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

12 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 George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-689?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-689: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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: UI - Shell > Affects Versions: 1.1.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha5 > > > 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

12 years, 10 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-707?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-707: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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 > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha5 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-598) CommandCompleter should permit the highlight of some candidate items (for use then as recommended candidate)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-598?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-598: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > CommandCompleter should permit the highlight of some candidate items (for use then as recommended candidate) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-598 > URL: https://issues.jboss.org/browse/FORGE-598 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell, Usability > Affects Versions: 1.0.5.Final > Reporter: Rafael Benevides > Labels: commandcompleter, shell, > Fix For: 2.0.0.Alpha5 > > > For example: > {code} > someplugin --option <TAB> > **CANDIDATE3** (show in WHITE and as first item) CANDIDATE1 CANDIDATE2 > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-657) Missing mime-mapping in web.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-657?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-657: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > Missing mime-mapping in web.xml > ------------------------------- > > Key: FORGE-657 > URL: https://issues.jboss.org/browse/FORGE-657 > Project: Forge > Issue Type: Bug > Components: Java EE APIs > Reporter: George Gastaldi > Labels: starter > Fix For: 2.0.0.Alpha5 > > > To eliminate the annoying log jboss server log: > {code} > 23:59:54,914 AVVERTENZA [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-1) JSF1091: No mime type could be found for file favicon.ico. To resolve this, add a mime-type mapping to the applications web.xml > {code} > you should add on web.xml: > {code:xml} > <mime-mapping> > <extension>ico</extension> > <mime-type>image/x-icon</mime-type> > </mime-mapping> > {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, 10 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-688?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-688: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 (was: 2.0.0.Alpha4) > 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.Alpha5 > > > 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2013