January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11767) require jsch 0.1.49 in our plugin and add it to our mirrors

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11767?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-11767. -------------------------------------- Resolution: Rejected We did not have any issues with jsch 0.1.46 so far. Never touch a running system even more if others in Eclipse are depending on jsch. Closing as rejected. > require jsch 0.1.49 in our plugin and add it to our mirrors > ----------------------------------------------------------- > > Key: JBIDE-11767 > URL: https://issues.jboss.org/browse/JBIDE-11767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > in OpenShift we currently depend on jsch 0.1.44. JCraft release 0.1.48 in the meantime that improves / fixes bugs that are related to port forwarding (http://www.jcraft.com/jsch/ChangeLog): > {quote} > - bugfix: in the agent forwarding mode, "ssh-add -l" on the remote > will freeze. FIXED > - change: for the efficiency, channel opening will be delayed > in local port forwarding. > {quote} > The jsch update site is available here: http://eclipse.jcraft.com/site.xml > JSch released 0.1.49 in the meantime. Changelog: http://www.jcraft.com/jsch/ChangeLog -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13355) jbossws testsuite is failing on 3.3.2 test runs

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13355?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-13355: --------------------------------------- That doesn't seem to explain why there were resource deletion problems. > jbossws testsuite is failing on 3.3.2 test runs > ----------------------------------------------- > > Key: JBIDE-13355 > URL: https://issues.jboss.org/browse/JBIDE-13355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 3.3.2 > > > jbossws webservices test runs are failing. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Seem to be a mix of things not something I recall seeing before. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11767) require jsch 0.1.49 in our plugin and add it to our mirrors

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11767?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11767: ------------------------------------- Description: in OpenShift we currently depend on jsch 0.1.44. JCraft release 0.1.48 in the meantime that improves / fixes bugs that are related to port forwarding (http://www.jcraft.com/jsch/ChangeLog): {quote} - bugfix: in the agent forwarding mode, "ssh-add -l" on the remote will freeze. FIXED - change: for the efficiency, channel opening will be delayed in local port forwarding. {quote} The jsch update site is available here: http://eclipse.jcraft.com/site.xml JSch released 0.1.49 in the meantime. Changelog: http://www.jcraft.com/jsch/ChangeLog was: in OpenShift we currently depend on jsch 0.1.44. JCraft release 0.1.48 in the meantime that improves / fixes bugs that are related to port forwarding (http://www.jcraft.com/jsch/ChangeLog): {quote} - bugfix: in the agent forwarding mode, "ssh-add -l" on the remote will freeze. FIXED - change: for the efficiency, channel opening will be delayed in local port forwarding. {quote} The jsch update site is available here: http://eclipse.jcraft.com/site.xml > require jsch 0.1.49 in our plugin and add it to our mirrors > ----------------------------------------------------------- > > Key: JBIDE-11767 > URL: https://issues.jboss.org/browse/JBIDE-11767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > in OpenShift we currently depend on jsch 0.1.44. JCraft release 0.1.48 in the meantime that improves / fixes bugs that are related to port forwarding (http://www.jcraft.com/jsch/ChangeLog): > {quote} > - bugfix: in the agent forwarding mode, "ssh-add -l" on the remote > will freeze. FIXED > - change: for the efficiency, channel opening will be delayed > in local port forwarding. > {quote} > The jsch update site is available here: http://eclipse.jcraft.com/site.xml > JSch released 0.1.49 in the meantime. Changelog: http://www.jcraft.com/jsch/ChangeLog -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13254) In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13254?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13254: ----------------------------------- Fix Version/s: 4.1.0.Alpha1 > In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13254 > URL: https://issues.jboss.org/browse/JBIDE-13254 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 3.3.1, 4.0.0.Beta2 > Environment: WFK 2.1.0.CR2 Seam.2.3.0.Final-redhat-1, JBDS 5.0.1.GA, JBDS 6.0.0.Beta2a > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > After importing a Seam 2.3 seam-gen generated project in JBDS, the EL completion for Seam Messages doesn't work. > This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS. > > Actual results: > Even though the "messages" component is suggested, no actual messages from the properties files are suggested. A warning is shown for e.g #{messages['org.jboss.seam.NotLoggedIn']}. > Expected results: > Messages from messages_xx.properties should be suggested without warnings. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13205) XML Editors not always update status bar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13205?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13205: ----------------------------------- Fix Version/s: 4.1.x > XML Editors not always update status bar > ---------------------------------------- > > Key: JBIDE-13205 > URL: https://issues.jboss.org/browse/JBIDE-13205 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml source editing > Affects Versions: 4.0.0.CR1 > Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121129-0502-B147.jar > Reporter: Daniel Azarov > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.1.x > > Attachments: TLDEditor1.png, TLDEditor1.png, TLDEditor2.png, TLDEditor2.png > > > When I open tld file in JBoss Tools Tag Library Editor first time it does not show any information in status bar: > !TLDEditor1.png! > If I switch to tab "Source" or did it before status bar looks fine: > !TLDEditor2.png! -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13205) XML Editors not always update status bar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13205?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13205: ----------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) > XML Editors not always update status bar > ---------------------------------------- > > Key: JBIDE-13205 > URL: https://issues.jboss.org/browse/JBIDE-13205 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml source editing > Affects Versions: 4.0.0.CR1 > Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121129-0502-B147.jar > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.1.x > > Attachments: TLDEditor1.png, TLDEditor1.png, TLDEditor2.png, TLDEditor2.png > > > When I open tld file in JBoss Tools Tag Library Editor first time it does not show any information in status bar: > !TLDEditor1.png! > If I switch to tab "Source" or did it before status bar looks fine: > !TLDEditor2.png! -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13351: ----------------------------------- Fix Version/s: 4.1.x > Dialogs look and fill problems > ------------------------------ > > Key: JBIDE-13351 > URL: https://issues.jboss.org/browse/JBIDE-13351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Trivial > Fix For: 4.1.x > > Attachments: ADDJBossToolsRuntimeDialog.png, BrowseFontDialog.png, EditServletClassDialog.png, EditTLDFilesDialog.png, NewRepositoryDialog.png, NewTemplateDialog.png > > > Follow dialogs should have a banner: > All dialogs can be found in Preferences (menu Window->Preferences) > 1. JBoss Tools->JBoss Tools Runtime Detection, button "Add", BTW it should be "Add..." > !ADDJBossToolsRuntimeDialog.png! > 2. JBoss Tools->Web->Editors->JSF Flow Diagram, buttons "Browse..." > !BrowseFontDialog.png! > 3. JBoss Tools->Remote Repositories, button "Add..." > !NewRepositoryDialog.png! > 4. JBoss Tools->Web->Visual Page Editor->Code Templates, button "New..." > !NewTemplateDialog.png! > 5. JBoss Tools->Web->Visual Page Editor->Code Templates, button "Import..." -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11767) require jsch 0.1.48 in our plugin and add it to our mirrors

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11767?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11767: ------------------------------------------ Orbit still has jsch 0.1.46: http://download.eclipse.org/tools/orbit/downloads/drops/I20121212174845/ > require jsch 0.1.48 in our plugin and add it to our mirrors > ----------------------------------------------------------- > > Key: JBIDE-11767 > URL: https://issues.jboss.org/browse/JBIDE-11767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > in OpenShift we currently depend on jsch 0.1.44. JCraft release 0.1.48 in the meantime that improves / fixes bugs that are related to port forwarding (http://www.jcraft.com/jsch/ChangeLog): > {quote} > - bugfix: in the agent forwarding mode, "ssh-add -l" on the remote > will freeze. FIXED > - change: for the efficiency, channel opening will be delayed > in local port forwarding. > {quote} > The jsch update site is available here: http://eclipse.jcraft.com/site.xml -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11767) require jsch 0.1.49 in our plugin and add it to our mirrors

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11767?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11767: ------------------------------------- Summary: require jsch 0.1.49 in our plugin and add it to our mirrors (was: require jsch 0.1.48 in our plugin and add it to our mirrors) > require jsch 0.1.49 in our plugin and add it to our mirrors > ----------------------------------------------------------- > > Key: JBIDE-11767 > URL: https://issues.jboss.org/browse/JBIDE-11767 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > in OpenShift we currently depend on jsch 0.1.44. JCraft release 0.1.48 in the meantime that improves / fixes bugs that are related to port forwarding (http://www.jcraft.com/jsch/ChangeLog): > {quote} > - bugfix: in the agent forwarding mode, "ssh-add -l" on the remote > will freeze. FIXED > - change: for the efficiency, channel opening will be delayed > in local port forwarding. > {quote} > The jsch update site is available here: http://eclipse.jcraft.com/site.xml -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11780) OpenShift: Correct importing exception message

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11780?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-11780. -------------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.x) Resolution: Cannot Reproduce Bug I cannot reproduce the bug. M2E apparently allows 2 maven workspace projects with the same pom-name (and different project names): 1) Import OpenShift application 2) Rename the project (not the name in the pom) 3) re-import the OpenShift application Result: It works, no error happens while importing OR 1) Clone OpenShift application 2) Import it to your workspace as Maven project 3) Rename the project (not the name in the pom) 4) Re-Import it again Result: It works > OpenShift: Correct importing exception message > ---------------------------------------------- > > Key: JBIDE-11780 > URL: https://issues.jboss.org/browse/JBIDE-11780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Alpha1 > > > I was trying to import application with same name in pom.xml as I had in my workspace. The following exception message contains 'project null'. I assume that the message is not filled with correct project name. > {code} > org.jboss.tools.openshift.express.internal.ui.ImportFailedException: Could not import project null. One of the possible reasons is that theres already a project in your workspace that matches the openshift application/maven name of the OpenShift application. Please rename your workspace project in that case and start over again. > at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ImportNewProject.execute(ImportNewProject.java:75) > at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.importProject(OpenShiftExpressApplicationWizardModel.java:92) > at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:274) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- 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

13 years, 6 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 January 2013