March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19473: ------------------------------------ Suspect the error is caused by the fact that we can only declare a category ONCE across all discovery plugins, but the category ref'd by the EA plugin is not in the Central plugin.xml > Central can't load Discovery catalog > ------------------------------------ > > Key: JBIDE-19473 > URL: https://issues.jboss.org/browse/JBIDE-19473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found. > The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content. > Log says > {quote} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar > {quote} > I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19500: ---------------------------------- Assignee: Max Rydahl Andersen > 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: Max Rydahl Andersen > > 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.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19471) Cordova platform targeting

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19471?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19471: --------------------------------- Fix Version/s: 4.3.0.Alpha2 > Cordova platform targeting > -------------------------- > > Key: JBIDE-19471 > URL: https://issues.jboss.org/browse/JBIDE-19471 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.3.0.Alpha2 > > > Since cordova ceased to do cadence releases and started doing individual platform releases, it is harder for us to be compatible with Cordova CLI. > Also it is making it confusing for users since there is no concept of Cordova release anymore. > We need to support targeting individual cordova platform and version combinations instead of the single cordova version that we use today. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19472) Switch to use the new plugin syntax on config.xml

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19472?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19472: --------------------------------- Fix Version/s: 4.3.0.Alpha2 > Switch to use the new plugin syntax on config.xml > ------------------------------------------------- > > Key: JBIDE-19472 > URL: https://issues.jboss.org/browse/JBIDE-19472 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.3.0.Alpha2 > > > Cordova CLI started using <plugin> to persist plugin that needs to be restored. We need to switch to use <plugin> instead of <feature> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19524) Make sure OpenShift tooling works with EGit 4

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19524?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19524: ------------------------------------------ turns out EGit 4 requires java 7 and I thus need to require java 7 for my egit plugins, too. Once this is fixed there are no compilation errors left. The API seems compatible. Running the tooling and real-life testing is required though to see if there are any problems at runtime. > Make sure OpenShift tooling works with EGit 4 > --------------------------------------------- > > Key: JBIDE-19524 > URL: https://issues.jboss.org/browse/JBIDE-19524 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > Eclipse Mars will use EGit 4 (and our target platform is about to switch to EGit 4) and we thus have to make sure our tooling works with EGit 4 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19526) JPA validation doesn't detect generator strategy file removal

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-19526: ------------------------------------ Summary: JPA validation doesn't detect generator strategy file removal Key: JBIDE-19526 URL: https://issues.jboss.org/browse/JBIDE-19526 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.2.3.CR1 Environment: JBDS 8.1.0.CR1 Reporter: Jiri Peterka Fix For: 4.3.0.Alpha2 JPA Validator normally checks if generator strategy exist. For example when you give wrong name, it reports error which is expected. But when strategy file removed by project explorer it doesn't report any error and reports no error in project. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19525) JPA project needs cleanup after second import

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19525?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-19525: --------------------------------- Attachment: errors-after-2nd-import.png > JPA project needs cleanup after second import > --------------------------------------------- > > Key: JBIDE-19525 > URL: https://issues.jboss.org/browse/JBIDE-19525 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.3.CR1 > Environment: JBDS 8.1.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Alpha2 > > Attachments: errors-after-2nd-import.png > > > After second import of the same project there are errors and clean project is needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19525) JPA project needs cleanup after second import

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-19525: ------------------------------------ Summary: JPA project needs cleanup after second import Key: JBIDE-19525 URL: https://issues.jboss.org/browse/JBIDE-19525 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate, upstream Affects Versions: 4.2.3.CR1 Environment: JBDS 8.1.0.CR1 Reporter: Jiri Peterka Fix For: 4.3.0.Alpha2 After second import of the same project there are errors and clean project is needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19524) Make sure OpenShift tooling works with EGit 4

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19524: ---------------------------------------- Summary: Make sure OpenShift tooling works with EGit 4 Key: JBIDE-19524 URL: https://issues.jboss.org/browse/JBIDE-19524 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.3.0.Alpha2 Eclipse Mars will use EGit 4 (and our target platform is about to switch to EGit 4) and we thus have to make sure our tooling works with EGit 4 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19447) Constraint violation resolving org.jboss.tools.browsersim.ui

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19447?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19447: ------------------------------------------------ I run a build manually, everything is fine both locally and on jenkins. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Will leave this issue opened to keep my eye on browsersim build > Constraint violation resolving org.jboss.tools.browsersim.ui > ------------------------------------------------------------ > > Key: JBIDE-19447 > URL: https://issues.jboss.org/browse/JBIDE-19447 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > Build is OK, and publish is working, but tests are failing: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-browsersim_master/136/console} > 00:04:56.920 !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-03-13 08:51:58.758 > 00:04:56.920 !MESSAGE FrameworkEvent ERROR > 00:04:56.920 !STACK 0 > 00:04:56.920 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [265] > 00:04:56.920 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.3.0" > 00:04:56.921 -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true" > 00:04:56.921 org.jboss.tools.browsersim.ui [266] > 00:04:56.921 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.javafx.mock; bundle-version="3.6.0"; resolution:="optional" > 00:04:56.921 Bundle was not resolved because of a uses contraint violation. > 00:04:56.921 org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] because it is exposed to package 'org.eclipse.jetty.util.component' from resources org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"] and org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] via two dependency chains. > 00:04:56.922 > 00:04:56.922 Chain 1: > 00:04:56.922 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] > 00:04:56.923 require: (&(osgi.wiring.bundle=org.eclipse.jetty.util)(bundle-version>=8.1.14)) > 00:04:56.923 | > 00:04:56.923 provide: osgi.wiring.bundle: org.eclipse.jetty.util > 00:04:56.923 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"] > 00:04:56.923 > 00:04:56.923 Chain 2: > 00:04:56.923 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] > 00:04:56.924 require: (&(osgi.wiring.bundle=org.eclipse.jetty.websocket)(bundle-version>=8.1.14)) > 00:04:56.924 | > 00:04:56.924 provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.jetty.websocket"; bundle-version:Version="8.1.14.v20131031" > 00:04:56.924 org.eclipse.jetty.websocket [osgi.identity; osgi.identity="org.eclipse.jetty.websocket"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.924 import: (&(osgi.wiring.package=org.eclipse.jetty.io)(&(version>=8.1.0)(!(version>=9.0.0)))) > 00:04:56.924 | > 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.io; uses:=org.eclipse.jetty.util.log > 00:04:56.925 org.eclipse.jetty.io [osgi.identity; osgi.identity="org.eclipse.jetty.io"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.925 import: (&(osgi.wiring.package=org.eclipse.jetty.util.log)(&(version>=8.1.0)(!(version>=9.0.0)))) > 00:04:56.925 | > 00:04:56.925 export: osgi.wiring.package: org.eclipse.jetty.util.log; uses:=org.eclipse.jetty.util.component > 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.util.component > 00:04:56.925 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.926 at org.eclipse.osgi.container.Module.start(Module.java:434) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > 00:04:56.927 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 March 2015