July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16161: ------------------------------- Fix Version/s: (was: 4.3.x) > Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16161: ------------------------------------ OK, so that just leaves this commit [1] which we could undo from master if it's no longer required. [1] https://github.com/jbosstools/jbosstools-build/pull/127/files > Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Mickael Istria > Fix For: 4.3.x, 4.5.1.AM1 > > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-16161: ---------------------------------- Assignee: Nick Boldt (was: Mickael Istria) > Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Nick Boldt > Fix For: 4.3.x, 4.5.1.AM1 > > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16161: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.x) > Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Nick Boldt > Fix For: 4.3.x, 4.5.1.AM1 > > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4454) Path to JDK needs to be updated after every update of JDK

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4454?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4454: ---------------------------------- I can't figure out how to prevent adding the -vm flag into the devstudio.ini even if Default is selected. But I did add some logic to check for /etc/alternatives [1] and use that instead so at least the installation is more portable when updating jdk versions. {code:title=devstudio.ini} -vm /etc/alternatives/java_sdk/bin/java ...{code} [1] https://github.com/jbdevstudio/jbdevstudio-product/pull/468 [~dgolovin] do you know how to suppress adding the -vm flag when the value added is the default, or when the Default radio button is selected? > Path to JDK needs to be updated after every update of JDK > --------------------------------------------------------- > > Key: JBDS-4454 > URL: https://issues.jboss.org/browse/JBDS-4454 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, installer > Affects Versions: 11.0.0.AM1 > Environment: Fedora 26 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: image-2017-06-30-11-01-40-783.png, jdk_selected_alternatives.png, screenshot-1.png > > > After every update of JDK, path to JDK in file devstudio.ini needs to be updated. This does not happening in Eclipse. > !image-2017-06-30-11-01-40-783.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4454) Path to JDK needs to be updated after every update of JDK

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4454?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4454: ----------------------------- Attachment: jdk_selected_alternatives.png > Path to JDK needs to be updated after every update of JDK > --------------------------------------------------------- > > Key: JBDS-4454 > URL: https://issues.jboss.org/browse/JBDS-4454 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, installer > Affects Versions: 11.0.0.AM1 > Environment: Fedora 26 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: image-2017-06-30-11-01-40-783.png, jdk_selected_alternatives.png, screenshot-1.png > > > After every update of JDK, path to JDK in file devstudio.ini needs to be updated. This does not happening in Eclipse. > !image-2017-06-30-11-01-40-783.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1153) Missing Fuse category in Devstudio IS standalone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1153?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1153: ----------------------------------- Hey [~apodhrad] - what do you think of this? http://download.jboss.org/jbosstools/oxygen/staging/updates/integration-s... > Missing Fuse category in Devstudio IS standalone installer > ---------------------------------------------------------- > > Key: JBTIS-1153 > URL: https://issues.jboss.org/browse/JBTIS-1153 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: devstudio_vs_devstudiois.png > > > The Devstudio installer contains a category for installing Fuse tooling but Devstudio IS installer doesn't. IMHO the Devstudio IS installer should contain everything from Devstudio, wdyt? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24768) openshift connection wizard advanced section persists changes when canceled

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24768?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24768: -------------------------------- Description: When you have an openshift connection, if you right-click on it and edit it, you can then change it's properties. If you expand the advanced section, and make changes, and then cancel the wizard, all changes are persisted when they should not be. > openshift connection wizard advanced section persists changes when canceled > --------------------------------------------------------------------------- > > Key: JBIDE-24768 > URL: https://issues.jboss.org/browse/JBIDE-24768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Rob Stryker > > When you have an openshift connection, if you right-click on it and edit it, you can then change it's properties. If you expand the advanced section, and make changes, and then cancel the wizard, all changes are persisted when they should not be. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24768) openshift connection wizard advanced section persists changes when canceled

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-24768: ----------------------------------- Summary: openshift connection wizard advanced section persists changes when canceled Key: JBIDE-24768 URL: https://issues.jboss.org/browse/JBIDE-24768 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.0.Final Reporter: Rob Stryker -- 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:46 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 For a list of devdoc docs to read, see JBIDE-24767. 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 --> 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... > 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

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