April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3710) use brackets logo in icon for Developer Platform installer .exe

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3710: ----------------------------- Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu..., https://github.com/redhat-developer-tooling/developer-platform-install/pu... > use brackets logo in icon for Developer Platform installer .exe > --------------------------------------------------------------- > > Key: JBDS-3710 > URL: https://issues.jboss.org/browse/JBDS-3710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3774?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3774: -------------------------------- Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu..., https://github.com/redhat-developer-tooling/developer-platform-install/pu... (was: https://github.com/redhat-developer-tooling/developer-platform-install/pu...) > Failed due to 2 attempts at installing CDK's vagrant box > -------------------------------------------------------- > > Key: JBDS-3774 > URL: https://issues.jboss.org/browse/JBDS-3774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows 10 Pro > Reporter: Burr Sutter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: install.log, vagrant.log, vbox.log > > > Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed: > C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f" > 'vagrant' is not recognized as an internal or external command, > operable program or batch file. > ... > Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed: > C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2 > c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box" > The box you're attempting to add already exists. Remove it before > adding it again or add it with the `--force` flag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3778) Add checksum verification for downloaded resources

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3778?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3778: ----------------------------------- Assignee: Denis Golovin (was: Nick Boldt) > Add checksum verification for downloaded resources > -------------------------------------------------- > > Key: JBDS-3778 > URL: https://issues.jboss.org/browse/JBDS-3778 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: Havoc > Fix For: 9.1.0.GA > > > When downloading from remote site anything can happen, installer build and installer itself should verify checksum for downloaded resources. > * add method createSHA256(file) into gulpfile.js to create sha256 checksum for file > * here is an example http://www.hacksparrow.com/how-to-generate-md5-sha1-sha512-sha256-checksu... > * then we will need to create SHA256 for vagrant and virtualBox or download them if they are available > * and then we can skip downloading if it's already on disk > Request comes from Product Security team. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21746?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21746: ----------------------------------------------- The log level can be setup in the config.ini file with the eclipse.log.level parameter. The value can be set to INFO, WARNING and ERROR. WARNING and ERROR will not write INFO messages. However, user may want to see info, but not too much of it. I would suggest to write info in this case only if option org.jboss.tools.openshift.ui/debug is set to true. If exception is thrown then error is logged, that is good enough for non-debug mode. [~jcantrill], [~fbricon], what do you think? > 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 > Fix For: 4.4.0.Alpha1 > > > 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
0
0 / 0

[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22133 at 4/8/16 2:22 PM: ------------------------------------------------------------------ I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong. If this is the case you should experience the same using oc. [~xiazhao2015] Do you? was (Author: adietish): I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong. If this is the case you should experience the same using oc. Do you? > Get error "UnsupportedMediaType' when create project/applications from JBT on Mac > --------------------------------------------------------------------------------- > > Key: JBIDE-22133 > URL: https://issues.jboss.org/browse/JBIDE-22133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262 > Mac OS > Reporter: Xia Zhao > Assignee: Jeff Cantrill > Labels: openshift_v3 > > Get error "UnsupportedMediaType" when create project and applications from JBT on Mac -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22133 at 4/8/16 2:12 PM: ------------------------------------------------------------------ I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong. If this is the case you should experience the same using oc. Do you? was (Author: adietish): I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong. > Get error "UnsupportedMediaType' when create project/applications from JBT on Mac > --------------------------------------------------------------------------------- > > Key: JBIDE-22133 > URL: https://issues.jboss.org/browse/JBIDE-22133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262 > Mac OS > Reporter: Xia Zhao > Assignee: Jeff Cantrill > Labels: openshift_v3 > > Get error "UnsupportedMediaType" when create project and applications from JBT on Mac -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22139) 20% of openshift tests are not run

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22139?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-22139. --------------------------------- Resolution: Done we're up to 407 running tests now at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift... > 20% of openshift tests are not run > ---------------------------------- > > Key: JBIDE-22139 > URL: https://issues.jboss.org/browse/JBIDE-22139 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: test > Fix For: 4.4.0.Alpha1 > > > I realized Openshift builds only run ~ 337 tests via tycho, but we have about 411 tests to run. > This is caused by that stupid tycho-surefire setting that only runs testsuites. Guess what? Some of those test classes are not added to any test suite. > As a developer I just write my test class and expect the build to pick it up automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-651) Add SAP 8.0.0.Beta1 tooling to devstudio extras

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-651?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-651: ---------------------------------- I've update the staging extras site. I'll update the development and stable sites when we go to smoke test. Please try: -Djboss.discovery.site.integration-stack-sap.url=http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/extras/jboss-fuse-sap-tool-suite/ > Add SAP 8.0.0.Beta1 tooling to devstudio extras > ----------------------------------------------- > > Key: JBTIS-651 > URL: https://issues.jboss.org/browse/JBTIS-651 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: build, distribution > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > The file at http://download.jboss.org/jbosstools/configuration/ide-config.properties specifies extras for JBDS 9.x as follows > * https://devstudio.redhat.com/9.0/staging/updates/integration-stack/extras/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ex... > (the stable refers to the development extras) > First of all, the staging extras doesn't contain any SAP bundles. Second, the developemnt extras contain only the SAP tooling of version 8.0.0.Alpha1. > Note that there is a newer version of SAP tooling which is 8.0.0.Beta1 available at > http://download.jboss.org/jbosstools/mars/integration/updates/integration... > The above site can be used in JBDS by adding the following VM argument > -Djboss.discovery.site.integration-stack-sap.url=http://download.jboss.org/jbosstools/mars/integration/updates/integration-stack/extras/jboss-fuse-sap-tool-suite/8.0.0.Beta1/all/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22145: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22145: ----------------------------------- Labels: (was: respin-b) > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- 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