Thomas Weinert

Handling the extension phars for a tool in a separate way would be the best solution. I am playing around with hardlinks for the phars at the moment, trying to...

I opened a merge request for it. However it might make sense to move some logic as options into the `PharActivator` implementations. Maybe something like: `$activator->activate($source, $destination, PharActivator::FORCE_COPY | PharActivator::EXECUTABLE);`...

After using it for I while I have some more feedback. It is possible to exclude/include single Phars in PHPStorm.  The Phar setup in PHPStorm is really convenient -...

Maybe not a flag, but an configuration option. Phive does not have that, so that would be a bigger change. Between two contributors of a project one could have Phive...

I was not speaking about code completion, but IDE integration. PHPStorm has plugins that integrate the tools, so that you can use them via GUI and internal functions. Currently Phive...

Maybe this is only needed on Windows. I don't get a local symlink. On windows the `tools` directory only includes bat files that call the Phar inside the local storage...

The file, PHPStorm seems to validate the file and extract the version.

Putting the *.phar files into the tools directory has the downside that an IDE might recognize it as part of the project code. But it will allow for IDE integration...

Yes, jasmine is a little special - it is always available in the tests. *afaik* Karma loads it. Adding an `import 'jasmine';` to the spec file results in dependency error:...

I got a step further by creating my own jasmine boot script and including it into `polyfill.ts`: ``` (function() { var jasmineRequire = require('jasmine-core/lib/jasmine-core/jasmine'); window.jasmine = jasmineRequire.core(jasmineRequire); var env =...