[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24896?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24896:
------------------------------------
Failing tests:
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
* https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cannot start any JBoss server
> -----------------------------
>
> Key: JBIDE-24896
> URL: https://issues.jboss.org/browse/JBIDE-24896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.1.AM2
>
>
> When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE:
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> {code}
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1.
> This is with devstudio 11.1.0.AM1 B873.
> As indicated by Rob, this is likely caused by this commit from JBIDE-24758:
> https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24896?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24896:
-------------------------------
Fix Version/s: 4.5.1.AM2
(was: 4.5.1.AM1)
> Cannot start any JBoss server
> -----------------------------
>
> Key: JBIDE-24896
> URL: https://issues.jboss.org/browse/JBIDE-24896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.1.AM2
>
>
> When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE:
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> {code}
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1.
> This is with devstudio 11.1.0.AM1 B873.
> As indicated by Rob, this is likely caused by this commit from JBIDE-24758:
> https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24896?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24896:
------------------------------------
Decision on retrospective call today: this prevents AM1 release, so we will NOT release AM1.
> Cannot start any JBoss server
> -----------------------------
>
> Key: JBIDE-24896
> URL: https://issues.jboss.org/browse/JBIDE-24896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.1.AM1
>
>
> When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE:
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> {code}
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1.
> This is with devstudio 11.1.0.AM1 B873.
> As indicated by Rob, this is likely caused by this commit from JBIDE-24758:
> https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24439) Block PRs for merge untill the Jenkins build is successful (protected branches)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24439?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24439:
------------------------------------
Once again, it was decided that protected branches are not (yet) a good idea, because:
* for urgent changes we need a workaround (eg. Andre being owner of openshift repo, so doesn't have to wait for PR review)
* owners might not have the discipline to wait for PR reviews
* PR reviews may not be effective since we have a small team and limited shared SME knowledge (eg., Rob is the only SME for server adapters, so others doing review isn't so useful)
Instead, we've decided to push on having the integration tests run more frequently to catch regressions like [1] faster.
[1] https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927...
> Block PRs for merge untill the Jenkins build is successful (protected branches)
> -------------------------------------------------------------------------------
>
> Key: JBIDE-24439
> URL: https://issues.jboss.org/browse/JBIDE-24439
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: LATER
>
>
> As discussed in this thread [1], we'd like to implement *Protected Branches* and
> *Required Status Checks* [2] for some jbosstools-* projects.
> [1] http://lists.jboss.org/pipermail/jbosstools-dev/2017-May/011948.html
> [2] https://help.github.com/articles/defining-the-mergeability-of-pull-requests/
> We will therefore need to document some requirements in jbosstools-devdoc about how to properly submit PRs when version-bumping is required:
> {quote}Make sure if your PR requires a version bump that the PR includes TWO commits. One for the change, and one for the version bump. That way the pair of commits can be built in the PR build and verify it works, AND when cherry picking the commit across branches, you can pick only the change and not the version-bump commit too.
> {quote}
> And we need to decide if we want to do what Fuse Tools does and require that PRs be reviewed before they can be merged, if we're ready to have that additional overhead on every PR.
> [~jeffmaury] as project lead can you state which project(s) you'd like to see changed in github, and which ones should be changed as such:
> * jbosstools-_____
> ** Protected Branch = master
> ** Required Status Check(s) = ....? (which checks do we want)
> ** PR reviews required = [true/false]
> From that list of projects / requirements, we can then create subtask JIRAs to track the workj & the changes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24802 at 8/28/17 8:05 AM:
-------------------------------------------------------------------
The PR was merged by mistake, it still has issues.
As agreed with Rob, I'll PR to his PR so that [~rob.stryker] sees how to get things done via databinding (no way around it here, manual changes to the error state would get overriden by the databinding)
was (Author: adietish):
As agreed with Rob, I'll PR to his PR so that [~rob.stryker] sees how to get things done via databinding (no way around it here, manual changes to the error state would get overriden by the databinding)
> Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24802
> URL: https://issues.jboss.org/browse/JBIDE-24802
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM2
>
> Attachments: Spectacle.F10835.png
>
>
> On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive.
> !Spectacle.F10835.png!
> And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24896?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-24896:
-------------------------------
Fix Version/s: 4.5.1.AM1
> Cannot start any JBoss server
> -----------------------------
>
> Key: JBIDE-24896
> URL: https://issues.jboss.org/browse/JBIDE-24896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.1.AM1
>
>
> When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE:
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> {code}
> {code}
> An internal error occurred during: "Starting WildFly 10.1".
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1.
> This is with devstudio 11.1.0.AM1 B873.
> As indicated by Rob, this is likely caused by this commit from JBIDE-24758:
> https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24573) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24573?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24573:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.5.1.AM1)
> Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24573
> URL: https://issues.jboss.org/browse/JBIDE-24573
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server, upstream
> Affects Versions: 4.4.4.Final
> Environment: windows 7 eclipse neon maven
> Reporter: stefano canu
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: pfi-test.zip, pom.xml
>
>
> I 'm tryng to deploy to wildfly 10 an ear project (maven) composed by one war and one jar (ejb) project, but the ear deployed with eclipse wildfly connector is different form one present in the target foleder, library in web-inf lib is missing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24781) Propose to create OpenShift server adapters automatically when creating application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24781?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24781:
-------------------------------------
Fix Version/s: 4.5.1.AM2
(was: 4.5.1.AM1)
> Propose to create OpenShift server adapters automatically when creating application
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-24781
> URL: https://issues.jboss.org/browse/JBIDE-24781
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.1.AM2
>
>
> I'm trying to push an Eclipse project as an OpenShift application with Red Hat Developer Studio. When I create the application, the wizard asks me for an Eclipse project. I would expect that a server adapter would be created by default for this project, or that at least creating a server adapter would be proposed automatically (but remain cancellable).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24802:
-------------------------------------
Fix Version/s: 4.5.1.AM2
(was: 4.5.1.AM1)
> Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24802
> URL: https://issues.jboss.org/browse/JBIDE-24802
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM2
>
> Attachments: Spectacle.F10835.png
>
>
> On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive.
> !Spectacle.F10835.png!
> And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months