RestfulBlue opened a new issue #7312: [PROPOSAL] Windows build
URL: https://github.com/apache/incubator-druid/issues/7312
 
 
   ### Description
   
   Currently druid cannot be builded under windows. Previously 0.12.3 was 
building fine(even debugging was fine), but currently where are many problems 
with druid-console. 
   At first it uses bash scripts, and looks like they can be replaced in follow 
way : 
   1) replace clean script with maven clean plugin
   2) replace cp-to script with maven resources plugin
   3) replace build script with webpack. At first it copies old druid-console. 
Its also can be done with maven plugin. But i dont understand what is happening 
after it. It looks like its importing css using script ._.
   ```
   sed 's|url("assets|url("/assets|g' 
"./node_modules/@blueprintjs/core/dist/blueprint.css" > lib/blueprint.css
   ```
   is there any issues doing it using webpack?
   something like 
   ```
   import '@blueprintjs/core/dist/blueprints.css!'
   ```
   
   At second, it uses maven frontend plugin. I think most of interprise 
companies uses some internal network and custom ssl keys. 
   This can be handled making another maven profile, which will build console 
using globally provided npm ( which is already configured to work in such 
environment) without node installation phase. This is not really windows 
problem. For example in our  isolated production environment npm/node is 
preconfigured and globally provided by jenkins
   
   if everything with changes described before is ok, i will try to make it
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to