February 2015 - jbosstools-issues

[JBoss JIRA] (JBTIS-383) Display only those categories which are fully supported

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-383?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-383. ------------------------------ Fix Version/s: 4.2.0.CR2 8.0.0.CR2 Resolution: Done Split the JBTIS TP so as to not leak in non .Final components into GA. > Display only those categories which are fully supported > ------------------------------------------------------- > > Key: JBTIS-383 > URL: https://issues.jboss.org/browse/JBTIS-383 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 4.2.0.CR2, 8.0.0.CR2 > > Attachments: jbdsis_categories.png > > > When you install tooling from > http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio... > you will also see categories which are not fully supported. > For example, JBoss Business Process and Rules Development is not supported yet (not all features are final) but the category is displayed, see the attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19125) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19125?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-19125. -------------------------------- Resolution: Done > For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear] > -------------------------------------------------------------------- > > Key: JBIDE-19125 > URL: https://issues.jboss.org/browse/JBIDE-19125 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.2.3.Beta1 > > > For JBIDE 4.2.3.Beta1 [Aerogear]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3. > Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19125) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19125?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19125: -------------------------------------- bumped the versions.. From build perspective we should be done. I still need to pick the functionality into 4.2.x. > For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear] > -------------------------------------------------------------------- > > Key: JBIDE-19125 > URL: https://issues.jboss.org/browse/JBIDE-19125 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.2.3.Beta1 > > > For JBIDE 4.2.3.Beta1 [Aerogear]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3. > Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19116) itests not being linked from build page

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19116: ---------------------------------------- Fixed with https://github.com/jbdevstudio/jbdevstudio-ci/commit/6a43dbde4321f2532548... Thanks for the review. > itests not being linked from build page > --------------------------------------- > > Key: JBIDE-19116 > URL: https://issues.jboss.org/browse/JBIDE-19116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19116) itests not being linked from build page

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19116: ---------------------------------------- Seems like my replace operation was a mess and I didn't check it carefully. I'll do it again and make a PR before pushing. > itests not being linked from build page > --------------------------------------- > > Key: JBIDE-19116 > URL: https://issues.jboss.org/browse/JBIDE-19116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19116) itests not being linked from build page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19116 at 2/3/15 10:32 AM: ------------------------------------------------------------- [~mickael_istria] Why did you remove some of the archived artifacts, including {code}sources/*/tests/*/target/work/configuration/*.log,sources/*/tests/*/target/work/data/.metadata/*.log{code} ? {code} - <artifacts>results/*/all/*Update*.zip,sources/*/target/jacoco.exec,sources/*/tests/*/target/work/configuration/*.log,sources/*/tests/*/target/work/data/.metadata/*.log, sources/target/coverage-report/**</artifacts> + <artifacts>results/*/all/*Update*.zip,sources/*/target/jacoco.exec,sources/*/*tests/*/target/coverage-report/**</artifacts> {code} was (Author: nickboldt): [~mickael_istria] Why did you remove some of the archived artifacts, including {code}sources/*/tests/*/target/work/configuration/*.log,sources/*/tests/*/target/work/data/.metadata/*.log{code} ? {code} - <artifacts>results/*/all/*Update*.zip,sources/*/target/jacoco.exec,sources/*/tests/*/target/work/configuration/*.log,sources/*/tests/*/target/work/data/.metadata/*.log, sources/target/coverage-report/**</artifacts> + <artifacts>results/*/all/*Update*.zip,sources/*/target/jacoco.exec,sources/*/*tests/*/target/coverage-report/**</artifacts> {code} > itests not being linked from build page > --------------------------------------- > > Key: JBIDE-19116 > URL: https://issues.jboss.org/browse/JBIDE-19116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19116) itests not being linked from build page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19116: ------------------------------------ [~mickael_istria] Why did you remove some of the archived artifacts, including {code}sources/*/tests/*/target/work/configuration/*.log,sources/*/tests/*/target/work/data/.metadata/*.log{code} ? {code} - <artifacts>results/*/all/*Update*.zip,sources/*/target/jacoco.exec,sources/*/tests/*/target/work/configuration/*.log,sources/*/tests/*/target/work/data/.metadata/*.log, sources/target/coverage-report/**</artifacts> + <artifacts>results/*/all/*Update*.zip,sources/*/target/jacoco.exec,sources/*/*tests/*/target/coverage-report/**</artifacts> {code} > itests not being linked from build page > --------------------------------------- > > Key: JBIDE-19116 > URL: https://issues.jboss.org/browse/JBIDE-19116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central) IDE v.0.7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19045: ------------------------------------ I will put Tern and Angular 0.7 into the JBT & JBDS update sites, because we need to continue to support users on 4.2.2/8.0.x/0.6 who don't upgrade, and users on 4.2.3/8.1/0.7 who do. > Update Tern.java (TP) and AngularJS (Central) IDE v.0.7 > ------------------------------------------------------- > > Key: JBIDE-19045 > URL: https://issues.jboss.org/browse/JBIDE-19045 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, jsp/jsf/xml/html source editing, target-platform > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.2.3.Beta1 > > > We are going to update Tern to v0.7.0 for 4.2.x. > Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002) > p2diff output: > {code} > ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > < tern.eclipse.ide.tools.core [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159] > < tern.eclipse.ide.tools.ui [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159] > < tern-jsdt-feature.feature.jar [0.7.0.201412012159] > < tern.server.nodejs [0.7.0.201412012159] > < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159] > < tern.core [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159] > < tern.eclipse.ide.core [0.7.0.201412012159] > < tern-server-nodejs-feature.feature.group [0.7.0.201412012159] > < tern-feature.feature.group [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159] > < tern.eclipse.ide.ui [0.7.0.201412012159] > < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159] > < tern-jsdt-feature.feature.group [0.7.0.201412012159] > < tern-feature.feature.jar [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159] > < tern.eclipse.ide.jsdt [0.7.0.201412012159] > < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159] > < tern.eclipse [0.7.0.201412012159] > > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610] > > tern.eclipse.ide.core [0.6.0.201409231610] > > tern-feature.feature.jar [0.6.0.201409231610] > > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610] > > tern.server.nodejs [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610] > > tern-jsdt-feature.feature.jar [0.6.0.201409231610] > > tern-feature.feature.group [0.6.0.201409231610] > > tern.eclipse.ide.tools.ui [0.6.0.201409231610] > > tern-jsdt-feature.feature.group [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610] > > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610] > > tern.eclipse [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610] > > tern.eclipse.ide.ui [0.6.0.201409231610] > > tern.core [0.6.0.201409231610] > > tern-server-nodejs-feature.feature.group [0.6.0.201409231610] > > tern.eclipse.ide.tools.core [0.6.0.201409231610] > > tern.eclipse.ide.jsdt [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610] > > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610] > === Summary === > ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3327) Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3327?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3327: ----------------------------------------- Assignee: Michelle Murray > Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0 > -------------------------------------------------------- > > Key: JBDS-3327 > URL: https://issues.jboss.org/browse/JBDS-3327 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 9.0.0.GA > > > We have been testing primarily on Yosemite (and Mavericks) for some time and there's no reason why not include Yosemite. > This is the JBDS support matrix doc: https://access.redhat.com/articles/427493 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3327) Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3327?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3327: ------------------------------------------- [~mmurray] related to JBDS-3330 ? stay here or move to TOOLSDOC ? > Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0 > -------------------------------------------------------- > > Key: JBDS-3327 > URL: https://issues.jboss.org/browse/JBDS-3327 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Fix For: 9.0.0.GA > > > We have been testing primarily on Yosemite (and Mavericks) for some time and there's no reason why not include Yosemite. > This is the JBDS support matrix doc: https://access.redhat.com/articles/427493 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015