December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-8849) JPA project revalidation after export to db

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8849?page=com.atlassian.jira.plugin... ] Jeff MAURY reassigned JBIDE-8849: --------------------------------- Assignee: Koen Aers > JPA project revalidation after export to db > ------------------------------------------- > > Key: JBIDE-8849 > URL: https://issues.jboss.org/browse/JBIDE-8849 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate, upstream > Affects Versions: 3.2.1.M1 > Environment: JBDS 4.1.0 m1 H359 > Reporter: Jiri Peterka > Assignee: Koen Aers > Labels: jpa > Fix For: 4.5.0.AM1 > > > 1. Create datasource and open it > 2. Let's have JPA Project referenced datasource from step above > 3. Create entity M with table name Z, you'll get Table "Z" cannot be resolved > 4. Project -> JPA Tools -> Generate Tables from Entities with "Check Export to database" selected > 5. Finish > After doing this project entity is not yet valid > It would be nice, if connection could be refreshed and code revalidated automatically after export to db (it could be also configurable if desired) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8849) JPA project revalidation after export to db

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8849?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-8849: ------------------------------ Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > JPA project revalidation after export to db > ------------------------------------------- > > Key: JBIDE-8849 > URL: https://issues.jboss.org/browse/JBIDE-8849 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate, upstream > Affects Versions: 3.2.1.M1 > Environment: JBDS 4.1.0 m1 H359 > Reporter: Jiri Peterka > Assignee: Koen Aers > Labels: jpa > Fix For: 4.5.0.AM1 > > > 1. Create datasource and open it > 2. Let's have JPA Project referenced datasource from step above > 3. Create entity M with table name Z, you'll get Table "Z" cannot be resolved > 4. Project -> JPA Tools -> Generate Tables from Entities with "Check Export to database" selected > 5. Finish > After doing this project entity is not yet valid > It would be nice, if connection could be refreshed and code revalidated automatically after export to db (it could be also configurable if desired) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6554) Export configuration to orm.xml file

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6554?page=com.atlassian.jira.plugin... ] Jeff MAURY reassigned JBIDE-6554: --------------------------------- Assignee: Koen Aers > Export configuration to orm.xml file > ------------------------------------ > > Key: JBIDE-6554 > URL: https://issues.jboss.org/browse/JBIDE-6554 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.1 > Reporter: Dmitry Geraskov > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.5.0.AM1 > > > Need to create exporter and templates to export orm.xml like hbm files are exported now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6554) Export configuration to orm.xml file

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6554?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-6554: ------------------------------ Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > Export configuration to orm.xml file > ------------------------------------ > > Key: JBIDE-6554 > URL: https://issues.jboss.org/browse/JBIDE-6554 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.1 > Reporter: Dmitry Geraskov > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.5.0.AM1 > > > Need to create exporter and templates to export orm.xml like hbm files are exported now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[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.0.AM1 (was: 4.4.x) > 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.AM1 > > > 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)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21587) Move OpenShift databinding utils to common

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21587?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21587: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.5.x) > Move OpenShift databinding utils to common > ------------------------------------------ > > Key: JBIDE-21587 > URL: https://issues.jboss.org/browse/JBIDE-21587 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common, openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Alexey Kazakov > Fix For: 4.5.0.AM1 > > > We have databinding utils in OpenShift that we want to move to commons/base -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21602) Sonar build for openshift is failing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21602?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21602: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.5.x) > Sonar build for openshift is failing > ------------------------------------ > > Key: JBIDE-21602 > URL: https://issues.jboss.org/browse/JBIDE-21602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Mickael Istria > Fix For: 4.5.0.AM1 > > Attachments: sonar-build-output.txt > > > Sonar for openshift is currently failing in our jenkins at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > I see it complaining in the build about an incompatible bytecode version: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version 51.0 > {code} > The full build output is attached [^sonar-build-output.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23373) Application Wizard: Connection info could be visible on first wizard page

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23373?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23373: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Application Wizard: Connection info could be visible on first wizard page > ------------------------------------------------------------------------- > > Key: JBIDE-23373 > URL: https://issues.jboss.org/browse/JBIDE-23373 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: application_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > > In New OpenShift Application wizard on the first wizard page there is a project combo to choose a project for a new application. We are missing a connection info on this page so user don't see for which connection is an application created. It seems to be obvious, that it is for selected project from OpenShift Explorer (if view is visible = modal dialog is not on top of it at that moment) but in case of several connections with same project, it could cause troubles. > We could have it similar as it is in Deploy Docker Image wizard, where we display connection info. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23136: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.5.0.AM1) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22613: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016