June 2017 - jbosstools-issues - Jboss List Archives

[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 updated JBIDE-24592: ---------------------------------- Labels: cdk central-ci (was: ) > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci > Fix For: 4.5.0.AM2 > > > 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, 9 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 updated JBIDE-24592: ---------------------------------- Component/s: integration-tests > 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.AM2 > > > 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, 9 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 updated JBIDE-24592: ---------------------------------- Component/s: integration-tests > 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 > Fix For: 4.5.0.AM2 > > > 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, 9 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 updated JBIDE-24592: ---------------------------------- Component/s: (was: integration-tests) > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.5.0.AM2 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22199) N&N for Betas are not aggregated into *.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22199?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22199. ------------------------------ Fix Version/s: 4.3.1.Final (was: 4.5.x) Resolution: Done Closing for 4.3.1.Final. Clearly the additional enhancement is not desired. > N&N for Betas are not aggregated into *.Final > --------------------------------------------- > > Key: JBIDE-22199 > URL: https://issues.jboss.org/browse/JBIDE-22199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.1.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.1.Final > > > As discussed yesterday on hipchat, this doesn't work as expected. > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html > should contain new features for cr1/final as well as relevant features from Beta1 and Beta2: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.html > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta2.html > Xavier said it doesn't work because there is no item in the releases yaml, but it was suggested to try and create an empty item as a workaround. Whether or not this has been done I don't know - I don't see any such commit in the repo. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24184: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.Final) > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24222: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.Final) > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: help_wanted > Fix For: 4.5.0.AM2 > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12452) Add support for creating and auto-discovering JBoss AS "user instances"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12452?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12452: -------------------------------- Labels: help_wanted (was: ) > Add support for creating and auto-discovering JBoss AS "user instances" > ----------------------------------------------------------------------- > > Key: JBIDE-12452 > URL: https://issues.jboss.org/browse/JBIDE-12452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.1.Final > Environment: Fedora 17 and above > Fedora JBoss AS package (jboss-as) > Reporter: Dan Allen > Assignee: Rob Stryker > Labels: help_wanted > Fix For: LATER > > > The Fedora JBoss AS package supports creating user instances of JBoss AS. A user instance allows an unprivileged user to run JBoss AS out of that user's home directory. An instance is created using the jboss-as-cp script. For example: > {code} > jboss-as-cp -l $HOME/applications/jboss-as-user-instance > {code} > The user instance is skinny, meaning it only contains the configuration files for the instance. The libraries are kept in the system instance and referenced by the custom startup script: > {code} > JBOSS_BASE_DIR=$HOME/applications/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml > {code} > JBoss Tools does not currently auto-detect these instances. However, it could offer to create and/or auto-discover them. > It's possible to get JBoss Tools to control the user instance, but it requires tweaking the startup flags in the server configuration. Here's how: > 1. Have JBoss AS auto-discover the system instance at /usr/share/java > 2. Open the server launch configuration > 3. Uncheck the box "Always update arguments related to the runtime" so our changes don't get overwritten > 4. Replace the VM arguments that contain "jboss" with: > -Dorg.jboss.boot.log.file=${env_var:HOME}/applications/jboss-as-user-instance/log/boot.log -Dlogging.configuration=file:${env_var:HOME}/applications/jboss-as-user-instance/configuration/logging.properties -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=${env_var:HOME}/applications/jboss-as-user-instance > Having native support for JBoss AS to auto-detect and configure user instances would be ideal. > If changes are required in the jboss-as-cp script, please use this issue tracker: https://bugzilla.redhat.com/buglist.cgi?component=jboss-as&product=Fedora... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12452) Add support for creating and auto-discovering JBoss AS "user instances"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12452?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12452: ------------------------------------- Comment from Marek: You should probably look for "wildfly-cp". Saying this - I'm not sure what's the status of this package, I stepped out as a maintainer about a year ago. It's now community maintained and from what I see - it's not in a great state :) But the "cp" script is there for sure: http://pkgs.fedoraproject.org/cgit/rpms/wildfly.git/tree/wildfly-cp.sh --- To note, I didn't see this script anywhere I looked :| > Add support for creating and auto-discovering JBoss AS "user instances" > ----------------------------------------------------------------------- > > Key: JBIDE-12452 > URL: https://issues.jboss.org/browse/JBIDE-12452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.1.Final > Environment: Fedora 17 and above > Fedora JBoss AS package (jboss-as) > Reporter: Dan Allen > Assignee: Rob Stryker > Labels: help_wanted > Fix For: LATER > > > The Fedora JBoss AS package supports creating user instances of JBoss AS. A user instance allows an unprivileged user to run JBoss AS out of that user's home directory. An instance is created using the jboss-as-cp script. For example: > {code} > jboss-as-cp -l $HOME/applications/jboss-as-user-instance > {code} > The user instance is skinny, meaning it only contains the configuration files for the instance. The libraries are kept in the system instance and referenced by the custom startup script: > {code} > JBOSS_BASE_DIR=$HOME/applications/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml > {code} > JBoss Tools does not currently auto-detect these instances. However, it could offer to create and/or auto-discover them. > It's possible to get JBoss Tools to control the user instance, but it requires tweaking the startup flags in the server configuration. Here's how: > 1. Have JBoss AS auto-discover the system instance at /usr/share/java > 2. Open the server launch configuration > 3. Uncheck the box "Always update arguments related to the runtime" so our changes don't get overwritten > 4. Replace the VM arguments that contain "jboss" with: > -Dorg.jboss.boot.log.file=${env_var:HOME}/applications/jboss-as-user-instance/log/boot.log -Dlogging.configuration=file:${env_var:HOME}/applications/jboss-as-user-instance/configuration/logging.properties -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=${env_var:HOME}/applications/jboss-as-user-instance > Having native support for JBoss AS to auto-detect and configure user instances would be ideal. > If changes are required in the jboss-as-cp script, please use this issue tracker: https://bugzilla.redhat.com/buglist.cgi?component=jboss-as&product=Fedora... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12452) Add support for creating and auto-discovering JBoss AS "user instances"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12452?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12452: -------------------------------- Fix Version/s: LATER (was: 4.5.0.AM1) > Add support for creating and auto-discovering JBoss AS "user instances" > ----------------------------------------------------------------------- > > Key: JBIDE-12452 > URL: https://issues.jboss.org/browse/JBIDE-12452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.1.Final > Environment: Fedora 17 and above > Fedora JBoss AS package (jboss-as) > Reporter: Dan Allen > Assignee: Rob Stryker > Fix For: LATER > > > The Fedora JBoss AS package supports creating user instances of JBoss AS. A user instance allows an unprivileged user to run JBoss AS out of that user's home directory. An instance is created using the jboss-as-cp script. For example: > {code} > jboss-as-cp -l $HOME/applications/jboss-as-user-instance > {code} > The user instance is skinny, meaning it only contains the configuration files for the instance. The libraries are kept in the system instance and referenced by the custom startup script: > {code} > JBOSS_BASE_DIR=$HOME/applications/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml > {code} > JBoss Tools does not currently auto-detect these instances. However, it could offer to create and/or auto-discover them. > It's possible to get JBoss Tools to control the user instance, but it requires tweaking the startup flags in the server configuration. Here's how: > 1. Have JBoss AS auto-discover the system instance at /usr/share/java > 2. Open the server launch configuration > 3. Uncheck the box "Always update arguments related to the runtime" so our changes don't get overwritten > 4. Replace the VM arguments that contain "jboss" with: > -Dorg.jboss.boot.log.file=${env_var:HOME}/applications/jboss-as-user-instance/log/boot.log -Dlogging.configuration=file:${env_var:HOME}/applications/jboss-as-user-instance/configuration/logging.properties -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=${env_var:HOME}/applications/jboss-as-user-instance > Having native support for JBoss AS to auto-detect and configure user instances would be ideal. > If changes are required in the jboss-as-cp script, please use this issue tracker: https://bugzilla.redhat.com/buglist.cgi?component=jboss-as&product=Fedora... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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