December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21214) Domain modification via Credential preferences page doesn't work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21214?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21214: ----------------------------------- Fix Version/s: 4.3.1.Beta2 4.4.0.Alpha1 > Domain modification via Credential preferences page doesn't work > ---------------------------------------------------------------- > > Key: JBIDE-21214 > URL: https://issues.jboss.org/browse/JBIDE-21214 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Environment: Fedora 22 KDE 64 bit > Reporter: Vlado Pakan > Assignee: Rob Stryker > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > 1. Open Window > Preferences > JBoss Tools > Creddentials > 2. Add Domain > 3. Modify domain via Edit button and choose OK > ERROR: Domain is not modified it shows previous domain name in prefences page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3562: ---------------------------------- Blog added to previous PR, which Alexey has merged: https://github.com/jbosstools/jbosstools-website/pull/527 Now just waiting for it to go live... http://tools.jboss.org/blog/ > Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501) > -------------------------------------------------------------------------- > > Key: JBDS-3562 > URL: https://issues.jboss.org/browse/JBDS-3562 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.CVE-2015-7501-GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.CVE-2015-7501-GA > > Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png > > > Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds. > Because JBDS 9.0.0 includes the compromised version of > apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which > will include: > a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.* > b) repin of JBDS update sites and installer jars > To that end, I've created the following new branches: > https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x > https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x > And I've bumped the version of the target platforms in the 4.50.x and > 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT, > respectively. > JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the > 4.3.1.x branch. > https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3... > (new, 9.0.1) > https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x > (updated to 9.1.0) > So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for > 9.0.1, Beta1 for 9.1.0) and target platforms are used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20531: --------------------------------------- [~mlabuda] Maybe..but then we have to provide additional validators right? > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-20531 > URL: https://issues.jboss.org/browse/JBIDE-20531 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > Attachments: Service and routing page.png, service port edit dialog.png > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20093) Application wizard: I cannot browse workspace when using local template/json

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20093?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20093. --------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.x) Assignee: Fred Bricon Resolution: Done That one was fixed as part of JBDS-3489 (commit https://github.com/jbosstools/jbosstools-openshift/commit/9b6e8d60ff1bf6b...) > Application wizard: I cannot browse workspace when using local template/json > ---------------------------------------------------------------------------- > > Key: JBIDE-20093 > URL: https://issues.jboss.org/browse/JBIDE-20093 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: templates-from-local-filesystem.png > > > if I have projects cloned in openshift with kubernetes.json or templates I can't load them from the openshift app wizard. > The wizard forces me to use the local file system which is rather limiting. > Suggestion: support both workspace/filesystem buttons. > Steps: > # EXEC: launch New application wizard for v3 (create app from template) > # ASSERT: application wizard pops up > # EXEC: choose "Use a template from local filesystem", hit "Browse" > !templates-from-local-filesystem.png! > Result: > I can browse the local filesystem > Expected > I would like to be able to pick a template from a workspace project -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20508) Makes workflow to modify application based on OS v3 templates user friendly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20508?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20508. --------------------------------- Resolution: Won't Fix Closing as Won't fix as JBDS-3489 should cover that issue > Makes workflow to modify application based on OS v3 templates user friendly > --------------------------------------------------------------------------- > > Key: JBIDE-20508 > URL: https://issues.jboss.org/browse/JBIDE-20508 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Critical > Fix For: 4.3.1.Beta1 > > > Currently if user wants to modify an existing application based on a template with source code, user has to fork a repo containing source code, copy URL of a fork and paste it into template parameter SOURCE_CODE_URL. This is a bit unfriendly work flow from my point of view, because it requires several steps: > 1) At first user has to know an URL of a source code for a template. Intuitively user would go through New Application Wizard to Template Parameters wizard page and check value of SOURCE_CODE_URL parameter. > 2) Fork a repository containing source code - it requires switching to browser and go to the repository web page and fork repo. > 3) Copy a URL of user's source code repo (its easier to use SSH url git@github.com:user/repo.git to avoid filling in credentials for a github account) > plus importing an application, making changes, commit and push. > Would it be possible to create a fork and use user specific URL automatically? E.g. show a dialog to enter github username and tooling would via git API fork the repo and put the user specific source code URL into wizard page as template parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-20609: -------------------------------------- Pros and Cons for this feature - as shown in the videos. If a user knows which early access feature he wants to work with, then the new approach may be better as they will not have to hunt for the feature in a list of multiple features offering early access. However, if they are curious about exploring the full set of what is available in early access, the old approach may work better. I'd recommend not rushing this feature into Beta1 until we can get a better/wider consensus from everyone. Thx! > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-537) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-537?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-537: ---------------------------------- Hey [~rhopp] - Just trying to reproduce this issue on my end. I did this: 1. Download JBDS 9.0.0.GA stand-alone installer from http://www.jboss.org/products/devstudio/get-started/#!project=devstudio 2. Install JBDS 9.0.0.GA (jboss-devstudio-9.0.0.GA-installer-standalone.jar 3. ./jbdevstudio Note that in JBoss Central - the Fuse Project does not exist because 'Early Access' is not enabled in the Software/Update tab.!fuse1.png|thumbnail! 4. Select the Software/Update tab !fuse2.png|thumbnail! - check the 'Enable Early Access' checkbox. 5. Select the 'Getting Started' tab - the Fuse Integration Project is now available. !fuse3.png|thumbnail! 6. The wizard will install fuse tooling !fuse4.png|thumbnail! !fuse5.png|thumbnail! Installation complete !fuse6.png|thumbnail! Please try the above sequence. Thanks! ref: [~nickboldt] > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-537 > URL: https://issues.jboss.org/browse/JBTIS-537 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Paul Leacu > Priority: Critical > Attachments: fuse1.png, fuse2.png, fuse3.png, fuse4.png, fuse5.png, fuse6.png > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-537) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-537?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-537: ----------------------------- Attachment: fuse4.png > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-537 > URL: https://issues.jboss.org/browse/JBTIS-537 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Paul Leacu > Priority: Critical > Attachments: fuse1.png, fuse2.png, fuse3.png, fuse4.png, fuse5.png, fuse6.png > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20113) core plugins need extension points for ui integration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20113?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20113: ------------------------------------- [~adietish] wasn't this fixed by JBIDE-21153 and https://github.com/jbosstools/jbosstools-openshift/commit/e52fc1575420659... > core plugins need extension points for ui integration > ----------------------------------------------------- > > Key: JBIDE-20113 > URL: https://issues.jboss.org/browse/JBIDE-20113 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.3.x > > > JBIDE-15496 did the initial separation into ui/core plugins but implemented a simplified ui integration where core needed to open ui. UI should have extension points that core registers against -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21235) Incorrect updating Runtime Enfironment input in server editor

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-21235: --------------------------------------------- Summary: Incorrect updating Runtime Enfironment input in server editor Key: JBIDE-21235 URL: https://issues.jboss.org/browse/JBIDE-21235 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.0.Alpha1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Priority: Minor 1. Create in preferences several server runtime environments for the same JBoss runtime type. 2. Create a server for one of them and open it in the server editor. 3. Select another 'Runtime Environment' and save the change. 4. Open preferences and add one more new runtime environment for the same runtime type. 5. In server editor 'Runtime Environment' returned to the original choice - failure. 6. Close/reopen server editor - 'Runtime Environment' shows correct choice saved before. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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