[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
[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
[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