April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22141) jboss-app.xml validate problem in JBDS 8.0.0.GA.

by xu zhang (JIRA)

xu zhang created JBIDE-22141: -------------------------------- Summary: jboss-app.xml validate problem in JBDS 8.0.0.GA. Key: JBIDE-22141 URL: https://issues.jboss.org/browse/JBIDE-22141 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.3.Final Reporter: xu zhang Create "jboss-app.xml" from attachment of article "https://access.redhat.com/solutions/268733" in JBDS 8.0.0, error shows: ~~~ No grammar constraints (DTD or XML Schema) referenced in the document. ~~~ Customer wants JBDS to validate "jboss-app.xml" correctly. Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22140) jboss-web.xml validate problem in JBDS 8.0.0.GA.

by xu zhang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22140?page=com.atlassian.jira.plugi... ] xu zhang updated JBIDE-22140: ----------------------------- Description: Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: ~~~ No grammar constraints (DTD or XML Schema) referenced in the document. ~~~ Customer wants JBDS to validate "jboss-web.xml" correctly. Please let us know if it will be resolved in the next release/patch. was: Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: ~~~ No grammar constraints (DTD or XML Schema) referenced in the document. ~~~ Please let us know if it will be resolved in the next release/patch. > jboss-web.xml validate problem in JBDS 8.0.0.GA. > ------------------------------------------------ > > Key: JBIDE-22140 > URL: https://issues.jboss.org/browse/JBIDE-22140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final > Reporter: xu zhang > > Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: > ~~~ > No grammar constraints (DTD or XML Schema) referenced in the document. > ~~~ > Customer wants JBDS to validate "jboss-web.xml" correctly. > Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22140) jboss-web.xml validate problem in JBDS 8.0.0.GA.

by xu zhang (JIRA)

xu zhang created JBIDE-22140: -------------------------------- Summary: jboss-web.xml validate problem in JBDS 8.0.0.GA. Key: JBIDE-22140 URL: https://issues.jboss.org/browse/JBIDE-22140 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.3.Final Reporter: xu zhang Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: ~~~ No grammar constraints (DTD or XML Schema) referenced in the document. ~~~ Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3739 at 4/8/16 4:44 AM: ------------------------------------------------------------- [~rob.stryker], I don't know when the next build of cdk.zip is available, but vagrant-service-manager 1.0.0 has been released and is available using: vagrant plugin install vagrant-service-manager This should be the final version for our release if no major issues are found. Or so says Hardy :) EDIT: It turns out there is a new build of CDK right now. It's a candidate for GA. http://cdk-builds.usersys.redhat.com/builds/weekly/08-Apr-2016/ was (Author: mmalina): [~rob.stryker], I don't know when the next build of cdk.zip is available, but vagrant-service-manager 1.0.0 has been released and is available using: vagrant plugin install vagrant-service-manager This should be the final version for our release if no major issues are found. Or so says Hardy :) > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Hardy Ferentschik > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3739: ------------------------------------- [~rob.stryker], I don't know when the next build of cdk.zip is available, but vagrant-service-manager 1.0.0 has been released and is available using: vagrant plugin install vagrant-service-manager This should be the final version for our release if no major issues are found. Or so says Hardy :) > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Hardy Ferentschik > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3739: ----------------------------------- [~akazakov] Any update? Did this make it into an installer build? > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Hardy Ferentschik > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22034) Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22034?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-22034 at 4/8/16 4:25 AM: ------------------------------------------------------------ I don't think we can remove the Pin Console item as it is quite hardwired in the console framework. But working on adding a toggle action for Show Console output when Standard Out Changes was (Author: jeffmaury): I don't think we can remove the Pin Console item as it is quite hardwire in the console framework. But working on adding a toggle action for Show Console output when Standard Out Changes > Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22034 > URL: https://issues.jboss.org/browse/JBIDE-22034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.4.x > > > Currently console containing output of rsync contains Pin Console toggle item which is useless there. Item should be changed to Show Console Output When Standard Out Changes which, when is enabled, show console view when output in it changes - this makes sense because if user want to track what have been rsynced, this is nice way to do it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22034) Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22034?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22034: ------------------------------------ I don't think we can remote the Pin Console item as it is quite hardwire in the console framework. But working on adding a toggle action for Show Console output when Standard Out Changes > Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22034 > URL: https://issues.jboss.org/browse/JBIDE-22034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.4.x > > > Currently console containing output of rsync contains Pin Console toggle item which is useless there. Item should be changed to Show Console Output When Standard Out Changes which, when is enabled, show console view when output in it changes - this makes sense because if user want to track what have been rsynced, this is nice way to do it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22034) Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22034?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-22034 at 4/8/16 4:25 AM: ------------------------------------------------------------ I don't think we can remove the Pin Console item as it is quite hardwire in the console framework. But working on adding a toggle action for Show Console output when Standard Out Changes was (Author: jeffmaury): I don't think we can remote the Pin Console item as it is quite hardwire in the console framework. But working on adding a toggle action for Show Console output when Standard Out Changes > Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22034 > URL: https://issues.jboss.org/browse/JBIDE-22034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.4.x > > > Currently console containing output of rsync contains Pin Console toggle item which is useless there. Item should be changed to Show Console Output When Standard Out Changes which, when is enabled, show console view when output in it changes - this makes sense because if user want to track what have been rsynced, this is nice way to do it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22134: --------------------------------------- [~jcantrill] For example, I was experiencing this issue when I tried to deploy openshift/wildfly-90-centos7 image to OpenShift. When inspecting the docker image the following is present: {code}"ExposedPorts": { "8080/tcp": {} },{code} {code}"Env": [ "PATH=/opt/app-root/src/bin:/opt/app-root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "STI_SCRIPTS_URL=image:///usr/libexec/s2i", "STI_SCRIPTS_PATH=/usr/libexec/s2i", "HOME=/opt/app-root/src", "BASH_ENV=/opt/app-root/etc/scl_enable", "ENV=/opt/app-root/etc/scl_enable", "PROMPT_COMMAND=. /opt/app-root/etc/scl_enable", "WILDFLY_VERSION=9.0.2", "WILDFLY_VERSION_BIN=9.0.2.Final", "MAVEN_VERSION=3.3.3" ],{code} I think those are (meta)data we are using in wizard and somehow, sometimes they are not present in Deploy Docker Image to OpenShift wizard. Table containing env. vars and ports are empty in the wizard. This is happening when an image is already pulled locally. But so far, as I mentioned, I was not able to find a reliable way to reproduce it. I was not experiencing this when I was trying to use an image which has not been pulled yet. But it does not necessary mean it is a cause of it or it has something to do with that, but it could be related. > Sometimes docker image data are not shown in Deploy to OpenShift wizard > ----------------------------------------------------------------------- > > Key: JBIDE-22134 > URL: https://issues.jboss.org/browse/JBIDE-22134 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016