Github user xyztdanid4 commented on the issue:
https://github.com/apache/metron/pull/952
@merrimanr
As we agreed yesterday I did the required changes in the pom xml-s.
I had to update the node dependency of the projects, otherwise the build
was failed, cause one of the depende
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/952
I think we are on board with switching to yarn so no concerns there. There
was a discussion on it but if anyone now feels differently, speak up.
Sounds like we still have a lot of work to
Github user xyztdanid4 commented on the issue:
https://github.com/apache/metron/pull/952
@merrimanr
although it should work with npm as well, cause then it will use the
package.json to install the dependencies.
---
Github user xyztdanid4 commented on the issue:
https://github.com/apache/metron/pull/952
@merrimanr
Yes this is the right way to switch to yarn.
Yes we have install yarn locally.
I did not know that we have so much dependency on npm. But for me it was
hard to add new depen
Github user xyztdanid4 commented on the issue:
https://github.com/apache/metron/pull/952
@merrimanr
---
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/952
I'm having trouble understanding what this PR actually does. I see that
package-lock.json was removed and yarn.lock was added. Is that all that's
needed to switch to yarn? Do we need to also upd
Github user xyztdanid4 commented on the issue:
https://github.com/apache/metron/pull/952
@simonellistonball I am not sure. Probably no.
---
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/952
Have the dependencies, License and Notices files been updated?
---
