January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2044: ---------------------------------- As this is described as optional, I've downgraded it. Also moved it from 8.x to 9.x/10.x so it's more on the current triage radar. > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Optional > Labels: discuss > Fix For: 9.x, 10.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Fix Version/s: 9.x 10.x (was: 8.x) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 9.x, 10.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2044: ----------------------------- Priority: Minor (was: Major) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Minor > Labels: discuss > Fix For: 9.x, 10.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20532) Allow a user to add volumes during deploy image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20532?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20532: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Allow a user to add volumes during deploy image wizard > ------------------------------------------------------ > > Key: JBIDE-20532 > URL: https://issues.jboss.org/browse/JBIDE-20532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.CR1 > > > Allow a user to add volumes when deploying an image. This will probably require expanding beyond emptydir volumes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21431) [OpenShift Explorer] Occasionally, ConnectionNotFoundExceptions are thrown

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21431?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21431. --------------------------------- Assignee: Andre Dietisheim Resolution: Done That should be fixed by now > [OpenShift Explorer] Occasionally, ConnectionNotFoundExceptions are thrown > -------------------------------------------------------------------------- > > Key: JBIDE-21431 > URL: https://issues.jboss.org/browse/JBIDE-21431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Occasionally, I haven't found a pattern yet, an exception is thrown when trying to access some of the resources in the openshift explorer. Simply click on a resource and boom : > {noformat} > org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named tac > at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41) > at org.jboss.tools.openshift.internal.core.WatchManager.startWatch(WatchManager.java:71) > at org.jboss.tools.openshift.internal.core.WatchManager.startWatch(WatchManager.java:66) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:187) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified in the image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21452: ---------------------------------------- Assignee: Andre Dietisheim > Server Adapter wizard: Should use deployments-dir as specified in the image > --------------------------------------------------------------------------- > > Key: JBIDE-21452 > URL: https://issues.jboss.org/browse/JBIDE-21452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta2 > > > The server adapter is currently using a hard-coded deployments dir */op/app-root/src* that the user can manually edit in the wizard though. > The images now specify the deployments-dir in a label (see CLOUD-243) > {code} > com.redhat.deployments-dir > {code} > We should use this instead of the hard-coded one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified in the image

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21452: ---------------------------------------- Summary: Server Adapter wizard: Should use deployments-dir as specified in the image Key: JBIDE-21452 URL: https://issues.jboss.org/browse/JBIDE-21452 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim The server adapter is currently using a hard-coded deployments dir */op/app-root/src* that the user can manually edit in the wizard though. The images now specify the deployments-dir in a label (see CLOUD-243) {code} com.redhat.deployments-dir {code} We should use this instead of the hard-coded one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified in the image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21452: ------------------------------------- Fix Version/s: 4.3.1.Beta2 > Server Adapter wizard: Should use deployments-dir as specified in the image > --------------------------------------------------------------------------- > > Key: JBIDE-21452 > URL: https://issues.jboss.org/browse/JBIDE-21452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Fix For: 4.3.1.Beta2 > > > The server adapter is currently using a hard-coded deployments dir */op/app-root/src* that the user can manually edit in the wizard though. > The images now specify the deployments-dir in a label (see CLOUD-243) > {code} > com.redhat.deployments-dir > {code} > We should use this instead of the hard-coded one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3557) JBDS Installer should be EPL licensed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3557 at 1/14/16 11:05 AM: ------------------------------------------------------------ To Denis' point... should we include updated/revised software license terms in the EULA in the installer [1] ? [1] http://www.redhat.com/f/pdf/licenses/GLOBAL_EULA_JBoss_English_20101110.pdf Currently, the EULA mentions LGPL 2.1, but no mention of ASL or EPL: {quote} 1. License Grant. Subject to the following terms, Red Hat, Inc. (“Red Hat”) grants to you a perpetual, worldwide license to the Programs (each of which may include multiple software components) pursuant to the GNU Lesser General Public License v. 2.1. With the exception of certain image files identified in Section 2 below, each software component is governed by a license that permits you to run, copy, modify, and redistribute (subject to certain obligations in some cases) the software component. This EULA pertains solely to the Programs and does not limit your rights under, or grant you rights that supersede, the license terms applicable to any particular component. {quote} was (Author: nickboldt): To Denis' point... should we include software license terms in the EULA in the installer [1] ? [1] http://www.redhat.com/f/pdf/licenses/GLOBAL_EULA_JBoss_English_20101110.pdf > JBDS Installer should be EPL licensed > ------------------------------------- > > Key: JBDS-3557 > URL: https://issues.jboss.org/browse/JBDS-3557 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer, legal > Reporter: Ken Finnigan > Assignee: Nick Boldt > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21431) [OpenShift Explorer] Occasionally, ConnectionNotFoundExceptions are thrown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21431?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21431: ------------------------------------------ [~fbricon] with my fix in JBIDE-21433 I expect this to be resolved. > [OpenShift Explorer] Occasionally, ConnectionNotFoundExceptions are thrown > -------------------------------------------------------------------------- > > Key: JBIDE-21431 > URL: https://issues.jboss.org/browse/JBIDE-21431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Occasionally, I haven't found a pattern yet, an exception is thrown when trying to access some of the resources in the openshift explorer. Simply click on a resource and boom : > {noformat} > org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named tac > at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41) > at org.jboss.tools.openshift.internal.core.WatchManager.startWatch(WatchManager.java:71) > at org.jboss.tools.openshift.internal.core.WatchManager.startWatch(WatchManager.java:66) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:187) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > {noformat} -- 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 January 2016