November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16161: ---------------------------------------- {quote}If you try it locally, you will see that a lot of services aren't started. The tests are started, but the most of them either freeze or fail.{quote} Ok, so some pieces of code may depend on PlatformAdmin. Do you know if those are inside JBT or Eclipse? Anyway, using PlatformAdmin is somehow deprecated in favor of Wiring API, We should migrate our code, and the bundles we depend on, to this Wiring API if possible {quote}The org.eclipse.tycho.surefire.osgibooter plugin won't start without the PlatformAdmin service, so a lot of the tests won't be run correctly.{quote} That's not exactly true. The PlatformAdmin is only used for login purpose, if it's not there surefire.osgibooter will continue and run tests (cf quote previously "The tests are started"). I've seen some test suite working without PlatformAdmin, I'd like ours to behave the same way, and rely on more sustainable API (Wiring API). {quote}I can't find any components that build{quote} See for example https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... {quote}Adding the o.e.e4.rcp feature would be the easiest solution{quote} I agree, but I feel it's better to look for the more sustainable solution (Wiring API) instead of the easiest one. > Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna > ------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Mickael Istria > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16161: --------------------------------------- {quote} If the test actually depend on PlatformAdmin, I'd rather have them reworked to depend on the OSGi Wiring API which is a standard provided by Luna. {quote} The org.eclipse.tycho.surefire.osgibooter plugin depends on PlatformAdmin. It doesn't matter if some test depends on it. > Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna > ------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Mickael Istria > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16161: --------------------------------------- {quote} You report is more focused on a solution than on the issue: In the case of base component, how does it fail? How do you see the error? Are tests at least starting? {quote} If you take a look at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... you will see the build is aborted after two hour timeout. If you try it locally, you will see that a lot of services aren't started. The tests are started, but the most of them either freeze or fail. For instance, CompatibilityEditor isn't initialized and all the tests that open a JBoss editor fail with a NPE. {quote} It seems to me that Tycho tests can generally run without PlatformAdmin being available (it probably depends on some test specificities). {quote} See http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-surefire/... The org.eclipse.tycho.surefire.osgibooter plugin won't start without the PlatformAdmin service, so a lot of the tests won't be run correctly. The following message can be often seen in the log: "Could not acquire PlatformAdmin server". {quote} Most other components have successfully run their tests without change in parent pom. I'm not sure changing surefire configuration is the optimal solution. {quote} I can't find any components that build on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... The most of them require the base component that isn't built. Adding the o.e.e4.rcp feature would be the easiest solution. It is also possible to create a separate feature containing the compatibility fragment and include it to the main build or to every test separately. You may also want to take a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=407097 > Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna > ------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Mickael Istria > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16134) CordovaSim should start the livereload server

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16134?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16134: ------------------------------------------------ I guess there is a lot of controversy around that issue: 1. [~gercan], your options requires dependency from browsersim to livereload. Assuming that BrowserSim/CordovaSim can be installed without livereload. I don't think creating dependencies is a good idea. 2. [~maxandersen], it make sense, but don't you think this dialog would be annoying? And what should be done after this dialog? Should we "uncheck" livereload option in browsersim after that? > CordovaSim should start the livereload server > --------------------------------------------- > > Key: JBIDE-16134 > URL: https://issues.jboss.org/browse/JBIDE-16134 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > > CordovaSim should configure and start the livereload server when the livereload is enabled. > If starting the server from CordovaSim menu is a big problem, alternately, the server can always be configured and started before a CordovaSim launch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16164) Missing provider names and inconsistent or plugin names for org.eclipse.vjet plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16164?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16164: ------------------------------- Summary: Missing provider names and inconsistent or plugin names for org.eclipse.vjet plugins (was: No provider for VJET plugin) > Missing provider names and inconsistent or plugin names for org.eclipse.vjet plugins > ------------------------------------------------------------------------------------ > > Key: JBIDE-16164 > URL: https://issues.jboss.org/browse/JBIDE-16164 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Attachments: no-provider-for-vjet.png > > > There is an empty provider field for VJET plugin, see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16164) Missing provider names and inconsistent plugin names for org.eclipse.vjet plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16164?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16164: ------------------------------- Summary: Missing provider names and inconsistent plugin names for org.eclipse.vjet plugins (was: Missing provider names and inconsistent or plugin names for org.eclipse.vjet plugins) > Missing provider names and inconsistent plugin names for org.eclipse.vjet plugins > --------------------------------------------------------------------------------- > > Key: JBIDE-16164 > URL: https://issues.jboss.org/browse/JBIDE-16164 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0.CR1a, L64 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Attachments: no-provider-for-vjet.png > > > There is an empty provider field for VJET plugin, see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2801: ---------------------------------- In JBDS 7.0, the maven.gwt feature depends on the e42 feature. This is fixed in 7.1.0 / 4.1.1 (maven.gwt.feature version 1.5.4) [1] to allow co-installation of JBDS 7.x and GWT e42 *or e43* feature. [1] https://github.com/jbosstools/jbosstools-central/commit/124f18781be6dc713... So, if a JBDS 7.0 user has the maven.gwt.feature < 1.5.4 installed, they need to perform two updates to be fully up to date: a) Help > Check for updates (or Help > Install) new to update from 7.0.x to 7.1.0.GA b) Central > Software/update (with remediation option 2) to update from GWT 3.2 e42 to GWT 3.4 e43 > Investigate use of GWT/GPE 3.4 in JBT/JBDS Central > -------------------------------------------------- > > Key: JBDS-2801 > URL: https://issues.jboss.org/browse/JBDS-2801 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: new_and_noteworthy > Fix For: 7.1.0.CR1 > > Attachments: install-new-gpe-1.png, install-new-gpe-2.png, install-new-gpe-3.png, install-new-gpe-4.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png > > > New 3.4.2 mirrors: > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013... > http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013... > Note that at least one IU had been renamed: > OLD: > * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar > * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar > NEW: > * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43) > * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42) > If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement: > {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24} > <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16119) CordovaSim "windows" will not open

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16119?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-16119: ------------------------------------- [~burrsutter], what do you think about changing CSS cursor property - http://jsfiddle.net/LzCz9/ . IMO, it's the neatest solution > CordovaSim "windows" will not open > ---------------------------------- > > Key: JBIDE-16119 > URL: https://issues.jboss.org/browse/JBIDE-16119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Environment: Mac OSX lion > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Attachments: CordovaSim.jpg > > > See video, trying to get access to the accelerometer drop-down > http://www.screencast.com/t/RBwdqXxeCsHJ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2836) No provider for VJET plugin

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2836?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2836: ----------------------------- CDW release: + (was: ?) > No provider for VJET plugin > --------------------------- > > Key: JBDS-2836 > URL: https://issues.jboss.org/browse/JBDS-2836 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 7.1.0.CR1 > Environment: JBDS 7.1.0.CR1a, L64 > Reporter: Jiri Peterka > Attachments: no-provider-for-vjet.png > > > There is an empty provider field for VJET plugin, see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2836) No provider for VJET plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2836?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2836: ----------------------------- CDW devel_ack: + (was: ?) Status: New (was: New) > No provider for VJET plugin > --------------------------- > > Key: JBDS-2836 > URL: https://issues.jboss.org/browse/JBDS-2836 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 7.1.0.CR1 > Environment: JBDS 7.1.0.CR1a, L64 > Reporter: Jiri Peterka > Attachments: no-provider-for-vjet.png > > > There is an empty provider field for VJET plugin, see the screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 November 2013