August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22966: ------------------------------- Fix Version/s: 4.4.1.Final > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Mappings: > * BZ Product = Red Hat Software Collections --> RH-ECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (generate automatically) > * Version = rh-eclipse46 --> rh-eclipse46 > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22966: ---------------------------------- Summary: create bzira fork that supports scraping RH bugzilla Key: JBIDE-22966 URL: https://issues.jboss.org/browse/JBIDE-22966 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Affects Versions: 4.4.1.AM3 Reporter: Nick Boldt Sample issue to scrape: https://bugzilla.redhat.com/show_bug.cgi?id=1363849 More issues: https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... Mappings: * BZ Product = Red Hat Software Collections --> RH-ECLIPSE jira * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (generate automatically) * Version = rh-eclipse46 --> rh-eclipse46 * Target Milestone --> label in JIRA * Target Release -> label in JIRA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22913: --------------------------------------- Do we have JBIDE issue for that too? It would be nice if we could track it as well in JBIDE and mark as upstream issue. > Server Adapter: Publish does not work > ------------------------------------- > > Key: JBIDE-22913 > URL: https://issues.jboss.org/browse/JBIDE-22913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > > When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error. > {code} > Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it. > Ignoring the following flags because they only apply to rsync: --exclude, --no-perms > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2 > {code} > I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22913 at 8/9/16 10:56 AM: ---------------------------------------------------------------- Well commit has been merged day before the build has been done. So if build did not last for almost 30 hours, it should contain the commit. Now I downloaded latest devstudio build with build ID AM3-v20160809-0722-B5729, that means it just few hours old and it has new OpenShift tooling plugins, but the issue is still there. was (Author: mlabuda): Well, that OpenShift java restclient build is one day older than the commit fixing the issue. Now I downloaded latest devstudio build with build ID AM3-v20160809-0722-B5729, that means it just few hours old and it has new OpenShift tooling plugins, but the issue is still there. > Server Adapter: Publish does not work > ------------------------------------- > > Key: JBIDE-22913 > URL: https://issues.jboss.org/browse/JBIDE-22913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > > When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error. > {code} > Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it. > Ignoring the following flags because they only apply to rsync: --exclude, --no-perms > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2 > {code} > I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-819: ------------------------------------ Attachment: camel_icons_jbdsis901ga.png > Update fuse icons for 9.0.1.GA > ------------------------------ > > Key: JBTIS-819 > URL: https://issues.jboss.org/browse/JBTIS-819 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, Fuse IDE > Affects Versions: 9.0.1.CR3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > Attachments: camel_icons_jbdsis901ga.png > > > Update the fuse icons - they are out of date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-819: -------------------------------------- on Red Hat Central for the Project Wizard and when looking at Eclipse About Dialog / Installed Software > Update fuse icons for 9.0.1.GA > ------------------------------ > > Key: JBTIS-819 > URL: https://issues.jboss.org/browse/JBTIS-819 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, Fuse IDE > Affects Versions: 9.0.1.CR3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > > Update the fuse icons - they are out of date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-819: ----------------------------------------- So far, I have found the following places * icon in opened editor * icon at the root of a fuse project * icon at a route (e.g. blueprint.xml) > Update fuse icons for 9.0.1.GA > ------------------------------ > > Key: JBTIS-819 > URL: https://issues.jboss.org/browse/JBTIS-819 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, Fuse IDE > Affects Versions: 9.0.1.CR3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > > Update the fuse icons - they are out of date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22913: ------------------------------------ No I was referring to OSJC-264 > Server Adapter: Publish does not work > ------------------------------------- > > Key: JBIDE-22913 > URL: https://issues.jboss.org/browse/JBIDE-22913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > > When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error. > {code} > Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it. > Ignoring the following flags because they only apply to rsync: --exclude, --no-perms > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2 > {code} > I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22965: --------------------------------------- Nope, there were some manual tests performed a long time ago, whether proxy works and it worked, not sure how it is working now. I don't have resources nor time capabilities to include this into test plans so it was one time test. > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.Final > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-819: ----------------------------------------- [~pleacu], where can I see the new icons? > Update fuse icons for 9.0.1.GA > ------------------------------ > > Key: JBTIS-819 > URL: https://issues.jboss.org/browse/JBTIS-819 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, Fuse IDE > Affects Versions: 9.0.1.CR3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > > Update the fuse icons - they are out of date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

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