January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21456) Remove central themes plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21456?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21456: ---------------------------------------- FYI, the theme was much improved for GTK. For windows and osx, there is not much I can do. It seems like the theme needs to match some OSX patterns that I'm not aware of. Working on good themes for Win and osx could be part of a workshop with other interested parties in our next meeting. > Remove central themes plugin > ---------------------------- > > Key: JBIDE-21456 > URL: https://issues.jboss.org/browse/JBIDE-21456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > > The central themes are not used nor have received any updates for 3+ years. > I suggest we remove them. > Reason I noticed them was I noticed we have weird packages in https://github.com/jbosstools/jbosstools-central/tree/master/central/plug.... > There is probably a reason why but since we don't even use or update the themes why don't > we just remove them ? > [~mickael_istria] any comments ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21050) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21050?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21050: ---------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.4.x) > webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar > ---------------------------------------------------------------------------------- > > Key: JBIDE-21050 > URL: https://issues.jboss.org/browse/JBIDE-21050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Rob Stryker > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.3.1.Beta2 > > > WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules. > The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later. > The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb. > See also: https://issues.jboss.org/browse/JBIDE-20802 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21050) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21050?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21050: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.Beta2) > webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar > ---------------------------------------------------------------------------------- > > Key: JBIDE-21050 > URL: https://issues.jboss.org/browse/JBIDE-21050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Rob Stryker > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.4.x > > > WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules. > The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later. > The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb. > See also: https://issues.jboss.org/browse/JBIDE-20802 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21050) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21050?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21050: --------------------------------------- [~rob.stryker], The PR does not break the build but I can't see how it makes the endpoints usable in the Launchbar. Can you provide me with more information on how to "run" a JAX-RS endpoint in there ? > webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar > ---------------------------------------------------------------------------------- > > Key: JBIDE-21050 > URL: https://issues.jboss.org/browse/JBIDE-21050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Rob Stryker > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.3.1.Beta2 > > > WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules. > The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later. > The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb. > See also: https://issues.jboss.org/browse/JBIDE-20802 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21456) Remove central themes plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21456?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21456: --------------------------------------------- I don't think having a different color scheme helps devstudio, we should rather spend time improving the colorschemes/styles upstream to the benefit of everyone. > Remove central themes plugin > ---------------------------- > > Key: JBIDE-21456 > URL: https://issues.jboss.org/browse/JBIDE-21456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > > The central themes are not used nor have received any updates for 3+ years. > I suggest we remove them. > Reason I noticed them was I noticed we have weird packages in https://github.com/jbosstools/jbosstools-central/tree/master/central/plug.... > There is probably a reason why but since we don't even use or update the themes why don't > we just remove them ? > [~mickael_istria] any comments ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21456) Remove central themes plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21456?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21456: ---------------------------------------- No comments. I don't really care. Themes can be a good opportunity for branding JBDS, but it seems like using those is not something we are really interested in. > Remove central themes plugin > ---------------------------- > > Key: JBIDE-21456 > URL: https://issues.jboss.org/browse/JBIDE-21456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > > The central themes are not used nor have received any updates for 3+ years. > I suggest we remove them. > Reason I noticed them was I noticed we have weird packages in https://github.com/jbosstools/jbosstools-central/tree/master/central/plug.... > There is probably a reason why but since we don't even use or update the themes why don't > we just remove them ? > [~mickael_istria] any comments ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21456) Remove central themes plugin

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-21456: ------------------------------------------- Summary: Remove central themes plugin Key: JBIDE-21456 URL: https://issues.jboss.org/browse/JBIDE-21456 Project: Tools (JBoss Tools) Issue Type: Task Components: central Reporter: Max Rydahl Andersen The central themes are not used nor have received any updates for 3+ years. I suggest we remove them. Reason I noticed them was I noticed we have weird packages in https://github.com/jbosstools/jbosstools-central/tree/master/central/plug.... There is probably a reason why but since we don't even use or update the themes why don't we just remove them ? [~mickael_istria] any comments ? -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3557: ------------------------------------------- About central/plugins/org.jboss.tools.central.themes - we don't or at least should not be using that anywhere anymore but I took a look and did not see any issues since it is *dual* licensed under LGPL and GPL and we are fine using LGPL. There are other issues in this though - i.e. why do we have net.jeeyul.eclipse.themes.rendering packages in our code base. But that is a seperate issue. > 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 > 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, 5 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3557: ------------------------------------------- About changing existing content we've copied/derived then no, we do not want to change nor can we (in most cases) change the license. If the license is problematic we need to get it relicensed by the original authors or remove the code. But again, afaics [~nickboldt] are hunting inside the code of what the installer installs (our plugins) not the installer - hence it is separate issue than this. [~nickboldt] in other words, if you find code you believe is inproperly licensed and not okey to use outside the installer please put that in a separate jira. > 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 > 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, 5 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3557: ------------------------------------------- [~nickboldt] please stop searching for things *outside* the installer to change to EPL. This is *only* about the installer itself, not what is delivered *via* the installer. License info *inside* plugin features is about the license of our plugins *NOT* about the license of the installer. > 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 > 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, 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