January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2951) Eclipse Documentation and Context Help

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2951?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2951: -------------------------------- Fix Version/s: 9.0.x > Eclipse Documentation and Context Help > -------------------------------------- > > Key: JBDS-2951 > URL: https://issues.jboss.org/browse/JBDS-2951 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: documentation > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.x > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3295) Product update fails on windows if installation folder and user home are on different devices

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3295?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3295: -------------------------------- Fix Version/s: 9.0.0.Alpha1 > Product update fails on windows if installation folder and user home are on different devices > --------------------------------------------------------------------------------------------- > > Key: JBDS-3295 > URL: https://issues.jboss.org/browse/JBDS-3295 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: p2-product > Affects Versions: 8.0.1.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3309) Add Sapphire to JBDS target-platform

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3309?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3309: -------------------------------------- +1 > Add Sapphire to JBDS target-platform > ------------------------------------ > > Key: JBDS-3309 > URL: https://issues.jboss.org/browse/JBDS-3309 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 9.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 9.0.0.Alpha1 > > > Batch component depends on Sapphire. So in order to get batch included by default in JBDS, we must have Sapphire available in JBDS TP. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19025: ---------------------------------------- Here is what my solution looks like: * For JBT, remove things that are only necessary for JBDS: https://github.com/mickaelistria/jbosstools-discovery/commit/385e260c1982... * For JBDS, create new artifacts and adapt current ones to JBDS: https://github.com/mickaelistria/jbdevstudio-discovery/commit/bc78a42266b... . I have an experiment build (no publish) for this repo on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-centraltar... > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Reporter: Mickael Istria > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19017: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... build and job disabled. Only thing left to do is push the release to QE, respin Central/EA/Discovery, and finish up the N&N. > Prepare for 4.2.2.Final release > ------------------------------- > > Key: JBIDE-19017 > URL: https://issues.jboss.org/browse/JBIDE-19017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.2.Final > > > TODOs for preparing for the 4.2.2 release. > For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: > a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK > b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19025: ---------------------------------------- Another benefit is that currently, we're only validating the Central/EA .target against the jbosstools one, which doesn't guarantee anything about compatibility with JBDS. Splitting them would allow to have a real validation against JBDS TP. > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Reporter: Mickael Istria > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19025: ------------------------------------ Seems to me too that if we're splitting JBT [discovery + central update] and JBDS [discovery + central update] we could migrate this content out of jbosstools-discovery and into jbdevstudio-product + jbosstools-build-sites. > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Reporter: Mickael Istria > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19025: ------------------------------------ Since EA only contains things from JBT, there's no need to build it as a target platform. We can simplify by building it as a simple update site. See JBIDE-18984. > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Reporter: Mickael Istria > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19025: ------------------------------- Description: Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. was: Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. So we should split the content of Central/EA for JBT and JBDS, and have them separated in dinstinct .target: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Reporter: Mickael Istria > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19025: ------------------------------- Summary: Separate JBT and JBDS Central and EA sites (was: Separate JBT and JBDS discovery) > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Reporter: Mickael Istria > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA for JBT and JBDS, and have them separated in dinstinct .target: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015