August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4012) NPE in izpack installer Unpacker extension - progress tracker

by Paul Leacu (JIRA)

Paul Leacu created JBDS-4012: -------------------------------- Summary: NPE in izpack installer Unpacker extension - progress tracker Key: JBDS-4012 URL: https://issues.jboss.org/browse/JBDS-4012 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: installer Reporter: Paul Leacu Assignee: Paul Leacu java.lang.NullPointerException at com.izforge.izpack.installer.Unpacker.processRuntimes(Unpacker.java:865) at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:589) at java.lang.Thread.run(Thread.java:745) Need to move the progress tracker down one line. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23036: ------------------------------------ No, because JBT 4.4.0 users are using the 4.60.0.Final TP, not the forthcoming 4.60.1.Final one. Won't even affect 4.4.1.AM1 / AM2 / AM3 users because they can still update to the latest as it'll be included in JBT/devstudio update site directly, instead of the JBT/devstudio TP. All we're doing it moving it from one site to the other, but the composite site users see will still have all the same docker tooling features. (Well, it'll have NEWER versions.) > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-23036: ------------------------------------- [~nickboldt] I probably didn't express myself correctly. My point is we need to provide a stable location for the docker bits once we have a release. I believe the pom reference points to a mirrored location anyway so we always are in control of what we serve to the users, eventually. > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23036: ---------------------------------------- Can it affect JBT 4.4.0 users somehow? If we remove it from TP for 4.4.1? > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23029: ------------------------------------------ [~mlabuda] can you please comment on the aim to be able run tests individually? > Integration tests: Tests should be able to run individually > ----------------------------------------------------------- > > Key: JBIDE-23029 > URL: https://issues.jboss.org/browse/JBIDE-23029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need). > This is even more true since running the whole suite is a lengthy task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23029: ------------------------------------- Comment: was deleted (was: a great way it seems, to get a requirement fullfilled (without erroring - ex. test needs a connection) would be to provide an annotiation like the requirement assertion @RunIf. Something like @Requires or @Needs could fit well.) > Integration tests: Tests should be able to run individually > ----------------------------------------------------------- > > Key: JBIDE-23029 > URL: https://issues.jboss.org/browse/JBIDE-23029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need). > This is even more true since running the whole suite is a lengthy task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23036: ------------------------------------ You can't have it in both places, [~fbricon]. The whole point of moving it OUT of the TP is to get faster updates. If it's in the TP *and* in the root pom, you've just doubled your process and gained no speed. > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-23036: ------------------------------------- Ok to have the dependency declared in the pom.xml. However, we still need to keep Docker/Vagrant in the TP for the releases > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23036: ------------------------------------------ let's move forward, +1 > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23036: ------------------------------------ Latest nightly build is 2.1.0.201608222202 on http://download.eclipse.org/linuxtools/updates-docker-nightly/ I'll pull this version today and submit a PR to get it into the openshift build ASAP. > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016