July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24568) Review all tests for Docker Tooling in upstream

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24568?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24568: ---------------------------------- Description: Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=519932 Implement these tests: Display Log Network Mode - network configuration Edit DockerFile was: Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=519932 Implement these tests: Display Log Remove Log Copy from container Network Mode - network configuration Edit DockerFile Terminal test > Review all tests for Docker Tooling in upstream > ----------------------------------------------- > > Key: JBIDE-24568 > URL: https://issues.jboss.org/browse/JBIDE-24568 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.Final > > > Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=519932 > Implement these tests: > Display Log > Network Mode - network configuration > Edit DockerFile -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24538) Wildfly 9 and above need remote+http protocol for jmx

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24538?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24538. --------------------------------- I was able to reproduce the warning in devstudio 10.4.0.GA when starting WildFly 10. I had to start devstudio from cli using: {code} ./devstudio-10.4.0.GA/studio/devstudio.app/Contents/MacOS/devstudio -consolelog {code} Then I tried the same with devstudio 11.0.0.AM2 with WildFly 10 and EAP 7.0 and there was no warning. So that confirms it's fixed. Closing. > Wildfly 9 and above need remote+http protocol for jmx > ----------------------------------------------------- > > Key: JBIDE-24538 > URL: https://issues.jboss.org/browse/JBIDE-24538 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > When connecting to a wf9 / wf10 / wf11 or associated eap's via jmx, console spits out the following: > {code} > Jun 05, 2017 4:16:34 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > {code} -- 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 Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24243: ----------------------------------------- I see nothing related to this https://docs.google.com/document/d/15piSdr35GaEnfLRIrhGyIS7XPT-85p_K6gMbw... "Dec, 2017 - next Dev tools release train which will have the online manifest file which will address the customer experience with tooling." which i don't know what it means > 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-24592) Study Foreman documentation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24592?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24592: --------------------------------------- Also, https://www.youtube.com/watch?v=_R8-0KAkoPc looks interesting. Btw. The above mentioned repo is using GNU license, which seems alright for us. But other software might be a problem: Readme.md -> Licenses section -> SysInternals. [~ppitonak] [~psrna] Could you please take a look? > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci > Fix For: 4.5.0.Final > > > This issue consists of going through foreman documentation, tutorials and manuals. > Afterwards, it could be possible to address another steps in this process. > Docs: > https://www.theforeman.org/manuals/1.15/index.html > https://beryju.org/en/blog/getting-started-foreman-part-1#install_os > http://projects.theforeman.org/issues/432 > https://groups.google.com/forum/#!topic/foreman-users/FP9uTb8TAFY -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24592) Study Foreman documentation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24592?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24592 at 7/27/17 5:07 AM: ---------------------------------------------------------------- I think that this one can do: https://github.com/kireevco/wimaging Especially these points are interesting in our case: * No extra servers like WDS needed - all relevant settings can be configured in Foreman directly * Optional local user creation * Correctly report finished host building I will give it a try. See if it works for our case (windows bare metal provisioning, setting up user, connects to jenkins, etc...) was (Author: odockal): I think that this one can do: https://github.com/kireevco/wimaging Especially this points are interesting in our case: * No extra servers like WDS needed - all relevant settings can be configured in Foreman directly * Optional local user creation * Correctly report finished host building I will give it a try. See if it works for our case (windows bare metal provisioning, setting up user, connects to jenkins, etc...) > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci > Fix For: 4.5.0.Final > > > This issue consists of going through foreman documentation, tutorials and manuals. > Afterwards, it could be possible to address another steps in this process. > Docs: > https://www.theforeman.org/manuals/1.15/index.html > https://beryju.org/en/blog/getting-started-foreman-part-1#install_os > http://projects.theforeman.org/issues/432 > https://groups.google.com/forum/#!topic/foreman-users/FP9uTb8TAFY -- 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 Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24243: ----------------------------------------- on the initial document I put some comments included some others that i think were not answered/addressed: https://docs.google.com/a/redhat.com/document/d/15piSdr35GaEnfLRIrhGyIS7X... - how to have/use the API baseline? How to have it automatically configured in dev environment? - External API, we currently don't take care about what is in internal packages and what is public API as nobody is extending us as far as we know, should we do a cleanup and put almost everything in internal packages? > 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-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24243: ----------------------------------------- do we have the possibility to release Fuse Tooling apart on its own update site already? is it automated? Is it documented how to do that? This was something agreed https://docs.google.com/document/d/15piSdr35GaEnfLRIrhGyIS7XPT-85p_K6gMbw... (bookmark need to be agreed I guess to have it working, otherwise search for "Agreed Release process" ) > 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-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24243: ----------------------------------------- {quote}bq. someone from Fuse Tooling took time to read the full JBoss Tools dev doc - 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?{quote} My idea was that at least one Fuse Tooling guy read carefully the Dev doc to spot which tasks still need to be done as it seems that it was not really done. Thanks for having created [JBIDE-24767] > 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-24767) ensure Fuse Tools team knows where the devdocs are and has read them

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24767?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24767: ----------------------------------------- This reading need to spot all remaining tasks o do to be fully harmonized with Jboss Tools > ensure Fuse Tools team knows where the devdocs are and has read them > -------------------------------------------------------------------- > > Key: JBIDE-24767 > URL: https://issues.jboss.org/browse/JBIDE-24767 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.Final > > > Aurelien asked:{quote}Also, does someone from Fuse Tooling took time to read the full JBoss Tools dev doc to ensure that we are on the same page? > {quote} > So here's a list of some useful docs: > * 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... > More: > > * https://github.com/jbosstools/jbosstools-devdoc/blob/master/README.adoc -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24592) Study Foreman documentation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24592?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24592: --------------------------------------- I think that this one can do: https://github.com/kireevco/wimaging Especially this points are interesting in our case: * No extra servers like WDS needed - all relevant settings can be configured in Foreman directly * Optional local user creation * Correctly report finished host building I will give it a try. See if it works for our case (windows bare metal provisioning, setting up user, connects to jenkins, etc...) > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci > Fix For: 4.5.0.Final > > > This issue consists of going through foreman documentation, tutorials and manuals. > Afterwards, it could be possible to address another steps in this process. > Docs: > https://www.theforeman.org/manuals/1.15/index.html > https://beryju.org/en/blog/getting-started-foreman-part-1#install_os > http://projects.theforeman.org/issues/432 > https://groups.google.com/forum/#!topic/foreman-users/FP9uTb8TAFY -- 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