[JBoss JIRA] (JBIDE-18012) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18012:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [JST]
Key: JBIDE-18012
URL: https://issues.jboss.org/browse/JBIDE-18012
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR1 [JST]: 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 JST 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)
9 years, 11 months
[JBoss JIRA] (JBIDE-18013) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18013:
----------------------------------
Summary: 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
Priority: Blocker
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.2.6#6264)
9 years, 11 months
[JBoss JIRA] (JBIDE-18014) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18014:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Server]
Key: JBIDE-18014
URL: https://issues.jboss.org/browse/JBIDE-18014
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR1 [Server]: 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 Server 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)
9 years, 11 months
[JBoss JIRA] (JBDS-3114) For JBDS 8.0.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3114:
--------------------------------
Summary: For JBDS 8.0.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
Key: JBDS-3114
URL: https://issues.jboss.org/browse/JBDS-3114
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 8.0.0.CR1
For JBDS 8.0.0.CR1: 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...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 11 months
[JBoss JIRA] (JBIDE-18010) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18010:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
Key: JBIDE-18010
URL: https://issues.jboss.org/browse/JBIDE-18010
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.2.0.CR1
For JBIDE 4.2.0.CR1: 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...]
See also: JBDS-3114
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 11 months
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-15884:
-------------------------------------------
Assignee: Ilya Buziuk (was: Konstantin Marmalyukov)
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 11 months
[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17881:
-------------------------------------
Estimated Difficulty: Medium
> 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
> Priority: Critical
> 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.2.6#6264)
9 years, 11 months
[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17881:
---------------------------------------------
bumping to critical since you as a user have no idea if your app is actually published or not.
> 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
> Priority: Critical
> 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.2.6#6264)
9 years, 11 months
[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17881:
----------------------------------------
Priority: Critical (was: Major)
> 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
> Priority: Critical
> 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.2.6#6264)
9 years, 11 months