October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15597. --------------------------------- Verified in JBDS 7.1.0.Beta1 Build id: Beta1-v20131026-0928-B470 > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Alpha1, 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Assignee: Andre Dietisheim > Priority: Blocker > Labels: new_and_noteworthy, respin-a > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: app-config-page.png, edit-environment-variables.png, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, jira-JBIDE-15598-wizard-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg, openshift.ogv > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15368) jbosstools-server has API Compatibility problem

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15368?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15368. --------------------------------- Closing, since not verifiable by QA. > jbosstools-server has API Compatibility problem > ----------------------------------------------- > > Key: JBIDE-15368 > URL: https://issues.jboss.org/browse/JBIDE-15368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Labels: api-compatibility > Fix For: 4.1.1.Alpha1 > > > Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem: > "The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added". > According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2 > || Interface change || Conditions || Compatibility || > |Add API field|If interface not implementable by Clients | Binary compatible| > |Add API field|If interface implementable by Clients| Breaks compatibility (2)| > (2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15651) EAP 6.2 cannot be connected to in MBean Explorer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15651?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15651. --------------------------------- Verified in JBDS 7.1.0.Beta1a B470 > EAP 6.2 cannot be connected to in MBean Explorer > ------------------------------------------------ > > Key: JBIDE-15651 > URL: https://issues.jboss.org/browse/JBIDE-15651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.1.1.Alpha2 > Environment: JBDS 7.1.0.Alpha2 B431 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.1.1.Beta1 > > > When you start EAP 6.2.0.ER4 (or ER5) added manually and then try Show in -> MBean Explorer, it will show the server as [disconnected] and the server won't connect. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15751) default server name for eap6.2 includes string 6.1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15751?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15751. --------------------------------- Verified in JBDS 7.1.0.Beta1a B470 > default server name for eap6.2 includes string 6.1 > -------------------------------------------------- > > Key: JBIDE-15751 > URL: https://issues.jboss.org/browse/JBIDE-15751 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.1.1.Beta1 > > > A simple missed plus sign in a display string. > New server wizard, checking eap6.1+ server type, has default name of eap6.1. This should be 6.1+ -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15774) Runtime edit window shows EAP 6.1 instead of EAP 6.1+

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15774?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15774. --------------------------------- OK, I didn't know that it's the exact same string used here as in the other jira. And I verified it shows up correctly as 6.1+ in JBDS 7.1.0.Beta1a B470. Closing. > Runtime edit window shows EAP 6.1 instead of EAP 6.1+ > ----------------------------------------------------- > > Key: JBIDE-15774 > URL: https://issues.jboss.org/browse/JBIDE-15774 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0.Beta1 B441 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.1.1.Beta1 > > Attachments: eap-6.2-runtime.png > > > In line with JBIDE-15614 and JBIDE-15751, this should be updated, too: > When I detect EAP 6.2 using runtime detection, it rightly shows the type as EAP 6.2, but then when I check the runtime later, it displays EAP 6.1 at the top: > !eap-6.2-runtime.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

12 years, 5 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-2797. ------------------------------- OK, in that case I am closing the JIRA now - JBDS 7.1.0.Beta1 includes this fix. [~dgolovin] please create the jira for removal of unused code. > .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: Denis Golovin > Priority: Critical > Labels: respin-a > Fix For: 7.1.0.Beta1 > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2768: --------------------------------------- [~nickboldt], PR submitted: https://github.com/jbdevstudio/jbdevstudio-website/pull/43 I've tried to keep it simple but use RH writing style. Adapt as necessary. > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > Attachments: JBDS2768_simplified.png > > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > And that links to instructions on community site: > http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2649) Installer shouldn't contain Google Eclipse features/plugins

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2649?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2649: ----------------------------- CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? > Installer shouldn't contain Google Eclipse features/plugins > ----------------------------------------------------------- > > Key: JBDS-2649 > URL: https://issues.jboss.org/browse/JBDS-2649 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.1.GA > Reporter: Fred Bricon > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.Alpha1 > > Attachments: jbds2649-maven-gwt-no-longer-installed-by-default.png, JBDS2649.patch.txt > > > jbdevstudio-product-eap-universal-7.0.0.Beta1-v20130526-0839-B241.jar contains the google plugins, it shouldn't : > !http://content.screencast.com/users/fbricon/folders/Jing/media/a7764301-6ad0-4631-b289-1e35683e3fb2/2013-05-29_0949.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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2649) Installer shouldn't contain Google Eclipse features/plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2649?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2649: ----------------------------- CDW release: ? Status: New (was: New) Target Release: 8.0.0.GA > Installer shouldn't contain Google Eclipse features/plugins > ----------------------------------------------------------- > > Key: JBDS-2649 > URL: https://issues.jboss.org/browse/JBDS-2649 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.1.GA > Reporter: Fred Bricon > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.Alpha1 > > Attachments: jbds2649-maven-gwt-no-longer-installed-by-default.png, JBDS2649.patch.txt > > > jbdevstudio-product-eap-universal-7.0.0.Beta1-v20130526-0839-B241.jar contains the google plugins, it shouldn't : > !http://content.screencast.com/users/fbricon/folders/Jing/media/a7764301-6ad0-4631-b289-1e35683e3fb2/2013-05-29_0949.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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assis for AngularJS expressions in html files

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15714: ---------------------------------------- Prototype demo of AngularJS content assist working via JBoss Tools Livereload plugin- http://www.screenr.com/F7bH > Dynamic content assis for AngularJS expressions in html files > ------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.x > > -- 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, 5 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