[jbosstools-issues] [JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse

Nick Boldt (JIRA) issues at jboss.org
Wed Jun 13 15:32:00 EDT 2018


    [ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591154#comment-13591154 ] 

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)


More information about the jbosstools-issues mailing list