[JBoss JIRA] (FORGEPLUGINS-106) AS7 Plugin allows installation of inexistent ZIPs
by George Gastaldi (JIRA)
George Gastaldi created FORGEPLUGINS-106:
--------------------------------------------
Summary: AS7 Plugin allows installation of inexistent ZIPs
Key: FORGEPLUGINS-106
URL: https://issues.jboss.org/browse/FORGEPLUGINS-106
Project: Forge Plugins
Issue Type: Bug
Components: JBoss AS Plugin
Reporter: George Gastaldi
Assignee: James Perkins
Priority: Critical
JBoss AS 7.2.0.Final is not available in the central maven repository nor in the JBoss Nexus.
This option should not appear in the available versions list.
Marking as critical since a lot of people is having this problem.
--
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, 9 months
[JBoss JIRA] (FORGE-822) Proxy settings utility for plugin writers
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-822?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-822:
----------------------------------
Affects Version/s: 1.2.2.Final
(was: 1.2.3.Final)
> Proxy settings utility for plugin writers
> -----------------------------------------
>
> Key: FORGE-822
> URL: https://issues.jboss.org/browse/FORGE-822
> Project: Forge
> Issue Type: Enhancement
> Components: Shell
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> There is a utility class that the built-in plugins may use to read the proxy information from the Forge user configuration. This is the org.jboss.forge.shell.util.ProxySettgins class, which is part of the forge-shell project.
> However, the plugins that are not part of that module do not have access at runtime to this utility class. So if they need information about the HTTP proxy, the plugin writers have to know all the details how these are set in the ~/.forge/config.xml file.
> The solution is to move the ProxySettings class to the same package, but in the forge-shell-api project. The latter can be safely accessed by the plugins.
--
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, 9 months
[JBoss JIRA] (FORGE-822) Proxy settings utility for plugin writers
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-822?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-822.
---------------------------------
Resolution: Done
Merged. Thanks !
> Proxy settings utility for plugin writers
> -----------------------------------------
>
> Key: FORGE-822
> URL: https://issues.jboss.org/browse/FORGE-822
> Project: Forge
> Issue Type: Enhancement
> Components: Shell
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> There is a utility class that the built-in plugins may use to read the proxy information from the Forge user configuration. This is the org.jboss.forge.shell.util.ProxySettgins class, which is part of the forge-shell project.
> However, the plugins that are not part of that module do not have access at runtime to this utility class. So if they need information about the HTTP proxy, the plugin writers have to know all the details how these are set in the ~/.forge/config.xml file.
> The solution is to move the ProxySettings class to the same package, but in the forge-shell-api project. The latter can be safely accessed by the plugins.
--
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, 9 months