February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3590: ----------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/363, https://github.com/jbdevstudio/jbdevstudio-product/pull/364 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/363) > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL?{quote} > Richard Fontana replied:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Thus, we should add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3590 at 2/3/16 2:45 PM: ---------------------------------------------------------- PR to add LICENSE to 4.3.x & master branch installers: https://github.com/jbdevstudio/jbdevstudio-product/pull/363 https://github.com/jbdevstudio/jbdevstudio-product/pull/364 Also does some additional refactoring/cleanup and adds composite*.xml files to the root of the installer so that the jar once again works like an update site zip (JBDS-3589). was (Author: nickboldt): PR to add LICENSE to 4.3.x branch installers: https://github.com/jbdevstudio/jbdevstudio-product/pull/363 Also does some additional refactoring/cleanup and adds composite*.xml files to the root of the installer so that the jar once again works like an update site zip (JBDS-3589). > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL?{quote} > Richard Fontana replied:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Thus, we should add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3590 at 2/3/16 2:42 PM: ---------------------------------------------------------- PR to add LICENSE to 4.3.x branch installers: https://github.com/jbdevstudio/jbdevstudio-product/pull/363 Also does some additional refactoring/cleanup and adds composite*.xml files to the root of the installer so that the jar once again works like an update site zip (JBDS-3589). was (Author: nickboldt): PR to add LICENSE to 4.3.x branch installers: https://github.com/jbdevstudio/jbdevstudio-product/pull/363 Also does some additional refactoring/cleanup and adds composite*.xml files to the root of the installer so that the jar once again works like an update site zip. > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL?{quote} > Richard Fontana replied:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Thus, we should add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 resolved JBDS-3557. ------------------------------ Fix Version/s: 9.1.0.Beta2 (was: 9.1.0.CR1) Resolution: Done Max requested that we move the addition of a LICENSE file to the installer jars into a separate JIRA. Thus: https://issues.jboss.org/browse/JBDS-3590 Resolving for 9.1.0.Beta2 > 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: 10.0.0.Alpha1, 9.1.0.Beta2 > > > For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL > Sources code in repository ether has Apache Licence or no license. > IzPack distribution jar's and licenses: > 1. kunstoff Look and Feel is under LGPL http://kunstoff.incors.com/archive/licence.php3 > 2. Birosoft Liquid Look and Feel > The source code (except the files or methods mentioned below) of the look and feel is released under the LGPL (GNU Lesser General Public License), > which you can view on http://www.gnu.org/copyleft/lesser.html. > Some methods are marked as SUN proprietary, the LGPL does not apply for those methods. > 3. JGoodies Karsten Lentzsch - BSD open source license http://www.jgoodies.com/downloads/libraries/ > 4. Metouia Look And Feel: a free pluggable look and feel for java - LGPLv2.1 http://grepcode.com/file/repo1.maven.org/maven2/net.sf.squirrel-sql.third... > 5. Nimbus Look And Feel > This library is free software; you can redistribute it and/or > * modify it under the terms of the GNU Lesser General Public > * License as published by the Free Software Foundation; either > * version 2.1 of the License, or (at your option) any later version. > 6. Substance Java Look and Feel (bundles several components with licenses listed below) > 6.1 Copyright (c) 2005-2007, Kirill Grouchnikov and contributors > All rights reserved. > Redistribution and use in source and binary forms, with or without > modification, are permitted provided that the following conditions are met: > * Redistributions of source code must retain the above copyright > notice, this list of conditions and the following disclaimer. > * Redistributions in binary form must reproduce the above copyright > notice, this list of conditions and the following disclaimer in the > documentation and/or other materials provided with the distribution. > * Neither the name of the Kirill Grouchnikov and contributors nor > the names of its contributors may be used to endorse or promote products > derived from this software without specific prior written permission. > 6.2 Source code, documentation and binaries of the Quaqua Look and > Feel (also called "this software") are subject to the GNU Lesser > General Public License (LGPL). > 6.3. MOZILLA PUBLIC LICENSE Version 1.1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3590: ----------------------------- Story Points: 3 > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL? > Richard Fontana said:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3590: ----------------------------- Description: Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL?{quote} Richard Fontana replied:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} Thus, we should add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. was: Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL? Richard Fontana said:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} Add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL?{quote} > Richard Fontana replied:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Thus, we should add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3590: ----------------------------- Description: Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL? Richard Fontana said:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} Add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. was:Add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL? > Richard Fontana said:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3590: -------------------------------- Summary: add LICENSE file to root of installer jars Key: JBDS-3590 URL: https://issues.jboss.org/browse/JBDS-3590 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: build, installer Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21436) Pod tab should display all pods associated with a deployment

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21436?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21436. --------------------------------- Assignee: Jeff Cantrill Resolution: Done I can see build pods in the pods tab now. Marking as resolved > Pod tab should display all pods associated with a deployment > ------------------------------------------------------------ > > Key: JBIDE-21436 > URL: https://issues.jboss.org/browse/JBIDE-21436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > Selecting a deployed app in the deployment view of the explorer should only display the deployed pods, but the pods tab should also include any other pods associated with the deployment (e.g. build pods, deployer pods) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21624) Add Deploy menu to deployment configs

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21624?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21624: ---------------------------------- Git Pull Request: https://github.com/openshift/openshift-restclient-java/pull/110, https://github.com/jbosstools/jbosstools-openshift/pull/945 (was: https://github.com/openshift/openshift-restclient-java/pull/110) > Add Deploy menu to deployment configs > ------------------------------------- > > Key: JBIDE-21624 > URL: https://issues.jboss.org/browse/JBIDE-21624 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > We currently cannot trigger a deployment of a Deployment Config, like in the webconsole. Hopefully it should be trivial to implement. > * Add context menu in tabs for deploymentconfigs of deployment > * Add context menu to explorer view when selecting deployment (service) > * * There should be only one dc, but choose the one with the latest created timestamp if more than 1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016