June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18119) Add Tests to support jbide-17919

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18119?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18119: ------------------------------------------ closing as partially done, more coverage was planned but efforts are now focused on OpenShift v3 where snapshots will get replaced. > Add Tests to support jbide-17919 > -------------------------------- > > Key: JBIDE-18119 > URL: https://issues.jboss.org/browse/JBIDE-18119 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Priority: Minor > Labels: tests > Fix For: LATER > > > Add the tests to support the changes made to JBIDE-17919 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18119) Add Tests to support jbide-17919

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18119?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-18119. -------------------------------------- Resolution: Partially Completed > Add Tests to support jbide-17919 > -------------------------------- > > Key: JBIDE-18119 > URL: https://issues.jboss.org/browse/JBIDE-18119 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Priority: Minor > Labels: tests > Fix For: LATER > > > Add the tests to support the changes made to JBIDE-17919 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18119) Add Tests to support jbide-17919

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18119?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-18119. ------------------------------------ > Add Tests to support jbide-17919 > -------------------------------- > > Key: JBIDE-18119 > URL: https://issues.jboss.org/browse/JBIDE-18119 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Priority: Minor > Labels: tests > Fix For: LATER > > > Add the tests to support the changes made to JBIDE-17919 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11134) Application wizard: Do not put Eclipse files into .gitignore if an existing project is shared with different Git repository

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11134?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11134: --------------------------------------------- Not closing because we don't have time, closed because it is for v1 and it works okey now. we will need to consider this when doing v3 support though. > Application wizard: Do not put Eclipse files into .gitignore if an existing project is shared with different Git repository > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-11134 > URL: https://issues.jboss.org/browse/JBIDE-11134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Lucia Jelinkova > Priority: Minor > Labels: application_wizard > Fix For: LATER > > > When enabling an OpenShift application for an existing project that already contains Git configuration the OpenShift should not change the .classpath, .project and .settings configuration in .gitignore. The user might have had a reason not to ignore them and might be surprised when his configuration changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18119) Add Tests to support jbide-17919

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18119?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-18119: ------------------------------------------- Resolution: (was: Won't Fix) Assignee: Andre Dietisheim (was: Jeff Cantrill) the PR related to this issue seem to have been merged - was this not done then ? > Add Tests to support jbide-17919 > -------------------------------- > > Key: JBIDE-18119 > URL: https://issues.jboss.org/browse/JBIDE-18119 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Priority: Minor > Labels: tests > Fix For: LATER > > > Add the tests to support the changes made to JBIDE-17919 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-14341. --------------------------------------- Resolution: Rejected OpenShift v1/v2 Cartridges no longer makes sense to create tooling for. Work will focus around openshift v3, kubernetes and Docker. closing as wont fix. > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Assignee: Andre Dietisheim > Priority: Optional > Fix For: LATER > > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20078) [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20078?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20078: -------------------------------- Fix Version/s: 4.3.0.Beta2 > [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20078 > URL: https://issues.jboss.org/browse/JBIDE-20078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.3.0.Beta2 > > > Steps to reproduce: > 1) Create a workspace with 1 (or more) server adapters (of any type) > 2) Install jbt launchbar > 3) restart workbench > 4) Verify server exists > 5) Window -> Preferences -> Remote Development/Remote Connections page > 6) Expand combo, select Server Adapter > 7) Verify some matching o.e.remote exist that match existing server adapters in server view [FAIL] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20078) [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20078?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-20078: ----------------------------------- Assignee: Rob Stryker > [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20078 > URL: https://issues.jboss.org/browse/JBIDE-20078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > Steps to reproduce: > 1) Create a workspace with 1 (or more) server adapters (of any type) > 2) Install jbt launchbar > 3) restart workbench > 4) Verify server exists > 5) Window -> Preferences -> Remote Development/Remote Connections page > 6) Expand combo, select Server Adapter > 7) Verify some matching o.e.remote exist that match existing server adapters in server view [FAIL] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-14341: ---------------------------------------- Resolution: (was: Won't Fix) Assignee: Andre Dietisheim reopening to specify proper reason for closing > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Assignee: Andre Dietisheim > Priority: Optional > Fix For: LATER > > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20078) [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20078?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20078. --------------------------------- Resolution: Done This seems to have been committed already. Oops ;) > [launchbar] installing into workspace with pre-existing servers yields no matching o.e.remote connection > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20078 > URL: https://issues.jboss.org/browse/JBIDE-20078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > Steps to reproduce: > 1) Create a workspace with 1 (or more) server adapters (of any type) > 2) Install jbt launchbar > 3) restart workbench > 4) Verify server exists > 5) Window -> Preferences -> Remote Development/Remote Connections page > 6) Expand combo, select Server Adapter > 7) Verify some matching o.e.remote exist that match existing server adapters in server view [FAIL] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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