August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24782) When creating an app, source resource path should be computed relatively to Git repo root

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24782?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-24782: ---------------------------------------- Assignee: Andre Dietisheim > When creating an app, source resource path should be computed relatively to Git repo root > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24782 > URL: https://issues.jboss.org/browse/JBIDE-24782 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Assignee: Andre Dietisheim > Fix For: 4.5.x > > > When creating an OpenShift application with the OpenShift wizard and associating a Java project, I get asked for a source path. The default value is `app`. I would expect it, in case the project is under a Git repository, to automatically pre-set it to the relative path of the project in the Git repo, which is the most probable good value we can infer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24780) Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24780?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-24780: ---------------------------------------- Assignee: Rob Stryker > Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24780 > URL: https://issues.jboss.org/browse/JBIDE-24780 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Assignee: Rob Stryker > Fix For: 4.5.x > > > I've created an OpenShift Application from Eclipse IDE providing it an Eclipse Project as input. > Then I tried to create a server adapter for this project. It didn't work initially because the project isn't a Faceted Web project. I had to quit the OpenShift wizard, make the project a faceted one and restart the wizard. > I would expect the wizard to create a server adapter to suggest and link to a way to make the project associated with the application a web project in Eclipse IDE so it's one less step to understand for users before it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24783: ------------------------------------- Issue Type: Bug (was: Feature Request) > Update default registry url for cdk 3 > ------------------------------------- > > Key: JBIDE-24783 > URL: https://issues.jboss.org/browse/JBIDE-24783 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > Yesterday I started cdk 3 and it seemed to start ok, but was not really ok. > The registry command didn't really work: > {code} > $ ./minishift openshift registry > No information found for 'service/docker-registry' > {code} > The result is that the openshift connection details showed this under Image Registry URL: > https://hub.openshift.rhel-cdk.10.1.2.2.xip.io > This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-24783: ---------------------------------------- Assignee: Rob Stryker > Update default registry url for cdk 3 > ------------------------------------- > > Key: JBIDE-24783 > URL: https://issues.jboss.org/browse/JBIDE-24783 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, openshift > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > Yesterday I started cdk 3 and it seemed to start ok, but was not really ok. > The registry command didn't really work: > {code} > $ ./minishift openshift registry > No information found for 'service/docker-registry' > {code} > The result is that the openshift connection details showed this under Image Registry URL: > https://hub.openshift.rhel-cdk.10.1.2.2.xip.io > This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24783: ------------------------------------- Fix Version/s: 4.5.x > Update default registry url for cdk 3 > ------------------------------------- > > Key: JBIDE-24783 > URL: https://issues.jboss.org/browse/JBIDE-24783 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, openshift > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > Yesterday I started cdk 3 and it seemed to start ok, but was not really ok. > The registry command didn't really work: > {code} > $ ./minishift openshift registry > No information found for 'service/docker-registry' > {code} > The result is that the openshift connection details showed this under Image Registry URL: > https://hub.openshift.rhel-cdk.10.1.2.2.xip.io > This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24784) Investigate Docker test failure during provisioning of RHEL7

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24784?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-24784: ------------------------------------------ [~jkopriva] why was it set to LATER? > Investigate Docker test failure during provisioning of RHEL7 > ------------------------------------------------------------ > > Key: JBIDE-24784 > URL: https://issues.jboss.org/browse/JBIDE-24784 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.5.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: LATER > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24794) Hibernate Reverse Engineering doesn't work on 4.5.0.AM2

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24794?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24794: ------------------------------------- Fix Version/s: 4.5.x > Hibernate Reverse Engineering doesn't work on 4.5.0.AM2 > ------------------------------------------------------- > > Key: JBIDE-24794 > URL: https://issues.jboss.org/browse/JBIDE-24794 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Dmitrii Bocharov > Fix For: 4.5.x > > Attachments: 4.4.4.Final-works.webm, 4.5.0.AM2-doesnt-work.webm > > > Reverse Engineering doesn't work at the moment, but it worked in 4.4.4.Final. See the attahced screencasts for details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24803: ------------------------------------- Fix Version/s: 4.5.x > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-867. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24804) UnsupportedOperationException below ResourceLabelsPageModel.dispose (thrown in Collections$UnmodifiableCollection.clear)

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24804?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24804: ------------------------------------- Fix Version/s: 4.5.x > UnsupportedOperationException below ResourceLabelsPageModel.dispose (thrown in Collections$UnmodifiableCollection.clear) > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24804 > URL: https://issues.jboss.org/browse/JBIDE-24804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Automated Error Reporting Bot > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > The following problem was reported via the automated error reporting: > Message: > java.lang.UnsupportedOperationException: null > at java.util.Collections$UnmodifiableCollection.clear(Collections.java:1074) > at org.jboss.tools.openshift.internal.ui.wizard.common.ResourceLabelsPageModel.dispose(ResourceLabelsPageModel.java:87) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.dispose(DeployImageWizardModel.java:102) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.fromimage.ApplicationSourceFromImageModel.dispose(ApplicationSourceFromImageModel.java:267) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.dispose(NewApplicationWizard.java:189) > at org.eclipse.jface.wizard.WizardDialog.hardClose(WizardDialog.java:837) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:798) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.jface | 3.12.2.v20170113-2113 | 3.12.2.v20170113-2113 | > | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 | > | org.jboss.tools.openshift.ui | 3.3.3.v20170510-2204 | 3.3.3.v20170510-2204 | > Operating Systems: > | MacOSX | 10.12.5 | 10.12.5 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5986d628e4b007cf146... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24840) Batch integration tests started to fail on searching batch artifacts

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24840?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24840: ------------------------------------- Fix Version/s: 4.5.x > Batch integration tests started to fail on searching batch artifacts > -------------------------------------------------------------------- > > Key: JBIDE-24840 > URL: https://issues.jboss.org/browse/JBIDE-24840 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Fix For: 4.5.x > > > Batch search feature stopped working in integration tests. It might be connected with removal of seam/deltaspike plugins or it just might says that project used in tests needs an adjustment (adding missing feature from central, and ships it together during testing). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 August 2017