April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24323) Set up docker registry when cdk 3 server adapter is started

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24323?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24323: ---------------------------------- Description: Apparently nobody requested this for cdk 3 yet, so it hasn't been implemented. For minishift / cdk 3, the command is: minishift openshift registry > Set up docker registry when cdk 3 server adapter is started > ----------------------------------------------------------- > > Key: JBIDE-24323 > URL: https://issues.jboss.org/browse/JBIDE-24323 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.4.Final > > > Apparently nobody requested this for cdk 3 yet, so it hasn't been implemented. > For minishift / cdk 3, the command is: > minishift openshift registry -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24323) Set up docker registry when cdk 3 server adapter is started

by Martin Malina (JIRA)

Martin Malina created JBIDE-24323: ------------------------------------- Summary: Set up docker registry when cdk 3 server adapter is started Key: JBIDE-24323 URL: https://issues.jboss.org/browse/JBIDE-24323 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.4.4.AM3 Reporter: Martin Malina -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1095) Fuse: Improve the checking if there is a dialog for changing the perspective

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1095: ---------------------------------------- Summary: Fuse: Improve the checking if there is a dialog for changing the perspective Key: JBTIS-1095 URL: https://issues.jboss.org/browse/JBTIS-1095 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.4.3.CR1 Reporter: Andrej Podhradsky Assignee: Tomáš Sedmík Fix For: 4.4.3.CR1 Improve the checking if there is a dialog for changing the perspective. Note that this dialog can be turned off via direct API. If you still want the current logic then please execute it only if the property for changing the perspective is on. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24322: ------------------------------------- Story Points: 8 Sprint: devex #131 May 2017 > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24322: -------------------------------- Description: During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. We noticed that during the publishing or local change. The Publish function, always creates a nested deploy directory inside an existing one. For instance inside /opt/eap/standalone/deployments/ 1st Publish: deploy/server.war/ 2nd Publish: deploy/deploy/server.war/ 3nd Publish: deploy/deploy/deploy/server.war/ So with 3 publish, you end up with 3 deployed same application. This happen also inside the local workspaces for the synchronisation: .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift The EAP7 images is the jboss-eap70-openshift:latest. Do you have any idea why this happen? was: Hi Max, Dominik Wotruba gave me your contact and I am writing you this email with the hope that you can give us an hint about the following situation with the Openshift Server adapter plugin. During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. We noticed that during the publishing or local change. The Publish function, always creates a nested deploy directory inside an existing one. For instance inside /opt/eap/standalone/deployments/ 1st Publish: deploy/server.war/ 2nd Publish: deploy/deploy/server.war/ 3nd Publish: deploy/deploy/deploy/server.war/ So with 3 publish, you end up with 3 deployed same application. This happen also inside the local workspaces for the synchronisation: .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift The EAP7 images is the jboss-eap70-openshift:latest. Do you have any idea why this happen? > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-24322: ----------------------------------- Assignee: Dmitrii Bocharov (was: Rob Stryker) > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > > Hi Max, > Dominik Wotruba gave me your contact and I am writing you this email with the hope that you can give us an hint about the following situation with the Openshift Server adapter plugin. > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24322: -------------------------------- Fix Version/s: 4.4.4.Final > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > > Hi Max, > Dominik Wotruba gave me your contact and I am writing you this email with the hope that you can give us an hint about the following situation with the Openshift Server adapter plugin. > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-24322: ----------------------------------- Summary: Openshift publisher keeps getting more nested Key: JBIDE-24322 URL: https://issues.jboss.org/browse/JBIDE-24322 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Final Reporter: Rob Stryker Hi Max, Dominik Wotruba gave me your contact and I am writing you this email with the hope that you can give us an hint about the following situation with the Openshift Server adapter plugin. During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. We noticed that during the publishing or local change. The Publish function, always creates a nested deploy directory inside an existing one. For instance inside /opt/eap/standalone/deployments/ 1st Publish: deploy/server.war/ 2nd Publish: deploy/deploy/server.war/ 3nd Publish: deploy/deploy/deploy/server.war/ So with 3 publish, you end up with 3 deployed same application. This happen also inside the local workspaces for the synchronisation: .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift The EAP7 images is the jboss-eap70-openshift:latest. Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-24322: ----------------------------------- Assignee: Rob Stryker > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > > Hi Max, > Dominik Wotruba gave me your contact and I am writing you this email with the hope that you can give us an hint about the following situation with the Openshift Server adapter plugin. > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24298) Could not find "org.sonatype.tycho.m2e.feature.feature.group/0.9.0.201609061714" in the repositories of the current location

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24298?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-24298: ------------------------------------ [~apodhrad] [~tsedmik] - please try once more (sorry for the churn). The JBTIS TP 4.4.3.CR1-SNAPSHOT no longer directly includes m2eclipse-tycho but gets it from jbosstools-multiple. > Could not find "org.sonatype.tycho.m2e.feature.feature.group/0.9.0.201609061714" in the repositories of the current location > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24298 > URL: https://issues.jboss.org/browse/JBIDE-24298 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Tomáš Sedmík > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.4.2.Final > > > Here http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho/ in _Composite*.xml_ files _0.9.0.201609061714_ version is not specified. > {code} > [INFO] Adding repository http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho > [INFO] Fetching compositeContent.xml from http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho/ (467B) > [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho... (5.89kB) > [ERROR] Failed to resolve target definition /home/fedora/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.4.2.Final/target-platform-4.4.2.Final-base.target: Could not find "org.sonatype.tycho.m2e.feature.feature.group/0.9.0.201609061714" in the repositories of the current location -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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