[JBoss JIRA] (FORGE-784) Creating a command named javascript doesn't code complete correctly
by John Ament (JIRA)
John Ament created FORGE-784:
--------------------------------
Summary: Creating a command named javascript doesn't code complete correctly
Key: FORGE-784
URL: https://issues.jboss.org/browse/FORGE-784
Project: Forge
Issue Type: Bug
Components: Shell
Affects Versions: 1.2.0.Final
Reporter: John Ament
Create a plugin "javascript"
Sourced the plugin into my active shell.
did a completion attempt. typed in "jav" and hit tab. It expanded my entry to "java" and prompted me to choose "javascript" or "java" however it immediately completed to "java" and wanted to create a new class.
--
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-783) Create a UICommand resolution strategy
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-783?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III updated FORGE-783:
-------------------------------------
Description: We will need a UICommand resolution strategy for when there are conflicts between UICommand names/etc (possible solutions are to use addon's maven coordinates, the description, etc.) (was: We will need a UICommand resolution strategy for when there are conflicts (addon maven coordinates, the description, etc.))
Component/s: JBoss Tools Integration
Plugin API
Plugin Repository
Shell
> Create a UICommand resolution strategy
> --------------------------------------
>
> Key: FORGE-783
> URL: https://issues.jboss.org/browse/FORGE-783
> Project: Forge
> Issue Type: Task
> Components: JBoss Tools Integration, Plugin API, Plugin Repository, Shell
> Reporter: Koen Aers
> Fix For: 2.0.0.Alpha1
>
>
> We will need a UICommand resolution strategy for when there are conflicts between UICommand names/etc (possible solutions are to use addon's maven coordinates, the description, etc.)
--
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-782) Forge should support multiple repositories
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-782?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-782:
----------------------------------
Fix Version/s: 1.2.1.Final
Affects Version/s: 1.2.0.Final
> Forge should support multiple repositories
> ------------------------------------------
>
> Key: FORGE-782
> URL: https://issues.jboss.org/browse/FORGE-782
> Project: Forge
> Issue Type: Feature Request
> Components: Plugin Repository
> Affects Versions: 1.2.0.Final
> Reporter: John Ament
> Fix For: 1.2.1.Final
>
>
> Forge currently has a DEFAULT_PLUGIN_REPO but no way to have additional plugin repos. It should be possible for companies to have internal repositories for plugins that may not be open source.
> Workaround right now is to copy the yaml file locally and add other proprietary plugins to it.
--
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-782) Forge should support multiple repositories
by John Ament (JIRA)
John Ament created FORGE-782:
--------------------------------
Summary: Forge should support multiple repositories
Key: FORGE-782
URL: https://issues.jboss.org/browse/FORGE-782
Project: Forge
Issue Type: Feature Request
Components: Plugin Repository
Reporter: John Ament
Forge currently has a DEFAULT_PLUGIN_REPO but no way to have additional plugin repos. It should be possible for companies to have internal repositories for plugins that may not be open source.
Workaround right now is to copy the yaml file locally and add other proprietary plugins to it.
--
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