June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22495) For JBIDE 4.4.0.Final: Prepare for Final/GA [Central]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22495?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22495. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Final: Prepare for Final/GA [Central] > ----------------------------------------------------- > > Key: JBIDE-22495 > URL: https://issues.jboss.org/browse/JBIDE-22495 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [Central]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.x > git push origin jbosstools-4.4.x > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* 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. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14073) add remote deployment feature as EAP6 CLI does to JBDS.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14073?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14073: -------------------------------- Fix Version/s: 4.5.0.Alpha1 (was: 4.4.x) > add remote deployment feature as EAP6 CLI does to JBDS. > ------------------------------------------------------- > > Key: JBIDE-14073 > URL: https://issues.jboss.org/browse/JBIDE-14073 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Assignee: Rob Stryker > Labels: UHG > Fix For: 4.5.0.Alpha1 > > > EAP6 CLI provides feature to do remote deployment: > bin/jboss-cli.sh --connect --controller="127.0.0.1:9999" --command="deploy ../tmp/sample.war" --user="User" > Is it possible to have such feature available in JBDS? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22486) For JBIDE 4.4.0.Final: Prepare for Final/GA [OpenShift]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22486?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22486. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Final: Prepare for Final/GA [OpenShift] > ------------------------------------------------------- > > Key: JBIDE-22486 > URL: https://issues.jboss.org/browse/JBIDE-22486 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [OpenShift]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.x > git push origin jbosstools-4.4.x > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* 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. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2925) We want tools to allow interacting with jboss servers via management operations as much as possible to integrate better with RBAC, arquillian, domain mode etc.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2925?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-2925: ------------------------------ Fix Version/s: 11.0.0.Alpha1 (was: 10.0.0.GA) > We want tools to allow interacting with jboss servers via management operations as much as possible to integrate better with RBAC, arquillian, domain mode etc. > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2925 > URL: https://issues.jboss.org/browse/JBDS-2925 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 11.0.0.Alpha1 > > > Pushing this. Not all subtasks are done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21059: ------------------------------------- A commit was made for this jira, but it definitely needs testing, so I've pushed this off. Theoretically this should be possible now. I'll work with [~xcoulon] to see if it fits his needs or requires additional changes. > Server Adapter does not connect in debug mode on WF in a Docker container > -------------------------------------------------------------------------- > > Key: JBIDE-21059 > URL: https://issues.jboss.org/browse/JBIDE-21059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.1.Alpha1 > > > I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line : > {code} > CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"] > {code} > I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit. > On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22271) Test failure in server: dtd schema files missing in plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22271?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22271. --------------------------------- Resolution: Done fixed in another jira. Current builds seem blue. > Test failure in server: dtd schema files missing in plugin > ---------------------------------------------------------- > > Key: JBIDE-22271 > URL: https://issues.jboss.org/browse/JBIDE-22271 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Final > > > Server tests have been failing on this test: > org.jboss.tools.as.test.core.catalog.CatalogMissingEntriesTest.testMissingEntries (from org.jboss.tools.as.test.core.ASToolsTestSuite) > /schema/dtd/properties.dtd is not found in plugin.xml > /schema/dtd/datatypes.dtd is not found in plugin.xml > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas... > Sorry if this has been reported elsewhere, I couldn't find it. > Not sure if it's too late to fix in Alpha1 or not. Up to you. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21059: -------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > Server Adapter does not connect in debug mode on WF in a Docker container > -------------------------------------------------------------------------- > > Key: JBIDE-21059 > URL: https://issues.jboss.org/browse/JBIDE-21059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.1.Alpha1 > > > I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line : > {code} > CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"] > {code} > I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit. > On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22499) Read CDK's Docker Registry url from service manager plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22499?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22499: -------------------------------- Parent: (was: JBIDE-22193) Issue Type: Feature Request (was: Sub-task) > Read CDK's Docker Registry url from service manager plugin > ---------------------------------------------------------- > > Key: JBIDE-22499 > URL: https://issues.jboss.org/browse/JBIDE-22499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.Alpha1 > > > we need to get the docker registry url from adb-utils (https://github.com/projectatomic/adb-utils/issues/113) and store it in the connection properties (See API in JBIDE-22314) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22499) Read CDK's Docker Registry url from service manager plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22499?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22499: -------------------------------- Sprint: (was: devex #115 May 2016) > Read CDK's Docker Registry url from service manager plugin > ---------------------------------------------------------- > > Key: JBIDE-22499 > URL: https://issues.jboss.org/browse/JBIDE-22499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.Alpha1 > > > we need to get the docker registry url from adb-utils (https://github.com/projectatomic/adb-utils/issues/113) and store it in the connection properties (See API in JBIDE-22314) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22499) Read CDK's Docker Registry url from service manager plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22499?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22499: -------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.x) > Read CDK's Docker Registry url from service manager plugin > ---------------------------------------------------------- > > Key: JBIDE-22499 > URL: https://issues.jboss.org/browse/JBIDE-22499 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.Alpha1 > > > we need to get the docker registry url from adb-utils (https://github.com/projectatomic/adb-utils/issues/113) and store it in the connection properties (See API in JBIDE-22314) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016