September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23171) Remove unused imports in org.jboss.tools.hibernate.jpt.core.internal.context.HibernateTable

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23171?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23171. ------------------------------------ verified in github > Remove unused imports in org.jboss.tools.hibernate.jpt.core.internal.context.HibernateTable > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23171 > URL: https://issues.jboss.org/browse/JBIDE-23171 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23181) Remove unused imports in org.jboss.tools.hibernate.jpt.core.internal.context.HibernateIdMapping

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23181?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23181. ------------------------------------ verified in github > Remove unused imports in org.jboss.tools.hibernate.jpt.core.internal.context.HibernateIdMapping > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23181 > URL: https://issues.jboss.org/browse/JBIDE-23181 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23146) Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23146?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23146. ------------------------------------ verified in github > Add missing $NON-NLS-1$ tags in org.jboss.tools.hibernate.ui.xml.editor.HibernatePropertiesContentAssistProcessor > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23146 > URL: https://issues.jboss.org/browse/JBIDE-23146 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23212: -------------------------------------- Assignee: Nick Boldt cc: [~mickael_istria] > Baseline check does not seem to work with features > -------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho, > Fix For: 4.4.2.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23213: --------------------------------------- Good suggestions. So for Ubuntu we should probably have these: 16.04.1 LTS and 16.10 And for Fedora, I agree with you that we should be able to contain Fedora 25 and thus end up with: Fedora 24 and 25 > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23213: ------------------------------- Description: It's time to review the available platforms on which we test devstudio / jbt. Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. [0] https://wiki.ubuntu.com/Releases * Should we move to 16.04.1 LTS and 16.10? * Should we move to 14.04.5 LTS and 16.04.1 LTS ? * Should we move to 14.04.5 LTS and 16.10? Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? [2] https://fedoraproject.org/wiki/Releases/25/Schedule * Should we move to F24 and F25? was: It's time to review the available platforms on which we test devstudio / jbt. Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available when 10.2 / 4.4.2 is released in Dec 2016. https://wiki.ubuntu.com/Releases * Should we move to 16.04.1 LTS and 16.10? * Should we move to 14.04.5 LTS and 16.04.1 LTS ? * Should we move to 14.04.5 LTS and 16.10? > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Fix For: 4.4.2.AM3 > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23213: ---------------------------------- Assignee: Martin Malina > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23213: ------------------------------- Fix Version/s: 4.4.2.AM3 > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23213: ---------------------------------- Summary: Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 Key: JBIDE-23213 URL: https://issues.jboss.org/browse/JBIDE-23213 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.1.Final Reporter: Nick Boldt It's time to review the available platforms on which we test devstudio / jbt. Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available when 10.2 / 4.4.2 is released in Dec 2016. https://wiki.ubuntu.com/Releases * Should we move to 16.04.1 LTS and 16.10? * Should we move to 14.04.5 LTS and 16.04.1 LTS ? * Should we move to 14.04.5 LTS and 16.10? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-23212: ---------------------------------- Summary: Baseline check does not seem to work with features Key: JBIDE-23212 URL: https://issues.jboss.org/browse/JBIDE-23212 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.1.Final Reporter: Jeff MAURY Fix For: 4.4.2.AM1 The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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