August 2017 - jbosstools-issues - Jboss List Archives

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24797: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM1) > 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 > 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, 7 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24797: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > 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 > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24801) Remove no-cache header for xml schema files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24801?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24801: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM1) > Remove no-cache header for xml schema files > ------------------------------------------- > > Key: JBIDE-24801 > URL: https://issues.jboss.org/browse/JBIDE-24801 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > This is a followup of JBIDE-20610 . In the past we were trying to figure out how to make validation in Eclipse faster. The problem is that xml schema files return no-cache header and so Eclipse needs to fetch them over and over again. > We tried to solve this on Eclipse side - allow ignoring of the no-cache http header. But why not try to solve this properly on the server side at least where we have control over it? I think there is no reason why request to urls like http://jboss.org/j2ee/dtd/service-ref_4_0.dtd should return no-cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24835) Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24835?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24835: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM1) > Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24835 > URL: https://issues.jboss.org/browse/JBIDE-24835 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24835) Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24835?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24835: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24835 > URL: https://issues.jboss.org/browse/JBIDE-24835 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 #137 September 2017 (was: devex #136 August 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 > Priority: Critical > Fix For: 4.5.1.AM2 > > > * 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, 7 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 commented on JBIDE-24799: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.1.AM2 and sprint 6483 > 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 > Priority: Critical > Fix For: 4.5.1.AM2 > > > * 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4519) Show Download/Install/Failed/Complete Information for Installer

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-4519?page=com.atlassian.jira.plugin.... ] Catherine Robson commented on JBDS-4519: ---------------------------------------- Thanks, looks great! > Show Download/Install/Failed/Complete Information for Installer > --------------------------------------------------------------- > > Key: JBDS-4519 > URL: https://issues.jboss.org/browse/JBDS-4519 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Mohit Suman > Assignee: Mohit Suman > Fix For: 11.1.0.AM1 > > Attachments: dwnl-info.png, status-new.png > > > Add textual/visual information mentioning the current state of the package Download/Install/Dailed/Complete. > 1. Adds a spinner for Download/Installation/Verification. > 2. error icon for failed download. > 3. Ok icon for complete installation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24870) switch to new Oxygen baselines & update plugin/feature versions accordingly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24870?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24870. ------------------------------ > switch to new Oxygen baselines & update plugin/feature versions accordingly > --------------------------------------------------------------------------- > > Key: JBIDE-24870 > URL: https://issues.jboss.org/browse/JBIDE-24870 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > When I apply this PR [1], we'll be comparing our latest build against the Oxygen release, not the old Neon one. > [1] https://github.com/jbosstools/jbosstools-build/pull/259 > As such, features and plugins will need to be bumped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24885) Tycho tests are not working properly

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24885?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24885. -------------------------------- I can't check if tests are passing because there is not mentioned which tests were broken, but I see that Nick has reverted that commit correctly. Closing. > Tycho tests are not working properly > ------------------------------------ > > Key: JBIDE-24885 > URL: https://issues.jboss.org/browse/JBIDE-24885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > Attachments: errorLog.txt > > > The following dependency > {code} > <dependency> > <type>eclipse-feature</type> > <artifactId>org.eclipse.e4.rcp</artifactId> > <version>0.0.0</version> > </dependency> > {code} > was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some *org.eclipse.jdt.core* issues. By adding the dependency the test work properly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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