May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19346: ------------------------------------- PRs look fine to me. I don't see the need to move the files under /configuration for now. If we do, we'll also need to maintain per-version sub folders hierarchy there > jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19346 > URL: https://issues.jboss.org/browse/JBIDE-19346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ? > {code} > $➔ cat jbosstools-earlyaccess.properties > #Mon Sep 01 18:54:14 CEST 2014 > org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63] > org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649] > org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218] > {code} > -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-433) MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-433?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-433. ------------------------------ Fix Version/s: 8.0.2.CR1 Resolution: Done The Fuse Tooling build for Beta5 has been corrected: http://download.jboss.org/jbosstools/updates/development/luna/integration... > MASTER build of Fuse tooling in JBDS-IS 8.0.2.ER1 > ------------------------------------------------- > > Key: JBTIS-433 > URL: https://issues.jboss.org/browse/JBTIS-433 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 8.0.2.CR1 > > > Current build of JBDS-IS 8.0.2.ER1 contains MASTER build of Fuse tooling, namely 7.3.0.v20150428-1634-H488-MASTER. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-435) Add Integration Stack SAP support variables in devstudio ide-config.properties

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-435?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-435. ------------------------------ Resolution: Done Added ide-config.properties SAP variable values for devstudio as well as jbosstools https://github.com/jbosstools/jbosstools-download.jboss.org/commit/4ae50a... > Add Integration Stack SAP support variables in devstudio ide-config.properties > ------------------------------------------------------------------------------ > > Key: JBTIS-435 > URL: https://issues.jboss.org/browse/JBTIS-435 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > The following two variables are defined for JBTIS/ SAP support: > {code} > jboss.discovery.site.integration-stack-sap.url|jbosstools|4.2=http://down... > jboss.discovery.site.integration-stack-sap.feature=org.fusesource.ide.sap.feature.feature.group > {code} > define similar variables for the devstudio section of ide-config.properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19711: ------------------------------------- > do we have a bugzilla open about having apis that ask for targets instead of having to keep manually updating a list that potentially can get out of sync and just generally makes it hard to maintain? No... we don't. I'm not sure why or how this could get out-of-sync? Every time a server is added or removed, my listener is informed. My listener then adds an org.eclipse.remote server, and adds a launchbar element. There's honestly more risk of o.e.remote list of servers getting out of sync than there is with launchbar, because launchbar doesn't persist any of the launch objects on workspace close, while o.e.remote keeps the list saved somewhere... which means an extra o.e.remote connection is more likely to stick around and cause trouble. Honestly, the internal model in launchbar is really quite messy. It kind of scares me to touch it, but I don't exactly feel empowered to rewrite / reorganize the entire class. What's more, they're being *very* nitpicky over my every patch, even ones I've felt so far were very non-controversial. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov edited comment on JBIDE-19773 at 5/8/15 1:51 PM: ------------------------------------------------------------------------ Issues we might have under various Linux distros: * We need to be sure that browser was created. Otherwise, show error message like we do it for Visual Editor. Usecase: User does not install vpe(haven't got our old XulRunner bundles) + has no webkit installed ** In error message we should advice to install webkit library (it's easier) in accordance to GTK2/GTK3 * If browser was created, we need to detect which engine is used: ** old xulrunner. Then show simplified version of central ** webkit/new xulrunner: everything is fine I don't remember can we even launch Eclipse on RHEL6 under GTK3(RHEL7 under GTK2). If yes - this two cases also must be documented(switch back to default GTK). That's in my TODO list for Monday was (Author: kmarmaliykov): Issues we might have under various Linux distros: * We need to be sure that browser was created. Otherwise, show error message like we do it for Visual Editor. Usecase: User does not install vpe(haven't got our old XulRunner bundles) + has no webkit installed ** In error message we should advice to install webkit library (it's easier) in accordance to GTK2/GTK3 * If browser was created, we need to detect which engine is used: ** old xulrunner. Then show simplified version of central ** webkit/new xulrunner: everything is fine I don't remember can we even launch Eclipse on RHEL6 under GTK3(RHEL7 under GTK2). If yes - this two cases also must be documented(switch back to default GTK). > Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do? > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19773 > URL: https://issues.jboss.org/browse/JBIDE-19773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Beta1 > > > It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution. > Context: > {quote} > * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > * SWT problem? GTK problem? xvnc/xvfb problem? > * missing webkit package on RHEL7 ? > * @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages) > * what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_... {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19773: ------------------------------------------------ Issues we might have under various Linux distros: * We need to be sure that browser was created. Otherwise, show error message like we do it for Visual Editor. Usecase: User does not install vpe(haven't got our old XulRunner bundles) + has no webkit installed ** In error message we should advice to install webkit library (it's easier) in accordance to GTK2/GTK3 * If browser was created, we need to detect which engine is used: ** old xulrunner. Then show simplified version of central ** webkit/new xulrunner: everything is fine I don't remember can we even launch Eclipse on RHEL6 under GTK3(RHEL7 under GTK2). If yes - this two cases also must be documented(switch back to default GTK). > Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do? > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19773 > URL: https://issues.jboss.org/browse/JBIDE-19773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Beta1 > > > It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution. > Context: > {quote} > * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > * SWT problem? GTK problem? xvnc/xvfb problem? > * missing webkit package on RHEL7 ? > * @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages) > * what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_... {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19500: ----------------------------------- Sprint: Sprint #3 May 2015 > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3411: -------------------------------- Fix Version/s: 9.0.0.Beta1 > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-19772. ----------------------------------- Resolution: Cannot Reproduce Bug > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Fix For: 4.2.3.Final > > Attachments: .log, bookmarks.xml, jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19772: ---------------------------------- Component/s: build > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Fix For: 4.2.3.Final > > Attachments: .log, bookmarks.xml, jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015