[JBoss JIRA] (JBIDE-17218) [compilation]fix openshift build
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17218?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-17218 at 4/30/14 4:51 AM:
-------------------------------------------------------------------
[~rob.stryker] You deprecated org.jboss.ide.eclipse.as.ui.UIUtil but no indication what's replacing it? Compilation fails in OpenShift because the method overload that's used in the OpenShift Server Editor was removed.
was (Author: adietish):
[~rob.stryker] You deprecated org.jboss.ide.eclipse.as.ui.UIUtil but no indication what's replacing it?
> [compilation]fix openshift build
> --------------------------------
>
> Key: JBIDE-17218
> URL: https://issues.jboss.org/browse/JBIDE-17218
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Denis Golovin
> Priority: Blocker
>
> openshif buiild is broken right now
> {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.tools.openshift.express.ui: Compilation failure: Compilation failure:
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[53]
> [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyButtonCommand;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyButtonCommand cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[54]
> [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyComboCommand;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyComboCommand cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[55]
> [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyCommand;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyCommand cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[221]
> [ERROR] browseDestButton.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, null, 0, 100, 0));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[223]
> [ERROR] deployFolderText.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, 0, 0, browseDestButton, -5));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[240]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetProjectCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[247]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetOverrideCommand(server));
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetOverrideCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[254]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetRemoteCommand(server));
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetRemoteCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[260]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetDeployFolderCommand(server));
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetDeployFolderCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[303]
> [ERROR] public class SetRemoteCommand extends ServerWorkingCopyPropertyCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[311]
> [ERROR] public class SetProjectCommand extends ServerWorkingCopyPropertyComboCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyComboCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[318]
> [ERROR] protected void postOp(int type) {
> [ERROR] ^^^^^^^^^^^^^^^^
> [ERROR] The method postOp(int) of type OpenShiftServerEditorSection.SetProjectCommand must override or implement a supertype method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[323]
> [ERROR] public class SetDeployFolderCommand extends ServerWorkingCopyPropertyCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[331]
> [ERROR] public class SetOverrideCommand extends ServerWorkingCopyPropertyButtonCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyButtonCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[339]
> [ERROR] protected void postOp(int type) {
> [ERROR] ^^^^^^^^^^^^^^^^
> [ERROR] The method postOp(int) of type OpenShiftServerEditorSection.SetOverrideCommand must override or implement a supertype method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerWizardComposite.java:[273]
> [ERROR] browseDeployFolderButton.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, null, 0, 100, 0));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerWizardComposite.java:[277]
> [ERROR] deployFolderText.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, 0, 0, browseDeployFolderButton, -5));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] 17 problems (17 errors)
> {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, 11 months
[JBoss JIRA] (JBIDE-17218) [compilation]fix openshift build
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17218?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-17218:
------------------------------------------
[~rob.stryker] You deprecated org.jboss.ide.eclipse.as.ui.UIUtil but no indication what's replacing it?
> [compilation]fix openshift build
> --------------------------------
>
> Key: JBIDE-17218
> URL: https://issues.jboss.org/browse/JBIDE-17218
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Denis Golovin
> Priority: Blocker
>
> openshif buiild is broken right now
> {code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.tools.openshift.express.ui: Compilation failure: Compilation failure:
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[53]
> [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyButtonCommand;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyButtonCommand cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[54]
> [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyComboCommand;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyComboCommand cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[55]
> [ERROR] import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyCommand;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.jboss.ide.eclipse.as.ui.editor.ServerWorkingCopyPropertyCommand cannot be resolved
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[221]
> [ERROR] browseDestButton.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, null, 0, 100, 0));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[223]
> [ERROR] deployFolderText.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, 0, 0, browseDestButton, -5));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[240]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetProjectCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[247]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetOverrideCommand(server));
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetOverrideCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[254]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetRemoteCommand(server));
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetRemoteCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[260]
> [ERROR] ((ServerEditorPartInput) input).getServerCommandManager().execute(new SetDeployFolderCommand(server));
> [ERROR] ^^^^^^^
> [ERROR] The method execute(IUndoableOperation) in the type ServerResourceCommandManager is not applicable for the arguments (OpenShiftServerEditorSection.SetDeployFolderCommand)
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[303]
> [ERROR] public class SetRemoteCommand extends ServerWorkingCopyPropertyCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[311]
> [ERROR] public class SetProjectCommand extends ServerWorkingCopyPropertyComboCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyComboCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[318]
> [ERROR] protected void postOp(int type) {
> [ERROR] ^^^^^^^^^^^^^^^^
> [ERROR] The method postOp(int) of type OpenShiftServerEditorSection.SetProjectCommand must override or implement a supertype method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[323]
> [ERROR] public class SetDeployFolderCommand extends ServerWorkingCopyPropertyCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[331]
> [ERROR] public class SetOverrideCommand extends ServerWorkingCopyPropertyButtonCommand {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] ServerWorkingCopyPropertyButtonCommand cannot be resolved to a type
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerEditorSection.java:[339]
> [ERROR] protected void postOp(int type) {
> [ERROR] ^^^^^^^^^^^^^^^^
> [ERROR] The method postOp(int) of type OpenShiftServerEditorSection.SetOverrideCommand must override or implement a supertype method
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerWizardComposite.java:[273]
> [ERROR] browseDeployFolderButton.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, null, 0, 100, 0));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-openshift/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/behaviour/OpenShiftServerWizardComposite.java:[277]
> [ERROR] deployFolderText.setLayoutData(UIUtil.createFormData2(0, 5, 100, -5, 0, 0, browseDeployFolderButton, -5));
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] Access restriction: The method createFormData2(Object, int, Object, int, Object, int, Object, int) from the type FormDataUtility is not accessible due to restriction on classpath entry /home/eskimo/Projects/jbdevstudio/4.2.x/fork/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.wtp.ui/target/classes
> [ERROR] 17 problems (17 errors)
> {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, 11 months
[JBoss JIRA] (JBIDE-16596) OpenShift Server Adapter Editor: Timeouts and publishing fields are too small
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16596:
-------------------------------------
Original Estimate: 2 hours
Remaining Estimate: 2 hours
> OpenShift Server Adapter Editor: Timeouts and publishing fields are too small
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16596
> URL: https://issues.jboss.org/browse/JBIDE-16596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.2.0.Beta2
>
> Attachments: small_field.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
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, 11 months
[JBoss JIRA] (JBIDE-16596) OpenShift Server Adapter Editor: Timeouts and publishing fields are too small
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16596:
-------------------------------------
Summary: OpenShift Server Adapter Editor: Timeouts and publishing fields are too small (was: OpenShift Server Adapter: Timeouts and publishing fields are too small)
> OpenShift Server Adapter Editor: Timeouts and publishing fields are too small
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16596
> URL: https://issues.jboss.org/browse/JBIDE-16596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
> Attachments: small_field.png
>
>
> In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
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, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-492:
------------------------------------------
Ideas for the new shiny landing page? how about something along the lines of the Features index page [4], where each plug-in has it's own linked icon which goes off the the docs info.
How will the docs info be presented? how about something along the lines of the N&N [5], so an expanding panel on one side with the various docs versions and once expanded then the content for each plug-in is presented.
[4] http://tools.jboss.org/features/index.html
[5] http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta1.html
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
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, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-492:
------------------------------------------
I think there is some confusion here so I would like to clarify. For a moment forget that the enterprise docs exist. *This is about the community docs only.*
We have a great modern clean new tools.jboss.org website [1] but the link on [2] for reference docs goes off to an old looking docs landing page [3]. It is this docs landing page that I want to revamp and bring into the modern era. If this means moving to asciidoc for community docs then let's do that - but only if I get a nice new shiny landing page to go with it :)
[1] http://tools.jboss.org/
[2] http://tools.jboss.org/documentation/
[3] http://docs.jboss.org/tools/
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
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, 11 months
[JBoss JIRA] (JBIDE-17206) Forge 2 plugin fails to startup due to missing files in org.jboss.tools.forge2.runtime plugin
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17206?page=com.atlassian.jira.plugi... ]
George Gastaldi updated JBIDE-17206:
------------------------------------
Description:
I installed Eclipse Luna and installed the Forge 2 JBT Plugin from http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_mast...
When pressing Ctrl+4, the Forge 2 popup fails with an error. By analyzing the logs, I noticed that the addon-repository inside directory org.jboss.tools.forge2.runtime_2.0.1.Beta2-v20140427-0750-B598 is missing the forge-addon JARs.
By building locally, the JARs are properly kept, so I suppose it's some build-related issue. This issue must be fixed ASAP, otherwise Forge 2 is useless inside Eclipse
was:
I installed Eclipse Luna and installed the Forge 2 JBT Plugin from http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_mast...
When pressing Ctrl+5, the Forge 2 popup fails with an error. By analyzing the logs, I noticed that the addon-repository inside directory org.jboss.tools.forge2.runtime_2.0.1.Beta2-v20140427-0750-B598 is missing the forge-addon JARs.
By building locally, the JARs are properly kept, so I suppose it's some build-related issue. This issue must be fixed ASAP, otherwise Forge 2 is useless inside Eclipse
> Forge 2 plugin fails to startup due to missing files in org.jboss.tools.forge2.runtime plugin
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-17206
> URL: https://issues.jboss.org/browse/JBIDE-17206
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Environment: Eclipse Luna 4.4.M6
> Reporter: George Gastaldi
> Priority: Blocker
> Attachments: screenshot.png
>
>
> I installed Eclipse Luna and installed the Forge 2 JBT Plugin from http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_mast...
> When pressing Ctrl+4, the Forge 2 popup fails with an error. By analyzing the logs, I noticed that the addon-repository inside directory org.jboss.tools.forge2.runtime_2.0.1.Beta2-v20140427-0750-B598 is missing the forge-addon JARs.
> By building locally, the JARs are properly kept, so I suppose it's some build-related issue. This issue must be fixed ASAP, otherwise Forge 2 is useless inside Eclipse
--
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, 11 months