July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3944) Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3944?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-3944: ---------------------------- Attachment: (was: error_message.png) > Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3944 > URL: https://issues.jboss.org/browse/JBDS-3944 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, platform-installer > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 10.0.0.GA > > Attachments: appears_to_hang.png, error.png > > > See the attached screenshots - starting the CDK runtime as a server appears to hang as the error dialog is opened "behind" the Dev Studio IDE window. > It's possible that a user will overlook where to locate the error dialog. Can we add a note/warning about this to the user docs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3944) Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3944?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-3944: ---------------------------- Comment: was deleted (was: Draft of content.) > Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3944 > URL: https://issues.jboss.org/browse/JBDS-3944 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, platform-installer > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 10.0.0.GA > > Attachments: appears_to_hang.png, error.png > > > See the attached screenshots - starting the CDK runtime as a server appears to hang as the error dialog is opened "behind" the Dev Studio IDE window. > It's possible that a user will overlook where to locate the error dialog. Can we add a note/warning about this to the user docs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3944) Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3944?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3944: --------------------------------- [~ldimaggio] - I've added a message to the docs draft and attached a screenshot since it includes the error screenshot you posted. Can you have a look and let me know if it looks okay to you? > Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3944 > URL: https://issues.jboss.org/browse/JBDS-3944 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, platform-installer > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 10.0.0.GA > > Attachments: appears_to_hang.png, error.png, error_message.png > > > See the attached screenshots - starting the CDK runtime as a server appears to hang as the error dialog is opened "behind" the Dev Studio IDE window. > It's possible that a user will overlook where to locate the error dialog. Can we add a note/warning about this to the user docs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3944) Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3944?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-3944: ---------------------------- Attachment: error_message.png Draft of content. > Installing "over" existing installation can fail due to duplicate vagrant env - error dialog may be hidden from user > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3944 > URL: https://issues.jboss.org/browse/JBDS-3944 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, platform-installer > Affects Versions: 10.0.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 10.0.0.GA > > Attachments: appears_to_hang.png, error.png, error_message.png > > > See the attached screenshots - starting the CDK runtime as a server appears to hang as the error dialog is opened "behind" the Dev Studio IDE window. > It's possible that a user will overlook where to locate the error dialog. Can we add a note/warning about this to the user docs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Shane Bryzak resolved ERT-132. ------------------------------ Fix Version/s: Neon.1 (4.6) Resolution: Done > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Shane Bryzak > Labels: General, bzira > Fix For: Neon.1 (4.6) > > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22550) Prepare parent pom for 4.4.1 / 10.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22550?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22550. ------------------------------ Fix Version/s: 4.4.1.AM1 (was: 4.4.1.AM2) Resolution: Done > Prepare parent pom for 4.4.1 / 10.1 > ----------------------------------- > > Key: JBIDE-22550 > URL: https://issues.jboss.org/browse/JBIDE-22550 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM1 > > > * upversion parent pom to 4.4.1.Alpha1 > * set new lastStableRepository = http://download.jboss.org/jbosstools/neon/staging/updates/ to ensure baseline checks look at 4.4.0.Final instead of 4.3.x versions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22557: ------------------------------- Fix Version/s: 4.4.1.AM1 > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22557 > URL: https://issues.jboss.org/browse/JBIDE-22557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM1, 4.4.1.AM2 > > > For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22557. ------------------------------ Resolution: Done > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22557 > URL: https://issues.jboss.org/browse/JBIDE-22557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM2, 4.4.1.AM1 > > > For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22557: ------------------------------------ Done: * versionwatch: 0.4.100 (no parent) * devdoc, dl.jb.org: N/A * maven-plugins: 0.25.1-SNAPSHOT (no parent) * build: 4.4.1.Alpha1-SNAPSHOT, with BUILD_ALIAS=AM1 * build-sites: uses pp 4.4.1.Alpha1-SNAPSHOT * build-ci: bumped to 4.4.1.AM2-SNAPSHOT > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22557 > URL: https://issues.jboss.org/browse/JBIDE-22557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM2 > > > For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22704) Application Wizard: Application based on builder images do not have prefilled configuration

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22704?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22704: ----------------------------------------------- I guess that in this use case ApplicationSourceFromImageModel.setDockerConnection() (inherited from DeployImageWizardModel is not called), so that DeployImageWizardModel.dockerConnection remains null until getDockerConnection() is called, but it must be not called in this case either. That means that method DeployImageWizardModel.lookupImageMetadata may need to call getDockerConnection() instead of just accessing field dockerConnection. > Application Wizard: Application based on builder images do not have prefilled configuration > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22704 > URL: https://issues.jboss.org/browse/JBIDE-22704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > When opening a New OpenShift Application wizard either from Central or shell menu File - New, details in builder image part of wizard are missing. E.g. there is no default resource name (build configuration wizard page), environment variables (Deployment Configuration and Scalability wizard page) or port mapping (Service and Routing Settings wizard page). When opening the wizard from context menu of an OpenShift 3 project, its works fine. -- 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 July 2016