[JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team
by Ondrej Dockal (Jira)
[ https://issues.redhat.com/browse/JBIDE-26893?page=com.atlassian.jira.plug... ]
Ondrej Dockal closed JBIDE-26893.
---------------------------------
> Create universal template and label that would accommodate different rhel needed by interop testing team
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26893
> URL: https://issues.redhat.com/browse/JBIDE-26893
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests, qa
> Affects Versions: 4.13.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: jenkins
> Fix For: 4.14.0.Final
>
>
> We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel7-interop and rhel8-interop), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo.
> Reqs:
> * UMB trigger for interop rhel to run provision job with
> * job will be parametrized based on rhel version given by umb message
> * jenkins provisioning job build description needs to be updated to have available info about rhel version
>
> Pros:
> * do not need to change code via PR every time there is new bits to test
> * probably can be fully automated
> Cons:
> * only one version to test at a time
> * complex and possibly unstable?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-26917) CDK runtime detection does not work for folder with minishift.exe on windows system
by Ondrej Dockal (Jira)
[ https://issues.redhat.com/browse/JBIDE-26917?page=com.atlassian.jira.plug... ]
Ondrej Dockal closed JBIDE-26917.
---------------------------------
Verified on CR Studio: 12.14.0.GA-v20200227-0726-B6011.
> CDK runtime detection does not work for folder with minishift.exe on windows system
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26917
> URL: https://issues.redhat.com/browse/JBIDE-26917
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, runtime-detection
> Affects Versions: 4.13.0.Final
> Environment: Windows 10
> Reporter: Ondrej Dockal
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.14.0.Final
>
>
> Runtime detection does not find CDK server adapter when given folder with minishift.exe binary. It does not happen on linux systems.
> Steps:
> 1. Have studio opened and CDK binary downloaded
> 2. Preferences -> JBossTools -> Jboss Runtime Detection
> 3. Add
> 4. Choose folder with cdk binary -> Open
> 5. ASSERT: Searching for runtimes dialog is shown with offered CDK 3.2+ server adapter
> Acutally: on windows it does not recognize adapter. On linux this works.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-18578) Additional javaee7-samples import issues
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-18578?page=com.atlassian.jira.plug... ]
Zbyněk Červinka commented on JBIDE-18578:
-----------------------------------------
Update - still same issues for the following
Red Hat CodeReady Studio
Version: 12.14.0.GA
Build id: GA-v20200227-0726-B6011
Build date: 20200227-0726
> Additional javaee7-samples import issues
> ----------------------------------------
>
> Key: JBIDE-18578
> URL: https://issues.redhat.com/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
> Priority: Major
> Fix For: 4.15.x
>
> Attachments: The Problems view.png
>
>
> 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.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27032) Update Maven ITests to JavaEE 8/7 components
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27032?page=com.atlassian.jira.plug... ]
Zbyněk Červinka closed JBIDE-27032.
-----------------------------------
Issue has been fixed and tested, I am closing this JIRA.
Red Hat CodeReady Studio version:
Version: 12.14.0.GA
Build id: GA-v20200227-0726-B6011
Build date: 20200227-0726
> Update Maven ITests to JavaEE 8/7 components
> --------------------------------------------
>
> Key: JBIDE-27032
> URL: https://issues.redhat.com/browse/JBIDE-27032
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, maven
> Affects Versions: 4.14.0.AM1
> Reporter: Josef Kopriva
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.14.0.Final
>
>
> Please review all maven ITests and update to use JavaEE 8 components.
> Use https://access.redhat.com/articles/113373 to find correct versions
> You need to go through all tests and review them, if they are using old technology/specification and create new tests to use technology/specification from Java EE7 and 8.
> E.g. all configurators tests and maybe more tests.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27080) Project wizard fails on Windows
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-27080?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-27080:
----------------------------------
Priority: Blocker (was: Major)
> Project wizard fails on Windows
> -------------------------------
>
> Key: JBIDE-27080
> URL: https://issues.redhat.com/browse/JBIDE-27080
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: quarkus
> Affects Versions: 4.14.0.Final
> Reporter: Jeff MAURY
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.15.0.AM1
>
>
> The wizard fails when trying to set up permissions on the tool file and on Windows.
> The stack trace is:
> {code:java}
> java.lang.UnsupportedOperationException
> at java.nio.file.Files.setPosixFilePermissions(Files.java:2044)
> at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.makeExecutable(CodeProjectWizardController.java:149)
> at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.createMavenProject(CodeProjectWizardController.java:136)
> at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.createProject(CodeProjectWizardController.java:88)
> at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.run(CodeProjectWizardController.java:67)
> at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27079) ADT is not correctly installed
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBIDE-27079?page=com.atlassian.jira.plug... ]
Stephane Bouchet commented on JBIDE-27079:
------------------------------------------
[~jkopriva]: I cannot reproduce on a fresh install.
Please note that i also installed android sdk from scratch ( not installed before ) .
The step I did:
- get latest 4.14.0.GA Devstudio
- install ADT from central (ADT 23.0.7.2120684)
- restart
- get an error saying Android SDK not found. opened Preferences > Android: nothing in the path
- installed manually the sdkmanager
- restart devstudio
- still error about Android SDK not found, opened Preferences > Android and set path to sdk manager.
- Android SDK manager opens and ask for downloading Android SDK.
- After Android SDK installation succeed, no errors from devstudio.
It seems the error come from a previously installed Android SDK. Can you verify your Preferences > Android page?
> ADT is not correctly installed
> ------------------------------
>
> Key: JBIDE-27079
> URL: https://issues.redhat.com/browse/JBIDE-27079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.14.0.Final
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Major
> Attachments: image-2020-03-03-07-52-43-757.png
>
>
> Android SDK is not correctly installed, after installation and restart there is error message:
> !image-2020-03-03-07-52-43-757.png|thumbnail!
> When I click on OPenSDK manager, nothing happens.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27080) Project wizard fails on Windows
by Jeff MAURY (Jira)
Jeff MAURY created JBIDE-27080:
----------------------------------
Summary: Project wizard fails on Windows
Key: JBIDE-27080
URL: https://issues.redhat.com/browse/JBIDE-27080
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: quarkus
Affects Versions: 4.14.0.Final
Reporter: Jeff MAURY
Assignee: Koen Aers
Fix For: 4.15.0.AM1
The wizard fails when trying to set up permissions on the tool file and on Windows.
The stack trace is:
{code:java}
java.lang.UnsupportedOperationException
at java.nio.file.Files.setPosixFilePermissions(Files.java:2044)
at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.makeExecutable(CodeProjectWizardController.java:149)
at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.createMavenProject(CodeProjectWizardController.java:136)
at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.createProject(CodeProjectWizardController.java:88)
at org.jboss.tools.quarkus.ui.wizard.CodeProjectWizardController.run(CodeProjectWizardController.java:67)
at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month