October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ] David Hladky commented on JBDS-3547: ------------------------------------ If you click on the [http://tools.jboss.org/downloads/devstudio/mars/9.0.0.GA.html|http://tool...] link and hower above the download links (any version), all the link start with the Eloqua server [http://www.redhat.com/j/elqNow/elqRedir.htm?ref=....] and the reference goes to the Download manager. The correct version should be just the Download manager link (the four dots from my example). > Eloqua tracking of Eloqua tracked links > --------------------------------------- > > Key: JBDS-3547 > URL: https://issues.jboss.org/browse/JBDS-3547 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 9.0.0.GA > Reporter: David Hladky > > I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice. > I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20737: --------------------------------------- For the record, this article might help: http://www.projectatomic.io/blog/2015/08/why-we-dont-let-non-root-users-r... > On Linux, non-root user us not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 10/22/15 9:38 PM: -------------------------------------------------------------- [~akazakov] Could we just close this and open a new issue if there's further devdoc needed? Figure if after 2 weeks there's been no feedback on my work, it must be good... right? :D was (Author: nickboldt): [~akazakov] Could we just close this and open a new issue if there's further devdoc needed? > 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, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.x > > > 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.4.11#64026)

10 years, 5 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 commented on JBIDE-18820: ------------------------------------ [~akazakov] Could we just close this and open a new issue if there's further devdoc needed? > 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, devdoc > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Labels: devdoc > Fix For: 4.3.x > > > 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.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20737: -------------------------------------- Assignee: Xavier Coulon (was: Misha Ali) The blog and documentation have been updated. Assigning to [~xcoulon] to see what else we can do. > On Linux, non-root user us not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20737: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > On Linux, non-root user us not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19765) Add description to easy import wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19765?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19765: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Add description to easy import wizard > ------------------------------------- > > Key: JBIDE-19765 > URL: https://issues.jboss.org/browse/JBIDE-19765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > Attachments: wizard.png > > > There is no descrption of the wizard (see picture attached). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19768: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.Beta1) > Add possibility to select which nested projects to import > --------------------------------------------------------- > > Key: JBIDE-19768 > URL: https://issues.jboss.org/browse/JBIDE-19768 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Final, 4.4.0.Alpha1 > > > At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import. > Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20765: ----------------------------------- Component/s: central > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, discovery > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20765: ----------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, discovery > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 October 2015