April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3739: ------------------------------------- I decided to reopen this JIRA since [~mlabuda] just reported that he sees exactly the same behavior as I do (I'm on Mac, he's on linux). > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Hardy Ferentschik > Priority: Blocker > Labels: havoc > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-729) JBDS 9.1 GA: Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-729?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-729: ---------------------------------------- You can see the aggregated N&N content on stage here: http://tools.stage.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Fina... > JBDS 9.1 GA: Release Notes > -------------------------- > > Key: TOOLSDOC-729 > URL: https://issues.jboss.org/browse/TOOLSDOC-729 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create release notes for GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22198) Sometimes validation for required parameter in Template Parameters wizard page when creating an application is not available

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22198?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22198: ----------------------------------------------- Parameter is validated at rendering its table cell. Page validation status is computed iterating over the validation results of parameters. I can suppose that at the time of the first validation, rendering may be not called yet. [~aurelien.pupier], try reproducing the issue when you first visit 'Template Parameters' page and when you go back to select another template and forward again to template parameters. > Sometimes validation for required parameter in Template Parameters wizard page when creating an application is not available > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22198 > URL: https://issues.jboss.org/browse/JBIDE-22198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Attachments: screenshot-1.png > > > Having a validation, forbidding to go to next page and click finish will provide more guidance to user and avoid him an error dialog when clicking finish -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-654: ---------------------------------- Hey [~ldimaggio] - the only real visible difference between the JBDSIS stand-alone installer and the JB DS stand-alone installer is the size and the addition of this attachment: [^inst1.png] [~aileenc] [~bfitzpat] - this installer is an example - since Fuse Tooling is still EA only the Fuse Tooling example from Central doesn't show up. Once JBDSIS 9.0.0.GA is out of the way I'll move Fuse from EA to the released side (in preparation of JBDSIS 9.0.1) and we should get a better feel. We did discuss the idea of having a Fuse Tooling specific installer (that has Fuse Tooling checked off for you) but creating a specific installer vs. asking the user to check off the Fuse box didn't seem worth it. I like the stand-alone installer and think that having all of the released components available to select (with Fuse on top) seems like a good solution. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-654: ----------------------------- Attachment: inst1.png > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22195: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-22195: ------------------------------------- Assignee: Xavier Coulon > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22200) Create and use Neon M7 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22200?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22200: ------------------------------------ For M7, equinox.log has been removed. But our current M5 TP (4.60.0.Alpha1) doesn't include that plugin. So no impact there. > Create and use Neon M7 target platform > -------------------------------------- > > Key: JBIDE-22200 > URL: https://issues.jboss.org/browse/JBIDE-22200 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Prepare TP to use Neon M7 bits. Cloned from JBIDE-21386. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-729) JBDS 9.1 GA: Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-729?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-729: ---------------------------------------- Thanks for the update, [~mhusnain]. 1. OK 2. OK 3. The New Features content is now incomplete. It should be a merge of Beta1, Beta2 and CR1/GA. In theory it should be exactly the same as displayed here: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html But unfortunately for now the aggregation doesn't work there yet. Hopefully that will be resolved soon. For each item, there is an option whether or not it should be aggregated to the Final one - for example the CDK server adapter was released in one of the Betas, but it's still relevant to list this in the GA release notes. So I recommend you wait until this works correctly on the JBoss Tools website. Here is the final page: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html Beta1: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.html Beta2: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html I created a JIRA to have this fixed: JBIDE-22199 4. This is the query you're using now: {code} (project in (JBDS) AND affectedVersion < 9.1.0.GA AND fixVersion in (9.1.0.Beta1, 9.1, 9.1.0.Beta2, 9.1.0.CR1, 9.1.0.Final, 9.1.0.GA, "9.1 Beta2", "9.1 CR1", "9.1 GA") OR project in (JBIDE) AND affectedVersion < 4.3.1.Final AND fixVersion in (4.3.1.Beta1, 4.3.1, 4.3.1.Beta2, 4.3.1.CR1, 4.3.1.Final)) AND type in (Bug) AND resolution in (Done) {code} I have a couple of comments: I thought you wanted to remove "affectedVersion"? I'm fine either way, but I'm confused why you added it back now. The versions for JBDS seem wrong. You have some items that don't really exist. We only have these: 9.1.0.Beta1, 9.1.0.Beta2, 9.1.0.CR1, 9.1.0.GA. For JBIDE, you have one redundant version: 4.3.1 5. OK > JBDS 9.1 GA: Release Notes > -------------------------- > > Key: TOOLSDOC-729 > URL: https://issues.jboss.org/browse/TOOLSDOC-729 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create release notes for GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-654: ----------------------------------------- [~pleacu] - is there any chance we can update the summary (step 7) of the installer to include the "additional bits" the user selects? or select all the fuse bits by default on step 6? > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 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 April 2016