April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-640) Cannot install JBDS-IS EA in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-640?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-640: -------------------------------- Assignee: Paul Leacu > Cannot install JBDS-IS EA in offline mode > ----------------------------------------- > > Key: JBTIS-640 > URL: https://issues.jboss.org/browse/JBTIS-640 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found > {code} > EDIT: this can be resolved by adding JBDS-IS 9.0.0.CR1 zip file (the GA one) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22126) OpenShift tooling - New application buttons are truncated

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22126?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22126: ----------------------------------------------- On my Ubuntu, the fix of JBIDE-22032 improved these buttons, they were truncated before exactly as shown on the screenshot. The attached pull request checks the required width for the button, and if it is larger than the default width, sets it. > OpenShift tooling - New application buttons are truncated > --------------------------------------------------------- > > Key: JBIDE-22126 > URL: https://issues.jboss.org/browse/JBIDE-22126 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Attachments: openshift_buttons.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-641) create both master and staging discovery compoistes/ metadata

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-641: -------------------------------- Summary: create both master and staging discovery compoistes/ metadata Key: JBTIS-641 URL: https://issues.jboss.org/browse/JBTIS-641 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.3.0.Final, 9.0.0.GA Modify the discovery generation utility to create both 'master' and staging composites/ metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 8 or above on windows

by Tobias van den Berg (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ] Tobias van den Berg edited comment on JBIDE-22078 at 4/6/16 2:00 PM: --------------------------------------------------------------------- Since the summary is changed from Wildfly 10 to Wildfly 8 or above, please notice the difference in behavior between Wildfly 8 and Wildfly 10. The error message is the same indeed, but the behavior is different. Wildfly 10: clean/publish --> error --> application not longer available/published --> restart server and re-add project required Wildfly 8: clean/publish --> error --> application somehow still available (and up to date) This makes is much harder to develop/test on Wildfly 10 since it takes a lot of time to restart the server every time. This isn't required on Wildfly 8. was (Author: tvdberg): Since the summary is changed from Wildfly 10 to Wildfly 8 or above, please notice the difference in behavior between Wildfly 8 and Wildfly 10. The error message is the same indeed, but the behavior is different. Wildfly 10: clean/publish --> error --> application not longer available/published --> restart server and re-add project required Wildfly 8: clean/publish --> error --> application somehow still available This makes is much harder to develop/test on Wildfly 10 since it takes a lot of time to restart the server every time. This isn't required on Wildfly 8. > Error publishing war file to wildfy 8 or above on windows > --------------------------------------------------------- > > Key: JBIDE-22078 > URL: https://issues.jboss.org/browse/JBIDE-22078 > 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: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.3.1.CR1 > > Attachments: Logfile.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-22078) Error publishing war file to wildfy 8 or above on windows

by Tobias van den Berg (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ] Tobias van den Berg commented on JBIDE-22078: --------------------------------------------- Since the summary is changed from Wildfly 10 to Wildfly 8 or above, please notice the difference in behavior between Wildfly 8 and Wildfly 10. The error message is the same indeed, but the behavior is different. Wildfly 10: clean/publish --> error --> application not longer available/published --> restart server and re-add project required Wildfly 8: clean/publish --> error --> application somehow still available This makes is much harder to develop/test on Wildfly 10 since it takes a lot of time to restart the server every time. This isn't required on Wildfly 8. > Error publishing war file to wildfy 8 or above on windows > --------------------------------------------------------- > > Key: JBIDE-22078 > URL: https://issues.jboss.org/browse/JBIDE-22078 > 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: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.3.1.CR1 > > Attachments: Logfile.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] (JBDS-3696) Browse buttons should not respond when a file dialog is opened

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ] Joshua Wilson updated JBDS-3696: -------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 4.1.4.GA) > Browse buttons should not respond when a file dialog is opened > -------------------------------------------------------------- > > Key: JBDS-3696 > URL: https://issues.jboss.org/browse/JBDS-3696 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Joshua Wilson > Labels: havoc, ui > Fix For: 10.0.0.Alpha1 > > > Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile

by Rafael Benevides (JIRA)

Rafael Benevides created JBIDE-22128: ---------------------------------------- Summary: Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile Key: JBIDE-22128 URL: https://issues.jboss.org/browse/JBIDE-22128 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 Openshift plugin 3.1.0.Final-v20160401-2357-B263 Reporter: Rafael Benevides I have a Java project with an "openshift" maven profile that creates a ROOT.war When I create a "Server Adapter", the openshift plugins deploys the name of the project.war The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22121) Using remote OpenShift server prompt to accept a certificate is shown several times for different certificates

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22121?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22121: -------------------------------- Fix Version/s: 4.4.x > Using remote OpenShift server prompt to accept a certificate is shown several times for different certificates > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22121 > URL: https://issues.jboss.org/browse/JBIDE-22121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: new_connection > Fix For: 4.4.x > > > When I am trying to connect to internal servers (https://api.engint.openshift.com or https://api.ded-stage-aws.openshift.com/) by OAuth using token, I am prompted several times to accept various SSL certificates. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22121) Using remote OpenShift server prompt to accept a certificate is shown several times for different certificates

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22121?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22121: ------------------------------------- If you look at the Certificate tab in the workspace preferences, you'll see each belong to a different server. So I'd say this is entirely expected that you need to approve each of them. This seems more of a server configuration problem. The alternative would be to accept all certificates silently, but then that'd prolly not be very secure :-) The thing that is really missing is displaying for which server the certificate needs to be approved, but that's covered by JBIDE-16517. Overall this smells like a Won't fix issue to me. > Using remote OpenShift server prompt to accept a certificate is shown several times for different certificates > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22121 > URL: https://issues.jboss.org/browse/JBIDE-22121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: new_connection > > When I am trying to connect to internal servers (https://api.engint.openshift.com or https://api.ded-stage-aws.openshift.com/) by OAuth using token, I am prompted several times to accept various SSL certificates. -- 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 commented on JBDS-3774: ------------------------------------- [~burrsutter]if you open powershell or cmd and call {code}'vagrant'{code} what do you get? > 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

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