July 2014 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------------------ [~maxandersen] I mean running browsersim *in Eclipse process*(which integration test does and maybe must be done for tests) requires efxclipse. We don't need it cause we run browsersim on its own process. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17990: --------------------------------------------- [~hwellmann] this statement has not been true for the last 3-4 years: {quote}Seeing that Eclipse never really deletes any updated plugins{quote} Eclipse does actually these days "garbage collect" plugins that is not used by the latest updates. Just a FYI > Organize imports does not work for Maven dependencies > ----------------------------------------------------- > > Key: JBIDE-17990 > URL: https://issues.jboss.org/browse/JBIDE-17990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.Beta3 > Environment: Oracle JDK 1.8.0_05, Eclipse Luna > Reporter: Harald Wellmann > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize Imports is broken in my workspace. More precisely, I'm referring to the capability of finding the package a class lives in and generating the {{import}} directive with the FQCN. > The corresponding Quick Fix is also broken. > It only works for class names from sources in the workspace, it no longer works for class names from a Maven dependency in the local repository. > This is even worse than JBIDE-17724, I'll have to revert to Beta2. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16575: --------------------------------------------- eh - why does browsersim require efxclipse ? we dont have that installed when running jbosstools ? > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-18028) IMPORTANT/URGENT etc. from asciidoc gets no styling

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-18028: ------------------------------------------- Summary: IMPORTANT/URGENT etc. from asciidoc gets no styling Key: JBIDE-18028 URL: https://issues.jboss.org/browse/JBIDE-18028 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: website Reporter: Max Rydahl Andersen the adminitions documented here http://asciidoctor.org/docs/asciidoc-writers-guide/#admonitions renders without any styling on website/blog. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17913) Users don't notice the software update tab - can we make it more visibile on the front page ?

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17913?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-17913: ------------------------------------- In theory, there should be a Switchyard and Teiid Project wizard/archetype available as well. > Users don't notice the software update tab - can we make it more visibile on the front page ? > --------------------------------------------------------------------------------------------- > > Key: JBIDE-17913 > URL: https://issues.jboss.org/browse/JBIDE-17913 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Max Rydahl Andersen > Assignee: Burr Sutter > Fix For: 4.2.0.CR1 > > > We are getting complaints users does not notice that they can install things like integration stack from software update page. > Could we make this more clear onthe front page ? > Maybe remove the ticketmonster example image and put "highlights" from central on this page instead ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18001) Consider using a more pale shade of yellow to identify Early Access content in JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18001?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18001: ----------------------------------- Assignee: Nick Boldt (was: Mickael Istria) > Consider using a more pale shade of yellow to identify Early Access content in JBoss Central > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18001 > URL: https://issues.jboss.org/browse/JBIDE-18001 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, discovery > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.2.0.CR1 > > > From [~maxandersen] (sic): > {quote} > (2014-07-30 09:43:42) maxandersen: nickboldt1: yes but having a paler yellow actually sounds like better than what is there now > (2014-07-30 09:47:42) maxandersen: nickboldt1: suggestions to make the bigy ellow we got now very welcome. thus yes if we dont have a jira for better suggestion for this alrady > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18001) Consider using a more pale shade of yellow to identify Early Access content in JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18001?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18001: ---------------------------------------- I have to admit I don't care much about how much yellow is the yellow, but implementation looks good, so +0. > Consider using a more pale shade of yellow to identify Early Access content in JBoss Central > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18001 > URL: https://issues.jboss.org/browse/JBIDE-18001 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, discovery > Affects Versions: 4.2.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.2.0.CR1 > > > From [~maxandersen] (sic): > {quote} > (2014-07-30 09:43:42) maxandersen: nickboldt1: yes but having a paler yellow actually sounds like better than what is there now > (2014-07-30 09:47:42) maxandersen: nickboldt1: suggestions to make the bigy ellow we got now very welcome. thus yes if we dont have a jira for better suggestion for this alrady > {quote} -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17909?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17909: ---------------------------------------- PR merged. Build in progress: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... > 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] (JBDS-3058) Workaround to JBDS-3054 causes the blank/white welcome screen bug to return

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3058?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-3058. ------------------------------ Release Notes Text: This is no longer reproducible. Resolution: Done > Workaround to JBDS-3054 causes the blank/white welcome screen bug to return > --------------------------------------------------------------------------- > > Key: JBDS-3058 > URL: https://issues.jboss.org/browse/JBDS-3058 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: welcome > Affects Versions: 8.0.0.Beta2 > Environment: JBDS 8.0.beta2.respin-a > RHEL 6.5 > OpenJDK 1.7 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 8.0.x > > Attachments: workaround_bug.png > > > If the workaround defined in JBDS-3054 is used (-Dorg.jboss.tools.vpe.loadxulrunner=false), then the welcome screen becomes blank. See attached screenshot. -- 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: 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: Alexey Kazakov > 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

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