June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-789) Extend DroolsProjectTest and MavenProjectTest

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/JBTIS-789?page=com.atlassian.jira.plugin.... ] Tomas David updated JBTIS-789: ------------------------------ Description: E > Extend DroolsProjectTest and MavenProjectTest > --------------------------------------------- > > Key: JBTIS-789 > URL: https://issues.jboss.org/browse/JBTIS-789 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: drools/ jBPM, QE > Reporter: Tomas David > Assignee: Tomas David > Priority: Minor > > E -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-789) Extend DroolsProjectTest and MavenProjectTest

by Tomas David (JIRA)

Tomas David created JBTIS-789: --------------------------------- Summary: Extend DroolsProjectTest and MavenProjectTest Key: JBTIS-789 URL: https://issues.jboss.org/browse/JBTIS-789 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: drools/ jBPM, QE Reporter: Tomas David Assignee: Tomas David Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15978) Properties view: URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15978?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-15978: ---------------------------------------- Assignee: (was: Dmitry Bocharov) > Properties view: URL for embedded cartridges is empty > ----------------------------------------------------- > > Key: JBIDE-15978 > URL: https://issues.jboss.org/browse/JBIDE-15978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: properties > Fix For: LATER > > Attachments: empty-url-property.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20125) Import wizard, application wizard: use easy import, not our custom facility

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20125?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20125: ------------------------------------- Summary: Import wizard, application wizard: use easy import, not our custom facility (was: v3 Import-, application wizard: use easy import, not our custom facility) > Import wizard, application wizard: use easy import, not our custom facility > --------------------------------------------------------------------------- > > Key: JBIDE-20125 > URL: https://issues.jboss.org/browse/JBIDE-20125 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.x > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The current impl of the import wizard in v2 and v3 is using a custom import logic where it launches m2e for repositories that have a pom.xml and "General project" for all the others. In JBDS-3285 [~mickael_istria] contributed a new Easy import facility for Eclipse that we should use instead of our own minimalistic, custom made approach -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3951: -------------------------------- Fix Version/s: 10.0.1.Alpha1 > Installer needs to add the VirtualBox install directory to the PATH > ------------------------------------------------------------------- > > Key: JBDS-3951 > URL: https://issues.jboss.org/browse/JBDS-3951 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.1.Alpha1 > > > The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found. > As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3609: ----------------------------- Attachment: 3609_06152016_112757.png 3609_06152016_112229.png 3609_06152016_112343.png 3609_06152016_112445.png Screenshots captured from installing devstudio-10.0.0.GA-v20160615-1853-B33-installer-standalone.jar ... * [^3609_06152016_112229.png] * [^3609_06152016_112343.png] * [^3609_06152016_112445.png] * [^3609_06152016_112757.png] > update splashscreen, about gfx, start icon for developers.redhat.com > -------------------------------------------------------------------- > > Key: JBDS-3609 > URL: https://issues.jboss.org/browse/JBDS-3609 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 10.0.0.GA > > Attachments: 3609_06152016_112229.png, 3609_06152016_112343.png, 3609_06152016_112445.png, 3609_06152016_112757.png, about-jbds10.png, devstudio_assets_revised.zip, launcher-icons-jbds10.png, splash-jbds10.png > > > update splashscreen, about gfx, start icon for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22452) Application Wizard: Git reference text widget does not validate values

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22452?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22452: ------------------------------------------ Fix Version/s: 4.4.1.Alpha1 (was: 4.4.x) > Application Wizard: Git reference text widget does not validate values > ---------------------------------------------------------------------- > > Key: JBIDE-22452 > URL: https://issues.jboss.org/browse/JBIDE-22452 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > On the Build Configuration wizard page there is a text widget for git reference. Tooltip say there could be put branch, tag or commit. There is no validation at the moment. Although the field is optional, it would be nice if there is any value, it would be validated. Commits are hexadecimal values what is less restrictive then tags or branches. For tag and branches see reference at https://git-scm.com/docs/git-check-ref-format or use "git check-ref-format --help". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22452) Application Wizard: Git reference text widget does not validate values

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22452?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22452: ----------------------------------------------- [~adietish], please take a look at the pull request that implements the basic format validation. > Application Wizard: Git reference text widget does not validate values > ---------------------------------------------------------------------- > > Key: JBIDE-22452 > URL: https://issues.jboss.org/browse/JBIDE-22452 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > > On the Build Configuration wizard page there is a text widget for git reference. Tooltip say there could be put branch, tag or commit. There is no validation at the moment. Although the field is optional, it would be nice if there is any value, it would be validated. Commits are hexadecimal values what is less restrictive then tags or branches. For tag and branches see reference at https://git-scm.com/docs/git-check-ref-format or use "git check-ref-format --help". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22606) Document go_offline.groovy usage

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22606: ----------------------------------- Summary: Document go_offline.groovy usage Key: JBIDE-22606 URL: https://issues.jboss.org/browse/JBIDE-22606 Project: Tools (JBoss Tools) Issue Type: Task Components: project-examples Affects Versions: 4.4.0.Final Reporter: Fred Bricon The go_offline.groovy scripts currently lacks a detailed documentation, most notably on the example descriptor format requirements, we ought to fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22225: ------------------------------------- [~fbricon], I also run the app on Openshift with DEV_MODE=true (this exposes 5858 port and runs node with *--debug* option), however I did it via *os* CLI. Basically, I was not able to debug the app on OpenShift (keep getting "connection refused"). So, I firstly decided to understand how to debug container with the node app locally and after that switch to OpenShift instance (I assume that the idea behind debugging container locally and on OpenShift is just the same) > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.x > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016