September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24895) some smoke and weekly jobs are configured for multiple OSes but only run on rhel7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24895?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24895: ------------------------------- Sprint: devex #138 September 2017 > some smoke and weekly jobs are configured for multiple OSes but only run on rhel7 > --------------------------------------------------------------------------------- > > Key: JBIDE-24895 > URL: https://issues.jboss.org/browse/JBIDE-24895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, build, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > > Just wondering why there's a chunk of shell script in the aerogear.it.smoke job that allows it to run on linux, rhel, or osx... but the job is only configured to run on rhel7 slaves. > Is the code boilerplate, or is the job supposed to run on more than one type of OS? > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.1.AM3 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4530) Work to remove all upstream 3rd party deps in the devstudio rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4530?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4530: ----------------------------- Sprint: devex #138 September 2017 > Work to remove all upstream 3rd party deps in the devstudio rpm > --------------------------------------------------------------- > > Key: JBDS-4530 > URL: https://issues.jboss.org/browse/JBDS-4530 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > This is a wrapper issue for a number of subtasks and linked issues related to eliminating the 3rd party plugins in the devstudio copr rpm, so that it can ultimately be built w/ brew. > Tasks include: > * add rpms already in Fedora to SCL/DevTools (eg., Datatools, WTP Dali/JPT) > * create new rpms in Fedora (buildship, recommenders/snipmatch, sapphire[1], m2e & extras[2], m2e-wtp & extras[3], tern.java) > * removal of old/duplicate versions in the target platform (javax.activation, guava, jetty, asm, aries > * ensure we're using the latest linuxtools/docker tools (including new features/plugins added for 6.1/6.1.1) > [1] may require contributing a Maven/Tycho build upstream to that project so we can then consume it in Koji/Brew > [2] m2e extras include: buildhelper, egit, mavenarchiver > [3] m2e.wtp extras include: jaxrs, jpa, jsf -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24939: ------------------------------- Sprint: devex #138 September 2017 > update target platform & Central to Oxygen.1 > -------------------------------------------- > > Key: JBIDE-24939 > URL: https://issues.jboss.org/browse/JBIDE-24939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions_sorted_no_featurejars_no_sources.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff.txt > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24243: ------------------------------- Sprint: devex #132 May 2017, devex #138 September 2017 (was: devex #132 May 2017, devex #137 September 2017) > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.1.AM3 > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24773) Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24773?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24773: ---------------------------------- Assignee: Nick Boldt > Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24773 > URL: https://issues.jboss.org/browse/JBIDE-24773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24773) Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24773?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24773: ------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.Final) > Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24773 > URL: https://issues.jboss.org/browse/JBIDE-24773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24773) Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24773?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24773: ------------------------------------ If you want a .target file that contains jboss tools features (which are by definition of a target platform VERSIONED), you'll need to rebuild the .target file every time there's a new JBT release. But that could be every CI build, or every AMx milestone (one change every 3 weeks). How often would you want to rebuild & republish this? In theory it could be pushed back into github every time it's rebuilt, or just published to nexus. > Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24773 > URL: https://issues.jboss.org/browse/JBIDE-24773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Fix For: 4.5.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24797: ------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc, hibernate, openshift, server > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24480) Configure sonar for jbosstools-base

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24480?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24480: ------------------------------- Sprint: devex #132 May 2017, devex #138 September 2017 (was: devex #132 May 2017, devex #137 September 2017) > Configure sonar for jbosstools-base > ----------------------------------- > > Key: JBIDE-24480 > URL: https://issues.jboss.org/browse/JBIDE-24480 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > Configure PR builds + master daily builds with storing the results and test coverage -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017