January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3302) Multiple org.eclipse.jdt.annotation plugins present in JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3302?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3302: ---------------------------------- [~jpeterka] please see JBIDE-19057 in which I've externalized the list of excludes to a properties file for better management. > Multiple org.eclipse.jdt.annotation plugins present in JBDS > ----------------------------------------------------------- > > Key: JBDS-3302 > URL: https://issues.jboss.org/browse/JBDS-3302 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.1.GA > Environment: JBDS 8.0.1.GA > Reporter: Jiri Peterka > Priority: Minor > Attachments: jbds3302.png > > > Since JBDS 8.0.0 there are multiple plugins for org.eclipse.jdt.annotation present, specifically 1.1.0 and 2.0.0 > Is there any reason for that? If yes, let's add it to known exceptions, if not older version should be probably removed. I haven't found any directly depending bundles after quick search. > Discovered by vwatch - http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3261) JSR-356: Websockets. Import, build, run on server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3261?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3261: ---------------------------------- [~akazakov] [~mlabuda] I can create a new Websockets component in JBIDE and JBDS JIRAs, if you tell me who the component lead should be. > JSR-356: Websockets. Import, build, run on server > ------------------------------------------------- > > Key: JBDS-3261 > URL: https://issues.jboss.org/browse/JBDS-3261 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Burr Sutter > Assignee: Xavier Coulon > Priority: Critical > Fix For: 9.0.x > > > Support for import (without error), build, Run on Server and Debug on Server. > https://github.com/javaee-samples/javaee7-samples/tree/master/websocket -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Alexander Kurtakov commented on JBDS-3331: ------------------------------------------ Steps to follow: 1. On supported version of RHEL 6.x or 7.x add Red Hat Developer Toolset subscription as described on https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/3... 2. Run `yum install devtoolset-3-eclipse` . This would install what used to be called Eclipse classic aka http://download.eclipse.org/eclipse/downloads/drops4/R-4.4.1-201409250400... rebuild. 3. Start eclipse and install from JBoss Tools update site as usual. > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Len DiMaggio > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19047) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19047?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19047: ------------------------------------- I can't see anything obviously wrong in the settings. Except the EAR facet version == 1.3, which seems odd when deploying to wildfly. That can be changed with maven-ear-plugin>configuration>version=7 then update project configuration. But that really is unrelated to the deployment issue. You could try to * remove the ear from wildlfy * stop server * delete data, deployments, log, tmp folders from the WILDFLY_HOME/standalone/ * start the server * add EAR If application.xml exists in ear/target/m2e-wtp/ear-resources/META-INF, it should really be deployed > Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin > ---------------------------------------------------------------------------- > > Key: JBIDE-19047 > URL: https://issues.jboss.org/browse/JBIDE-19047 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Environment: Ubuntu 14.04, Wildfly 8.2.0 FInal, Eclipse Luna > Reporter: Nick . > Assignee: Fred Bricon > Fix For: 4.3.x > > Attachments: sample.zip, settings.zip > > > Hi, > I have a maven EAR project, which contains a couple of WAR and JAR files. I'm using Eclipse Luna (tried STS and IntelliJ ) IDE with JBoss Tools 1.6.0 (latest). > When I try to deploy my EAR to Wildfly (as well as in EAP 6.2.0) with JBoss Tools from eclipse i'm facing the following issues. > My Jars (external jars and project jar) are getting copied into WEB-INF/lib and EAR/lib, where i expected it to be only in EAR/lib. > EAR application.xml is not getting copied into EAR/META-INF/ folder > But when i use command line to build my project , i'm not experiencing the above issue. > FYI : We are using <skinnyWars>true</skinnyWars>. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18900: ------------------------------------- [~maxandersen], in terms of adding new launch shortcut for remote FH and ripple proxy issue. It seems that both remote and local FH works fine with the *disabled* proxy settings. So, the easiest way to add full FH support is to use 'disabled' proxy by default rather than exposing them to the launch config. Warning about using remote proxy can be implemented on js (and probably contributed to incubator-ripple). WDYT? Here is the PR - https://github.com/jbosstools/jbosstools-aerogear/pull/106 > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3322) JSR-356: Websockets. Content-assist for annotations

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3322: ------------------------------------- What should do content assist for those annotation? Just offer WebSocket related annotation in Template Proposals? Or is there meant some "magic" with content assist? > JSR-356: Websockets. Content-assist for annotations > --------------------------------------------------- > > Key: JBDS-3322 > URL: https://issues.jboss.org/browse/JBDS-3322 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 9.0.x > > > As a Java EE developer, I wish to take advantage of the new Websockets capability. > Content-assist for annotations such as @ServerEndpoint, @OnMessage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3261) JSR-356: Websockets. Import, build, run on server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3261?page=com.atlassian.jira.plugin.... ] Marián Labuda edited comment on JBDS-3261 at 1/22/15 10:42 AM: --------------------------------------------------------------- >From QE perspective I would like to have another component too. Having WebSockets in webservices is a bit confusing because of differencies. We already splitted webservices component into JAX-RS and JAX-WS by labels. I don't think it's a good idea to put it there. was (Author: mlabuda): >From QE perspective I would like to have another component too. Having WebSockets in webservices is a bit confusing because of differencies. We already splitted webservices component into JAX-RS and JAX-WS. I don't think it's a good idea put it there. > JSR-356: Websockets. Import, build, run on server > ------------------------------------------------- > > Key: JBDS-3261 > URL: https://issues.jboss.org/browse/JBDS-3261 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Burr Sutter > Assignee: Xavier Coulon > Priority: Critical > Fix For: 9.0.x > > > Support for import (without error), build, Run on Server and Debug on Server. > https://github.com/javaee-samples/javaee7-samples/tree/master/websocket -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3261) JSR-356: Websockets. Import, build, run on server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3261?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3261: ------------------------------------- >From QE perspective I would like to have another component too. Having WebSockets in webservices is a bit confusing because of differencies. We already splitted webservices component into JAX-RS and JAX-WS. I don't think it's a good idea put it there. > JSR-356: Websockets. Import, build, run on server > ------------------------------------------------- > > Key: JBDS-3261 > URL: https://issues.jboss.org/browse/JBDS-3261 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Burr Sutter > Assignee: Xavier Coulon > Priority: Critical > Fix For: 9.0.x > > > Support for import (without error), build, Run on Server and Debug on Server. > https://github.com/javaee-samples/javaee7-samples/tree/master/websocket -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19063) Ensure that new "bumped.png" image is published when vwatch reports are archived in Jenkins / published to dl.jb.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19063?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19063: ------------------------------- Description: A new bumped icon has been added to the vwatch reports [ in jbdevstudio-qa/vwatch/target/bumped.png ], but it's not included in what is archived in Jenkins and published to dl.jb.org. So, we need to ensure that any images are published when vwatch reports are archived in Jenkins / published to dl.jb.org was: A new bumped icon has been added to the vwatch reports, but it's not included in what is archived in Jenkins and published to dl.jb.org. So, we need to ensure that any images are published when vwatch reports are archived in Jenkins / published to dl.jb.org > Ensure that new "bumped.png" image is published when vwatch reports are archived in Jenkins / published to dl.jb.org > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19063 > URL: https://issues.jboss.org/browse/JBIDE-19063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > > A new bumped icon has been added to the vwatch reports [ in jbdevstudio-qa/vwatch/target/bumped.png ], but it's not included in what is archived in Jenkins and published to dl.jb.org. > So, we need to ensure that any images are published when vwatch reports are archived in Jenkins / published to dl.jb.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3302) Multiple org.eclipse.jdt.annotation plugins present in JBDS

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3302?page=com.atlassian.jira.plugin.... ] Jiri Peterka commented on JBDS-3302: ------------------------------------ I've created upstream https://bugs.eclipse.org/bugs/show_bug.cgi?id=458163 for clarification. For now I'll add it into the ignored multiple version list in VW. > Multiple org.eclipse.jdt.annotation plugins present in JBDS > ----------------------------------------------------------- > > Key: JBDS-3302 > URL: https://issues.jboss.org/browse/JBDS-3302 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.1.GA > Environment: JBDS 8.0.1.GA > Reporter: Jiri Peterka > Priority: Minor > Attachments: jbds3302.png > > > Since JBDS 8.0.0 there are multiple plugins for org.eclipse.jdt.annotation present, specifically 1.1.0 and 2.0.0 > Is there any reason for that? If yes, let's add it to known exceptions, if not older version should be probably removed. I haven't found any directly depending bundles after quick search. > Discovered by vwatch - http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015