March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24068) Freemarker New and Noteworthy for 4.4.4.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24068?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24068. ------------------------------ Resolution: Rejected > Freemarker New and Noteworthy for 4.4.4.AM1 > --------------------------------------------------- > > Key: JBIDE-24068 > URL: https://issues.jboss.org/browse/JBIDE-24068 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > > Denis Golovin, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Freemarker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Freemarker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Freemarker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24049 #comment Create N&N for Freemarker 4.4.4.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Freemarker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24068) Freemarker New and Noteworthy for 4.4.4.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24068?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24068: ---------------------------------- Assignee: Jeff MAURY (was: Denis Golovin) > Freemarker New and Noteworthy for 4.4.4.AM1 > --------------------------------------------------- > > Key: JBIDE-24068 > URL: https://issues.jboss.org/browse/JBIDE-24068 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > > Denis Golovin, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Freemarker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Freemarker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Freemarker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24049 #comment Create N&N for Freemarker 4.4.4.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Freemarker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24114) [parent pom] do not skip baseline comparison check when -DskipTests=true

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24114?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24114: ------------------------------------ +1 > [parent pom] do not skip baseline comparison check when -DskipTests=true > ------------------------------------------------------------------------ > > Key: JBIDE-24114 > URL: https://issues.jboss.org/browse/JBIDE-24114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > Currently, when you build with -DskipTests, the baseline checks are also skipped. This means that if you make a change to a file in a plugin, and build it locally to see if anything breaks, but forget to bump the version of the plugin and its containing feature, you won't see the baseline check failure until it's built in Jenkins and someone like me complains about it to you directly. > This happened recently in the 4.4.x branch for changes to openshift and base. > So I propose this change in parent pom for 4.4.x and master branches: > {code} > - <skipBaselineComparison>${skipTestsOrITests}</skipBaselineComparison> > + <skipBaselineComparison>false</skipBaselineComparison> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24115) Move integration tests to 4.4.4 in jbosstools-4.4.x branch

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24115?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-24115: ------------------------------- Description: move all versions to 4.4.4-SNAPSHOT (was: 1) Upgrade parent to 4.4.4.AM2 2) move all versions to 4.4.4-SNAPSHOT) > Move integration tests to 4.4.4 in jbosstools-4.4.x branch > ---------------------------------------------------------- > > Key: JBIDE-24115 > URL: https://issues.jboss.org/browse/JBIDE-24115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.4.4.AM1 > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.4.4.AM2 > > > move all versions to 4.4.4-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24114) [parent pom] do not skip baseline comparison check when -DskipTests=true

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24114?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24114: ------------------------------------ Proposed / emailed to list: http://lists.jboss.org/pipermail/jbosstools-dev/2017-March/011898.html > [parent pom] do not skip baseline comparison check when -DskipTests=true > ------------------------------------------------------------------------ > > Key: JBIDE-24114 > URL: https://issues.jboss.org/browse/JBIDE-24114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > Currently, when you build with -DskipTests, the baseline checks are also skipped. This means that if you make a change to a file in a plugin, and build it locally to see if anything breaks, but forget to bump the version of the plugin and its containing feature, you won't see the baseline check failure until it's built in Jenkins and someone like me complains about it to you directly. > This happened recently in the 4.4.x branch for changes to openshift and base. > So I propose this change in parent pom for 4.4.x and master branches: > {code} > - <skipBaselineComparison>${skipTestsOrITests}</skipBaselineComparison> > + <skipBaselineComparison>false</skipBaselineComparison> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24114) [parent pom] do not skip baseline comparison check when -DskipTests=true

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24114?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24114: ---------------------------------- Assignee: Jeff MAURY (was: Nick Boldt) > [parent pom] do not skip baseline comparison check when -DskipTests=true > ------------------------------------------------------------------------ > > Key: JBIDE-24114 > URL: https://issues.jboss.org/browse/JBIDE-24114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > Currently, when you build with -DskipTests, the baseline checks are also skipped. This means that if you make a change to a file in a plugin, and build it locally to see if anything breaks, but forget to bump the version of the plugin and its containing feature, you won't see the baseline check failure until it's built in Jenkins and someone like me complains about it to you directly. > This happened recently in the 4.4.x branch for changes to openshift and base. > So I propose this change in parent pom for 4.4.x and master branches: > {code} > - <skipBaselineComparison>${skipTestsOrITests}</skipBaselineComparison> > + <skipBaselineComparison>false</skipBaselineComparison> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24115) Move integration tests to 4.4.4 in jbosstools-4.4.x branch

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24115?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-24115: ---------------------------------- Assignee: Martin Malina > Move integration tests to 4.4.4 in jbosstools-4.4.x branch > ---------------------------------------------------------- > > Key: JBIDE-24115 > URL: https://issues.jboss.org/browse/JBIDE-24115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.4.4.AM1 > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.4.4.AM2 > > > 1) Upgrade parent to 4.4.4.AM2 > 2) move all versions to 4.4.4-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24115) Move integration tests to 4.4.4 in jbosstools-4.4.x branch

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-24115: ---------------------------------- Summary: Move integration tests to 4.4.4 in jbosstools-4.4.x branch Key: JBIDE-24115 URL: https://issues.jboss.org/browse/JBIDE-24115 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: integration-tests Affects Versions: 4.4.4.AM1 Reporter: Pavol Srna Fix For: 4.4.4.AM2 1) Upgrade parent to 4.4.4.AM2 2) move all versions to 4.4.4-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24114) [parent pom] do not skip baseline comparison check when -DskipTests=true

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24114: ---------------------------------- Summary: [parent pom] do not skip baseline comparison check when -DskipTests=true Key: JBIDE-24114 URL: https://issues.jboss.org/browse/JBIDE-24114 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.4.AM1, 4.5.0.AM1 Reporter: Nick Boldt Currently, when you build with -DskipTests, the baseline checks are also skipped. This means that if you make a change to a file in a plugin, and build it locally to see if anything breaks, but forget to bump the version of the plugin and its containing feature, you won't see the baseline check failure until it's built in Jenkins and someone like me complains about it to you directly. This happened recently in the 4.4.x branch for changes to openshift and base. So I propose this change in parent pom for 4.4.x and master branches: {code} - <skipBaselineComparison>${skipTestsOrITests}</skipBaselineComparison> + <skipBaselineComparison>false</skipBaselineComparison> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24114) [parent pom] do not skip baseline comparison check when -DskipTests=true

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24114?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24114: ------------------------------- Fix Version/s: 4.4.4.AM2 4.5.0.AM1 > [parent pom] do not skip baseline comparison check when -DskipTests=true > ------------------------------------------------------------------------ > > Key: JBIDE-24114 > URL: https://issues.jboss.org/browse/JBIDE-24114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > Currently, when you build with -DskipTests, the baseline checks are also skipped. This means that if you make a change to a file in a plugin, and build it locally to see if anything breaks, but forget to bump the version of the plugin and its containing feature, you won't see the baseline check failure until it's built in Jenkins and someone like me complains about it to you directly. > This happened recently in the 4.4.x branch for changes to openshift and base. > So I propose this change in parent pom for 4.4.x and master branches: > {code} > - <skipBaselineComparison>${skipTestsOrITests}</skipBaselineComparison> > + <skipBaselineComparison>false</skipBaselineComparison> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017