August 2014 - jbosstools-issues - Jboss List Archives

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18018?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18018: -------------------------------------- Assignee: Daniel Azarov (was: Alexey Kazakov) > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [JavaEE] > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18018 > URL: https://issues.jboss.org/browse/JBIDE-18018 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Daniel Azarov > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [JavaEE]: 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 JavaEE 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

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18016?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18016: -------------------------------------- Assignee: Daniel Azarov (was: Alexey Kazakov) > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Base] > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18016 > URL: https://issues.jboss.org/browse/JBIDE-18016 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Daniel Azarov > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Base]: 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 Base 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-18029) find way to track plugins that are not branded

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18029?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18029: -------------------------------------- Assignee: Alexey Kazakov > find way to track plugins that are not branded > ---------------------------------------------- > > Key: JBIDE-18029 > URL: https://issues.jboss.org/browse/JBIDE-18029 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR1, 4.2.x > > > JBIDE-17989 reiterated that plugins that are not branded does not get detected. > Opening separate jira to find a way to make this possible. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17986: --------------------------------------------- assigning this to Fred to look at when he returns based on phone conversation I had with him. >From what he knows there are zero changes between what is used in Luna (signed version) and this latest nightly. In any case, the fix need to be done in Luna SR1, not something JBoss Tools can/should fix unless there is a serious breakage and in that case we still would like to make sure we distribute a version similar signed/packaged as the one in Luna. [~rcd] which stock Luna are you using ? m2e-wtp is in eclipse JavaEE install and thats where the m2e-mavenarchiver comes from. > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Fred Bricon > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17986: ---------------------------------------- Assignee: Fred Bricon (was: Nick Boldt) > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Fred Bricon > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18029) find way to track plugins that are not branded

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-18029: ------------------------------------------- Summary: find way to track plugins that are not branded Key: JBIDE-18029 URL: https://issues.jboss.org/browse/JBIDE-18029 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Reporter: Max Rydahl Andersen JBIDE-17989 reiterated that plugins that are not branded does not get detected. Opening separate jira to find a way to make this possible. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18029) find way to track plugins that are not branded

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18029?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18029: ---------------------------------------- Fix Version/s: 4.2.0.CR1 4.2.x > find way to track plugins that are not branded > ---------------------------------------------- > > Key: JBIDE-18029 > URL: https://issues.jboss.org/browse/JBIDE-18029 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.CR1, 4.2.x > > > JBIDE-17989 reiterated that plugins that are not branded does not get detected. > Opening separate jira to find a way to make this possible. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17508) Cordova config.xml editor stays open with unidentified error after HMT project is deleted

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17508?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17508: --------------------------------------- I cannot replicate it anymore on 4.2.0.Beta3 development release > Cordova config.xml editor stays open with unidentified error after HMT project is deleted > ----------------------------------------------------------------------------------------- > > Key: JBIDE-17508 > URL: https://issues.jboss.org/browse/JBIDE-17508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.2.0.Beta3 > > Attachments: cordova-config.png > > > Now after HMT project is created, config.xml is opened by default for it. Wen project is deleted, config.xml editor stays opened in broken state. > !cordova-config.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17508) Cordova config.xml editor stays open with unidentified error after HMT project is deleted

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17508?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17508: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.x) > Cordova config.xml editor stays open with unidentified error after HMT project is deleted > ----------------------------------------------------------------------------------------- > > Key: JBIDE-17508 > URL: https://issues.jboss.org/browse/JBIDE-17508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.2.0.Beta3 > > Attachments: cordova-config.png > > > Now after HMT project is created, config.xml is opened by default for it. Wen project is deleted, config.xml editor stays opened in broken state. > !cordova-config.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17508) Cordova config.xml editor stays open with unidentified error after HMT project is deleted

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17508?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-17508. --------------------------------- Resolution: Cannot Reproduce Bug > Cordova config.xml editor stays open with unidentified error after HMT project is deleted > ----------------------------------------------------------------------------------------- > > Key: JBIDE-17508 > URL: https://issues.jboss.org/browse/JBIDE-17508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.2.0.Beta3 > > Attachments: cordova-config.png > > > Now after HMT project is created, config.xml is opened by default for it. Wen project is deleted, config.xml editor stays opened in broken state. > !cordova-config.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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 August 2014