July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3496) AngularJS tooling is shown both with and without Early Access checked in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3496?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3496: ----------------------------- Fix Version/s: 9.0.0.CR1 > AngularJS tooling is shown both with and without Early Access checked in Central > -------------------------------------------------------------------------------- > > Key: JBDS-3496 > URL: https://issues.jboss.org/browse/JBDS-3496 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 9.0.0.CR1 > > Attachments: angular-displayed.png > > > In the Software/Update tab of Central in JBDS 9.0.0.Beta2, I can see AngularJS for Web Tools even without checking "Enable Early Access". > AFAIK, AngularJS tooling should be early access only. > Once I check the early access checkbox, it will suddenly turn yellow marking it as early access. > This only happens in JBDS. In JBoss Tools, it is not displayed unless you check the early access checkbox. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forward to local used port

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20397: --------------------------------------- [~adietish] If this is correct, its not a tooling issue but an issue with the binary since we defer to it for the actual port forwarding. Is there something we can do in the tooling to mitigate this? I will ask openshift dev about it as well. > [origin_intservice_59]Port forward to local used port > ----------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16379) Using symbolic links in the workspace path causes an infinite loop for m2e builder

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16379?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16379: ---------------------------------------- It's still worth opening an issue in bugzilla and link it here. Then we will have a place where we can track and discuss this problem even if they are not going to solve it in near future. > Using symbolic links in the workspace path causes an infinite loop for m2e builder > ---------------------------------------------------------------------------------- > > Key: JBIDE-16379 > URL: https://issues.jboss.org/browse/JBIDE-16379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.3.x > > > See JBIDE-16286 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3496) AngularJS tooling is shown both with and without Early Access checked in Central

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3496?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3496: ------------------------------------- OK, so the description really is different, but I would say it's pretty confusing - I wouldn't notice any difference if you didn't tell me. Normal says: AngularJS Tooling provides content assist and Ionic framework support. Early Access says: AngularJS Tooling provides content assist, navigation and Ionic framework support. So only one word difference :-\ and the title is exactly the same. And my JBoss Tools installation doesn't show the normal adapter in central, because it is installed by default (using JBT abridged category): {code} nattura:features rasp$ ls |grep angular org.jboss.tools.jst.angularjs.feature_3.7.0.Beta2-v20150724-2248-B29 {code} > AngularJS tooling is shown both with and without Early Access checked in Central > -------------------------------------------------------------------------------- > > Key: JBDS-3496 > URL: https://issues.jboss.org/browse/JBDS-3496 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Attachments: angular-displayed.png > > > In the Software/Update tab of Central in JBDS 9.0.0.Beta2, I can see AngularJS for Web Tools even without checking "Enable Early Access". > AFAIK, AngularJS tooling should be early access only. > Once I check the early access checkbox, it will suddenly turn yellow marking it as early access. > This only happens in JBDS. In JBoss Tools, it is not displayed unless you check the early access checkbox. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3496) AngularJS tooling is shown both with and without Early Access checked in Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3496?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3496: -------------------------------------- Yes, we have AngularJS in both centrals. EA and regular. But they are different. EA contains Eclipse AngularJS plugins. Regular just Ionic. They should have different descriptions. I'm not sure why you don't see it in JBT central. Could you have it already installed by any chance? > AngularJS tooling is shown both with and without Early Access checked in Central > -------------------------------------------------------------------------------- > > Key: JBDS-3496 > URL: https://issues.jboss.org/browse/JBDS-3496 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Attachments: angular-displayed.png > > > In the Software/Update tab of Central in JBDS 9.0.0.Beta2, I can see AngularJS for Web Tools even without checking "Enable Early Access". > AFAIK, AngularJS tooling should be early access only. > Once I check the early access checkbox, it will suddenly turn yellow marking it as early access. > This only happens in JBDS. In JBoss Tools, it is not displayed unless you check the early access checkbox. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20057) server store its passwords badly in secure storage

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20057?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20057. --------------------------------- Verified in JBDS 9.0.0.Beta2 B93. I checked that right now I have a mix of the old bad formatted keys and the new ones. Then I deleted all and saved a few passwords and it all used the new (nicer) format. Closing. > server store its passwords badly in secure storage > -------------------------------------------------- > > Key: JBIDE-20057 > URL: https://issues.jboss.org/browse/JBIDE-20057 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > Attachments: Preferences.png, scr.png > > > looks like we are somehow using bad formatted keys or groupings in our secure storage. > see screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20164) webtools server adapter installation UI is non-informative

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20164. --------------------------------- As I said above, this has been verified (now also by Nick) and since I closed the subtask as well, I'm closing this one also. > webtools server adapter installation UI is non-informative > ---------------------------------------------------------- > > Key: JBIDE-20164 > URL: https://issues.jboss.org/browse/JBIDE-20164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: install-jbossas-connector-from-nightly.png, Install_New_Extension_and_New_Server.png, jbt-server-adapters-beta2.png > > > When using the "download additional adapters" for JBoss Tools it has a few issues. > a) shows "null" for vendor > b) does not actually say it is for WildFly nor EAP servers > c) (idea) should we add OpenShift to this ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20173) Clean up UI errors in case RSE is not installed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20173?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20173: --------------------------------------- I tried this and somehow the rse plugins still got pulled in the installation. I wasn't able to track where it came from. I only installed the org.jboss.ide.eclipse.as.feature feature. Let me know if you have any other suggestion. But I'm not sure if it's worth the effort. > Clean up UI errors in case RSE is not installed > ----------------------------------------------- > > Key: JBIDE-20173 > URL: https://issues.jboss.org/browse/JBIDE-20173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > In an environment where RSE is not available, the UI fails in multiple fashions. It allows you to create RSE servers, even though it shouldn't. If there's a previously-existing RSE server, the server editor will fail to load with NPE. There is also no warning in the editor anywhere indicating that the server is incompatible with current profile. > Also, start / debug / etc should fail indicating profile is unavailable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20173) Clean up UI errors in case RSE is not installed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20173?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20173. --------------------------------- Unable to verify really, closing. > Clean up UI errors in case RSE is not installed > ----------------------------------------------- > > Key: JBIDE-20173 > URL: https://issues.jboss.org/browse/JBIDE-20173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > In an environment where RSE is not available, the UI fails in multiple fashions. It allows you to create RSE servers, even though it shouldn't. If there's a previously-existing RSE server, the server editor will fail to load with NPE. There is also no warning in the editor anywhere indicating that the server is incompatible with current profile. > Also, start / debug / etc should fail indicating profile is unavailable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3454) Mobile Hybrid Project not opening on the emulator

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3454?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3454: ------------------------------------ The errors that I see on the log are due to Android tools, specifically aapt, not working due to missing Linux libraries. Take a look at http://stackoverflow.com/questions/22701405/aapt-ioexception-error-2-no-s.... I think on Fedora something like "sudo yum install zlib.i686 libstdc++.i686" should fix the problem for you. > Mobile Hybrid Project not opening on the emulator > ------------------------------------------------- > > Key: JBDS-3454 > URL: https://issues.jboss.org/browse/JBDS-3454 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 9.0.0.Alpha2 > Reporter: Supriya Bharadwaj > Assignee: Gorkem Ercan > Priority: Minor > Attachments: error_project29july.log > > > I am trying to create a Mobile Hybrid project using the Mobile Hybrid Project wizard in JBoss Central. After its creation, the project does not open on the emulator. Also, if I export the project and try installing the apk file on a mobile android platform I get an "Application not installed" message. On certain environments (JBDS 9.0.0Alpha2 on RHEL 7) while trying to export the project it throws a "not an android project" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 July 2015