March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3360: ------------------------------------ Assigned to Martin M. to test with JBDS 8.1.0.beta1 > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Len DiMaggio reassigned JBDS-3360: ---------------------------------- Assignee: Martin Malina (was: Len DiMaggio) > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3250) Support for OpenShift 3 with Docker and Kubernetes

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3250: ------------------------------------ Unresolved QE ambiguity review question - preventing QE from acking: * Are committing to resolving all the JIRAs in this Epic for 9.0? Or, will we complete a subset (which JIRAs?) of these? > Support for OpenShift 3 with Docker and Kubernetes > -------------------------------------------------- > > Key: JBDS-3250 > URL: https://issues.jboss.org/browse/JBDS-3250 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 9.0.0.GA > > > Copied from JBDS-3278: > As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API. > The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture. > For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"): > {quote} > It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo…. > Our Eclipse end-user needs to be able to “browse” for it and select it > git clone it > make changes > git push it back > {quote} > This gives us 3 main use cases (as in mail and chats): > # Import existing OpenShift project (JBDS-3297) > # Push Changes to Existing OpenShift project (JBDS-3298) > # New Project from Template (template should have a default buildconfig, deployconfig and docker image) (JBDS-3306) > {quote} > Use Case #1 assumes a TON about what has happened before me. > - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL > - Assumes end-user is already logged in (there is no auth method at this time) > - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc. > {quote} > We have a more extensive document that outlines the usecases: > https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_... > {quote} > These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling: > 1) Create SSH Keys > 2) Upload SSH Keys > 3) Create Domain > 4) Add a database, message broker, cache (embeddable cartridge) > 5) Show In Web Browser > 6) Review Env Vars > 7) Edit Env Vars > 8) Review Logs > 9) Log Streaming > 10) SSH in > 11) Delete/Destroy > 12) Remote Debugging (though that might "just work") > 13) Snapshot creation > 14) Snapshot restore > 15) Port Forwarding > 16) Marker Files > 17) Node.js > 18) PHP > 19) Python > 20) C++ > 21) Perl > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3160) JSR-352: Java EE 7 Batch

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3160?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3160: ------------------------------------ Unresolved QE ambiguity review question - preventing QE from acking: * What specific features are we supporting? Are we adding the tree-form editor and nothing else? Something else? > JSR-352: Java EE 7 Batch > ------------------------ > > Key: JBDS-3160 > URL: https://issues.jboss.org/browse/JBDS-3160 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 9.0.0.CR1 > > Attachments: BatchEditor.png > > > Custom XML Editor for the Batch configuration XML > Example > https://github.com/javaee-samples/javaee7-samples/blob/master/batch/chunk... > JSR-352: Batch > I, the Java EE application developer, wish to create new and maintain Batch (JSR-352) applications in Eclipse. I need XML editing support, content-assist where appropriate and a Maven-based quickstart to help with getting started. > The quickstart should be easily importable into JBDS and allow for editing so that I, the Java EE app dev, can "make it my own" by changing its project name, group, artifact id and version, plus modifying the XML file, adding/removing classes, etc. > This effort should primarily be focused on the XML editing experience. The normal New Java Class wizard should support the batch related super classes (extends). Run As Run on Server should work as well. > Examples of the XML: > https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch... > https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-588) Generate Release Notes doc for JBDS 8.1.0CR1

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-588?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-588. -------------------------------- Resolution: Done > Generate Release Notes doc for JBDS 8.1.0CR1 > -------------------------------------------- > > Key: TOOLSDOC-588 > URL: https://issues.jboss.org/browse/TOOLSDOC-588 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Affects Versions: 4.2.3.Final > Reporter: Michelle Murray > Assignee: Misha Ali > Fix For: 4.2.3.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19468) [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19468?page=com.atlassian.jira.plugi... ] George Gastaldi edited comment on JBIDE-19468 at 3/18/15 11:20 AM: ------------------------------------------------------------------- This bug slipped through our fingers in the latest version. We just fixed that and should be available in the next release. The workaround is: # Open the pom.xml from the addon project # Add a {{<version.forge>}} property and set to 2.15.1.Final # Change the {{<version>}} from the {{forge-bom}} artifactId to use ${version.forge} was (Author: gastaldi): This bug slipped through our fingers in the latest version. We just fixed that and should be available in the next release. The workaround is: # Open the pom.xml from the addon project # Change the {{<version.furnace>}} property to {{<version.forge>}} and set to 2.15.1.Final # Change the {{<version>}} from the {{forge-bom}} artifactId to use ${version.forge} > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19 > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19468 > URL: https://issues.jboss.org/browse/JBIDE-19468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: Pavol Srna > Fix For: 4.2.3.CR1 > > Attachments: forge-err.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3245) Improve Eclipse Platform

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3245: ------------------------------- CDW qa_ack: + (was: ?) > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-3273 at 3/18/15 11:13 AM: -------------------------------------------------------------- Unresolved QE ambiguity review question - preventing QE from acking: * What will users see when this is implemented? Will they be able to search (how?) for quickstarts? was (Author: ldimaggio): Unresolved QE ambiguity review question - preventing QE from acking: What will users see when this is implemented? Will they be able to search (how?) for quickstarts? > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3322?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3322: ------------------------------------ Unresolved QE ambiguity review question - preventing QE from acking: * The examples that Max referred to are limited to fixing import statements - what exactly will we support for JBDS 9.0? > 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 > Priority: Minor > Labels: websockets > Fix For: 9.0.0.Alpha2 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-588) Generate Release Notes doc for JBDS 8.1.0CR1

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-588?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-588. -------------------------------- Resolution: Done Done and available on the stage now: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Generate Release Notes doc for JBDS 8.1.0CR1 > -------------------------------------------- > > Key: TOOLSDOC-588 > URL: https://issues.jboss.org/browse/TOOLSDOC-588 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Affects Versions: 4.2.3.Final > Reporter: Michelle Murray > Assignee: Misha Ali > Fix For: 4.2.3.CR1 > > -- 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