-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHAR: ComposerFilesParser.php searches for composer.(json|lock) inside the phar #1229
Comments
This kind of begs the question, what should be the |
Did you @patrickkusebauch or @dbrumann discussed, what deptrac sees as its
In the code I have seen Parameters for The documentations says: * `%currentWorkingDirectory%` The path Deptrac runs in
* `%projectDirectory%` The path where the configuration is stored.
But what I see in the code is: if (false === ($currentWorkingDirectory = getcwd())) {
throw CannotGetCurrentWorkingDirectoryException::cannotGetCWD();
}
....
$factory = new ServiceContainerBuilder($currentWorkingDirectory); public function build(): ContainerBuilder
{
$container = new ContainerBuilder();
$container->setParameter('currentWorkingDirectory', $this->workingDirectory);
self::registerCompilerPasses($container);
self::loadServices($container, $this->cacheFile);
$container->registerExtension(new DeptracExtension());
$container->setParameter('projectDirectory', $this->workingDirectory);
if (null !== $this->configFile) {
self::loadConfiguration($container, $this->configFile);
}
$container->compile(true);
return $container;
} I could work on this problem as soon as I understand the |
Nope, we didn't. |
I would say, relative to the |
$ ./deptrac.phar -c ../deptrac.yaml Warning: file_get_contents(composer.lock): Failed to open stream: No such file or directory in phar:///var/www/deptrac/tmp/deptrac.phar/src/Core/Layer/Collector/ComposerFilesParser.php on line 37 [ERROR] Analysis finished with an Exception. Could not parse file. Could not parse composer files. Could not load composer.lock file
The text was updated successfully, but these errors were encountered: