July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3960) Rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3960?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3960: ------------------------------ Fix Version/s: 10.1.0.AM2 > Rename platform installer artifacts to start with "devsuite" instead of "development-suite" > ------------------------------------------------------------------------------------------- > > Key: JBDS-3960 > URL: https://issues.jboss.org/browse/JBDS-3960 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Jan Richter > Fix For: 10.1.0.AM2 > > > Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" > So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3960) Rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3960?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3960: ------------------------------ Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu..., https://github.com/redhat-developer-tooling/developer-platform-install/pu... (was: https://github.com/redhat-developer-tooling/developer-platform-install/pu...) > Rename platform installer artifacts to start with "devsuite" instead of "development-suite" > ------------------------------------------------------------------------------------------- > > Key: JBDS-3960 > URL: https://issues.jboss.org/browse/JBDS-3960 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Jan Richter > > Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" > So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22664) Invalid registry URL when OS3 connection created by CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22664?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22664: ------------------------------------ [~rob.stryker] I was able to reproduce without your commit and checked that master fixes it (on Win10) > Invalid registry URL when OS3 connection created by CDK server > -------------------------------------------------------------- > > Key: JBIDE-22664 > URL: https://issues.jboss.org/browse/JBIDE-22664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: screenshot-1.png > > > When the OS3 connection is created when launching the CDK server, then the Docker registry URL is not valid (garbage characters at the end). This may be a Windows problem. The CDK version used what CDK 2.1RC5 (see [^screenshot-1.png]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3961: ------------------------------------- I could replicate this. > CDK installation failed with progress bar stuck in 99% > ------------------------------------------------------ > > Key: JBDS-3961 > URL: https://issues.jboss.org/browse/JBDS-3961 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Environment: h3. Operating System: > Windows 10 Pro 64 Bit > h3. Devstudio version > Devstudio 1.0 GA > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Labels: cdk > Fix For: 10.1.0.AM2, 10.1.0.AM3 > > Attachments: dev_studio_installation.PNG, install.log > > > I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations. > Observations: > CDK installation stuck in 99% with "failed" mark. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3960) Rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3960?page=com.atlassian.jira.plugin.... ] Jan Richter reassigned JBDS-3960: --------------------------------- Assignee: Jan Richter (was: Denis Golovin) > Rename platform installer artifacts to start with "devsuite" instead of "development-suite" > ------------------------------------------------------------------------------------------- > > Key: JBDS-3960 > URL: https://issues.jboss.org/browse/JBDS-3960 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Jan Richter > > Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" > So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22166) NullPointerException in CDICoreNature.dispose

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22166?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-22166. ------------------------------------ > NullPointerException in CDICoreNature.dispose > --------------------------------------------- > > Key: JBIDE-22166 > URL: https://issues.jboss.org/browse/JBIDE-22166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.1.CR1 > Reporter: Automated Error Reporting Bot > Assignee: Viacheslav Kabanovich > Fix For: 4.4.1.AM1 > > > The following problem was reported via the automated error reporting: > Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.cdi.core.CDICoreNature.dispose(CDICoreNature.java:721) > at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:96) > at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289) > at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:265) > at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:368) > at org.eclipse.core.internal.resources.Project.move(Project.java:964) > at org.eclipse.jdt.internal.corext.refactoring.changes.RenameJavaProjectChange.doRename(RenameJavaProjectChange.java:76) > at org.eclipse.jdt.internal.corext.refactoring.AbstractJavaElementRenameChange.perform(AbstractJavaElementRenameChange.java:89) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.access$0(DynamicValidationStateChange.java:1) > at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange$1.run(DynamicValidationStateChange.java:113) > at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) > at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5409) > at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.perform(DynamicValidationStateChange.java:116) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) > at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) > at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Bundles: > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160310-1245 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160222-1238 | > | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160118-2055 | > | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.7.0.v20160120-1732 | > | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20151129-1935 | > | org.eclipse.team.svn | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 | > | org.eclipse.team.svn.core | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 | > | org.eclipse.team.svn.ui | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 | > | org.eclipse.team.ui | 3.7.300.v20151117-1911 | 3.7.300.v20151117-1911 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20160108-0627 | > | org.jboss.tools.cdi.core | 1.7.1.CR1-v20160129-2014-B69 | 1.8.0.Alpha1-v20160108-2123-B916 | > Operating Systems: > | Linux | 4.0.4 | 4.0.4 | > | MacOSX | 10.10.5 | 10.11.3 | > | Windows | 6.1.0 | 6.1.0 | > The above information is a snapshot of the collected data. Visit [https://redhat.ctrlflow.com/reviewers/#!/problems/56cb04b0e4b0f02ab70a7d85 this page] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22650) When starting an OS3 server adapter from scratch, error is reported although connection can be established

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22650?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22650: ------------------------------------ [~adietish] I cannot reproduce with master. When the server adapter is started, the dialog box for the password is displayed and then server is started and published. > When starting an OS3 server adapter from scratch, error is reported although connection can be established > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22650 > URL: https://issues.jboss.org/browse/JBIDE-22650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.AM3 > > Attachments: screenshot-1.png > > > ASSERT: create an OS3 connection without password saved > ASSERT: create an OS3 server adapter > EXEC: restart Eclipse > EXEC: start the OS3 server adapter and give correct password > ASSERT: error is reported [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22766) Cannot load discovery directory - blocks use of Install/Update in Red Hat Central

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22766?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22766. ------------------------------- Yep, it works :) Closing. > Cannot load discovery directory - blocks use of Install/Update in Red Hat Central > --------------------------------------------------------------------------------- > > Key: JBIDE-22766 > URL: https://issues.jboss.org/browse/JBIDE-22766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > Attachments: jbdscentral-back.png, jbtcentral-back.png > > > Central is trying to access the following directories on the update site: > - https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... for devstudio > - http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis... for JBT > These directories don't exist on the update sites, so central software/update cannot load. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22696. ------------------------------- Verified with latest AM2. > jbosstools and devstudio sites / installer use old timestamps > ------------------------------------------------------------- > > Key: JBIDE-22696 > URL: https://issues.jboss.org/browse/JBIDE-22696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.1.AM2 > > Attachments: devstudio10.01.png, jbide22696.png, jbt441.png > > > Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22664) Invalid registry URL when OS3 connection created by CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22664?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22664: ------------------------------------- [~jeffmaury] I committed a patch which adds the VAGRANT_NO_COLOR environment variable to the service-manager call. Let's see if it works. I wasn't able to reproduce it, though... not even on windows. I'm not sure what may be different about the environment, but, I'm almost positive there's no way my patch will have a bad effect, so at the very least, it could fix it ;) > Invalid registry URL when OS3 connection created by CDK server > -------------------------------------------------------------- > > Key: JBIDE-22664 > URL: https://issues.jboss.org/browse/JBIDE-22664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: screenshot-1.png > > > When the OS3 connection is created when launching the CDK server, then the Docker registry URL is not valid (garbage characters at the end). This may be a Windows problem. The CDK version used what CDK 2.1RC5 (see [^screenshot-1.png]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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