February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21642) verify if it's possible to build, deploy, & test a JBT project from an existing tag

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21642: ---------------------------------- Summary: verify if it's possible to build, deploy, & test a JBT project from an existing tag Key: JBIDE-21642 URL: https://issues.jboss.org/browse/JBIDE-21642 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt Usecase: We want to rebuild something that we released a few months ago, for which there have been no significant changes (other than bumping feature/plugin versions and using a newer parent pom / target platform). So, we need a way to run a build from a tag (not a branch) and to ensure that re-deployment to /snapshots/builds/JOBNAME/ works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20731) Finish button in Import OpenShift Application wizard does nothing if repo is already cloned

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20731?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20731: ----------------------------------------------- [~mlabuda], could you please check if this issue is still actual. If it is, check if validation works after you manually change clone destination to a new value and then back to default. > Finish button in Import OpenShift Application wizard does nothing if repo is already cloned > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20731 > URL: https://issues.jboss.org/browse/JBIDE-20731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.CR1 > > > Finish button in OpenShift 3 Import OpenShift Application wizard is enabled if the wizard is opened via context menu of a build config even though the repository is already cloned in default git location. This allows users to click on Finish button, but nothing happens. If Import OpenShift Application is opened via context menu of a project or connection or the build config in Import OpenShift Application is selected, then the Finish button for already cloned repositories of a build config is disabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-704) JBDS-IS 8.0.5: Release Notes and link to tooling

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-704?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-704. ------------------------------ Resolution: Done Thanks, Andrej! Closing the issue. > JBDS-IS 8.0.5: Release Notes and link to tooling > ------------------------------------------------ > > Key: TOOLSDOC-704 > URL: https://issues.jboss.org/browse/TOOLSDOC-704 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new release notes and link to DV 6.3 docs page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20997) Should not be able to create duplicative labels

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20997?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20997: -------------------------------- Fix Version/s: 4.3.1.CR1 > Should not be able to create duplicative labels > ----------------------------------------------- > > Key: JBIDE-20997 > URL: https://issues.jboss.org/browse/JBIDE-20997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20997) Should not be able to create duplicative labels

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20997?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20997: ----------------------------------- Assignee: Viacheslav Kabanovich Resolution: Done PR applied in master and 4.3.x. Thanks [~scabanovich]! > Should not be able to create duplicative labels > ----------------------------------------------- > > Key: JBIDE-20997 > URL: https://issues.jboss.org/browse/JBIDE-20997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-552: ---------------------------------- How often would you like this job to run? You can queue it to run every time you publish a new build into one of these locations: * http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... * http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s... * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/disc... * https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/disc... > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-552: ---------------------------------- Tests are blue - for all 8 permutations of installation. http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p2... For example, this test shows successful installation of JBDS IS (both GA and EA content) onto eclipse-platform-4.5.2RC1-linux-gtk.tar.gz: {code}... 11:16:55 [p2.dir] Installing com.jboss.devstudio.integration-stack.bpr.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. 11:16:55 [p2.dir] Installing com.jboss.devstudio.integration-stack.ds.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. 11:16:55 [p2.dir] Installing com.jboss.devstudio.integration-stack.fuse.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. 11:16:55 [p2.dir] Installing com.jboss.devstudio.integration-stack.soa.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. ...{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p2... Same again JBDS IS install onto JEE bundle, eclipse-jee-mars-2-RC1-linux.gtk.x86.tar.gz: {code}... 11:06:02 [p2.dir] Installing com.jboss.devstudio.integration-stack.bpr.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. 11:06:02 [p2.dir] Installing com.jboss.devstudio.integration-stack.ds.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. 11:06:02 [p2.dir] Installing com.jboss.devstudio.integration-stack.fuse.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. 11:06:02 [p2.dir] Installing com.jboss.devstudio.integration-stack.soa.feature.feature.group 9.0.0.2015-11-03_12-11-52-B161-v20151103-1732-B161. ...{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p2... > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Omair Majid (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Omair Majid commented on JBDS-3586: ----------------------------------- [~pleacu], Sure, I have let them know. FWIW, I am not sure if it's possible from them to do this, depending on the JDK they use. The Oracle proprietary Java 8 does not verify the CRC and will happily unpack jars with a mismatch. > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Priority: Critical > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3589) no composite*.xml files in root of JBDS installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3589?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3589: ---------------------------------- PR to add composite*.xml files to 4.3.x & master branch installers: https://github.com/jbdevstudio/jbdevstudio-product/pull/363 https://github.com/jbdevstudio/jbdevstudio-product/pull/364 Also does some additional refactoring/cleanup and adds LICENSE file to the root of the installer so that the jar is clearly EPL'd (JBDS-3590). > no composite*.xml files in root of JBDS installer > ------------------------------------------------- > > Key: JBDS-3589 > URL: https://issues.jboss.org/browse/JBDS-3589 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > > JBDS installer no longer includes composite*.xml in its root folder, so the jar won't work as an offline update site (eg., for an offline install of JBDS IS into Eclipse) > {code} > org.eclipse.equinox.p2.core.ProvisionException: No repository found at jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/. > {code} > Workaround: > use jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/jbds/ as the update site path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3589) no composite*.xml files in root of JBDS installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3589?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3589: ----------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/363, https://github.com/jbdevstudio/jbdevstudio-product/pull/364 Story Points: 3 > no composite*.xml files in root of JBDS installer > ------------------------------------------------- > > Key: JBDS-3589 > URL: https://issues.jboss.org/browse/JBDS-3589 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > > JBDS installer no longer includes composite*.xml in its root folder, so the jar won't work as an offline update site (eg., for an offline install of JBDS IS into Eclipse) > {code} > org.eclipse.equinox.p2.core.ProvisionException: No repository found at jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/. > {code} > Workaround: > use jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/jbds/ as the update site path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 February 2016