[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21678?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21678:
----------------------------------------
Assignee: Viacheslav Kabanovich
> New Connection wizard: Getting started info is not visible by default
> ----------------------------------------------------------------------
>
> Key: JBIDE-21678
> URL: https://issues.jboss.org/browse/JBIDE-21678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: default_new_conn.png, rendered_new_conn.png
>
>
> In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection).
> See screenshot of fresh opened New Connection wizard:
> !default_new_conn.png!
> and after checkbox is (un)checked or server type is changed:
> !rendered_new_conn.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21696) New Connection wizard: Getting started info is not visible by default
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21696:
----------------------------------------
Summary: New Connection wizard: Getting started info is not visible by default
Key: JBIDE-21696
URL: https://issues.jboss.org/browse/JBIDE-21696
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Viacheslav Kabanovich
Fix For: 4.3.1.CR1
In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection).
See screenshot of fresh opened New Connection wizard:
!default_new_conn.png!
and after checkbox is (un)checked or server type is changed:
!rendered_new_conn.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21696) New Connection wizard: Getting started info is not visible by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21696:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> New Connection wizard: Getting started info is not visible by default
> ----------------------------------------------------------------------
>
> Key: JBIDE-21696
> URL: https://issues.jboss.org/browse/JBIDE-21696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: default_new_conn.png, rendered_new_conn.png
>
>
> In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection).
> See screenshot of fresh opened New Connection wizard:
> !default_new_conn.png!
> and after checkbox is (un)checked or server type is changed:
> !rendered_new_conn.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21696) New Connection wizard: Getting started info is not visible by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21696:
------------------------------------------
merged into master
> New Connection wizard: Getting started info is not visible by default
> ----------------------------------------------------------------------
>
> Key: JBIDE-21696
> URL: https://issues.jboss.org/browse/JBIDE-21696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: default_new_conn.png, rendered_new_conn.png
>
>
> In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection).
> See screenshot of fresh opened New Connection wizard:
> !default_new_conn.png!
> and after checkbox is (un)checked or server type is changed:
> !rendered_new_conn.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21100:
---------------------------------------
[~rob.stryker], I cannot replicate this in JBDS 9.1.0.Beta2 with WildFly 8.2.0. I just added the server using runtime detection and then started.
[~zhangxunan], is this issue still present? If so, could you provide exact steps to reproduce? What version of Eclipse, what version of JBoss Tools installed - or just the server adapter? How did you add the server? What settings did you use?
> start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21100
> URL: https://issues.jboss.org/browse/JBIDE-21100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)
> Reporter: carl zhang
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> please refer to
> https://developer.jboss.org/thread/265726?start=0&tstart=0
> refer to the picture of 28-Oct-2015 9:46 AM (layer 3)
> In the left panel: WildFly 8.x is configured to connect to localhost
> WildFly 8.x(1) is configured to connect to remote host (Linux)
> The localhost cannot finish start process. WildFly 8.x(1) (remote) can.
> What ports, or temp files, or anything else are checked when changing from starting to started state?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21695) 25 xml validation errors in
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-21695:
-----------------------------------
Summary: 25 xml validation errors in
Key: JBIDE-21695
URL: https://issues.jboss.org/browse/JBIDE-21695
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server, upstream
Reporter: Rob Stryker
25 xml validation errors on the git@github.com:jboss-developer/jboss-eap-quickstarts.git quickstart repository.
Description Resource Path Location Type
cvc-complex-type.2.4.a: Invalid content was found starting with element 'jee:interceptor-binding'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. jboss-ejb3.xml /jboss-ejb-security-interceptors/src/main/resources/META-INF line 31 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'aop:aspectj-autoproxy'. tools-config.xml /jboss-spring-petclinic/src/main/resources/spring line 40 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'context:component-scan'. mvc-core-config.xml /jboss-spring-petclinic/src/main/resources/spring line 39 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jdbc:embedded-database'. test-context.xml /jboss-spring-kitchensink-matrixvariables/src/test/resources line 40 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jee:jndi-lookup'. infrastructure.xml /jboss-spring-kitchensink-asyncrequestmapping/src/main/resources/META-INF/spring line 28 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jee:jndi-lookup'. infrastructure.xml /jboss-spring-kitchensink-matrixvariables/src/main/resources/META-INF/spring line 28 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jee:jndi-lookup'. infrastructure.xml /jboss-spring-kitchensink-springmvctest/src/main/resources/META-INF/spring line 28 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'mvc:annotation-driven'. jboss-as-spring-mvc-context.xml /jboss-spring-kitchensink-controlleradvice/src/main/webapp/WEB-INF line 28 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'mvc:annotation-driven'. test-context.xml /jboss-spring-kitchensink-springmvctest/src/test/resources line 48 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'tx:jta-transaction-manager'. infrastructure.xml /jboss-spring-kitchensink-asyncrequestmapping/src/main/resources/META-INF/spring line 36 XML Problem
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'tx:jta-transaction-manager'. infrastructure.xml /jboss-spring-kitchensink-matrixvariables/src/main/resources/META-INF/spring line 36 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-bean-validation/src/test/resources line 20 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-cdi-veto/src/test/resources line 20 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-kitchensink-jsp/src/test/resources line 21 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-kitchensink-ml-ear-ejb/src/test/resources line 21 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-shrinkwrap-resolver/src/test/resources line 21 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-spring-kitchensink-asyncrequestmapping/functional-tests/src/test/resources line 19 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-spring-kitchensink-basic/functional-tests/src/test/resources line 19 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-spring-kitchensink-matrixvariables/functional-tests/src/test/resources line 19 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-wsat-simple/src/test/resources line 21 XML Problem
cvc-elt.1: Cannot find the declaration of element 'beans'. business-config.xml /jboss-spring-petclinic/src/main/resources/spring line 27 XML Problem
cvc-elt.1: Cannot find the declaration of element 'datasources'. greeter-spring-quickstart-ds.xml /jboss-spring-greeter/src/main/webapp/WEB-INF line 23 XML Problem
Referenced file contains errors (http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_...). For more information, right click on the message in the Problems View and select "Show Details..." context-handlers.xml /jboss-wsat-simple/src/main/webapp/WEB-INF/classes line 1 XML Problem
Referenced file contains errors (jar:file:/home/rob/apps/eclipse/jbds/studio/plugins/org.jboss.tools.as.catalog_3.1.1.Beta2-v20160121-0132-B81.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-ejb-multi-server-app-one-ejb/src/main/resources/META-INF line 1 XML Problem
Referenced file contains errors (jar:file:/home/rob/apps/eclipse/jbds/studio/plugins/org.jboss.tools.as.catalog_3.1.1.Beta2-v20160121-0132-B81.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21662:
--------------------------------
Priority: Minor (was: Critical)
> Server adapter: workspace project is not automatically published if there was no initial publish
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21662
> URL: https://issues.jboss.org/browse/JBIDE-21662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Minor
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21662:
-------------------------------------
With workarounds being perform a publish manually, this does not seem critical at all.
> Server adapter: workspace project is not automatically published if there was no initial publish
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21662
> URL: https://issues.jboss.org/browse/JBIDE-21662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21684) jaxws quickstarts require nonexistant endorsed folder
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21684?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21684:
-------------------------------------
[~rafabene] [~fbricon] Any clue on these two issues?
Clone repo: http://github.com/wildfly/quickstart
Branch: 10.x
I'm not sure if this is an error with the quickstart or with maven's handling of it.
> jaxws quickstarts require nonexistant endorsed folder
> -----------------------------------------------------
>
> Key: JBIDE-21684
> URL: https://issues.jboss.org/browse/JBIDE-21684
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server, upstream
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> The jaxws quickstarts in the 10.x branch have the following errors:
> Endorsed directory '/home/rob/code/github/jboss_stuff/quickstart/jaxws-ejb/service/target/endorsed' is missing. You may need to a perform a
> Maven command line build in order to create it.
> Even after building from the command line, the requested folders are not created. This indicates that either there is something wrong with the build (ie it should be creating the endorsed folder) or this is a legacy detail that is no longer needed (ie the project does not actually require an endorsed directory, so the pom lines requesting it are unnecessary)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21684) jaxws quickstarts require nonexistant endorsed folder
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21684?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21684:
--------------------------------
Fix Version/s: 4.3.1.CR1
4.4.0.Alpha1
(was: 4.3.x)
> jaxws quickstarts require nonexistant endorsed folder
> -----------------------------------------------------
>
> Key: JBIDE-21684
> URL: https://issues.jboss.org/browse/JBIDE-21684
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server, upstream
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> The jaxws quickstarts in the 10.x branch have the following errors:
> Endorsed directory '/home/rob/code/github/jboss_stuff/quickstart/jaxws-ejb/service/target/endorsed' is missing. You may need to a perform a
> Maven command line build in order to create it.
> Even after building from the command line, the requested folders are not created. This indicates that either there is something wrong with the build (ie it should be creating the endorsed folder) or this is a legacy detail that is no longer needed (ie the project does not actually require an endorsed directory, so the pom lines requesting it are unnecessary)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month