June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3452) Certify JBDS 9.0 with Supported EAP Releases

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3452?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3452: ------------------------------------ This JIRA was logged to add an additional layer of safety - to ensure that the testing is covered for the 9.0 release - given all the recent confusion related to the EAP7 testing. > Certify JBDS 9.0 with Supported EAP Releases > -------------------------------------------- > > Key: JBDS-3452 > URL: https://issues.jboss.org/browse/JBDS-3452 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: runtime > Affects Versions: 9.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Martin Malina > Fix For: 9.0.0.Beta1 > > > See: EAP7-194 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Jeff Cantrill commented on JBDS-3298: ------------------------------------- [~burrsutter], [~maxandersen], [~adietish] We should revisit what we want out of this feature. I know there was talk about binary deployments, etc, but technically, you should be able to do this if your OpenShift buildconfig is setup correctly and your repo has the appropriate webhook configuration. A user would 'git push' which would trigger a build on openshift. > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ] Jeff Cantrill updated JBDS-3306: -------------------------------- Labels: new_and_noteworthy (was: ) > Create Deployment from Template > ------------------------------- > > Key: JBDS-3306 > URL: https://issues.jboss.org/browse/JBDS-3306 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Jeff Cantrill > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Beta1 > > > Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ] Jeff Cantrill resolved JBDS-3306. --------------------------------- Resolution: Done > Create Deployment from Template > ------------------------------- > > Key: JBDS-3306 > URL: https://issues.jboss.org/browse/JBDS-3306 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19949) Import app automatically from new app wizard

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19949: ------------------------------------- Summary: Import app automatically from new app wizard Key: JBIDE-19949 URL: https://issues.jboss.org/browse/JBIDE-19949 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Jeff Cantrill Run the new app from template wizard and import the app as an eclipse project when its complete -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow

by David Hladky (JIRA)

David Hladky created JBIDE-19948: ------------------------------------ Summary: Reimplement Eclipse Download plugin to allow dynamic work flow Key: JBIDE-19948 URL: https://issues.jboss.org/browse/JBIDE-19948 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection, server Affects Versions: 4.3.0.Alpha2 Reporter: David Hladky We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones. Under this issue I will create the tasks we need to achieve this goal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ] Jeff Cantrill commented on JBDS-3306: ------------------------------------- [~burrsutter] [~maxandersen] As coded now, you can basically do this flow with the exception of step "i". A user must explicitly import the new app. Post summit, we will add the import into the new app flow > Create Deployment from Template > ------------------------------- > > Key: JBDS-3306 > URL: https://issues.jboss.org/browse/JBDS-3306 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19010) As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19010?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19010: --------------------------------------- [~burrsutter] [~maxandersen] This is a blocker to JBDS-3306 but w are able to do this now but not as originally envisioned. Technically, a user can create a template that supports deploying something just an image and its service, like a database. It may not be as easy as in v2 or exactly how we want to do it in v3. I would suggest removing this is a blocker and revisit this feature post summit to decide if it is still needed and how exactly we envision it working. > As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19010 > URL: https://issues.jboss.org/browse/JBIDE-19010 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Priority: Blocker > Labels: application_wizard, v3 > Fix For: 4.3.0.Beta2 > > > https://trello.com/c/HyTyFlHw > This is the usecase where we want to deploy an image that most likely does not include a buildconfig, i.e. a database image. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19944: ------------------------------------- Once we have a replacement with the same xml structure, we'll just need to change https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-... > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19944: -------------------------------- Fix Version/s: 4.3.0.Beta2 > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-... > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015