May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19794) Provide content assist to create new JAX-RS resource method

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19794: ------------------------------------- Summary: Provide content assist to create new JAX-RS resource method Key: JBIDE-19794 URL: https://issues.jboss.org/browse/JBIDE-19794 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webservices Affects Versions: 4.2.3.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.x The JAX-RS tooling should provide more content assist, including creating methods annotated with {{@GET}}, {{@POST}}, etc.. with sensible parameters (entity, id). Once the code is inserted (with valid import statements and proper formatting), the user should be able to quickly edit the parameter types or names. See how the JDT classes are used in https://github.com/jbosstools/jbosstools-webservices/pull/232 to manipulate the existing code -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-640?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-640: ------------------------------------ Thanks, Len! Added the text into community docs here: * http://tools.jboss.org/documentation/howto/import_fh_app.html * http://tools.jboss.org/documentation/howto/hmt_firstapp.html Added the text into enterprise docs here: * https://access.redhat.com/articles/1295913 * https://access.redhat.com/articles/1400613 Found a few small things to fix up so have not sent a PR yet, but the enterprise versions of this note is already live. > Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS > -------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-640 > URL: https://issues.jboss.org/browse/TOOLSDOC-640 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > This is related to: https://issues.jboss.org/browse/JBIDE-19716 > The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19756: ------------------------------- Attachment: jbide19756_jbds-sources-zip.png Both JBT and JBDS have sources again: * 288M: http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al... * 292M: http://www.qa.jboss.com/binaries/RHDS/9.0/snapshots/builds/devstudio.prod... Note that for JBDS the source zip is a combination of the upstream JBT zip and the JBDS sources, so it contains *TWO* root folders. !jbide19756_jbds-sources-zip.png! Would you like these both pushed down under a jboss-devstudio-9.0.0.Beta1-installer-src/ folder instead? We could have * jboss-devstudio-9.0.0.Beta1-installer-src/ ** product/ ** jbosstools/ *** jbosstools-*-SHA/ (17 folders) or * jboss-devstudio-9.0.0.Beta1-installer-src/ ** jbdevstudio-product/ ** jbosstools-*-SHA/ (17 folders) or * something else ...? > jbosstools-src.zip has incomplete/misleading version info in folder names/structure > ----------------------------------------------------------------------------------- > > Key: JBIDE-19756 > URL: https://issues.jboss.org/browse/JBIDE-19756 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: jbide19756.png, jbide19756_jbds-sources-zip.png, jbide19756_new_subfolders_and_zipfile_name.png > > > Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named: > <componentname>_<buildqualifier>_<sha1> > example: > jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad > A few issues with this: > a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ? > b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-643) Document Maven Tools functionality in User Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-643?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-643: ------------------------------------ Scoping for 9.0 (and 8.1, for the time being). Tentative plan based on existing information and requirements outlined by Burr earlier: 1. Introduction - A brief intro exists in the introduction section of the maven tools ref guide (JBDS 7.1). 2. Install Maven in JBDS 3. Using maven (Basic) a. Create a new maven project - instructions for 7.1 in maven tools ref guide b. Create a maven module (pre-req is maven project) - instructions for 7.1 in maven tools ref guide c. Add maven support to an existing project - instructions for 7.1 in maven tools ref guide 4. Using Maven (Advanced) - wishlist of more advanced topics to cover after basics are done and published - how to enable autdownload of source and javadoc - usage of maven source lookup container (it somewhat automates the automatic download) - explain maven lifecycles and how it can result in warnings/errors you as user don't really care or want to care about - in here explain how jboss tools and eclipse provides some autoconfiguration based on what plugins are used - document the maven properties you can use to turn on/off this auto config such as enable hibernate, annotation processors, war projects etc. For the current scope, I'll create an article addressing the basics of using Maven with JBDS (i.e. points 1-3 from the tentative plan above), test it and get it approved by QE and publish it for the 8.1 docs, then test for 9.0 later and make changes if required. > Document Maven Tools functionality in User Guide > ------------------------------------------------ > > Key: TOOLSDOC-643 > URL: https://issues.jboss.org/browse/TOOLSDOC-643 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Michelle Murray > Assignee: Misha Ali > Labels: JBDS80_Approved_Scope > Fix For: 4.3.0.Final > > > Add a chapter to the JBDS User Guide on Maven Tools. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17686: ------------------------------------ [~rob.stryker] as per the error above, how do you set *jbosstools.test.jre.7* so that you don't get this error? {code}junit.framework.AssertionFailedError: Java Home provided by the jbosstools.test.jre.7 system property does not exist.{code} Shouldn't there be a default value in your root pom or test pom(s)? > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17686: ------------------------------- Attachment: org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt With the above PRs applied, I ran a full test suite... and got some failures. :( {code} mvn -version Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T12:29:23-05:00) Maven home: /opt/maven3 Java version: 1.7.0_17, vendor: Oracle Corporation Java home: /opt/jdk1.7.0_17/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.17.4-200.fc20.x86_64", arch: "amd64", family: "unix" mvn install -fae -e ... [INFO] org.jboss.tools.as.management.itests ............... FAILURE [ 41.132 s] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.22.0:test (default-test) on project org.jboss.tools.as.management.itests: There are test failures. Please refer to /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-server/as/itests/org.jboss.tools.as.management.itests/target/surefire-reports for the individual test results. {code} * [^org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt] > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19346: ------------------------------------ A) The usual process for all files on download.jboss.org and devstudio.redhat.com (other than those published by Jenkins) is to update the files in github, then push the update to the webserver (filemgmt). That way we have a backup / history + live files. This applies to things like ide-config.properties, earlyaccess.properties, jbosstools-directory.xml, devstudio-directory.xml, composite*.xml, ... B) It doesn't. He updates in github, pushes to the server, and then the rebuild of the jbosstools-discovery job pulls from that location. That location is * http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... * https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... We need different versions of these artifacts because we have 3 parallel streams of builds now: CI/snapshot/nightly, staging, and latest dev milestone (or stable release). This is most easily seen by looking in the http://download.jboss.org/jbosstools/configuration/ide-config.properties file: {code} # master version of jbosstools-earlyaccess.properties should be edited here, so the discovery job can fetch it: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... ### master is currently 4.3.0.Beta1 ### when staging 4.3.0.Beta1 ### latest development milestone (4.3.0.Alpha2) ... # master version of devstudio-earlyaccess.properties should be edited here, so the discovery job can fetch it: https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... ### master is currently 9.0.0.Beta1 ### when staging 9.0.0.Alpha2 ### latest development milestone (will be 9.0.0.Beta1) {code} If you're asking why we need a different version in master/ vs. 4.3.mars/ that's to allow changes in master branch (eg. Beta2) which are different from those in 4.3.mars (Beta1x branch). We might not need it, but this way it's available should the time come where we DO need to differentiate. > 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: Nick Boldt > Fix For: 4.3.0.Beta1 > > > 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] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19756: ------------------------------- Attachment: jbide19756_new_subfolders_and_zipfile_name.png With this commit, the zip filename and root folder are updated to Max's new requirement: https://github.com/jbosstools/jbosstools-build-sites/commit/d10925280a4f7... !jbide19756_new_subfolders_and_zipfile_name.png! > jbosstools-src.zip has incomplete/misleading version info in folder names/structure > ----------------------------------------------------------------------------------- > > Key: JBIDE-19756 > URL: https://issues.jboss.org/browse/JBIDE-19756 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: jbide19756.png, jbide19756_new_subfolders_and_zipfile_name.png > > > Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named: > <componentname>_<buildqualifier>_<sha1> > example: > jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad > A few issues with this: > a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ? > b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-583) Add Section for OpenShift v3

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-583?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-583: ------------------------------------------ [~maxandersen] - yes, that was what we decided. > Add Section for OpenShift v3 > ---------------------------- > > Key: TOOLSDOC-583 > URL: https://issues.jboss.org/browse/TOOLSDOC-583 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: User Guide > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > Add Section for OpenShift that is specific to architecture v3 which is based on Kubernetes and Docker. Should include similar section to what exists for v2 http://tools.jboss.org/documentation/howto/#developing-apps-for-the-cloud -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3283) Ionic palette should use 1.0.0.GA if available before devstudio is released

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3283?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3283. ---------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Beta2) Resolution: Done Done for Beta1. See JBIDE-19793. > Ionic palette should use 1.0.0.GA if available before devstudio is released > --------------------------------------------------------------------------- > > Key: JBDS-3283 > URL: https://issues.jboss.org/browse/JBDS-3283 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, requirements, target-platform, upstream > Affects Versions: 9.0.0.Alpha1 > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Fix For: 9.0.0.Beta1 > > > Graduate Ionic Framework Tooling capabilities out of Tech Preview (assuming the OSS upstream is also moving to 1.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