July 2017 - jbosstools-issues - Jboss List Archives

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4461: ---------------------------------- Slide deck updated to remove the link to the old doc and the link to this JIRA. https://docs.google.com/presentation/d/19v5HMRma0NVn2QD47-n6TmjvrO1YfXUyY... > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > Attachments: whats-in-devstudio-features-plugins-only.txt, whats-in-devstudio.png, whats-in-devstudio.txt > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4461. ---------------------------- Resolution: Rejected On 2017-07-26 at 11:26am, [~tim.moran] said: {quote}If Jeff/you/whomever can get that info in a reasonable amount of time then we don't need to keep producing it I'll leave it up to you guys if you want to maintain it or not; just keep in mind someone, someday might ask {quote} > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > Attachments: whats-in-devstudio-features-plugins-only.txt, whats-in-devstudio.png, whats-in-devstudio.txt > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 edited comment on JBIDE-24243 at 7/26/17 11:22 AM: -------------------------------------------------------------- 1. Re: blockers, I pinged about those in MM but not sure if anyone replied. I'll reopen this issue since they're apparently legit blockers and legit not yet done. 2. I'm not sure what you mean by "test structure harmonized" - can you open a subtask JIRA & explain what you need / what's missing in detail? 3. {quote}What about the integration of Fuse Tooling in the branch/tag process of JBoss Tools? I think that it was added in script but not yet functional, right?{quote} It's as functional as it can be given your repos won't let me push directly to them w/o a review. To further automate this, I've opened JBIDE-24765. We'll need something along those lines if jbosstools-openshift decides to also implement "do not push w/o review" on that repo, as per JBIDE-24439. 4. {quote}someone from Fuse Tooling took time to read the full JBoss Tools dev doc{quote} - do you want to open a subtask JIRA for that and assign it to "someone" to do? Or really, should EVERYONE in Fuse Tooling do that? Off the top of my head, the things you should be doing are: * features w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * plugins w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * test plugins w/ sources aggregated onto the jbosstools site: DONE * features in Central for JBT and devstudio: DONE * features should use `license-feature="org.jboss.tools.foundation.license.feature" license-feature-version="0.0.0"`: DONE for all 5 features {code} $➔ for f in $(find . -name feature.xml); do echo $f ; cat $f | grep foundation.license; done ./transformation/features/org.jboss.tools.fuse.transformation.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./jmx/features/org.fusesource.ide.jmx.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./core/features/org.fusesource.ide.core.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./servers/features/org.fusesource.ide.server.extensions.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./editor/features/org.fusesource.ide.camel.editor.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" {code} * plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) * new features and plugins should follow the above rules when created --> these TODOs moved to JBIDE-24766 devdoc docs to read include: * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/publis... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/third_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versio... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/community/cod... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/taggin... was (Author: nickboldt): 1. Re: blockers, I pinged about those in MM but not sure if anyone replied. I'll reopen this issue since they're apparently legit blockers and legit not yet done. 2. I'm not sure what you mean by "test structure harmonized" - can you open a subtask JIRA & explain what you need / what's missing in detail? 3. {quote}What about the integration of Fuse Tooling in the branch/tag process of JBoss Tools? I think that it was added in script but not yet functional, right?{quote} It's as functional as it can be given your repos won't let me push directly to them w/o a review. To further automate this, I've opened JBIDE-24765. We'll need something along those lines if jbosstools-openshift decides to also implement "do not push w/o review" on that repo, as per JBIDE-24439. 4. {quote}someone from Fuse Tooling took time to read the full JBoss Tools dev doc{quote} - do you want to open a subtask JIRA for that and assign it to "someone" to do? Or really, should EVERYONE in Fuse Tooling do that? Off the top of my head, the things you should be doing are: * features w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * plugins w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * test plugins w/ sources aggregated onto the jbosstools site: DONE * features in Central for JBT and devstudio: DONE * features should use `license-feature="org.jboss.tools.foundation.license.feature" license-feature-version="0.0.0"`: DONE for all 5 features {code} $➔ for f in $(find . -name feature.xml); do echo $f ; cat $f | grep foundation.license; done ./transformation/features/org.jboss.tools.fuse.transformation.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./jmx/features/org.fusesource.ide.jmx.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./core/features/org.fusesource.ide.core.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./servers/features/org.fusesource.ide.server.extensions.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./editor/features/org.fusesource.ide.camel.editor.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" {code} * plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) * new features and plugins should follow the above rules when created devdoc docs to read include: * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/publis... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/third_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versio... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/community/cod... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/taggin... > 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: Bug > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24766) verify correct copyright dates, terms and licenses

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24766: ---------------------------------- Summary: verify correct copyright dates, terms and licenses Key: JBIDE-24766 URL: https://issues.jboss.org/browse/JBIDE-24766 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: fusetools, fusetools-extras Affects Versions: 4.5.0.AM2 Reporter: Nick Boldt Verify the following are true: * plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" - see https://github.com/jbosstools/jbosstools-base/blob/master/foundation/feat... * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) - see https://github.com/jbosstools/jbosstools-base/blob/master/foundation/feat... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 edited comment on JBIDE-24243 at 7/26/17 11:18 AM: -------------------------------------------------------------- 1. Re: blockers, I pinged about those in MM but not sure if anyone replied. I'll reopen this issue since they're apparently legit blockers and legit not yet done. 2. I'm not sure what you mean by "test structure harmonized" - can you open a subtask JIRA & explain what you need / what's missing in detail? 3. {quote}What about the integration of Fuse Tooling in the branch/tag process of JBoss Tools? I think that it was added in script but not yet functional, right?{quote} It's as functional as it can be given your repos won't let me push directly to them w/o a review. To further automate this, I've opened JBIDE-24765. We'll need something along those lines if jbosstools-openshift decides to also implement "do not push w/o review" on that repo, as per JBIDE-24439. 4. {quote}someone from Fuse Tooling took time to read the full JBoss Tools dev doc{quote} - do you want to open a subtask JIRA for that and assign it to "someone" to do? Or really, should EVERYONE in Fuse Tooling do that? Off the top of my head, the things you should be doing are: * features w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * plugins w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * test plugins w/ sources aggregated onto the jbosstools site: DONE * features in Central for JBT and devstudio: DONE * features should use `license-feature="org.jboss.tools.foundation.license.feature" license-feature-version="0.0.0"`: DONE for all 5 features {code} $➔ for f in $(find . -name feature.xml); do echo $f ; cat $f | grep foundation.license; done ./transformation/features/org.jboss.tools.fuse.transformation.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./jmx/features/org.fusesource.ide.jmx.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./core/features/org.fusesource.ide.core.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./servers/features/org.fusesource.ide.server.extensions.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./editor/features/org.fusesource.ide.camel.editor.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" {code} * plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) * new features and plugins should follow the above rules when created devdoc docs to read include: * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/publis... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/third_... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versio... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/community/cod... * https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/taggin... was (Author: nickboldt): 1. Re: blockers, I pinged about those in MM but not sure if anyone replied. I'll reopen this issue since they're apparently legit blockers and legit not yet done. 2. I'm not sure what you mean by "test structure harmonized" - can you open a subtask JIRA & explain what you need / what's missing in detail? 3. {quote}What about the integration of Fuse Tooling in the branch/tag process of JBoss Tools? I think that it was added in script but not yet functional, right?{quote} It's as functional as it can be given your repos won't let me push directly to them w/o a review. To further automate this, I've opened JBIDE-24765. We'll need something along those lines if jbosstools-openshift decides to also implement "do not push w/o review" on that repo, as per JBIDE-24439. 4. {quote}someone from Fuse Tooling took time to read the full JBoss Tools dev doc{quote} - do you want to open a subtask JIRA for that and assign it to "someone" to do? Or really, should EVERYONE in Fuse Tooling do that? Off the top of my head, the things you should be doing are: * features w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * plugins w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * test plugins w/ sources aggregated onto the jbosstools site: DONE * features in Central for JBT and devstudio: DONE * features should use `license-feature="org.jboss.tools.foundation.license.feature" license-feature-version="0.0.0"`: DONE for all 5 features {code} $➔ for f in $(find . -name feature.xml); do echo $f ; cat $f | grep foundation.license; done ./transformation/features/org.jboss.tools.fuse.transformation.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./jmx/features/org.fusesource.ide.jmx.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./core/features/org.fusesource.ide.core.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./servers/features/org.fusesource.ide.server.extensions.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./editor/features/org.fusesource.ide.camel.editor.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" {code} * plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) * new features and plugins should follow the above rules when created > 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: Bug > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24765) implement workaround for blocked branches when we need to update parent poms automatically

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24765?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24765: ---------------------------------- Assignee: Nick Boldt > implement workaround for blocked branches when we need to update parent poms automatically > ------------------------------------------------------------------------------------------ > > Key: JBIDE-24765 > URL: https://issues.jboss.org/browse/JBIDE-24765 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Once protected branches are implemented, branching/tagging & simple root pom updates may not be possible w/o a review. > So, we need to implement an automated workflow that looks like this: > * submit a PR, then > * script a review (by a different user), then > * merge the PR -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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