March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23885) integration test: assert new element "Kind" and in all properties and changed structure in "Build" properties

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23885?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23885: ---------------------------------- Assignee: Pavol Srna > integration test: assert new element "Kind" and in all properties and changed structure in "Build" properties > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23885 > URL: https://issues.jboss.org/browse/JBIDE-23885 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Pavol Srna > Fix For: 4.5.0.AM1 > > > JBIDE-23841: In "Properties" we added a "Kind" property for all resources and changed the structure of the "Build" properties. > The integration tests should assert these changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23893) [cdk] follow up on changes to cdk3 for marker file

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23893?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23893: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > [cdk] follow up on changes to cdk3 for marker file > -------------------------------------------------- > > Key: JBIDE-23893 > URL: https://issues.jboss.org/browse/JBIDE-23893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.3.Final > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.4.4.AM2 > > > cdk v3 added marker files with credentials and version information. We need to make use of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23896) Allow user to choose hypervisor in editor and new server wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23896?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23896: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Allow user to choose hypervisor in editor and new server wizard > --------------------------------------------------------------- > > Key: JBIDE-23896 > URL: https://issues.jboss.org/browse/JBIDE-23896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.3.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.4.AM2 > > Attachments: cdk3tp.png > > > Users do not like going to customize cmd args unless absolutely necessary. The most common usecases should be doable from the server editor or the creation wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23893) [cdk] follow up on changes to cdk3 for marker file

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23893?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23893: --------------------------------------- Regarding runtime detection - all I can think of right now is that it would find the minishift binary within a folder. I agree that it may not provide much value, but it's not much different to cdk 2, no? For example you would need to open the server editor and set up the credentials after creating the server adapter. > [cdk] follow up on changes to cdk3 for marker file > -------------------------------------------------- > > Key: JBIDE-23893 > URL: https://issues.jboss.org/browse/JBIDE-23893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.3.Final > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.4.4.AM1 > > > cdk v3 added marker files with credentials and version information. We need to make use of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23893) [cdk] follow up on changes to cdk3 for marker file

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23893?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23893: --------------------------------------- [~rob.stryker], ok, that's fine, so can you please explain how it works today? The JIRA description doesn't have much detail. You mean when you create a cdk 3 runtime, you locate the binary somewhere and it will then load the marker file inside ~/.minishift/ ? Maybe best if you can follow steps to verify it works as expected? > [cdk] follow up on changes to cdk3 for marker file > -------------------------------------------------- > > Key: JBIDE-23893 > URL: https://issues.jboss.org/browse/JBIDE-23893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.3.Final > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.4.4.AM1 > > > cdk v3 added marker files with credentials and version information. We need to make use of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23924: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Fix For: 4.4.4.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23893) [cdk] follow up on changes to cdk3 for marker file

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23893?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23893: ------------------------------------- The 'marker file' works, but the runtime detection does not... You can still create the cdk server manually and it will find the marker file. We need to discuss whether runtime detection makes sense for cdk3 / minishift at all, and how it can work. I'd say that's a missing feature and needs its own jira. This issue, however, is that we're pulling the correct data from the marker file when creating the openshift and docker connections. > [cdk] follow up on changes to cdk3 for marker file > -------------------------------------------------- > > Key: JBIDE-23893 > URL: https://issues.jboss.org/browse/JBIDE-23893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.3.Final > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.4.4.AM1 > > > cdk v3 added marker files with credentials and version information. We need to make use of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24006) Wildfly server adapter does not report error and works inconsistently

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24006?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-24006: ----------------------------------- Assignee: Rob Stryker > Wildfly server adapter does not report error and works inconsistently > --------------------------------------------------------------------- > > Key: JBIDE-24006 > URL: https://issues.jboss.org/browse/JBIDE-24006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: server, server_adapter, wildfly > Fix For: 4.4.4.AM2 > > > If Wildfly uses 9999 as the management port, then no error is reported but the adapter does not work. > Here is an except we've got from the customer: > {noformat} > I have an important update on this. I think it's mostly good news. > I debugged the issue via a virtual session with the person that develops the WildFly plugin for NetBeans. What we found out is that the management port I was using, 9999, conflicts with Netty. For context, I had to specify a port override since 9990 commonly conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and 9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything basically breaks without a real error message indicating the underlying issue. Using 9990 on the other hand clearly indicated a port conflict. > I tried the same thing on Eclipse with exactly the same results. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24024) Server adapter editor, wizard: better tell me what the settings are for

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24024?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24024: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Server adapter editor, wizard: better tell me what the settings are for > ----------------------------------------------------------------------- > > Key: JBIDE-24024 > URL: https://issues.jboss.org/browse/JBIDE-24024 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Fix For: 4.5.0.Final > > Attachments: image-2017-03-03-11-43-41-941.png, image-2017-03-03-11-44-46-410.png > > > A server adapter will publish local files to a pod in OpenShift (via rsync). Our wizard and server adapter editors allows to set the adapter to fullfill this task. The wizard and the editor do a poor job explaining the purpose of those settings though: > The wizard generically states that it does "file synchronization" but fails to tell "from" where to "where" > !image-2017-03-03-11-43-41-941.png! > The editor is even poorer in usability. It wont say anything about file synchronization and even mixes settings for the source and destination: > !image-2017-03-03-11-44-46-410.png! > "Source Path" should be right below the "Eclipse Project" since it's providing further details for it. "Pod Deployment Path" should be right below "Resource" (år "Service" in older verisions of this editor" since it provides the path on pods that are identified by "Resource". > Ideally we'd also add labels "From" and "To" (or similar means to better identify the settings) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24023) Server adapter editor: I have no indication of what project the selected service is located in

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24023?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24023: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Server adapter editor: I have no indication of what project the selected service is located in > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-24023 > URL: https://issues.jboss.org/browse/JBIDE-24023 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Fix For: 4.5.0.Final > > Attachments: image-2017-03-03-10-45-25-851.png > > > steps to reproduce: > # ASSERT: have 2 nodejs (or eap- or any other) application running in 2 different projects, where you used the same template for both of them. Ex. "nodejs-example" in project "myPOC" and "nodejs-example" in project "myProject". > # EXEC: create a server adapter for 1 of them > # EXEC: open up the server adapter editor and look into "Service:" > Result: > You have no idea what service this adapter is publishing to, the one in "myPOC" or the one in "myProject"? > !image-2017-03-03-10-45-25-851.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2017