February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21745: ------------------------------------- [~rhopp] Are you using your jboss.org credentials, redhat access credentials, or developer.redhat.com credentials? And what is your actual username being used? Feel free to mark the response private. > Unable to download EAP 7 Beta runtime using username without "@redhat.com" > -------------------------------------------------------------------------- > > Key: JBIDE-21745 > URL: https://issues.jboss.org/browse/JBIDE-21745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final, 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > > Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. > Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: > {noformat} > You Entered All Necessary Information > Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. > {noformat} > But even after that I'm unable to download that runtime with the same credentials. > Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20541) wildfly-jts-application-component-2 quickstart fails to validate

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20541?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20541: ------------------------------------- [~sgilda] No, i didn't make one. > wildfly-jts-application-component-2 quickstart fails to validate > ----------------------------------------------------------------- > > Key: JBIDE-20541 > URL: https://issues.jboss.org/browse/JBIDE-20541 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly > Fix For: 4.3.0.Final > > > See https://issues.jboss.org/browse/WFLY-5250 for followup. > The above quickstart fails to validate in eclipse. It has the following lines in it: > {code} > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:iiop="urn:iiop" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd > http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd > urn:iiop jboss-ejb-iiop_1_0.xsd" > version="3.1" > impl-version="2.0"> > <assembly-descriptor> > <iiop:iiop> > <ejb-name>InvoiceManagerEJBImpl</ejb-name> > <iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name> > </iiop:iiop> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > The key line to note is: > {code} > urn:iiop jboss-ejb-iiop_1_0.xsd" > {code} > Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with: > {code} > urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd" > {code} > However, even once that is fixed, the quickstart still has other problems. For one example: > {code} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http:// > java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method- > permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/ > javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http:// > java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application- > exception}' is expected. > {code} > I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21746) Too much info shown in log when deploying a docker image to OpenShift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21746?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21746: ---------------------------------- Labels: openshift_v3 (was: ) > Too much info shown in log when deploying a docker image to OpenShift > --------------------------------------------------------------------- > > Key: JBIDE-21746 > URL: https://issues.jboss.org/browse/JBIDE-21746 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3 > > When deploying a docker image to OpenShift 3 server, there is too much logging in eclipse .log (in error log with severity info). For every created resource there is a message "Trying to create resource:" followed up by json of a resource. So for a deployed docker image it creates such info message for a new image stream, service, routing (if was checked) and deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21746) Too much info shown in log when deploying a docker image to OpenShift

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21746: ------------------------------------- Summary: Too much info shown in log when deploying a docker image to OpenShift Key: JBIDE-21746 URL: https://issues.jboss.org/browse/JBIDE-21746 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Priority: Minor When deploying a docker image to OpenShift 3 server, there is too much logging in eclipse .log (in error log with severity info). For every created resource there is a message "Trying to create resource:" followed up by json of a resource. So for a deployed docker image it creates such info message for a new image stream, service, routing (if was checked) and deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20541) wildfly-jts-application-component-2 quickstart fails to validate

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20541?page=com.atlassian.jira.plugi... ] Sande Gilda commented on JBIDE-20541: ------------------------------------- [~rhopp] : Was a JBoss EAP quickstart JIRA created for this issue? > wildfly-jts-application-component-2 quickstart fails to validate > ----------------------------------------------------------------- > > Key: JBIDE-20541 > URL: https://issues.jboss.org/browse/JBIDE-20541 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly > Fix For: 4.3.0.Final > > > See https://issues.jboss.org/browse/WFLY-5250 for followup. > The above quickstart fails to validate in eclipse. It has the following lines in it: > {code} > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:iiop="urn:iiop" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd > http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd > urn:iiop jboss-ejb-iiop_1_0.xsd" > version="3.1" > impl-version="2.0"> > <assembly-descriptor> > <iiop:iiop> > <ejb-name>InvoiceManagerEJBImpl</ejb-name> > <iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name> > </iiop:iiop> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > The key line to note is: > {code} > urn:iiop jboss-ejb-iiop_1_0.xsd" > {code} > Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with: > {code} > urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd" > {code} > However, even once that is fixed, the quickstart still has other problems. For one example: > {code} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http:// > java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method- > permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/ > javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http:// > java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application- > exception}' is expected. > {code} > I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ] Radim Hopp reassigned JBIDE-21745: ---------------------------------- Assignee: Rob Stryker > Unable to download EAP 7 Beta runtime using username without "@redhat.com" > -------------------------------------------------------------------------- > > Key: JBIDE-21745 > URL: https://issues.jboss.org/browse/JBIDE-21745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final, 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Rob Stryker > > Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. > Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: > {noformat} > You Entered All Necessary Information > Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. > {noformat} > But even after that I'm unable to download that runtime with the same credentials. > Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-21745: ------------------------------- Priority: Critical (was: Major) > Unable to download EAP 7 Beta runtime using username without "@redhat.com" > -------------------------------------------------------------------------- > > Key: JBIDE-21745 > URL: https://issues.jboss.org/browse/JBIDE-21745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final, 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > > Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. > Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: > {noformat} > You Entered All Necessary Information > Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. > {noformat} > But even after that I'm unable to download that runtime with the same credentials. > Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-21745: ---------------------------------- Summary: Unable to download EAP 7 Beta runtime using username without "@redhat.com" Key: JBIDE-21745 URL: https://issues.jboss.org/browse/JBIDE-21745 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.3.0.Final, 4.3.1.CR1 Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA Reporter: Radim Hopp Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: {noformat} You Entered All Necessary Information Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. {noformat} But even after that I'm unable to download that runtime with the same credentials. Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21698) Can't deploy Docker image to OpenShift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21698?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21698. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B190. > Can't deploy Docker image to OpenShift > -------------------------------------- > > Key: JBIDE-21698 > URL: https://issues.jboss.org/browse/JBIDE-21698 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Clone https://github.com/redhat-developer-tooling/openshift-vagrant/ (outside eclipse) > Create / Run CDK Server adapter pointing at openshift-vagrant/cdk-v2/ > Clone https://github.com/burrsutter/cdk_helloworlds > import swarm-helloworld as a maven project in the workspace > Run maven build mvn clean compile package on the project. > Right-click on swarm-helloworld/dockerfile > Run As > Docker Image Build > Select Docker connection from CDK > Use 172.30.80.211:5000/burr/swarm-helloworld as repo name > The image deploys to the CDK docker connection/registry (See Docker Explorer) > Right click on the deployed image > Deploy to OpenShift > Select OpenShift Project (create a new one if necessary) > =>Error Message : This docker image was not pulled in the selected Docker connection. Mapping ports will not be possible. > The Finish Button stays disabled > http://screencast.com/t/I2syMLXNcO8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20541) wildfly-jts-application-component-2 quickstart fails to validate

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20541?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20541: ------------------------------------- that's a question for [~sgilda] > wildfly-jts-application-component-2 quickstart fails to validate > ----------------------------------------------------------------- > > Key: JBIDE-20541 > URL: https://issues.jboss.org/browse/JBIDE-20541 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly > Fix For: 4.3.0.Final > > > See https://issues.jboss.org/browse/WFLY-5250 for followup. > The above quickstart fails to validate in eclipse. It has the following lines in it: > {code} > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:iiop="urn:iiop" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd > http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd > urn:iiop jboss-ejb-iiop_1_0.xsd" > version="3.1" > impl-version="2.0"> > <assembly-descriptor> > <iiop:iiop> > <ejb-name>InvoiceManagerEJBImpl</ejb-name> > <iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name> > </iiop:iiop> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > The key line to note is: > {code} > urn:iiop jboss-ejb-iiop_1_0.xsd" > {code} > Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with: > {code} > urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd" > {code} > However, even once that is fixed, the quickstart still has other problems. For one example: > {code} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http:// > java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method- > permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/ > javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http:// > java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application- > exception}' is expected. > {code} > I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2016