[JBoss JIRA] (JBIDE-25588) CDK server adapter timeouts during starting with JDK9
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25588?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25588:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> CDK server adapter timeouts during starting with JDK9
> -----------------------------------------------------
>
> Key: JBIDE-25588
> URL: https://issues.jboss.org/browse/JBIDE-25588
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.2.Final
> Environment: Fedora 26
> java-9-openjdk-9.0.1.11-4.fc26.x86_64
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.6.x
>
>
> CDK server adapter remains in state starting after CDK is started properly (in console you can see all steps passed without problem), one can connect to openshift via browser. Also, SSL untrusted certificate was accepted. There is running job: Starting Container Developer Environment 3.2+ Preparing launch delegate...: Launching delegate...
> Adapter will just timeout eventually.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25109:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Server adapter editor: provide ability to only change debug port (and not the debug port key)
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25109
> URL: https://issues.jboss.org/browse/JBIDE-25109
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.6.x
>
>
> Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19590:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.6.x
>
> Attachments: hibernate-psf-import.mp4, oomph-installer-hibernate-codebase.png
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23280) NullPointerException in ProtocolDependenciesService.getDependencies
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23280?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23280:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NullPointerException in ProtocolDependenciesService.getDependencies
> -------------------------------------------------------------------
>
> Key: JBIDE-23280
> URL: https://issues.jboss.org/browse/JBIDE-23280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.2.AM1
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.arquillian.editor.internal.services.ProtocolDependenciesService.getDependencies(ProtocolDependenciesService.java:101)
> at org.jboss.tools.arquillian.editor.internal.actions.AddDependenciesActionContributor$1.run(AddDependenciesActionContributor.java:49)
> at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDialog$1.linkActivated(PropertyEditorAssistDialog.java:146)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.activateLink(SapphireFormText.java:1583)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.handleMouseClick(SapphireFormText.java:1374)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.access$16(SapphireFormText.java:1345)
> at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText$6.mouseUp(SapphireFormText.java:445)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:221)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.sapphire.ui | 9.0.5.201605181639 | 9.0.5.201605181639 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57e9320ae4b02e6262...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25142) Stabilization of integration tests for OpenShift
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25142?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25142:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Stabilization of integration tests for OpenShift
> ------------------------------------------------
>
> Key: JBIDE-25142
> URL: https://issues.jboss.org/browse/JBIDE-25142
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: integration-tests, openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Labels: integration_tests, openshift_v3
> Fix For: 4.6.x
>
>
> Generally speaking there are 2 general rules of thumb that we need to aim for when fixing the tests:
> * We should have integration tests that are *larger usecases*: integration tests are time consuming to run, especially when compared to unit tests. It's therefore preferable to have *a few large* integration tests than many small integration tests
> * Integration tests should be *runnable individually*: the existing code base is requiring to run the tests in a specific sequence (ex. test Y is expecting an OpenShift resource - that test X creates - to exist). That's a major burden: one would have to run the whole lengthy suite to just create a new test for a new feature that was implemented
> * During stabilization try to reuse projects/apps/resources as much as it is possible to reduce time for building applications, so this needs to rewrite classes
> This jira tries to fix the remaining ITests for OpenShift (that are currently not included in stable suite) while aiming at the goals above:
> {code:java}
> // General
> OCBinaryLocationTest.class,
> // Connection
> CreateNewConnectionTest.class,
> StoreConnectionTest.class,
>
> // Project
> LinkToCreateNewProjectTest.class,
> // Application wizard handling
> OpenNewApplicationWizardTest.class,
> OpenNewApplicationWizardWithNoProjectTest.class,
> BuilderImageApplicationWizardHandlingTest.class,
>
> // Creation of a new application
> CreateApplicationFromTemplateTest.class,
> CreateApplicationOnBuilderImageTest.class,
> DeploymentTest.class,
>
> // Application handling
> DeleteResourceTest.class,
> OSExplorerResourceTest.class,
> TriggerBuildTest.class,
> ImportApplicationTest.class,
> PortForwardingTest.class,
> LogsTest.class,
> EditResourcesTest.class,
> HandleCustomTemplateTest.class,
> ImportApplicationWizardTest.class,
> // Advanced application testing
> DeployDockerImageTest.class,
> CreateResourcesTest.class,
> ScalingTest.class,
> //Server adapter
> ServerAdapterWizardHandlingTest.class,
> CreateServerAdapterTest.class,
> ServerAdapterFromResourceTest.class,
> PublishChangesTest.class,
> DebuggingEAPAppTest.class,
> {code}
> Test should be stable on all major platforms: Win, Linux and MacOS.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months