August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17296) Missing warning decorator on the "JAX-RS Web Services" node when no application is defined

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17296?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17296: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > Missing warning decorator on the "JAX-RS Web Services" node when no application is defined > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17296 > URL: https://issues.jboss.org/browse/JBIDE-17296 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > Moving to 4.2.0.CR1. The problem decorator on the "JAX-RS Web Services" node is not refresh as it should, but a call to the "refresh" action on that node fixes the problem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17233) Add usage tracking for the WS Tester

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17233?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17233: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > Add usage tracking for the WS Tester > ------------------------------------ > > Key: JBIDE-17233 > URL: https://issues.jboss.org/browse/JBIDE-17233 > 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.CR1 > > > Add usage tracking when the WS Tester is opened and when a request is submitted, so we can see how many people use it (or not) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBTIS-293: ------------------------------------- > Also maybe Snjezana Peco have an idea what root cause/fix is. I think this is a bug in the Luna OSGi because the order of activating bundles shouldn't affect if any bundles will be resolved. Re this issue, you can exclude the javax.xml.* dependencies for Java >= 1.6. > Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters > ----------------------------------------------------------------------------------------------------- > > Key: JBTIS-293 > URL: https://issues.jboss.org/browse/JBTIS-293 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > > If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don't get this error. > SESSION 2014-07-30 09:22:59.386 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_60-ea > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975] > Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model > -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true" > org.fusesource.ide.camel.model [977] > No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation. > org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains. > Chain 1: > org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] > require: (osgi.wiring.bundle=org.eclipse.core.runtime) > | > provide: osgi.wiring.bundle: org.eclipse.core.runtime > org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] > Chain 2: > org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] > import: (osgi.wiring.package=org.fusesource.camel.tooling.util) > | > export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model > io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"] > import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0)))) > | > export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters > org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"] > import: (osgi.wiring.package=javax.xml.bind.annotation.adapters) > | > export: osgi.wiring.package: javax.xml.bind.annotation.adapters > javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-253) Please update JBTIS TP dependencies to Luna Alpha1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-253?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-253: ---------------------------------- Any chance in seeing a http://download.jboss.org/jbosstools/updates/development/luna/integration... for Luna? (I'm spinning the 4.2.0.Alpha1 JBTIS based on JBTIS TP 4.2.0.Alpha6 this week). Just curious... > Please update JBTIS TP dependencies to Luna Alpha1 > -------------------------------------------------- > > Key: JBTIS-253 > URL: https://issues.jboss.org/browse/JBTIS-253 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: teiid > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Barry LaFond > > Greetings - welcome to Luna! > An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3]. > I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others. > Thanks! > [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al... > [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13399) ESB Runtime - defaults to highest supported version - when creating a new ESB project

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13399?page=com.atlassian.jira.plugi... ] Paul Leacu updated JBIDE-13399: ------------------------------- Assignee: Brian Fitzpatrick (was: Paul Leacu) > ESB Runtime - defaults to highest supported version - when creating a new ESB project > ------------------------------------------------------------------------------------- > > Key: JBIDE-13399 > URL: https://issues.jboss.org/browse/JBIDE-13399 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: integration-platform > Affects Versions: 3.2.2.Final > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: LATER > > > Example scenario: > New install of JBDS/JBossTools, install the ESB tooling, create a server runtime for SOA 5.2, and a corresponding ESB runtime of 4.10. > Then, create a new ESB project - and the ESB runtime displayed in the wizard is 4.12, as this automatically defaults to the highest supported facet version on the runtime. > For each version of ESB, we have declared an explicit facet. In org.jboss.tools.esb.project.core, we have facets defined (4.2,4.3,4.4,4.5,4.6,4.7,4.9,4.10,4.11,4.12) and assign them to EAP runtime components (4.3,5.0,6.0) (which are specified in the AS tools plug-ins). So every version of SOA-P based on EAP 4.3, 5.x, or 6.x supports every facet version we've defined thus far - up to 4.12 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13399) ESB Runtime - defaults to highest supported version - when creating a new ESB project

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13399?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-13399: ------------------------------------ Another ESB issue. > ESB Runtime - defaults to highest supported version - when creating a new ESB project > ------------------------------------------------------------------------------------- > > Key: JBIDE-13399 > URL: https://issues.jboss.org/browse/JBIDE-13399 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: integration-platform > Affects Versions: 3.2.2.Final > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: LATER > > > Example scenario: > New install of JBDS/JBossTools, install the ESB tooling, create a server runtime for SOA 5.2, and a corresponding ESB runtime of 4.10. > Then, create a new ESB project - and the ESB runtime displayed in the wizard is 4.12, as this automatically defaults to the highest supported facet version on the runtime. > For each version of ESB, we have declared an explicit facet. In org.jboss.tools.esb.project.core, we have facets defined (4.2,4.3,4.4,4.5,4.6,4.7,4.9,4.10,4.11,4.12) and assign them to EAP runtime components (4.3,5.0,6.0) (which are specified in the AS tools plug-ins). So every version of SOA-P based on EAP 4.3, 5.x, or 6.x supports every facet version we've defined thus far - up to 4.12 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-137) ESB Tests are failing locating project examples

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-137?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-137: ----------------------------- Assignee: Brian Fitzpatrick (was: Paul Leacu) > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBTIS-137 > URL: https://issues.jboss.org/browse/JBTIS-137 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-137) ESB Tests are failing locating project examples

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-137?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-137: ---------------------------------- Fitz - can you t ake a look at this one too? - ref JBTIS-162. > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBTIS-137 > URL: https://issues.jboss.org/browse/JBTIS-137 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3115) Include Ionic Palette in Central

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3115: ----------------------------------- [~dgolovin] I thought the same - Ionic goes with the AngularJS plugins - but Max suggested to me that the Ionic palette was just another derivative of the jQuery Mobile Palette, both are "HTML5" palettes and would work fine without the AngularJS tooling. > Include Ionic Palette in Central > -------------------------------- > > Key: JBDS-3115 > URL: https://issues.jboss.org/browse/JBDS-3115 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: p2-product > Affects Versions: 8.0.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3115) Include Ionic Palette

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3115: ------------------------------------- {quote}All Angularjs are currently thought to be via central. [12:45:22 PM] Max Rydahl Andersen: And we'll have angular project w/forge wizard that should depend on the angularjs feature. {quote} > Include Ionic Palette > --------------------- > > Key: JBDS-3115 > URL: https://issues.jboss.org/browse/JBDS-3115 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: p2-product > Affects Versions: 8.0.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > -- 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