November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18828) Add BPMN2, guvnor and teiid to tracked usage tooling components

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18828?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18828: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/354, https://github.com/jbosstools/jbosstools-base/pull/355 (was: https://github.com/jbosstools/jbosstools-base/pull/354) > Add BPMN2, guvnor and teiid to tracked usage tooling components > --------------------------------------------------------------- > > Key: JBIDE-18828 > URL: https://issues.jboss.org/browse/JBIDE-18828 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.2.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18837: ------------------------------- Description: When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. was: When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. Therefore we need manifest-level [4.2.1,4.2.1] requirements on upstream foundation.core in examples and central, to force this lock-step updating. And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Labels: respin-a > Fix For: 4.2.1.CR1 > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18837: ----------------------------------- Labels: respin-a (was: ) > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Labels: respin-a > Fix For: 4.2.1.CR1 > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,4.2.1] requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18837: ----------------------------------- Component/s: central project-examples > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,4.2.1] requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18837: ----------------------------------- Fix Version/s: 4.2.1.CR1 > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Fix For: 4.2.1.CR1 > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,4.2.1] requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18837: ---------------------------------- Summary: because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated Key: JBIDE-18837 URL: https://issues.jboss.org/browse/JBIDE-18837 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, common/jst/core Affects Versions: 4.2.1.CR1 Reporter: Nick Boldt When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. Therefore we need manifest-level [4.2.1,4.2.1] requirements on upstream foundation.core in examples and central, to force this lock-step updating. And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18836) Update TPs/requirements/installer with m2e-apt 1.1.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18836?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18836: ---------------------------------- Assignee: Nick Boldt > Update TPs/requirements/installer with m2e-apt 1.1.1 > ---------------------------------------------------- > > Key: JBIDE-18836 > URL: https://issues.jboss.org/browse/JBIDE-18836 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.1.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.2.1.Final > > > m2e-apt 1.1.1 has been released. > It's available from http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.1.1... > Can you add it to our TP/requirements/installer, pretty please? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18820 at 11/26/14 4:28 PM: -------------------------------------------------------------- inherit jbosstools.version from parent pom version (and let foundation code strip the -SNAPSHOT); this still means we have to rebuild foundation every time there's a new milestone, and always be incrementing to the latest parent pom... but we don't have to update any pointless jbosstools.version property: https://github.com/jbosstools/jbosstools-base/pull/357 https://github.com/jbosstools/jbosstools-base/pull/358 Similar solution for JBDS, but parsing root pom instead: https://github.com/jbdevstudio/jbdevstudio-product/pull/247 https://github.com/jbdevstudio/jbdevstudio-product/pull/248 Once the above are applied, we can then do this to clean out the crap I added to the parent pom: https://github.com/jbosstools/jbosstools-build/pull/159 https://github.com/jbosstools/jbosstools-build/pull/160 was (Author: nickboldt): inherit jbosstools.version from parent pom version (and let foundation code strip the -SNAPSHOT); this still means we have to rebuild foundation every time there's a new milestone, and always be incrementing to the latest parent pom... but we don't have to update any pointless jbosstools.version property: https://github.com/jbosstools/jbosstools-base/pull/357 https://github.com/jbosstools/jbosstools-base/pull/358 Similar solution for JBDS, but parsing root pom instead: https://github.com/jbdevstudio/jbdevstudio-product/pull/247 https://github.com/jbdevstudio/jbdevstudio-product/pull/248 > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Max Rydahl Andersen > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18836) Update TPs/requirements/installer with m2e-apt 1.1.1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18836?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18836: -------------------------------- Fix Version/s: 4.2.1.Final > Update TPs/requirements/installer with m2e-apt 1.1.1 > ---------------------------------------------------- > > Key: JBIDE-18836 > URL: https://issues.jboss.org/browse/JBIDE-18836 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.1.CR1 > Reporter: Fred Bricon > Fix For: 4.2.1.Final > > > m2e-apt 1.1.1 has been released. > It's available from http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.1.1... > Can you add it to our TP/requirements/installer, pretty please? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18836) Update TPs/requirements/installer with m2e-apt 1.1.1

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-18836: ----------------------------------- Summary: Update TPs/requirements/installer with m2e-apt 1.1.1 Key: JBIDE-18836 URL: https://issues.jboss.org/browse/JBIDE-18836 Project: Tools (JBoss Tools) Issue Type: Task Components: build Affects Versions: 4.2.1.CR1 Reporter: Fred Bricon m2e-apt 1.1.1 has been released. It's available from http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-apt/1.1.1... Can you add it to our TP/requirements/installer, pretty please? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 November 2014