October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2774?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2774: ----------------------------- CDW devel_ack: + (was: ?) > Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central > ---------------------------------------------------------------------------- > > Key: JBDS-2774 > URL: https://issues.jboss.org/browse/JBDS-2774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central > Affects Versions: 7.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: > http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ > (as per https://confluence.atlassian.com/display/IDEPLUGIN/Installing+the+Eclipse... ) > Mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.2... > Please review to decide if we should include this for Beta1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Vlado Pakan resolved JBDS-2709. ------------------------------- Resolution: Done > Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central > ---------------------------------------------------------- > > Key: JBDS-2709 > URL: https://issues.jboss.org/browse/JBDS-2709 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > As reported here: > https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=... > {quote} > Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN. > http://subclipse.tigris.org/update_1.10.x > Local repository compatibility between these tools and JBDS is very nice to have. > Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question. > {quote} > http://www.svnkit.com/download.php > Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15680) Parse SSH_URL in returned Application JSON response

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15680: ------------------------------------- Summary: Parse SSH_URL in returned Application JSON response Key: JBIDE-15680 URL: https://issues.jboss.org/browse/JBIDE-15680 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.1.1.Beta1 The OpenShift Broker response include an 'ssh_url' attribute that should be retrieved, as the way the OpenShift plugin forges the ssh_url is sometimes wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15679) Unable to create SSH session for application 'main' Auth fail

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15679: ------------------------------------- Summary: Unable to create SSH session for application 'main' Auth fail Key: JBIDE-15679 URL: https://issues.jboss.org/browse/JBIDE-15679 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Blocker Fix For: 4.1.1.Beta1 >From https://bugzilla.redhat.com/show_bug.cgi?id=1013294: "After having problem with Jboss Openshifts 4.0 not being able to connect to openshift servers resolved by a recent update, now I have three applications on a domain. Am able to manage two of those application but one always returns "Unable to create SSH session for application 'main' Auth fail" whenever I try to manage the application with JBoss openshift tools for Zend Studio. After investigating for a while I noticed that the UUID for the two applications are was able to access were the same as the username in the git url. However for the one that am unable to access the UUID is different from the username in the git url. Management with rhc and other ssh tools work but I need the JBoss tools because they make work easier. Is there any way I can update the UUID in JBoss Openshift tools." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 OSX users

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2797: ------------------------------------------- had chat with [~dgolovin] on this and it seems to boil down to use trying to have a OSX friendly name in the dock - no other reason for it and a symbolic link is not sufficient since the app generated will still say jbdevstudio. Thus there are two options afaics: 1) go back to only use jbdevstudio 2) make separate build for osx where this is fixed. #2 is definitely not for 7.1, #1 is a better option here. This would mean the installer should stop doing all this magic and the next installer simply won't generate this "JBoss Developer Studio.app" but only have jbdevstudio.app If we don't do that osx users will not actually get the proper full updates which is bad. That just leaves the central url pointing to development site, are we saying this happend just because the user installed an even earlier version of devstudio and thus got the default before GA ? that would need to get release noted to then that they need to stop using this broken launcher if they installed older versions. > .ini upgrade issue for 7.0.1 OSX users > -------------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2783) Increase default EGit/OpenShift timeout

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2783?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-2783. ------------------------------------- Resolution: Rejected Yes, agreeing to reject this since fixing it in jbds install scenario doesn't fix it for majority of our users (JBT and JBDS BYOE) and we dont use the egit timeout anyway (even though we could use it if higher than our own) > Increase default EGit/OpenShift timeout > --------------------------------------- > > Key: JBDS-2783 > URL: https://issues.jboss.org/browse/JBDS-2783 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift, p2-product > Affects Versions: 7.0.0.GA, 7.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Max Rydahl Andersen > Fix For: 7.1.0.Beta1 > > > Default value for EGit and OpenShift is 30 seconds. In most cases, this value is too short and isn't enoguh for a successful deploy of a dummy JEE app inside JBDS, which leads to a poor first impression. > As we can control the preferences in JBDS (with installer), I suggest we should make default to 60 which seems to behave better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15593: ------------------------------------- Assignee: Brian Fitzpatrick (was: Xavier Coulon) > WS Tester should put a warning when parameter is not valid > ---------------------------------------------------------- > > Key: JBIDE-15593 > URL: https://issues.jboss.org/browse/JBIDE-15593 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.Beta1 > > > WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type. > User should be allowed to submit the request with bad parameters if she really wants to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15593: --------------------------------------- [~bfitzpat], please let me know what you think about it and if we try to put that into 4.1.1.Beta1 or later. thanks Xavier > WS Tester should put a warning when parameter is not valid > ---------------------------------------------------------- > > Key: JBIDE-15593 > URL: https://issues.jboss.org/browse/JBIDE-15593 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Beta1 > > > WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type. > User should be allowed to submit the request with bad parameters if she really wants to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15428) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15428?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15428: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Max, I updated the PR (once again) and removed the unnecessary remaining "synchronized" block in the org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedListener class Assigning this issue back to you for a (hopefully) last PR review ;-) > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15428 > URL: https://issues.jboss.org/browse/JBIDE-15428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: After import.png, After workaround.png, Before import.png > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Vlado Pakan commented on JBDS-2709: ----------------------------------- Subclipse v1.10.2 installed from http://subclipse.tigris.org/update_1.10.x is working fine with JBDS and installs and uses SVNKit v1.8.0.9949 > Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central > ---------------------------------------------------------- > > Key: JBDS-2709 > URL: https://issues.jboss.org/browse/JBDS-2709 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > As reported here: > https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=... > {quote} > Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN. > http://subclipse.tigris.org/update_1.10.x > Local repository compatibility between these tools and JBDS is very nice to have. > Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question. > {quote} > http://www.svnkit.com/download.php > Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 October 2013