April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22229: ------------------------------- Sprint: devex #115 May 2017 (was: devex #113 April 2016) > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22229: ------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha1) > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21621: ------------------------------------ I don't recommend using /snapshots/ for a URL that will persist forever. Snapshots are by definition transitive. I've also renamed your folder to http://download.jboss.org/jbosstools/neon/snapshots/updates/reddeer/1.1.0... because it's 2016, not 2015. :D Re: deploying to JBoss Nexus: https://github.com/jboss-reddeer/reddeer/issues/1388 > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21621 at 4/27/16 11:19 AM: -------------------------------------------------------------- I don't recommend using /snapshots/ for a URL that will persist forever. Snapshots are by definition transitive. But for this first Alpha1 build it will fine. I've also renamed your folder to http://download.jboss.org/jbosstools/neon/snapshots/updates/reddeer/1.1.0... because it's 2016, not 2015. :D Re: deploying to JBoss Nexus: https://github.com/jboss-reddeer/reddeer/issues/1388 was (Author: nickboldt): I don't recommend using /snapshots/ for a URL that will persist forever. Snapshots are by definition transitive. I've also renamed your folder to http://download.jboss.org/jbosstools/neon/snapshots/updates/reddeer/1.1.0... because it's 2016, not 2015. :D Re: deploying to JBoss Nexus: https://github.com/jboss-reddeer/reddeer/issues/1388 > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-733) JBDS-IS GA Installation Guide

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-733?page=com.atlassian.jira.plug... ] Supriya Bharadwaj closed TOOLSDOC-733. -------------------------------------- Resolution: Done [~mhusnain], I have already created a JIRA for this task with mine and Andrej's progress on the task > TOOLSDOC-731. Hence closing this one. > JBDS-IS GA Installation Guide > ----------------------------- > > Key: TOOLSDOC-733 > URL: https://issues.jboss.org/browse/TOOLSDOC-733 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 9.0.0 > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Fix For: 9.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2044: ---------------------------------- Slip to next sprint as this should be fixed in Neon.0.M7. Will review once we're building on that TP in a couple weeks. > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha2 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Fix Version/s: 10.0.0.Alpha2 (was: 10.0.0.Alpha1) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha2 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Sprint: devex #114 May 2017 (was: devex #113 April 2016) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-731) Update: JBDS IS 9.0.0 GA Install Guide

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-731?page=com.atlassian.jira.plug... ] Supriya Bharadwaj updated TOOLSDOC-731: --------------------------------------- Fix Version/s: 9.0.0 > Update: JBDS IS 9.0.0 GA Install Guide > -------------------------------------- > > Key: TOOLSDOC-731 > URL: https://issues.jboss.org/browse/TOOLSDOC-731 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 9.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Debugging of OS 3 application creates a new replication controller

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22259: ------------------------------------- We're indeed modifying the current IDeploymentConfig https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or.... [~jcantrill] would it make sense to change the deployment instead? > Debugging of OS 3 application creates a new replication controller > ------------------------------------------------------------------ > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016