October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20849: ----------------------------------- Assignee: Andre Dietisheim > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Final > > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20849) Blank space in a New Connection dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20849?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20849: -------------------------------- Fix Version/s: 4.3.1.Final > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-20849 > URL: https://issues.jboss.org/browse/JBIDE-20849 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Final > > Attachments: openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20844: --------------------------------------- I will try that. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20844: ---------------------------------- Component/s: (was: upstream) > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20844: ---------------------------------------- [~snjeza] can we also warn the user if there is something wrong with the example? Add an error in the log at least? > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20844) kitchensink-cordova project examples are not imported into the workspace

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20844?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20844: --------------------------------------- [~rafabene] The kitchensink-cordova and kitchensink-cordova-contacts project examples are defined as maven projects, but don't contain pom.xml and JBT can't recognize them. See https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x/kitch... or https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x/kitch.... You should add pom.xml or define these project examples as Eclipse projects. > kitchensink-cordova project examples are not imported into the workspace > ------------------------------------------------------------------------ > > Key: JBIDE-20844 > URL: https://issues.jboss.org/browse/JBIDE-20844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.CR2 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: cordova.txt, screen.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20848) Release publish scripts and use them

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20848: ------------------------------- Priority: Blocker (was: Major) > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20850: ---------------------------------------- This is not a blocker since we can still produce and deploy good TP. The target-platform-validation mojo gives some guarantees, and doesn't depend on the specified Eclipse version. > target platform matrix job's install test step fails silently when using incompatible Eclipse version > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20850 > URL: https://issues.jboss.org/browse/JBIDE-20850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform: > {code} > [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554) > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755) > [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158) > > BUILD FAILED > /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > {code} > [p2.dir] !MESSAGE Only one of the following can be installed at once: > [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034) > [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859) > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > And yet the build is successful here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > This is most likely because all three configs are set to use the same Eclipse JEE bundle: > {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz > {code} > So... I guess there are two things we need here: > a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1 > b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20848) Release publish scripts and use them

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20848: ------------------------------- Labels: respin-a (was: ) > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20848) Release publish scripts and use them

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20848?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20848: ------------------------------- Fix Version/s: 4.3.0.CR2 > Release publish scripts and use them > ------------------------------------ > > Key: JBIDE-20848 > URL: https://issues.jboss.org/browse/JBIDE-20848 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.3.0.CR2, 4.3.0.Final > > > Since we're about to release 4.3.0.Final and see no blocker with publish scripts, it's time to release them and update parent pom to consume a static/stable release instead of a volatile snapshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 October 2015