April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14323) Maven Update Project should be hotkey bindable

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created JBIDE-14323: ------------------------------------------ Summary: Maven Update Project should be hotkey bindable Key: JBIDE-14323 URL: https://issues.jboss.org/browse/JBIDE-14323 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.1.0.Alpha1 Reporter: Lincoln Baxter III Currently it is not possible to bind a hotkey shortcut to "maven-->update project", forcing the user to go to the mouse and do a lot of clicking. This is a pretty big problem when projects go out of sync so frequently in larger projects ;) -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13958) OpenShift connection wizard forgets password on IDE restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13958?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13958: ------------------------------------------ I can reproduce it. I'll fix the issue. Nevertheless please try me to explain you what connection you get presented in the connections dialog since it seems to me, that it's not obvious. The connection dialog behaves in the following way: * you have *no connection selected* in the OpenShift Explorer: The most recently created/edited/used connection is preselected in the combo * you have *a connection selected* in the OpenShift Explorer: The selected connection is preselected in the combo Thus if you want to see the settings for your connection you have to select it in the OpenShift Explorer. Otherwise the most recently created/edited/used one gets presented to you in the connection dialog. In your case it didn't matter since you had only 1 connection. > OpenShift connection wizard forgets password on IDE restart > ------------------------------------------------------------ > > Key: JBIDE-13958 > URL: https://issues.jboss.org/browse/JBIDE-13958 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > Attachments: Connection_withoutPassword_afterIDErestart.png, Connection_withPassword.png > > > I created a new OpenShift connection and selected 'save password' (then was prompted to put in secure storage password). New connection is listed in OpenShift Explorer tab. > If I then click 'Connect to OpenShift' icon, the newly connected connection info is shown together with the password in the password field and the 'save password' check box is selected [attached image - Connection_withPassword.png]. > All good up to this point. > I then closed and reopened the IDE. If I then click 'Connect to OpenShift' icon, the newly connected connection info is shown but the password field is BLANK and the 'save password' check box is NOT selected [attached image - Connection_withoutPassword_afterIDErestart.png]. > This looks like a bug to me - the password field should be completed and the check box selected. > This issue only occurs when clicking 'connect to OpenShift' after an IDE restart. If double-click or expand connection in OpenShift Explorer tab after restart then the connection wizard remembers the password and skips straight to prompting for secure storage password as expected. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13977) updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13977?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13977: ------------------------------------ First use of the new pack step: https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... --> http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... > updates/requirements/*/build.xml scripts should include pack.gz artifacts (using p2.process.artifacts pack="true") to make resolving multiple.target faster > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13977 > URL: https://issues.jboss.org/browse/JBIDE-13977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite, upstream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > All ant scripts (updates/requirements/*/build.xml) used to mirror 3rd party reqs from Eclipse.org and other places should be updated to generate .pack.gz artifacts too. > {code}<p2.process.artifacts pack="true" repositoryPath="file:/${repoDirLocation}" />{code} > Refs: > * http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.... > * http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.... -- 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

1
0
0 / 0

[JBoss JIRA] (JBTIS-66) Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-66?page=com.atlassian.jira.plugin.s... ] Nick Boldt reassigned JBTIS-66: ------------------------------- Assignee: Robert (Bob) Brodt (was: Nick Boldt) Mirrored here: http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2... Questions: a) Why does each maintenance release live in a different URL? Why not just add the new content via composite site metadata to http://download.eclipse.org/bpmn2-modeler/site/ instead of http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ b) Do you plan to drop a new maintenance release every 3 weeks? The last update was 0.2.4 on 2013-04-09 @ 22:17. c) What's in 0.2.5 that SwitchYard *NEEDS* which wasn't in 0.2.4? d) Is there a new release planned for http://download.eclipse.org/bpmn2-modeler/bpmn2/site/ ? The BPMN2 Project Feature 0.7.0.201106271450 hasn't changed in almost 2 years, yet the Modeler/Editor drops a new release every 3 weeks. Thanks! > Mirror Eclipse BPMN2 Modeler v0.2.5 on jboss tools requirements > --------------------------------------------------------------- > > Key: JBTIS-66 > URL: https://issues.jboss.org/browse/JBTIS-66 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: releng, switchyard, target-platform > Affects Versions: 4.0.0 > Reporter: Robert (Bob) Brodt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0 > > > Here is the site URL: http://download.eclipse.org/bpmn2-modeler/site/0.2.5/ > This is required for SwitchYard 0.8. -- 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

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-310) redirect /latest to /reference where the latest released docs can be found

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-310?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-310: ------------------------------------- At the risk of feeding the trolls, creating a symlink locally and pushing it to the server via rsync over ssh can also be scripted: https://issues.jboss.org/browse/TOOLSDOC-310?focusedCommentId=12767281&pa... Added bonus is that the symlink can then reside in git, too. > redirect /latest to /reference where the latest released docs can be found > -------------------------------------------------------------------------- > > Key: TOOLSDOC-310 > URL: https://issues.jboss.org/browse/TOOLSDOC-310 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > for some reason https://github.com/jbosstools/jbosstools-documentation/pull/48 removed the latest link assuming latest is used to point to the nightly build. > That is not what it is for. > It is to point to the latest docs made available. > This link (before: http://docs.jboss.org/tools/latest/) was used to point to the last latest documentation. > I believe this should be put back since this is how other docs refer to the latest version. > We could even go so ar to create a docs.jboss.org/tools/4.0, docs.jboss.org/tools/3.3 etc. folder each with their /latest link in them. > Latest links are trivial to make with sftp as part of the release upload anyway thus should be all possible to script if it is too cumbersome to remember. -- 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

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-310) redirect /latest to /reference where the latest released docs can be found

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-310?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TOOLSDOC-310: ---------------------------------------------- [~nickboldt] and [~mmurray] do you have lftp installed ? {code} $ lftp sftp://tools@filemgmt.jboss.org:/docs_htdocs/tools $ ln -s 3.3.0.Final latest-test {code} seems to work for me with respect to symbolic link creation. Much simpler than rsync workaround IMO (and it can be scripted) > redirect /latest to /reference where the latest released docs can be found > -------------------------------------------------------------------------- > > Key: TOOLSDOC-310 > URL: https://issues.jboss.org/browse/TOOLSDOC-310 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > for some reason https://github.com/jbosstools/jbosstools-documentation/pull/48 removed the latest link assuming latest is used to point to the nightly build. > That is not what it is for. > It is to point to the latest docs made available. > This link (before: http://docs.jboss.org/tools/latest/) was used to point to the last latest documentation. > I believe this should be put back since this is how other docs refer to the latest version. > We could even go so ar to create a docs.jboss.org/tools/4.0, docs.jboss.org/tools/3.3 etc. folder each with their /latest link in them. > Latest links are trivial to make with sftp as part of the release upload anyway thus should be all possible to script if it is too cumbersome to remember. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14322) OpenShift wizard displays wrong cloning location

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-14322: -------------------------------------- Summary: OpenShift wizard displays wrong cloning location Key: JBIDE-14322 URL: https://issues.jboss.org/browse/JBIDE-14322 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Stefan Bunciak Fix For: 4.1.0.Beta1 Attachments: clonning.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14322) OpenShift wizard displays wrong cloning location

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14322?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-14322: ----------------------------------- Attachment: clonning.png > OpenShift wizard displays wrong cloning location > ------------------------------------------------ > > Key: JBIDE-14322 > URL: https://issues.jboss.org/browse/JBIDE-14322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Stefan Bunciak > Fix For: 4.1.0.Beta1 > > Attachments: clonning.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13958) OpenShift connection wizard forgets password on IDE restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13958?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13958: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have exactly 1 connection to OpenShift listed in the *OpenShift Explorer* # ASSERT: make sure your connection has the password stored to *Secure Storage* # EXEC: restart Eclipse # ASSERT: make sure no connection is selected in *OpenShift Explorer* # EXEC: hit *Connect to OpenShift* Result: The upcoming connection dialog has the connection selected but the password is not filled. > OpenShift connection wizard forgets password on IDE restart > ------------------------------------------------------------ > > Key: JBIDE-13958 > URL: https://issues.jboss.org/browse/JBIDE-13958 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > Attachments: Connection_withoutPassword_afterIDErestart.png, Connection_withPassword.png > > > I created a new OpenShift connection and selected 'save password' (then was prompted to put in secure storage password). New connection is listed in OpenShift Explorer tab. > If I then click 'Connect to OpenShift' icon, the newly connected connection info is shown together with the password in the password field and the 'save password' check box is selected [attached image - Connection_withPassword.png]. > All good up to this point. > I then closed and reopened the IDE. If I then click 'Connect to OpenShift' icon, the newly connected connection info is shown but the password field is BLANK and the 'save password' check box is NOT selected [attached image - Connection_withoutPassword_afterIDErestart.png]. > This looks like a bug to me - the password field should be completed and the check box selected. > This issue only occurs when clicking 'connect to OpenShift' after an IDE restart. If double-click or expand connection in OpenShift Explorer tab after restart then the connection wizard remembers the password and skips straight to prompting for secure storage password as expected. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14023) investigate and make sure that openshift-java-client test get blue when testing PROD, STG and INT

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14023?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14023: ------------------------------------------ Clayton Coleman answered: {quote} Streamline has been having problems with the ticket cache getting full and overflowing because we don't ever log out the ticket. It's possible that the volume of automated testing against stg was a trigger for this error. It's also possibly unrelated. Streamline is looking at giving us an API that validates the login but does not create a ticket. In the meantime, if you see these failures lets contact the streamline team and check for correlation. {quote} To me this seems like a reasonable explanation. The 500- and auth- errors dont appear frequently any more. Thus I'm closing this issue. > investigate and make sure that openshift-java-client test get blue when testing PROD, STG and INT > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-14023 > URL: https://issues.jboss.org/browse/JBIDE-14023 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > > our matrix-test is testing openshift-java-client against PROD, INT and STG which turns out to be very unreliable. The tests have a lot of issues which I cannot explain (server answers with 500 "internal error", Auth errors etc.). > On the other hand there's now a test that's using a dedicated instance which runs perfectly fine (currently blue). This integration test is included in the openshift test which tests all openshift components: > https://ci.dev.openshift.redhat.com/jenkins/job/broker_extended/ > We need to invetigate why the integration tests against PROD, STG and INT are still unreliable. -- 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

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 2013