jeff-aion
commented
5 years ago We can look into that but what is the problem? Which target? The build or the test? I wouldn't be surprised if how we are building or testing our stand-alone dist has picked up some kind of fileystem-level assumptions.
This was only intended to be a stop-gap until the Maven plugin was working. Now, the only reason to keep it alive is for some of the standalone CLI exploration cases, without having to develop a cyclic dependency on downstream tooling.
That said, we might end up making such a change and/or documenting manual build instructions to avoid possible confusion around this shell script (since we should ultimately deprecate and remove it).