June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24124) Add org.jboss.reddeer.graphiti to TP

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24124?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24124. -------------------------------- Verified, RedDeer Graphiti is included in TP and can be installed without remediation actions. Closing. > Add org.jboss.reddeer.graphiti to TP > ------------------------------------ > > Key: JBIDE-24124 > URL: https://issues.jboss.org/browse/JBIDE-24124 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.3.Final > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Please add the following unit to the TP > {code} > <unit id="org.jboss.reddeer.graphiti.feature.feature.group" version="1.2.1.Final"/> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24284) Add docker.reddeer to JBT/devstudio target platforms for 4.70.x (depends on Oxygen.0.M7)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24284?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24284. -------------------------------- Verified, org.eclipse.linuxtools.docker.reddeer is included in TP \[1\] \[1\] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > Add docker.reddeer to JBT/devstudio target platforms for 4.70.x (depends on Oxygen.0.M7) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-24284 > URL: https://issues.jboss.org/browse/JBIDE-24284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, integration-tests, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Pavol has requested that we add docker.reddeer plugins/features to the TP. > I assume this is for Oxygen-based target platforms. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23430) Run as -> Run on server -> browser might open too early causing http 404

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23430?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23430. --------------------------------- > Run as -> Run on server -> browser might open too early causing http 404 > ------------------------------------------------------------------------ > > Key: JBIDE-23430 > URL: https://issues.jboss.org/browse/JBIDE-23430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Josef Ludvicek > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: runas.png > > > There should be some mechanism to detect when application is succesfully deployed. > It is possible that on slow machine it starts to deploy and open internal web browser too early - before app is fully deployed. > Stepps: > * start eap server > * right click on app -> Run as -> run on server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23785) WF11 server adapter needed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23785?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23785. --------------------------------- Closing. Basic work flows work. > WF11 server adapter needed > --------------------------- > > Key: JBIDE-23785 > URL: https://issues.jboss.org/browse/JBIDE-23785 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > WF 11 server adapter needed. THis may require a new set of jars (or may not). Current test of wf11 nightly build seems to work with mgmt, no significant changes, but that can break. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24380. -------------------------------- > new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME} > ------------------------------------------------------------------- > > Key: JBIDE-24380 > URL: https://issues.jboss.org/browse/JBIDE-24380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: > {code} > - <jbosstools.test.jre.5></jbosstools.test.jre.5> > - <jbosstools.test.jre.6></jbosstools.test.jre.6> > - <jbosstools.test.jre.7></jbosstools.test.jre.7> > - <jbosstools.test.jre.8></jbosstools.test.jre.8> > + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> > + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> > + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> > + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> > {code} > This way, depending on what your system's definition of JAVA_HOME happens to be, you get a different effective pom, for your required JDK: > {code} > $ export JAVA_HOME=/opt/jdk1.8.0/ > $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre > <jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5> > <jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6> > <jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7> > <jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8> > (or, to use the JAVA_HOME set by alternatives...) > $ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e "s#.\+ $.\+$bin/java#\1#") > $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre > <jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5> > <jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6> > <jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7> > <jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24508) EAP 7.1 server adapter

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24508?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24508. --------------------------------- The adapter is there. If there are issues with it, they will be reported separately. Closing. > EAP 7.1 server adapter > ---------------------- > > Key: JBIDE-24508 > URL: https://issues.jboss.org/browse/JBIDE-24508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > EAP 7.x server adapter needs to be split into a 7.0 and 7.x. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24294) "Starting Container Development Environment 3" stays blocked when cdk launch is failing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24294?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-24294. ----------------------------------- Resolution: Cannot Reproduce Bug Changed resolution to Cannot reproduce bug. > "Starting Container Development Environment 3" stays blocked when cdk launch is failing > --------------------------------------------------------------------------------------- > > Key: JBIDE-24294 > URL: https://issues.jboss.org/browse/JBIDE-24294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: image-2017-04-24-14-46-36-250.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24294) "Starting Container Development Environment 3" stays blocked when cdk launch is failing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24294?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24294. --------------------------------- Closing. > "Starting Container Development Environment 3" stays blocked when cdk launch is failing > --------------------------------------------------------------------------------------- > > Key: JBIDE-24294 > URL: https://issues.jboss.org/browse/JBIDE-24294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: image-2017-04-24-14-46-36-250.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3510) [central-update] Include Buildship in jbosstools and devstudio OOTB

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-3510. ------------------------------ Verified, Buildship is included in JBT/BYOE and also is in RH Central. Closing. > [central-update] Include Buildship in jbosstools and devstudio OOTB > ------------------------------------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central-update > Affects Versions: 9.0.0.CR1, 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 11.0.0.AM1 > > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23779) Archive old JBoss Tools versions on Downloads and What's New pages

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23779?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23779. --------------------------------- This is done, currently there are only two stable versions on the overall What's New page. But I noticed that some versions are inaccessible now, so I created a new JIRA here: JBIDE-24529 > Archive old JBoss Tools versions on Downloads and What's New pages > ------------------------------------------------------------------- > > Key: JBIDE-23779 > URL: https://issues.jboss.org/browse/JBIDE-23779 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.4.3.AM1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.4.Final > > > there are too many versions displayed on https://tools.jboss.org/documentation/whatsnew/. Having 3 elements (1 development and 2 stable items) would be enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017