April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24312: ------------------------------------- Description: [~dbocharov] says that he cannot reproduce this. He has not a single SSL cert dialog using Linux. Environment: MacOS > Explorer: SSL certificate dialog shows up many many times when using internal test server > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24312 > URL: https://issues.jboss.org/browse/JBIDE-24312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Environment: MacOS > Reporter: Andre Dietisheim > > [~dbocharov] says that he cannot reproduce this. He has not a single SSL cert dialog using Linux. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24312: ---------------------------------------- Summary: Explorer: SSL certificate dialog shows up many many times when using internal test server Key: JBIDE-24312 URL: https://issues.jboss.org/browse/JBIDE-24312 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.AM3 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error While Executing jbosstools-openshift-4.4.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24301: ---------------------------------- Assignee: Dmitrii Bocharov > Error While Executing jbosstools-openshift-4.4.3 > ------------------------------------------------ > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > Attachments: issues.txt > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error While Executing jbosstools-openshift-4.4.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24301: ------------------------------- Fix Version/s: 4.4.4.Final > Error While Executing jbosstools-openshift-4.4.3 > ------------------------------------------------ > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Fix For: 4.4.4.Final > > Attachments: issues.txt > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19715: ------------------------------- Sprint: devex #116 June 2016, devex #128 February 2017, devex #131 May 2017 (was: devex #116 June 2016, devex #128 February 2017) > Get rid of "fullSite", stick with "repository" > ---------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.0.AM1 > > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20850: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.x) > 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.5.0.AM2 > > > 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 (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23480) update p2diff & p2browser to build against Neon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23480?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23480: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.x) > update p2diff & p2browser to build against Neon > ----------------------------------------------- > > Key: JBIDE-23480 > URL: https://issues.jboss.org/browse/JBIDE-23480 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.0.AM2 > > > To make them current and more easily used, make sure that both p2browser and p2diff can be compiled against Neon (not Luna) dependencies. > https://github.com/ifedorenko/p2-browser > https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21132) Create tool to verify all poms use -SNAPSHOT and manifests/feature.xml use .qualifier

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21132?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21132. ------------------------------ Fix Version/s: 4.4.4.Final (was: 4.4.x) Resolution: Rejected Won't do. > Create tool to verify all poms use -SNAPSHOT and manifests/feature.xml use .qualifier > ------------------------------------------------------------------------------------- > > Key: JBIDE-21132 > URL: https://issues.jboss.org/browse/JBIDE-21132 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > > In completing JBIDE-20908, Freemarker tools was accidentally upversioned from 1.5.0-SNAPSHOT to 1.5.1, which broke deployment to Nexus. Since we no longer publish update sites to Nexus (for reasons outlined in JBIDE-21012), we no longer have a build-based way to audit for this type of user error when upversioning. > So, we need something (a releng [1] mojo?) that can check for the presence/absence of > * -SNAPSHOT in poms > * .qualifier in manifests/feature.xml > [1] https://github.com/jbosstools/jbosstools-maven-plugins/tree/master/tycho-... > This could also be done as a releng script [2] but breaking the build locally would be better than preventing publishing AFTER Jenkins completes the build. > [2] https://github.com/jbosstools/jbosstools-build-ci/tree/jbosstools-4.3.x/util -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23738) create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23738?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23738: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.x) > create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23738 > URL: https://issues.jboss.org/browse/JBIDE-23738 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, rpm > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM2 > > > Per trello card [1], we should consider having a jbosstools rpm. > Could put the source for this in https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ or in jbdevstudio-product since it'll be a similar design to that one, including blacklists and dependencies. > [1] https://trello.com/c/YK6rdGRy/14-create-jbosstools-rpm-for-fedora-24-25 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23017: ------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016, devex #121 October 2016, devex #128 February 2017, devex #129 March 2017, devex #131 May 2017 (was: devex #119 August 2016, devex #120 September 2016, devex #121 October 2016, devex #128 February 2017, devex #129 March 2017) > use sshfs to speed up publishing process > ----------------------------------------- > > Key: JBIDE-23017 > URL: https://issues.jboss.org/browse/JBIDE-23017 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.4.AM3, 4.4.4.Final > > Attachments: staging-times.png > > > Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org. > If we could simply copy bits over sshfs, the process might be a lot faster than these times: > {code} > JBT coretests 1.1G: 59m20 > JBT core 1.2G: 64m23 > devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13 > devstudio (copy from local to www.qa) 3.1G: 6mins(?) > {code} > To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 April 2017