August 2014 - jbosstools-issues - Jboss List Archives

[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)

[ https://issues.jboss.org/browse/JBIDE-18010?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18010: ------------------------------------ No, I haven't talked to legal, but I suspect that if the code states that the original contribution comes from IBM (and others) in 2013, then it should be fine to state that the CURRENT copyright is {quote}Copyright (c) 2013-2014 Red Hat, Inc. and others.{quote} > 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 > Assignee: Nick Boldt > Priority: Blocker > Labels: task > 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)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17524) BrowserSim: not all source is shown for external URL

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17524?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17524: --------------------------------------- [~ibuziuk], thanks for reacting to that email! :) I will check this tomorrow unless somebody else beats me to it. > BrowserSim: not all source is shown for external URL > ---------------------------------------------------- > > Key: JBIDE-17524 > URL: https://issues.jboss.org/browse/JBIDE-17524 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > Attachments: Screenshot 2014-07-24 16.32.11.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17524) BrowserSim: not all source is shown for external URL

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17524?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17524: ------------------------------------- [~jpeterka], [~rawagner], [~mmalina] hello guys. In terms of the last "Getting ready for CR1: Nightly builds and bug verification" mail it would be really great if you could verify this bug on nightly. Hope there will be no surprises during CR1 ;-) NOTE: JBIDE-17718 and JBIDE-17587 are also affected by the fix, so please verify them in order to prevent potential breakage Thanks in advance! > BrowserSim: not all source is shown for external URL > ---------------------------------------------------- > > Key: JBIDE-17524 > URL: https://issues.jboss.org/browse/JBIDE-17524 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > Attachments: Screenshot 2014-07-24 16.32.11.png > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18041) Visual editor: refresh type preference is not saved.

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-18041: ---------------------------------------------- Summary: Visual editor: refresh type preference is not saved. Key: JBIDE-18041 URL: https://issues.jboss.org/browse/JBIDE-18041 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core Affects Versions: 4.2.0.Beta3 Reporter: Konstantin Marmalyukov Type of refresh(refresh-on-change or refresh-on-save) is not saved after editor(or view) is closed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18041) Visual editor: refresh type preference is not saved.

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18041?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-18041: ------------------------------------------- Fix Version/s: 4.2.0.CR1 > Visual editor: refresh type preference is not saved. > ---------------------------------------------------- > > Key: JBIDE-18041 > URL: https://issues.jboss.org/browse/JBIDE-18041 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > Type of refresh(refresh-on-change or refresh-on-save) is not saved after editor(or view) is closed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18041) Visual editor: refresh type preference is not saved.

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18041?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-18041: ---------------------------------------------- Assignee: Konstantin Marmalyukov > Visual editor: refresh type preference is not saved. > ---------------------------------------------------- > > Key: JBIDE-18041 > URL: https://issues.jboss.org/browse/JBIDE-18041 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > Type of refresh(refresh-on-change or refresh-on-save) is not saved after editor(or view) is closed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ] Xavier Coulon edited comment on JBDS-2847 at 8/5/14 8:17 AM: ------------------------------------------------------------- hello [~mmalina], You should be able to start working on this issue right now. Please note that the javaee7 samples on github use Groovy for some tests with Spock (as declared in the parent pom.xml), so you may have issues with Eclipse out-of-the-box. You have two options: - install the Groovy/JDT plugin - comment out the maven-compiler-plugin that uses the groovy-eclipse-compiler, so you don't need to install anything on your JBDS - the parent pom.xml needs to be updated manually, by adding the following line {quote} @@ -264,6 +264,7 @@ <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-eclipse-compiler</artifactId> <version>2.8.0-01</version> + <extensions>true</extensions> {quote} - then import the projects you want to test using {{File>Import>Existing Maven Projects}}. If you have errors during the import, such as: {quote} - Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile (execution: default-testCompile, phase: test-compile) - Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (execution: default- compile, phase: compile) {quote} then just mark them as permanently ignored. If the projects import ends up with misconfigured build paths, then remove the projects, then from the command line, remove the .project and .classpath files, along with the .settings folder in *each* project, then import the projects again. This _should_ work fine. [~maxandersen] also asked that we should test against Wildfly 8.1 using Java 8 (as mentionned in JBDS-2919). was (Author: xcoulon): hello [~mmalina], You should be able to start working on this issue right now. Please note that the javaee7 samples on github use Groovy for some tests with Spock (as declared in the parent pom.xml), so you may have issues with Eclipse out-of-the-box. You have two options: - install the Groovy/JDT plugin - comment out the maven-compiler-plugin that uses the groovy-eclipse-compiler, so you don't need to install anything on your JBDS [~maxandersen] also asked that we should test against Wildfly 8.1 using Java 8 (as mentionned in JBDS-2919). > Java EE 7 Tech Preview > ---------------------- > > Key: JBDS-2847 > URL: https://issues.jboss.org/browse/JBDS-2847 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.CR1 > > > Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly > https://github.com/javaee-samples/javaee7-samples > They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17543) Investigate JUnit test duration

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17543?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-17543. ----------------------------------- > Investigate JUnit test duration > --------------------------------- > > Key: JBIDE-17543 > URL: https://issues.jboss.org/browse/JBIDE-17543 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > > Seems like test duration is sometimes way too high, and looking at the logs, the JAX-RS Model seems to be build 2x before a test. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17466) Cleanup obsolete code after replacement of JAX-RS Wizard(s)

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17466?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-17466. ----------------------------------- > Cleanup obsolete code after replacement of JAX-RS Wizard(s) > ----------------------------------------------------------- > > Key: JBIDE-17466 > URL: https://issues.jboss.org/browse/JBIDE-17466 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.Beta3 > > Attachments: Screen Shot 2014-06-04 at 15.17.33.png > > > Some classes and resouces related to the former "Create sample RESTful Service" wizard were moved from {{org.jboss.tools.ws.ui}} to {{org.jboss.tools.ws.jaxrs.ui}} as part of JBIDE-9223, then replaced with other classes and resources as part of JBIDE-17151, but some classes still required by the "Simple Web Service" wizard were lost in the process, as reported in JBIDE-17459. The most straightforward solution for JBT 4.2.0.Beta2 was to restore those files and simply comment out the extension for the "Create sample RESTful Service" in {{org.jboss.tools.ws.ui/plugin.xml}} > But now it is time to do some cleanup. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15520) Clean UI and Core dependencies

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15520?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15520. ----------------------------------- > Clean UI and Core dependencies > ------------------------------ > > Key: JBIDE-15520 > URL: https://issues.jboss.org/browse/JBIDE-15520 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > > Move all *.ui.* dependencies from jaxrs.core to jaxrs.ui -- 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