December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15380) EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15380?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15380: ------------------------------------- Estimated Difficulty: Medium > EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER) > --------------------------------------------------------------------------------------- > > Key: JBIDE-15380 > URL: https://issues.jboss.org/browse/JBIDE-15380 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Mickael Istria > Fix For: LATER > > > When pushing to Openshift with JBT, it is very common to get a Timeout because the hooks take too much time to run. > Instead of this simple timeout, I'd rather see: > * The hooks output shown in the push dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15476) Allow users to provide downloadble cartidges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15476?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15476: ------------------------------------- Assignee: (was: Andre Dietisheim) Estimated Difficulty: Medium > Allow users to provide downloadble cartidges > -------------------------------------------- > > Key: JBIDE-15476 > URL: https://issues.jboss.org/browse/JBIDE-15476 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Alpha2 > Reporter: Andre Dietisheim > Labels: help_wanted > Fix For: LATER > > Attachments: 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.png, add-cartridge.png, add-downloadable-cartridge.png, new-application-1.png, new-application-2.png > > > OpenShift allows lately to provide your very own cartridge by giving it a git-url where the cartridge source may get cloned from. In the Web-UI this looks as follows: > !add-downloadable-cartridge.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14307) create unit-tests for Importing procedures

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14307?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14307: ------------------------------------- Assignee: (was: Andre Dietisheim) > create unit-tests for Importing procedures > ------------------------------------------ > > Key: JBIDE-14307 > URL: https://issues.jboss.org/browse/JBIDE-14307 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: LATER > > > The import startegies / procedures are pretty complex and we definitely should unit-test them. > Unfortunately they're still very tied to the UI and thus there's still some work to do to be able to unit-test them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13962) Help user configuring their DB connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13962?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13962: ------------------------------------- Estimated Difficulty: High > Help user configuring their DB connection > ------------------------------------------ > > Key: JBIDE-13962 > URL: https://issues.jboss.org/browse/JBIDE-13962 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Fix For: LATER > > > the port-forwarding tooling is a required step to setup the connection to the database, but then users are still on their own when they have to provide all that's necessary in the DataSource Explorer for example. This could be automatted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

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

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-14341: ------------------------------------- [~adietish]still a lower priority item > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13936) Server Adapter: Support deployment on multiple applications (eg: test vs prod)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13936?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13936: ------------------------------------- Estimated Difficulty: High > Server Adapter: Support deployment on multiple applications (eg: test vs prod) > ------------------------------------------------------------------------------- > > Key: JBIDE-13936 > URL: https://issues.jboss.org/browse/JBIDE-13936 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Labels: server_adapter > Fix For: LATER > > > could we support multiple platforms and have a workflow of the following kind: > 1 - user deploys to a 'test' platform/application > 2 - user tests/check it's all good > 3 - if so, he can deploy on the 'production' platform/application > This would mean, for example, having 2 server adapters and being able to support 2 'git remotes' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13962) Help user configuring their DB connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13962?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13962: ------------------------------------- Assignee: (was: Andre Dietisheim) > Help user configuring their DB connection > ------------------------------------------ > > Key: JBIDE-13962 > URL: https://issues.jboss.org/browse/JBIDE-13962 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Fix For: LATER > > > the port-forwarding tooling is a required step to setup the connection to the database, but then users are still on their own when they have to provide all that's necessary in the DataSource Explorer for example. This could be automatted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12333) Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12333?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12333: ------------------------------------- Estimated Difficulty: Medium > Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge) > -------------------------------------------------------------------------------------- > > Key: JBIDE-12333 > URL: https://issues.jboss.org/browse/JBIDE-12333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: enable-jenkins-build-2.png, enable-jenkins-build.png > > > If you want to switch to a jenkins based build you'd currently have to add the jenkins-client to your application. The OpenShift WebUI does this in a far more explicit and user friendly way: > It explicilty features a button that "enable jenkins build" > !enable-jenkins-build.png! > !enable-jenkins-build-2.png! > We should provide something equivalent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-13407: ------------------------------------- [~nickboldt]should we try again for JBDS 8 timeframe? > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > Attachments: dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12333) Application wizard, Embed wizard: Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12333?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12333: ------------------------------------- Summary: Application wizard, Embed wizard: Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge) (was: Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)) > Application wizard, Embed wizard: Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge) > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-12333 > URL: https://issues.jboss.org/browse/JBIDE-12333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: enable-jenkins-build-2.png, enable-jenkins-build.png > > > If you want to switch to a jenkins based build you'd currently have to add the jenkins-client to your application. The OpenShift WebUI does this in a far more explicit and user friendly way: > It explicilty features a button that "enable jenkins build" > !enable-jenkins-build.png! > !enable-jenkins-build-2.png! > We should provide something equivalent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 December 2013