July 2014 - jbosstools-issues - Jboss List Archives

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18012?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18012: -------------------------------------- Assignee: Alexey Kazakov > 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 > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > 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)

11 years, 8 months

1
0
0 / 0

[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: 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: Alexey Kazakov > 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-17909) Include Thym 0.1.0 snapshot into jbosstools TP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17909?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17909: --------------------------------------- PR looks good. +1 to release it. > Include Thym 0.1.0 snapshot into jbosstools TP > ---------------------------------------------- > > Key: JBIDE-17909 > URL: https://issues.jboss.org/browse/JBIDE-17909 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Include thym 0.1.0 snapshot release into JBossTools TP > Reason: plugins moved to Eclipse > License and owner: EPL, Eclipse.org > Original repo: http://download.eclipse.org/thym/snapshots/ > JBoss mirror: http://downloads.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNA... > Sources: THyM does not include source bundles/features yet (cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=440753 ) > Affected projects: jbosstools-aerogear > Include in JBDS: Yes > Type of dependency: distribution > List of bundles added/removed: > /org.eclipse.thym > /org.eclipse.thym.android.core > /org.eclipse.thym.android.ui > /org.eclipse.thym.core > /org.eclipse.thym.ios.core > /org.eclipse.thym.ios.ui > /org.eclipse.thym.ui > If applicable: > non-p2 repository: > non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-291) New 4.2.0 alpha of base target required

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-291?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-291. ------------------------------ Fix Version/s: 4.2.0.Alpha6-TP (was: 4.2.0.Beta1-TP) Resolution: Done Please use JBTIS 4.2.0.Alpha6 https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... or http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/ > New 4.2.0 alpha of base target required > --------------------------------------- > > Key: JBTIS-291 > URL: https://issues.jboss.org/browse/JBTIS-291 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.2.0.Alpha5-TP > Reporter: Paul Richardson > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.2.0.Alpha6-TP > > > The locus component of the base target has been respun hence the plugins are appended with v20131024-0922-B66 and no longer v20131024-0922-B64. > Consequently, the target does not resolve correctly due to > {code} > Adding repository https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... > [exec] [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/scorpion/.m2/repository/org/jboss/tools/target-platforms/komodo/1.0.0-SNAPSHOT/komodo-1.0.0-SNAPSHOT-komodo.target: Could not find "org.jboss > .tools.locus.jcip.annotations/1.0.0.Final-v20131024-0922-B64" in the repositories of the current location -> [Help 1] > [exec] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/scorpion/.m2/repository/org/jboss/tools/target-platforms/komodo/1.0.0-SNAPSHOT/komodo-1.0.0-SNAPSHOT-komodo. > target > {code} > Note: komodo is the renamed base target. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-245) Please update JBTIS TP dependencies to Luna Alpha1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-245?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-245: ---------------------------------- Hey Component Developers! A new JBTIS TP is available here [1] based on JBDS Core Beta3/ Eclipse Luna RC4. I'd like to put together a first Luna spin of the IS (JBTIS 4.2.0.Alpha1) next week (Aug 7). If you're not ready yet that's fine - this is an Alpha1 - but we may release it as an Early Access (exact release schedule to be determined). That way we can work out any installation kinks, etc. If you do plan on delivering a Luna update please let me know. Thanks! --paull [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/ ps. Please welcome Gomathi Anandan - she will be working as a PGM starting with JBDSIS. > Please update JBTIS TP dependencies to Luna Alpha1 > -------------------------------------------------- > > Key: JBTIS-245 > URL: https://issues.jboss.org/browse/JBTIS-245 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, savara, switchyard, teiid > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Greetings - welcome to Luna! > An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3]. > I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others. > Thanks! > [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al... > [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17461) Black Screen on iOS simulator when rerun Cordova project

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17461?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-17461: ------------------------------------ Assignee: Gorkem Ercan > Black Screen on iOS simulator when rerun Cordova project > -------------------------------------------------------- > > Key: JBIDE-17461 > URL: https://issues.jboss.org/browse/JBIDE-17461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > > 1. Create and Run Hybrid Mobile project on iOS simulator > ASSERT: App is properly displayed in iOS simulator > 2. Run it again on iOS simulator > ERROR: Only black screen is displayed in iOS simulator -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-17498: -------------------------------------- It is probably emulator is started but never really gets started so it keeps waiting. I think you are basically running to JBIDE-15279 for some reason affecting your emulator. > Can't run default hybrid project on device > ------------------------------------------ > > Key: JBIDE-17498 > URL: https://issues.jboss.org/browse/JBIDE-17498 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Environment: windows > Reporter: Ilya Buziuk > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > Attachments: BUILD SUCCESSFUL.png, Launching.png > > > After choosing *Run As.. -> Run on Android Device* getting exception: > {code} > !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618 > !MESSAGE Ant Build Failed > !STACK 1 > org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448) > at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499) > at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431) > at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163) > at org.apache.tools.ant.Task.perform(Task.java:347) > at org.apache.tools.ant.Target.execute(Target.java:435) > at org.apache.tools.ant.Target.performTasks(Target.java:456) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) > at org.apache.tools.ant.Project.executeTarget(Project.java:1364) > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36) > at org.apache.tools.ant.Project.executeTargets(Project.java:1248) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525) > 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.ant.core.AntRunner.run(AntRunner.java:371) > ... 12 more > !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618 > !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > !STACK 0 > E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv > Cause: The name is undefined. > Action: Check the spelling. > Action: Check that any custom tasks/types have been declared. > Action: Check that any <presetdef>/<macrodef> declarations have taken place. > at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499) > at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431) > at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163) > at org.apache.tools.ant.Task.perform(Task.java:347) > at org.apache.tools.ant.Target.execute(Target.java:435) > at org.apache.tools.ant.Target.performTasks(Target.java:456) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) > at org.apache.tools.ant.Project.executeTarget(Project.java:1364) > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36) > at org.apache.tools.ant.Project.executeTargets(Project.java:1248) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703) > at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525) > 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.ant.core.AntRunner.run(AntRunner.java:371) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265) > at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58) > at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620 > !MESSAGE Build failed... Build artifact does not exist > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17995) Highlighting Angular Tag Attributes and Expressions in JBoss Tools HTML Editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17995?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17995: ----------------------------------- Labels: new_and_noteworthy (was: ) > Highlighting Angular Tag Attributes and Expressions in JBoss Tools HTML Editor > ------------------------------------------------------------------------------ > > Key: JBIDE-17995 > URL: https://issues.jboss.org/browse/JBIDE-17995 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Labels: new_and_noteworthy > Fix For: 4.2.x > > > AngularJS Editor highlights Angular Tag Attributes and Expressions, while JBoss Tools HTML Editor doesn't: > We have to add such a feature into JBoss Tools HTML Editor. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

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

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18023?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-18023: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Arquillian] > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18023 > URL: https://issues.jboss.org/browse/JBIDE-18023 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Arquillian]: 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 Arquillian 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-18025) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Portlet]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18025?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-18025: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Portlet] > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18025 > URL: https://issues.jboss.org/browse/JBIDE-18025 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: portal-gatein > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Portlet]: 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 Portlet 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014