June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be replaced by "*" like used in all OpenShift tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19975?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19975: ------------------------------------- Labels: application_wizard (was: ) > v3 (Template) Application wizard: error markers for missing content should be replaced by "*" like used in all OpenShift tooling > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19975 > URL: https://issues.jboss.org/browse/JBIDE-19975 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: 4.3.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19951) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19951?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19951: ------------------------------------ If you have plugins in the master branch which are no longer the same as those in the 4.2.x branch, then YES. Like all projects, you need to upversion. https://wiki.eclipse.org/Version_Numbering#Overall_example > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests] > --------------------------------------------------------------- > > Key: JBIDE-19951 > URL: https://issues.jboss.org/browse/JBIDE-19951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Central Discovery]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19974: ---------------------------------- Component/s: upstream > Cannot detect running boot2docker on OS X > ----------------------------------------- > > Key: JBIDE-19974 > URL: https://issues.jboss.org/browse/JBIDE-19974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > > In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: > bash: no job control in this shell > An exception stack trace is not available. > Another warning is generated also: > Could not find default settings to connect to a local Docker daemon > An exception stack trace is not available. > I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: > export DOCKER_HOST=tcp://192.168.59.103:2376 > export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm > export DOCKER_TLS_VERIFY=1 > With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. > But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. > So something is wrong. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19974: ---------------------------------- Description: In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: bash: no job control in this shell An exception stack trace is not available. Another warning is generated also: Could not find default settings to connect to a local Docker daemon An exception stack trace is not available. I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: export DOCKER_HOST=tcp://192.168.59.103:2376 export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm export DOCKER_TLS_VERIFY=1 With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. So something is wrong. I logged an upstream bug here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624 was: In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: bash: no job control in this shell An exception stack trace is not available. Another warning is generated also: Could not find default settings to connect to a local Docker daemon An exception stack trace is not available. I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: export DOCKER_HOST=tcp://192.168.59.103:2376 export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm export DOCKER_TLS_VERIFY=1 With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. So something is wrong. > Cannot detect running boot2docker on OS X > ----------------------------------------- > > Key: JBIDE-19974 > URL: https://issues.jboss.org/browse/JBIDE-19974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > > In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: > bash: no job control in this shell > An exception stack trace is not available. > Another warning is generated also: > Could not find default settings to connect to a local Docker daemon > An exception stack trace is not available. > I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: > export DOCKER_HOST=tcp://192.168.59.103:2376 > export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm > export DOCKER_TLS_VERIFY=1 > With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. > But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. > So something is wrong. > I logged an upstream bug here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X

by Martin Malina (JIRA)

Martin Malina created JBIDE-19974: ------------------------------------- Summary: Cannot detect running boot2docker on OS X Key: JBIDE-19974 URL: https://issues.jboss.org/browse/JBIDE-19974 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Affects Versions: 4.3.0.Beta1 Reporter: Martin Malina In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: bash: no job control in this shell An exception stack trace is not available. Another warning is generated also: Could not find default settings to connect to a local Docker daemon An exception stack trace is not available. I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: export DOCKER_HOST=tcp://192.168.59.103:2376 export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm export DOCKER_TLS_VERIFY=1 With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. So something is wrong. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19642) [thym] Can not detect version. VERSION file ~/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19642?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19642. ------------------------------ Verified in 4.3.0.Beta1. > [thym] Can not detect version. VERSION file ~/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19642 > URL: https://issues.jboss.org/browse/JBIDE-19642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta1 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=465011 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19973) Build with Tycho 0.23 (or wait for 0.24?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19973?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19973: ------------------------------- Fix Version/s: 4.3.0.Beta2 > Build with Tycho 0.23 (or wait for 0.24?) > ----------------------------------------- > > Key: JBIDE-19973 > URL: https://issues.jboss.org/browse/JBIDE-19973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Tycho 0.23 is released [1]. > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > We should move parent pom, target platform builds, and other places where tychoVersion or tycho-version is set) to use the latest version. > This would also include releasing a new version of repo-utils and everything else in jbosstools-maven-plugins [2]. > [2] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19773: ------------------------------------- Please provide steps how to setup JBDS to use particular version of XulRunner > Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do? > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19773 > URL: https://issues.jboss.org/browse/JBIDE-19773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution. > Context: > {quote} > * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > * SWT problem? GTK problem? xvnc/xvfb problem? > * missing webkit package on RHEL7 ? > * @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages) > * what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_... {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19973) Build with Tycho 0.23 (or wait for 0.24?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19973?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19973: ------------------------------------ cc: [~mickael_istria] [~lhein] [~pleacu] > Build with Tycho 0.23 (or wait for 0.24?) > ----------------------------------------- > > Key: JBIDE-19973 > URL: https://issues.jboss.org/browse/JBIDE-19973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Tycho 0.23 is released [1]. > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 > We should move parent pom, target platform builds, and other places where tychoVersion or tycho-version is set) to use the latest version. > This would also include releasing a new version of repo-utils and everything else in jbosstools-maven-plugins [2]. > [2] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19973) Build with Tycho 0.23 (or wait for 0.24?)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19973: ---------------------------------- Summary: Build with Tycho 0.23 (or wait for 0.24?) Key: JBIDE-19973 URL: https://issues.jboss.org/browse/JBIDE-19973 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, target-platform Affects Versions: 4.3.0.Beta1 Reporter: Nick Boldt Tycho 0.23 is released [1]. [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23 We should move parent pom, target platform builds, and other places where tychoVersion or tycho-version is set) to use the latest version. This would also include releasing a new version of repo-utils and everything else in jbosstools-maven-plugins [2]. [2] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015