[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26065:
-------------------------------
Description:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
[1] http://www.nodeclipse.org/updates/
[2] https://marketplace.eclipse.org/content/nodeclipse
!eclipse-marketplace-nodeclipse.png|thumbnail!
Installed size is about 111M for these features:
{code}
org.nodeclipse_1.0.2.201509250223
org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
org.nodeclipse.pluginslist.feature_1.0.2.201509250223
com.eclipsesource.jshint.feature_0.10.1.20160216-0911
de.bastiankrol.startexplorer.feature_1.7.0
gitaddon.feature_1.0.0.20140303-0606
markdown.editor.feature_1.2.0.201501260515
net.mihai-nita.ansicon_1.3.1.201508091828
pm.eclipse.editbox.feature_0.70.0.201508180438
org.chromium.debug_0.3.9.201509250223
org.chromium.sdk_0.3.9.201509250223
tern-feature_1.1.0.201511082254
tern-jsdt-feature_1.1.0.201511082254
tern-server-nodejs-feature_1.1.0.201511082254
{code}
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
PR to do mirror, if licenses are allowed:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
was:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
[1] http://www.nodeclipse.org/updates/
[2] https://marketplace.eclipse.org/content/nodeclipse
!eclipse-marketplace-nodeclipse.png|thumbnail!
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
PR to do mirror, if licenses are allowed:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
>
> [1] http://www.nodeclipse.org/updates/
> [2] https://marketplace.eclipse.org/content/nodeclipse
> !eclipse-marketplace-nodeclipse.png|thumbnail!
> Installed size is about 111M for these features:
> {code}
> org.nodeclipse_1.0.2.201509250223
> org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223
> org.nodeclipse.pluginslist.feature_1.0.2.201509250223
> com.eclipsesource.jshint.feature_0.10.1.20160216-0911
> de.bastiankrol.startexplorer.feature_1.7.0
> gitaddon.feature_1.0.0.20140303-0606
> markdown.editor.feature_1.2.0.201501260515
> net.mihai-nita.ansicon_1.3.1.201508091828
> pm.eclipse.editbox.feature_0.70.0.201508180438
> org.chromium.debug_0.3.9.201509250223
> org.chromium.sdk_0.3.9.201509250223
> tern-feature_1.1.0.201511082254
> tern-jsdt-feature_1.1.0.201511082254
> tern-server-nodejs-feature_1.1.0.201511082254
> {code}
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26065:
-------------------------------
Description:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
[1] http://www.nodeclipse.org/updates/
[2] https://marketplace.eclipse.org/content/nodeclipse
!eclipse-marketplace-nodeclipse.png|thumbnail!
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
PR to do mirror, if licenses are allowed:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
was:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
[1] http://www.nodeclipse.org/updates/
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
PR to do mirror, if licenses are allowed:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2].
>
> [1] http://www.nodeclipse.org/updates/
> [2] https://marketplace.eclipse.org/content/nodeclipse
> !eclipse-marketplace-nodeclipse.png|thumbnail!
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26065:
-------------------------------
Description:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
[1] http://www.nodeclipse.org/updates/
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
PR to do mirror, if licenses are allowed:
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
was:
Steps to perform:
a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
b) add that to the 3rd party target platform used for building RH Central
c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
[1] http://www.nodeclipse.org/updates/
If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
>
> [1] http://www.nodeclipse.org/updates/
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
> PR to do mirror, if licenses are allowed:
> https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26065 at 6/13/18 3:31 PM:
-------------------------------------------------------------
Based on the list of features on Eclipse Marketplace [0], here are the licenses to review to decide if we can safely redistribute this via a mirror on devstudio.redhat.com and download.jboss.org, or else simply link to the upstream update site (as we do for JRebel) [1].
!eclipse-marketplace-nodeclipse.png|thumbnail!
!node-license-agreements.png|thumbnail!
[0] https://marketplace.eclipse.org/content/nodeclipse
[1] http://update.zeroturnaround.com/update-site-jboss/
* [^license-node-jshint-eclipse-license-unknown.txt]
* [^license-node-markdown-editor-EPL-version-unknown.txt]
* [^license-node-chromium.txt]
* [^license-nodepluginslist-paul-verest.txt]
* [^license-node-asl2.txt]
I believe we are safe with the EPL v1 and v2 stuff, plus the Apache License 2.0 stuff. And the MIT License is safe too, I think, but I haven't seen that one in ages so I'd need someone to confirm that as IANAL. :D
The ones that worry me are the other ones, linked above.
[~fontana] can you comment?
was (Author: nickboldt):
Based on the list of features on Eclipse Marketplace [0], here are the licenses to review to decide if we can safely redistribute this via a mirror on devstudio.redhat.com and download.jboss.org, or else simply link to the upstream update site (as we do for JRebel) [1].
!eclipse-marketplace-nodeclipse.png|thumbnail!
!node-license-agreements.png|thumbnail!
[0] https://marketplace.eclipse.org/content/nodeclipse
[1] http://update.zeroturnaround.com/update-site-jboss/
* [^license-node-jshint-eclipse-license-unknown.txt]
* [^license-node-markdown-editor-EPL-version-unknown.txt]
* [^license-node-chromium.txt]
* [^license-nodepluginslist-paul-verest.txt]
* [^license-node-asl2.txt]
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
>
> [1] http://www.nodeclipse.org/updates/
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26096) Modify API so debugging details can be returned from startServerAsync()
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26096?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-26096.
---------------------------------
Fix Version/s: 4.6.0.Final
Resolution: Done
0e0d5eb - (HEAD -> master, mine/master) JBIDE-26096 - update API to get debugging info so client can connect debugger (29 seconds ago) <Rob Stryker>
> Modify API so debugging details can be returned from startServerAsync()
> -----------------------------------------------------------------------
>
> Key: JBIDE-26096
> URL: https://issues.jboss.org/browse/JBIDE-26096
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.Final
>
>
> Modify the API so that a call to startServerAsync() can properly return debugging details, such as what host and port a debugger should connect to, and what type of debugger should be used.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26065:
-------------------------------
Attachment: eclipse-marketplace-nodeclipse.png
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
>
> [1] http://www.nodeclipse.org/updates/
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26096) Modify API so debugging details can be returned from startServerAsync()
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-26096:
-----------------------------------
Summary: Modify API so debugging details can be returned from startServerAsync()
Key: JBIDE-26096
URL: https://issues.jboss.org/browse/JBIDE-26096
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: stack-server-protocol
Affects Versions: 4.6.0.AM2
Reporter: Rob Stryker
Modify the API so that a call to startServerAsync() can properly return debugging details, such as what host and port a debugger should connect to, and what type of debugger should be used.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26065:
------------------------------------
Based on the list of features on Eclipse Marketplace [0], here are the licenses to review to decide if we can safely redistribute this via a mirror on devstudio.redhat.com and download.jboss.org, or else simply link to the upstream update site (as we do for JRebel) [1].
!eclipse-marketplace-nodeclipse.png|thumbnail!
!node-license-agreements.png|thumbnail!
[0] https://marketplace.eclipse.org/content/nodeclipse
[1] http://update.zeroturnaround.com/update-site-jboss/
* [^license-node-jshint-eclipse-license-unknown.txt]
* [^license-node-markdown-editor-EPL-version-unknown.txt]
* [^license-node-chromium.txt]
* [^license-nodepluginslist-paul-verest.txt]
* [^license-node-asl2.txt]
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
>
> [1] http://www.nodeclipse.org/updates/
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26065:
-------------------------------
Attachment: node-license-agreements.png
license-node-jshint-eclipse-license-unknown.txt
license-node-markdown-editor-EPL-version-unknown.txt
license-node-chromium.txt
license-nodepluginslist-paul-verest.txt
license-node-asl2.txt
> Add RH Central connector for nodeclipse
> ---------------------------------------
>
> Key: JBIDE-26065
> URL: https://issues.jboss.org/browse/JBIDE-26065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, central-update, updatesite, upstream
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
> Attachments: license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png
>
>
> Steps to perform:
> a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability
> b) add that to the 3rd party target platform used for building RH Central
> c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools*
> The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse.
>
> [1] http://www.nodeclipse.org/updates/
> If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months