[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22810:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Environment: windows
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v3, windows
> Fix For: 4.5.x
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-2625) Provide on-line installer launchable via JNLP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2625?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-2625.
---------------------------------
Resolution: Won't Fix
> Provide on-line installer launchable via JNLP
> ---------------------------------------------
>
> Key: JBDS-2625
> URL: https://issues.jboss.org/browse/JBDS-2625
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 7.0.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
>
> Instead of always downloading offline installer and then run installation manually, would be good to have online version of installer that would let:
> # start installer via JNLP
> # select if EAP/WildFly should be installed too
> (1) Should be easy to implement, because it requires only excluding update site bits from jar, provide URL for update site and create JNLP configuration;
> (2) Requires EAP download integration into IzPack (would be good if IzPack has supported online installation itself)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-18578) Additional javaee7-samples import issues
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18578?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18578:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Additional javaee7-samples import issues
> ----------------------------------------
>
> Key: JBIDE-18578
> URL: https://issues.jboss.org/browse/JBIDE-18578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.CR2
> Environment: JBDS 8.0.0.CR2
> Reporter: Jiri Peterka
> Assignee: Fred Bricon
> Fix For: 4.5.x
>
>
> Additional javaee7-samples import issues
> Clone and import https://github.com/javaee-samples/javaee7-samples as maven projects
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
> There are still some Java Problems, Maven Problems and XML Problems after import, most projects are without errors. Project should be imported without errors
> Java Problems
> {code}
> Description Resource Path Location Type
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 76 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 85 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 35 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 32 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 36 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
> SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
> SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
> The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" Greeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
> The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" SimpleGreeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
> The declared package "org.javaee7.cdi.nobeans.xml" does not match the expected package "test.java.org.javaee7.cdi.nobeans.xml" GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 1 Java Problem
> The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 3 Java Problem
> The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 4 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 12 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 13 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 14 Java Problem
> {code}
> Maven Problems:
> {code}
> Description Resource Path Location Type
> Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen (execution: default, phase: process-classes) pom.xml /jaxws-endpoint line 21 Maven Project Build Lifecycle Mapping Problem
> Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsimport (execution: default, phase: generate-sources) pom.xml /jaxws-client line 21 Maven Project Build Lifecycle Mapping Problem
> {code}
> and xml problems
> {code}
> Description Resource Path Location Type
> cvc-complex-type.2.1: Element 'jboss' must have no character or element information item [children], because the type's content type is empty. enforce-beans.xml /jax-rs-angularjs/src/test/resources line 4 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 25 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 25 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 28 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jaxrs-endpoint/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-embedded line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-remote line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-jbosseap-remote line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /send-receive/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /standalone/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /transactional/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /user-transaction/src/test/resources line 3 XML Problem
> cvc-pattern-valid: Value 'param1 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
> cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
> cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
> cvc-pattern-valid: Value 'param2 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
> cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
> cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
> {code}
> Additional issues:
> https://issues.jboss.org/browse/JBIDE-18352
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4412) DevSuite 1.4 Installer Make progress/status clearer/easier to see
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4412?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4412:
--------------------------------
Labels: ui (was: )
> DevSuite 1.4 Installer Make progress/status clearer/easier to see
> -----------------------------------------------------------------
>
> Key: JBDS-4412
> URL: https://issues.jboss.org/browse/JBDS-4412
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Priority: Minor
> Labels: ui
>
> The overall installation progress for DevSuite 1.4 is difficult to see. You've got to scroll back and forth through the boxes to look for the small text that indicates what's going on.
> Suggestions:
> # There should be an overall progress at the top
> # There should be some indication it is still working
> # the status text in the boxes is the same color and size as the version number and other comment text making it difficult to pick out. It's easy to miss that there is status text and that it is being updated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4412) DevSuite 1.4 Installer Make progress/status clearer/easier to see
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4412?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4412:
-----------------------------------
Assignee: Denis Golovin
> DevSuite 1.4 Installer Make progress/status clearer/easier to see
> -----------------------------------------------------------------
>
> Key: JBDS-4412
> URL: https://issues.jboss.org/browse/JBDS-4412
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Labels: ui
>
> The overall installation progress for DevSuite 1.4 is difficult to see. You've got to scroll back and forth through the boxes to look for the small text that indicates what's going on.
> Suggestions:
> # There should be an overall progress at the top
> # There should be some indication it is still working
> # the status text in the boxes is the same color and size as the version number and other comment text making it difficult to pick out. It's easy to miss that there is status text and that it is being updated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4410) DevSuite 1.4 Installer indicate download size during choice selection
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4410?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4410:
--------------------------------
Component/s: platform-installer
(was: installer)
> DevSuite 1.4 Installer indicate download size during choice selection
> ---------------------------------------------------------------------
>
> Key: JBDS-4410
> URL: https://issues.jboss.org/browse/JBDS-4410
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 11.0.0.AM2
>
>
> During the software selection phase the DevSuite 1.4 installer should indicate the approximate size of the download. The download size is shown during actual installation progress, but by that time it's too late.
> The two use cases I see for this:
> # A minishift/CDK user that is looking to try OpenShift might not want to download and install all of JBoss. Seeing the size of it ahead of time, would avoid some shock later.
> # When trying to decide between enabling Hyper-V or installing VirtualBox, knowing the size might influence the user to just enable Hyper-V.
> Note: I think I filed a bug against a previous version that the installer provides No estimate of the required disk space in order to proceed. Doesn't look like it is still open.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-22713) IOException in CentralHelper.extractIfNeeded
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22713?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22713:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> IOException in CentralHelper.extractIfNeeded
> --------------------------------------------
>
> Key: JBIDE-22713
> URL: https://issues.jboss.org/browse/JBIDE-22713
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to open C:\eclipse\plugins\org.jboss.tools.central_2.0.1.Final-v20160401-1059-B103\resources\jbosstools-central-webpage.zip
> {noformat}
> java.io.IOException: D:\OneDrive\TreinaWeb\Java Básico\JSE\.metadata\.plugins\org.jboss.tools.central\central\bc8a80b\index.html can not be found
> at org.jboss.tools.central.internal.CentralHelper.extractIfNeeded(CentralHelper.java:203)
> at org.jboss.tools.central.internal.CentralHelper.getCentralPageUrl(CentralHelper.java:122)
> at org.jboss.tools.central.internal.CentralHelper.getCentralUrl(CentralHelper.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5.run(GettingStartedHtmlPage.java:252)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.1.0.qualifier |
> Operating Systems:
> | Linux | 3.2.0 | 4.5.7.fc23 |
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 5.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571659e0e4b055563f...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months