[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 commented on FORGE-734:
------------------------------------------
Not sure I agree this makes sense. Capable is a more confusing term in this case, I think. Target is very explicit about "This thing can be the target of an annotation."
Capable seems more ... loose. What does it do with annotations? It is capable of something with them, but not exactly sure what.
> 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.Alpha1
>
>
> 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
13 years, 3 months
[JBoss JIRA] (FORGE-734) AnnotationTarget should be renamed to AnnotationCapable
by George Gastaldi (JIRA)
George Gastaldi created FORGE-734:
-------------------------------------
Summary: 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.Alpha1
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
13 years, 3 months
[JBoss JIRA] (FORGE-224) Create means for measuring usage via analytics
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-224?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-224:
----------------------------------
Status: Closed (was: Pull Request Sent)
Resolution: Done
> Create means for measuring usage via analytics
> ----------------------------------------------
>
> Key: FORGE-224
> URL: https://issues.jboss.org/browse/FORGE-224
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins, Shell
> Affects Versions: 1.0.6.Final
> Reporter: Rodney Russ
> Assignee: George Gastaldi
> Fix For: 1.2.0.Final
>
>
> JBoss Tools has a mechanism built in to gather statistics on usage. This provides good information on how decisions affect our existing user base as well as how to prioritize platforms to support. Having this capability will help in planning later releases with real data and not guesses.
--
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
13 years, 3 months
[JBoss JIRA] (FORGE-266) Forge Plugins should be decoupled from the Shell Interface, run standalone in JBoss Tools
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-266?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III reassigned FORGE-266:
----------------------------------------
Assignee: Lincoln Baxter III
> Forge Plugins should be decoupled from the Shell Interface, run standalone in JBoss Tools
> -----------------------------------------------------------------------------------------
>
> Key: FORGE-266
> URL: https://issues.jboss.org/browse/FORGE-266
> Project: Forge
> Issue Type: Feature Request
> Components: Brainstorming, JBoss Tools Integration
> Reporter: Lincoln Baxter III
> Assignee: Lincoln Baxter III
> Fix For: 2.0.0.Alpha1
>
>
> (01:41:28 PM) Lincoln: I'd like to start Forge in JBoss Tools, but instead of using the Shell, use the PluginMetadata to build a GUI to run Plugins from the IDE itself.
> (01:41:34 PM) Lincoln: Using windows and input fields, etc.
> (01:41:45 PM) Koen Aers: hm
> (01:42:07 PM) Lincoln: So workflow like this:
> (01:42:46 PM) Lincoln: <CTRL-4> JBT pops up a window like <CTRL-3> where you can type and it will search through the list of commands that are available
> (01:42:48 PM) Lincoln: you can pick one
> (01:42:51 PM) Lincoln: when you do
> (01:43:06 PM) Lincoln: JBT generates a UI for that command, with a list of required and optional fields, based on teh plugin metadata
--
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
13 years, 3 months