September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-17925) application wizard, embed wizard: content assist fields in "Code Anything" adds invalid/non-used values and seem to retain everything

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17925?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17925. --------------------------------- Verified in JBDS 8.0.0.CR1 build ID B201. > application wizard, embed wizard: content assist fields in "Code Anything" adds invalid/non-used values and seem to retain everything > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17925 > URL: https://issues.jboss.org/browse/JBIDE-17925 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Labels: application_wizard, embed_wizard > Fix For: 4.2.0.CR1 > > > while looking at JBIDE-16904 I found that > A) all values are stored into content assist history when focus lost - incl. invalid and non valid values > B) the field does not update its list unless window recreated > C) the list keeps growing - seem to be no limit. I stopped after reaching 20 values of garbage :) > I would expect only values that the validator approves to be saved and could even go so far to only store the one that actually gets used on finish. > All my intermediate typing should not be considered okey for use IMO -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12276) Research possibilities to use XULRunner >= 2.0, or WebKit/IE in VPE

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12276?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-12276. ------------------------------- > Research possibilities to use XULRunner >= 2.0, or WebKit/IE in VPE > -------------------------------------------------------------------- > > Key: JBIDE-12276 > URL: https://issues.jboss.org/browse/JBIDE-12276 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Reporter: Yahor Radtsevich > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > Prototype of an HTML editor using JavaScript for Eclipse<->browser interaction is created. > The source is available [here|http://anonsvn.jboss.org/repos/jbosstools/workspace/yradtsevich/simp...]. YouTube demo is [here|http://youtu.be/qeFoD2ka0b8]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17971) Domain wizard: should not be able to edit domain members as long as we did not create the domain

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17971?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17971. --------------------------------- Verified in JBDS 8.0.0.CR1 build ID B201. > Domain wizard: should not be able to edit domain members as long as we did not create the domain > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17971 > URL: https://issues.jboss.org/browse/JBIDE-17971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Catherine Robson > Assignee: Andre Dietisheim > Labels: domain_wizard, uxtest > Fix For: 4.2.0.CR1 > > Attachments: null-link.png, OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png > > > When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error: > https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123... > !null-link.png! > This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first. > Suggest that we change the create domain dialog to do the following: > 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached ) > 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached) > Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12844) VPE tests are slowing down with time

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12844?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-12844. ------------------------------- > VPE tests are slowing down with time > ------------------------------------ > > Key: JBIDE-12844 > URL: https://issues.jboss.org/browse/JBIDE-12844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, visual-page-editor-templates > Affects Versions: 4.0.0.Alpha2 > Reporter: Yahor Radtsevich > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > When VPE tests are run, every next test is executed slower and slower. > Looks like there is a resource leak. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8286) Prevent loading org.jboss.tools.vpe plugin on non-supported platforms

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8286?page=com.atlassian.jira.plugin... ] Vlado Pakan closed JBIDE-8286. ------------------------------ > Prevent loading org.jboss.tools.vpe plugin on non-supported platforms > --------------------------------------------------------------------- > > Key: JBIDE-8286 > URL: https://issues.jboss.org/browse/JBIDE-8286 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 3.2.0.CR1 > Reporter: Maxim Areshkau > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > Prevent loading org.jboss.tools.vpe plugin on non-supported platforms(OSX x86_64 and Win x86_64) for now. > It can be done via Eclipse-PlatformFilter line in MANIFEST.MF. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18013) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [VPE]

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18013?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18013. ------------------------------- Verified with JBDS 8.0.0.CR1-v20140831-0335-B201 > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [VPE] > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18013 > URL: https://issues.jboss.org/browse/JBIDE-18013 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [VPE]: Please perform the following *2* tasks: > 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below. > Be sure to also include *translated* files, where they exist. > *java files* > {code:title=*.java} > Copyright (c) 2010-2014 Red Hat, Inc. and others. > {code} > *html files* > {code:title=about.html} > © 2014 Red Hat, Inc. All rights reserved > {code} > *properties files* > {code:title=about.properties} > Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved > {code} > {code:title=about_fr.properties} > Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s. > {code} > {code:title=feature.properties} > Copyright (c) 2010-2014 Red Hat, Inc. and others. > {code} > {code:title=Messages.properties} > # Copyright (c) 2014 Red Hat, Inc. and others. > {code} > *xsd files* > {code:title=jboss-as-naming_1_3.xsd} > Copyright 2014, Red Hat, Inc., and individual contributors > {code} > 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*. > Be sure to also include *translated* files, where they exist. > *This step is particularly important for new plugins and features that have been added recently.* > Depending on how your plugin is configured you should see something like this in your *plugin.properties* files: > {code}BundleName = JMX Resources Bundle > BundleProvider = JBoss by Red Hat{code} > or > {code}Bundle-Name.0 = JBossTools Archives Core Plugin > Bundle-Vendor.0 = JBoss by Red Hat{code} > Then in your MANIFEST.MF files, you will reference these variables like this. > *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file! > {code}Bundle-Localization: plugin > Bundle-Name: %BundleName > Bundle-Vendor: %BundleProvider{code} > or > {code}Bundle-Localization: plugin > Bundle-Name: %Bundle-Name.0 > Bundle-Vendor: %Bundle-Vendor.0{code} > For features, check that your *feature.properties* file contains good values too: > {code}featureName=JMX Console > featureProvider=JBoss by Red Hat{code} > or > {code}featureName=JBoss Archives Tools > providerName=JBoss by Red Hat{code} > Then in your feature.xml files, you will reference these variables like this: > {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code} > or > {code}<feature label="%featureName" provider-name="%providerName" ...>{code} > 3. If you would like QE to review your changes, please *Resolve* this JIRA when done. > 4. If you do not require QE to review your changes, please *Close* this JIRA when done. > 5. If you have any questions, please contact [~nickboldt]. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18027) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [LiveReload]

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18027?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18027. ------------------------------- Verified with JBDS 8.0.0.CR1-v20140831-0335-B201 > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [LiveReload] > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18027 > URL: https://issues.jboss.org/browse/JBIDE-18027 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [LiveReload]: Please perform the following *2* tasks: > 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below. > Be sure to also include *translated* files, where they exist. > *java files* > {code:title=*.java} > Copyright (c) 2010-2014 Red Hat, Inc. and others. > {code} > *html files* > {code:title=about.html} > © 2014 Red Hat, Inc. All rights reserved > {code} > *properties files* > {code:title=about.properties} > Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved > {code} > {code:title=about_fr.properties} > Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s. > {code} > {code:title=feature.properties} > Copyright (c) 2010-2014 Red Hat, Inc. and others. > {code} > {code:title=Messages.properties} > # Copyright (c) 2014 Red Hat, Inc. and others. > {code} > *xsd files* > {code:title=jboss-as-naming_1_3.xsd} > Copyright 2014, Red Hat, Inc., and individual contributors > {code} > 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*. > Be sure to also include *translated* files, where they exist. > *This step is particularly important for new plugins and features that have been added recently.* > Depending on how your plugin is configured you should see something like this in your *plugin.properties* files: > {code}BundleName = JMX Resources Bundle > BundleProvider = JBoss by Red Hat{code} > or > {code}Bundle-Name.0 = JBossTools Archives Core Plugin > Bundle-Vendor.0 = JBoss by Red Hat{code} > Then in your MANIFEST.MF files, you will reference these variables like this. > *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file! > {code}Bundle-Localization: plugin > Bundle-Name: %BundleName > Bundle-Vendor: %BundleProvider{code} > or > {code}Bundle-Localization: plugin > Bundle-Name: %Bundle-Name.0 > Bundle-Vendor: %Bundle-Vendor.0{code} > For features, check that your *feature.properties* file contains good values too: > {code}featureName=JMX Console > featureProvider=JBoss by Red Hat{code} > or > {code}featureName=JBoss Archives Tools > providerName=JBoss by Red Hat{code} > Then in your feature.xml files, you will reference these variables like this: > {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code} > or > {code}<feature label="%featureName" provider-name="%providerName" ...>{code} > 3. If you would like QE to review your changes, please *Resolve* this JIRA when done. > 4. If you do not require QE to review your changes, please *Close* this JIRA when done. > 5. If you have any questions, please contact [~nickboldt]. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16174) Server Adapter: Remove unused legacy classes

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16174?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16174. --------------------------------- There are no longer such classes. > Server Adapter: Remove unused legacy classes > -------------------------------------------- > > Key: JBIDE-16174 > URL: https://issues.jboss.org/browse/JBIDE-16174 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: cleanup, server_adapter > Fix For: 4.2.0.CR1 > > > There are unused legacy classes that we should remove: > * OpenShiftServerBinaryBehaviourDelegate > * OpenShiftServerBinaryPublishMethod -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18127) Ionic palette: wizard "New Button" has wrong image

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18127?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18127. ------------------------------- Verified with JBDS 8.0.0.CR1-v20140831-0335-B201 > Ionic palette: wizard "New Button" has wrong image > -------------------------------------------------- > > Key: JBIDE-18127 > URL: https://issues.jboss.org/browse/JBIDE-18127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.CR1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: NewButtonWizard.png > > > Wizard has jQueryMobile Button image. We have special image for Ionic palette. > !NewButtonWizard.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-17881. --------------------------------- Verified in JBDS 8.0.0.CR1 build B201. > Publishing jobs are hanging in Progress view and in bottom right corner. > ------------------------------------------------------------------------ > > Key: JBIDE-17881 > URL: https://issues.jboss.org/browse/JBIDE-17881 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: server_adapter > Fix For: 4.2.0.CR1 > > Attachments: finished_job.png, hanging_finished_job.png > > > Publishing jobs are shown in Progress view. In previous versions they were removed from this view after finishing the job. Now they are still hanging there with status "Finished" and after removal and reopen Progress view they are still here. Instead of reopen view also Remove all Finished Jobs (double gray crosses in view) works fine too. > !finished_job.png! > Running job is also shown in bottom right corner. After finishing it is still hanging there. > !hanging_finished_job.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 September 2014