[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-16575:
-------------------------------------
Those are examples of what can be tested there are more scenarios.
1. Done
2. I can pass the same parameters as when BrowserSim starts as external process I guess didnt' check latest version of BrowserSim but was working with older versions
3. The same situation as in point 2.
Don't worry about test scenarios implementations I will take care about it that is what I'm supposed to do.
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18031) Widget disposed error when toggling EA features on/off
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18031:
----------------------------------
Summary: Widget disposed error when toggling EA features on/off
Key: JBIDE-18031
URL: https://issues.jboss.org/browse/JBIDE-18031
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, discovery
Affects Versions: 4.2.0.CR1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.2.0.CR1
1. Install JBT 4.2.0.Beta3 or CR1 (nightly) into Eclipse Luna eclipse-jee-luna-R-linux.gtk.x86_64.tar.gz
2. Launch JBT, and Central will open by itself (default)
3. Select Software/Update tab
4. Enable the "Enable Early Access" box, and click "Yes" to accept.
5. Disable the "Enable Early Access" box, and click "OK" to acknowledge.
(So far, so good.)
6. Close Central, then reopen it from the coolbar icon.
7. Repeat steps 4 and 5. This time, you will see errors such as this:
{code}
Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
{code}
{code}
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4441)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.SWT.error(SWT.java:4327)
at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:562)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$1.propertyChange(JBossCentralEditor.java:533)
at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:382)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:378)
at org.eclipse.ui.preferences.ScopedPreferenceStore$2.preferenceChange(ScopedPreferenceStore.java:197)
at org.eclipse.core.internal.preferences.EclipsePreferences$3.run(EclipsePreferences.java:896)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:899)
at org.eclipse.core.internal.preferences.EclipsePreferences.putBoolean(EclipsePreferences.java:926)
at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:553)
at org.jboss.tools.central.editors.SoftwarePage.access$11(SoftwarePage.java:506)
at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:236)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
{code}
eclipse.buildId=4.4.0.I20140606-1215
java.version=1.8.0
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation -Dorg.jboss.tools.vpe.loadxulrunner=false
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product -clean -showLocation -data /home/nboldt/eclipse/workspace-clean44 -consolelog -console -debug -Dorg.jboss.tools.vpe.loadxulrunner=false
{code}
8. Restart Eclipse. Errors go away. (Steps 4-5 work as expected.)
9. Close and re-open Central. Errors are back. (Steps 4-5 throw errors.)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-16575 at 8/1/14 8:43 AM:
------------------------------------------------------------------------
{quote}tests running BrowserSim via clicking on Toolbar Button in Eclipse checking if BrowserSim is able to run, opens selected web page and displays errors to Eclipse console - working now also with JavaFX
{quote}
This tests works becuase browsersim runs as external process
{quote}
displaying javascript errors to Eclipse console
displaying source code of web page opened in Browsersim in Eclipse
livereload functionality i.e. resource changed and saved in Eclipse is changed in BrowserSIm
{quote}
1. if I understand you correct communication with Eclipse console is already done, right?
2. this way browsersim must be runned as external process, otherwise opening page source will now work
3. must be a problem, don't know exactly
was (Author: kmarmaliykov):
{quote}tests running BrowserSim via clicking on Toolbar Button in Eclipse checking if BrowserSim is able to run, opens selected web page and displays errors to Eclipse console - working now also with JavaFX
{quote}
This tests works becuase browsersim runs as external process, doesn't it?
{quote}
displaying javascript errors to Eclipse console
displaying source code of web page opened in Browsersim in Eclipse
livereload functionality i.e. resource changed and saved in Eclipse is changed in BrowserSIm
{quote}
1. if I understand you correct communication with Eclipse console is already done, right?
2. this way browsersim must be runned as external process, otherwise opening page source will now work
3. must be a problem, don't know exactly
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17919) Snapshot wizard: snapshot file name is not refreshed upon changes between full and deployment type
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17919?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17919:
----------------------------------
Description:
When trying to create a new snapshot of FULL or DEPLOYMENT type after creating a snapshot earlier, there is no change of file name for the snapshot. It's still the same file name as it was for the snapshot created right before.
I think there was intention to let user overwrite previously created snapshot. But this brings complications because of snapshot type. We should not override FULL snapshot with DEPLOYMENT snapshot. I think also, that there should not be overriding at all, but it should be distinguished as it is (after workaround) by number of snapshot.
was:
When trying to create a new snapshot of type FULL or DEPLOYMENT after creating a snapshot earlier, there is no change of file name for the snapshot. It's still the same containing full in file name and if needed also a number of snapshot.
I think there was intention to let user overwrite previously created snapshot. But this brings complications because of snapshot type. We should not override FULL snapshot with DEPLOYMENT snapshot. I think also, that there should not be overriding at all, but it should be distinguished as it is (after workaround) by number of snapshot.
> Snapshot wizard: snapshot file name is not refreshed upon changes between full and deployment type
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17919
> URL: https://issues.jboss.org/browse/JBIDE-17919
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: snapshot_wizard
> Fix For: 4.2.0.CR1
>
>
> When trying to create a new snapshot of FULL or DEPLOYMENT type after creating a snapshot earlier, there is no change of file name for the snapshot. It's still the same file name as it was for the snapshot created right before.
> I think there was intention to let user overwrite previously created snapshot. But this brings complications because of snapshot type. We should not override FULL snapshot with DEPLOYMENT snapshot. I think also, that there should not be overriding at all, but it should be distinguished as it is (after workaround) by number of snapshot.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18026) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18026?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18026:
------------------------------------
[~ppalaga] Yes, this can wait until more pressing issues are solved, in order to avoid merge conflicts.
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18026
> URL: https://issues.jboss.org/browse/JBIDE-18026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Freemarker]: 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 Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-16575:
------------------------------------------------
{quote}tests running BrowserSim via clicking on Toolbar Button in Eclipse checking if BrowserSim is able to run, opens selected web page and displays errors to Eclipse console - working now also with JavaFX
{quote}
This tests works becuase browsersim runs as external process, doesn't it?
{quote}
displaying javascript errors to Eclipse console
displaying source code of web page opened in Browsersim in Eclipse
livereload functionality i.e. resource changed and saved in Eclipse is changed in BrowserSIm
{quote}
1. if I understand you correct communication with Eclipse console is already done, right?
2. this way browsersim must be runned as external process, otherwise opening page source will now work
3. must be a problem, don't know exactly
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18026) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18026?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18026:
-------------------------------
Assignee: Max Rydahl Andersen
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Freemarker]
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18026
> URL: https://issues.jboss.org/browse/JBIDE-18026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Freemarker]: 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 Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18024) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18024?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18024:
--------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Central]
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18024
> URL: https://issues.jboss.org/browse/JBIDE-18024
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Central]: 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 Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-2843) AngularJS Usability
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ]
Vlado Pakan commented on JBDS-2843:
-----------------------------------
[~akazakov] please are they going to be made UI changes regarding to AngularJS support in JBDS CR1? Just checking if I should expect some changes to AngularJS Code Assist support in CR1 or I will test it the same way as for JBDS 8.0.0.Beta3. Thanks for answer.
> AngularJS Usability
> -------------------
>
> Key: JBDS-2843
> URL: https://issues.jboss.org/browse/JBDS-2843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsp/jsf/xml/html source editing, requirements
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Related to JBIDE-14597
> Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
> Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
> Phase 3) Code Assist (cntrl-space) in .html
> Phase 4) Code Assist (cntrl-space) in .js
> Phase 5) Widget Palette (like our jQuery Mobile palete)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months