December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23645) Remove org.jboss.tools.ui.bot.ext from integration tests

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23645?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23645: ---------------------------------- Fix Version/s: 4.4.3.AM2 > Remove org.jboss.tools.ui.bot.ext from integration tests > -------------------------------------------------------- > > Key: JBIDE-23645 > URL: https://issues.jboss.org/browse/JBIDE-23645 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.3.AM2 > > > org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > This was previously discussed in JBIDE-23593 where I found the following tests that still use bot.ext. > I found out that some tests still use bot.ext: > {code} > $ find . -iname 'manifest.mf' -path '*/META-INF/*'|xargs grep 'ui\.bot\.ext'|sed 's/:.*//'|uniq > ./plugins/org.jboss.tools.jst.ui.bot/META-INF/MANIFEST.MF > ./plugins/org.jboss.tools.ui.bot.ext/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.portlet.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.seam.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.ws.ui.bot.test/META-INF/MANIFEST.MF > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23302: ------------------------------------ >From Ryszard: > Here is the commit I’ve done for bootstrap-community https://github.com/jbossorg/bootstrap-community/commit/e2dc8a990b3641e995... So you can either try merging it to your repo or just repeat the same what I did which is find in all files “http://static.jboss.org/“ and replace it with “//static.jboss.org/“. > Actually I realised that on your staging and prod sites you’ll probably use the minimalised CSS/JS versions and I need to push them to static.jboss.org. I’ll do that now. > Ok pushed the new versions, I hope they will work. You’ll need to update your _config/site.yml https://static.jboss.org/theme/css/bootstrap-community/2.3.1.6/ and https://static.jboss.org/theme/js/libs/bootstrap-community/2.3.1.6/ Xavier's changes to move up to the new bootstrap [1] are live in https://tools.stage.jboss.org/ and fonts are now appearing as expected when compared to http://tools.stage.jboss.org/ Xavier has pushed the change to our production branch too, so changes should appear shortly on https://tools.jboss.org/ We're ready to enable https (instead of the redirect) on tools.jboss.org, whenever you guys are ready to flip the switch. [1] https://github.com/jbosstools/jbosstools-website/commits/production > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Assignee: Xavier Coulon > Fix For: 4.4.3.AM1 > > Attachments: image.png, stage-http.png, stage.png > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Aurélien Pupier commented on JBTIS-1008: ---------------------------------------- I was wrong, it doesn't work neither with "installation" mode, I think that I had a CDK already running when i tried using it. so need to deal with the issue that I see when using the zip as local "software site" > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3593) Enable continuous delivery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3593?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3593: ----------------------------- Sprint: devex #125 December 2016 > Enable continuous delivery > -------------------------- > > Key: JBDS-3593 > URL: https://issues.jboss.org/browse/JBDS-3593 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.x > > > A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective). > If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt. > I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23302: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.5.x) > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Assignee: Xavier Coulon > Fix For: 4.4.3.AM1 > > Attachments: image.png, stage-http.png, stage.png > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4233: ----------------------------- Description: As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... was:As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Reporter: Nick Boldt > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4233: -------------------------------- Summary: Migrate jbosstools, devstudio, and release process jobs to Central CI Key: JBDS-4233 URL: https://issues.jboss.org/browse/JBDS-4233 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Reporter: Nick Boldt As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Aurélien Pupier edited comment on JBTIS-1008 at 12/22/16 9:42 AM: ------------------------------------------------------------------ I found a workaround few minutes ago. When using "Installation" mode for the Target platform, it works. I provided a PR with this new TP and with updated how-to: https://github.com/fusesource/fuseide/pull/794 i think that we will go with this limitation of not using a "software site" neither a "directory" was (Author: aurelien.pupier): I found a workaround few minutes ago. When using "Installation" mode for the Target platform, it works. I provided a PR with this new TP and with updated how-to: https://github.com/fusesource/fuseide/pull/794 > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Aurélien Pupier commented on JBTIS-1008: ---------------------------------------- I found a workaround few minutes ago. When using "Installation" mode for the Target platform, it works. I provided a PR with this new TP and with updated how-to: https://github.com/fusesource/fuseide/pull/794 > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1008: ----------------------------------- Since the full fuse TP builds okay it seems to be more related to WIndows? I did see this which seems relevant to your screen capture: ttps://bugs.eclipse.org/bugs/show_bug.cgi?id=434959 > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 December 2016