December 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-312) Generate source bundles for IS component features.

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-312?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-312. ------------------------------ Fix Version/s: 8.0.0.Beta2 4.2.0.Beta2 Resolution: Done Fully resolved with 4.2.0.Beta2/ 8.0.0.Beta2. > Generate source bundles for IS component features. > -------------------------------------------------- > > Key: JBTIS-312 > URL: https://issues.jboss.org/browse/JBTIS-312 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, switchyard, teiid > Affects Versions: 8.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.0.Beta2, 4.2.0.Beta2 > > > IS components must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS. > Courtesy [~nickboldt]: > How to make maven/tycho build source bundles and features: > In the upstream projects: > http://wiki.eclipse.org/Minerva#Source > Then in the aggregator for JBTIS/JBSIS update site: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > As a result, users can install sources from within JBDS rather than > needing a separate source zip with .java files. Way more useful, if > you're a java developer using JBDS/Eclipse. > If you also want to produce a zip of *actual source files* as pulled > from github, I have a script for that, too. > See: > 1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources > Produces a zip of the contents of the JBDS product build, so people can > build it offline. Does NOT include upstream sources. > Result: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... > (2.4M) > 2. > https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... > Produces a zip of upstream sources based on upstream project zips. This > is the old approach, since pulling a previously-built zip doesn't 100% > guarantee you're getting the correct version AND it requires that the > upstream project produce a source zip. > -OR- > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Fetches sources directly from github based on the source-reference in > the specified plugins' manifest.mf files, then collates those sources > into a single zip. > Results: > http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al... > (35M) > Ref: > (10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide. > (10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct? > (10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it. > (10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that > (10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience. > (10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles > (10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources > (10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized" > (10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (cc: pleacu ) > Components that generate source bundles: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > Some that don't: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18953: --------------------------------------- [~baciuv], sorry no, 4.2.1.Final is already packaged and is due today. What you can do for now is set the validation level to 'ignore' for this particular case: go to Preferences>JBoss Tools>JAX-RS>Jax-RS Validator and locate the "Missing Provider implementation" item in the "JAX-RS Provider" section of that page. This should at least remove the false-positive validation error messages until the bug is fixed. > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18953 > URL: https://issues.jboss.org/browse/JBIDE-18953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.client.ClientResponseContext; > import javax.ws.rs.client.ClientResponseFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter, ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-318) Generate source bundles for IS component features.

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-318?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-318. ------------------------------ Fix Version/s: 8.0.0.Beta2 4.2.0.Beta2 Resolution: Done Resolved with latest beta2. > Generate source bundles for IS component features. > -------------------------------------------------- > > Key: JBTIS-318 > URL: https://issues.jboss.org/browse/JBTIS-318 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: drools/ jBPM > Affects Versions: 8.0.0.Alpha1, 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > Fix For: 8.0.0.Beta2, 4.2.0.Beta2 > > > jBPM/ Drools must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS. > Courtesy [~nickboldt]: > How to make maven/tycho build source bundles and features: > In the upstream projects: > http://wiki.eclipse.org/Minerva#Source > Then in the aggregator for JBTIS/JBSIS update site: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > As a result, users can install sources from within JBDS rather than > needing a separate source zip with .java files. Way more useful, if > you're a java developer using JBDS/Eclipse. > If you also want to produce a zip of *actual source files* as pulled > from github, I have a script for that, too. > See: > 1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources > Produces a zip of the contents of the JBDS product build, so people can > build it offline. Does NOT include upstream sources. > Result: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma... > (2.4M) > 2. > https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... > Produces a zip of upstream sources based on upstream project zips. This > is the old approach, since pulling a previously-built zip doesn't 100% > guarantee you're getting the correct version AND it requires that the > upstream project produce a source zip. > -OR- > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Fetches sources directly from github based on the source-reference in > the specified plugins' manifest.mf files, then collates those sources > into a single zip. > Results: > http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al... > (35M) > Ref: > (10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide. > (10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct? > (10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it. > (10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that > (10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience. > (10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles > (10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources > (10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized" > (10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (cc: pleacu ) > Components that generate source bundles: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... > Some that don't: > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3267) JSON Editor

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3267?page=com.atlassian.jira.plugin.... ] Xavier Coulon reassigned JBDS-3267: ----------------------------------- Assignee: Xavier Coulon > JSON Editor > ----------- > > Key: JBDS-3267 > URL: https://issues.jboss.org/browse/JBDS-3267 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Xavier Coulon > > As a Java or Java EE developer, who wishes to test my JAX-RS endpoints as well as edit various JSON files, I need an editor that formats the nested curly braces, helps me to insure that I am not missing (nor have extra) curly braces, missing quotes, helps me to know when to use square brackets, etc. Ideally, the Eclipse Outline view would also work if I am editing a .json file. > Ideally, we would support both a full JSON editor as well as working within the Web Services Tester. > http://screencast.com/t/hWAtlMytghV6 > http://screencast.com/t/h4VWGyAuqw -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Valentin Baciu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ] Valentin Baciu commented on JBIDE-18953: ---------------------------------------- You're welcome Xavier. Any chance the fix can make it into 4.2.1.Final? > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18953 > URL: https://issues.jboss.org/browse/JBIDE-18953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.client.ClientResponseContext; > import javax.ws.rs.client.ClientResponseFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter, ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18953: --------------------------------------- Thanks for reporting this bug, [~baciuv] ! That's something I definitely need to fix. > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18953 > URL: https://issues.jboss.org/browse/JBIDE-18953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.client.ClientResponseContext; > import javax.ws.rs.client.ClientResponseFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter, ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18953: ---------------------------------- Fix Version/s: 4.3.0.Alpha1 > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18953 > URL: https://issues.jboss.org/browse/JBIDE-18953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.client.ClientResponseContext; > import javax.ws.rs.client.ClientResponseFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter, ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-18953: ------------------------------------- Assignee: Xavier Coulon > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18953 > URL: https://issues.jboss.org/browse/JBIDE-18953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Xavier Coulon > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.client.ClientResponseContext; > import javax.ws.rs.client.ClientResponseFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter, ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Valentin Baciu (JIRA)

Valentin Baciu created JBIDE-18953: -------------------------------------- Summary: Unexpected JAX-RS validation error for client filters Key: JBIDE-18953 URL: https://issues.jboss.org/browse/JBIDE-18953 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Final Reporter: Valentin Baciu We are using JAX-RS client filters in our project. One of the classes looks like this: ... import java.io.IOException; import javax.ws.rs.client.ClientRequestContext; import javax.ws.rs.client.ClientRequestFilter; import javax.ws.rs.client.ClientResponseContext; import javax.ws.rs.client.ClientResponseFilter; import javax.ws.rs.ext.Provider; ... @Provider public class ClientFilter implements ClientRequestFilter, ClientRequestFilter { ... } The class is part of a Dynamic Web Project with JAX-RS support turned on. The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2850) JavaScript Editing Support

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2850?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-2850. ------------------------------ All the issues in the epic are closed - closing the epic JIRA too. > JavaScript Editing Support > -------------------------- > > Key: JBDS-2850 > URL: https://issues.jboss.org/browse/JBDS-2850 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: jsp/jsf/xml/html source editing, requirements > Reporter: Burr Sutter > Assignee: Len DiMaggio > Labels: QE_JBDS80_needinfo > Fix For: 8.0.0.GA > > > 1) Support for code assist/completion (ctrl-space) for AngularJS $scope. > 2) Support for code jQuery $('# -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 December 2014