[JBoss JIRA] (JBIDE-24584) Rename cdk adapter to cdk 2
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24584?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-24584.
---------------------------------
Verified in devstudio:
Version: 11.0.0.AM2
Build id: AM2-v20170713-2124-B489
> Rename cdk adapter to cdk 2
> ---------------------------
>
> Key: JBIDE-24584
> URL: https://issues.jboss.org/browse/JBIDE-24584
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM2
>
>
> I just noticed that in the New Server wizard we have these two adapter types:
> Red Hat Container Development Kit
> Red Hat Container Development Kit 3
> Obviously I know the first one is 2.x, but if I didn't know there's no indication anywhere. So I think it's a good idea to rename it to reflect this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24528) Remove extremely old "server manager" toolbar icons
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24528?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24528.
---------------------------------
I can confirm that the icons are no longer there. Verified in devstudio-11.0.0.AM2-v20170713-2124-B489-installer-standalone.jar
> Remove extremely old "server manager" toolbar icons
> ---------------------------------------------------
>
> Key: JBIDE-24528
> URL: https://issues.jboss.org/browse/JBIDE-24528
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: affects_documentation
> Fix For: 4.5.0.AM2
>
> Attachments: JBIDE-24528.png
>
>
> A set of actions in the toolbar for setting a default server and starting / debugging / etc a server are old, poorly integrated, bypass the official wtp API, and provide limited to no value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4462) DevSuite Installer cache for downloaded files should be in ~/.devsuite/chache
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4462:
-----------------------------------
Summary: DevSuite Installer cache for downloaded files should be in ~/.devsuite/chache
Key: JBDS-4462
URL: https://issues.jboss.org/browse/JBDS-4462
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 11.0.0.AM2
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 11.0.0.GA
Current implementation downloads files in user specific temp folder ~/AppData/Local/Temp and sometimes windows removes those files during installation which causes random installation failures for various components.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-3587) Uninstalling features from central is misleading if the feature is required in JBDS
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3587?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3587:
-----------------------------------
There is nothing left in central that would be a default part of devstudio, so I guess there is no real need to investigate any deeper. [~nickboldt], WDYT?
> Uninstalling features from central is misleading if the feature is required in JBDS
> -----------------------------------------------------------------------------------
>
> Key: JBDS-3587
> URL: https://issues.jboss.org/browse/JBDS-3587
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 9.1.0.Beta2
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 11.0.0.GA
>
>
> Since some features are both in default JBDS installation and in central, you can try uninstalling them from central. The uninstall wizard will show a strange cryptic message saying:
> {noformat}"#the selected feature# cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled".{noformat}
> That basically means nothing gets uninstalled, but it still requires a restart just for good measure.
> The question is - Can it either be more clear that you can't just uninstall those features using central, or just allow it?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24586) Stabilize CDI and EasyImport tests
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24586?page=com.atlassian.jira.plugi... ]
Lukáš Valach updated JBIDE-24586:
---------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM2)
> Stabilize CDI and EasyImport tests
> ----------------------------------
>
> Key: JBIDE-24586
> URL: https://issues.jboss.org/browse/JBIDE-24586
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: install-tests, qa
> Affects Versions: 4.5.0.AM2
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 4.5.0.Final
>
>
> CDI, Deltaspike and Easy import tests are randomly failing on Oxygen (more then on Neon). Need to find out why and fix it.
> Especially on Mac all tests are failing because RedDeer isn't able to fullfill requirements (probably).
--
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 arjan tijms (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18578?page=com.atlassian.jira.plugi... ]
arjan tijms commented on JBIDE-18578:
-------------------------------------
{quote}When I build the project locally I get lots of test failures in this and other modules{quote}
Not all servers run all tests correctly. This is due to at least 2 reasons:
* The server has bugs that prevent the test from running correctly
* The server is not fully supported for all tests
At the moment Payara passes all tests, see:
https://travis-ci.org/javaee-samples/javaee7-samples/builds/242395197
A couple of tests need users with specific groups set up in the server's default proprietary identity store. This is a bit painful to do, but has been done for GlassFish and Soteria. For e.g. WildFly this has not been done, although you can workaround this by adding these users manually.
There's a couple more things like that.
The extras/ folder should probably be moved to a different project altogether.
> 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.0.Final
>
>
> 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