-
-
Notifications
You must be signed in to change notification settings - Fork 21
project-info.json missing "authenticated" flag sometimes if dependency has already been fetched into local maven repository #5
Comments
Can confirm, for local dependencies that are not available online. |
Same here -- trying to build a project-info.json on a big project with no local repo is a bit painful. |
The workaround given above does indeed work: Could we change the title of this issue to something slightly more descriptive? e.g.
|
Unfortunately the workaround does not work for me. I've even tried deleting the default local Maven repository but have had no luck. I'd appreciate any help if someone knows what the problem is. ---EDIT--- I tested the workaround on my system with Maven 3.2.5 in addition to Maven 3.3.9, but am still getting the
|
This is causing trouble for me too |
I think this is just caused by this line being hidden behind |
The better solution though is probably just to amend the builder in nixpkgs to not assume it's there. Something like |
The workaround also doesn't work for exhibitor, as it has two modules in the top-level project, exhibitor-core and exhibitor-standalone, the latter of which depends on the former, and so it'll always be a local repo. |
@copumpkin Did you manage to experiment with fixing missing "authenticated" as you mentioned in June? |
I followed up with @copumpkin's suggestion of |
The `authenticated` attribute is not always present in the `project-info.json` produced by maven2nix[0] We therefore check for its presence, and default it to false. [0]: NixOS/mvn2nix-maven-plugin#5 (comment)
@ttuegel Is it dependencies of dependencies that have no e.g. |
My current workaround is to use the following one liner:
mvn -Dmaven.repo.local=
mktemp -d -t mavenorg.nixos.mvn2nix:mvn2nix-maven-plugin:mvn2nix
The text was updated successfully, but these errors were encountered: