Improve publishing and sharing of pure JS modules/libraries

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4, Blue Ocean 1.1, Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.3, Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2

      Publishing of npm modules like core-js and jdl is error prone. 

      This could be automated away via tooling, or an alternative mavenised way of delivering shared should be invested in to speed up development and improve sharing of code. 

      Impacts on extensibility and plugin development. 

       

      cc cliffmeyers kzantow if there are always going to be pure JS modules, then perhaps we should split this in 2 - one for modularity/shared code and one for better publishing of vanilla npm modules - thoughts? 

            Assignee:
            Keith Zantow
            Reporter:
            Michael Neale
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: