[ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT #1040

vorburger · 2025-02-05T20:51:44Z

Recent PRs, including my "manual" #1039 as well as all dependabot & renovate PRs in the last 5 days, fail due to:

[INFO] Installing /home/runner/work/enola/enola/bazel-bin/java/dev/enola/enola-project.jar to /home/runner/.m2/repository/dev/enola/enola/0.0.1-SNAPSHOT/enola-0.0.1-SNAPSHOT.jar
[INFO] Installing /home/runner/work/enola/enola/bazel-bin/java/dev/enola/enola-pom.xml to /home/runner/.m2/repository/dev/enola/enola/0.0.1-SNAPSHOT/enola-0.0.1-SNAPSHOT.pom
[INFO] Installing /home/runner/work/enola/enola/bazel-bin/java/dev/enola/enola-project-src.jar to /home/runner/.m2/repository/dev/enola/enola/0.0.1-SNAPSHOT/enola-0.0.1-SNAPSHOT-sources.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.823 s
[INFO] Finished at: 2025-02-01T04:45:18Z
[INFO] ------------------------------------------------------------------------
+ learn/jbang/jbang learn/jbang/hello.java
Downloading JBang ...
Installing JBang...
[jbang] Resolving dependencies...
[jbang]    dev.enola:enola:0.0.1-SNAPSHOT
Error:  [ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT
[jbang] Run with --verbose for more details. The --verbose must be placed before the jbang command. I.e. jbang --verbose run [...]
Error: Process completed with exit code 1.

This used to work just fine, until a few days ago.

@maxandersen my hunch here is that https://github.com/jbangdev/jbang/releases/tag/v0.123.0 might be the culprit which broke this, somehow; and v0.122.0 from Dec 16, 2024 still worked... but for now that's just that, a hunch. I'll try to see if I can reliably reproduce this, before & after, and if so, update here.

PS: There is actually really 2 separate issues here:

(a) the fact that JBang is an "unstable" build time dependency of this project - I don't want ANYTHING external to EVER "just change by itself" (and I'm doing this by fixing versions for many other tools) - so one part of resolving this problem is to "pin" the JBang, somehow... @maxandersen any suggestions for how folks do this is very welcome! Maybe it would be cool if there was a .jbangversion tag file?

(b) fixing the actual problem

The text was updated successfully, but these errors were encountered:

vorburger · 2025-02-05T21:02:47Z

to "pin" the JBang, somehow...

This is a pretty ugly hack, but could do, for now:

$ rm -f ~/.jbang/bin/jbang.jar && JBANG_DOWNLOAD_VERSION=0.123.0 learn/jbang/jbang --version
Downloading JBang 0.123.0...
Installing JBang...
0.123.0

$ rm -f ~/.jbang/bin/jbang.jar && JBANG_DOWNLOAD_VERSION=0.122.0 learn/jbang/jbang --version
Downloading JBang 0.122.0...
Installing JBang...
0.122.0

my hunch here is that v0.123.0 might be the culprit which broke this, somehow; and v0.122.0 from Dec 16, 2024 still worked...

I cannot seem to reproduce this, it appears to work with both:

$ rm -f ~/.jbang/bin/jbang.jar && JBANG_DOWNLOAD_VERSION=0.123.0 learn/jbang/jbang learn/jbang/hello.java
Downloading JBang 0.123.0...
Installing JBang...
Hello World: DEVELOPMENT

$ rm -f ~/.jbang/bin/jbang.jar && JBANG_DOWNLOAD_VERSION=0.122.0 learn/jbang/jbang learn/jbang/hello.java
Downloading JBang 0.122.0...
Installing JBang...
Hello World: DEVELOPMENT

vorburger · 2025-02-05T21:10:29Z

Ah no, I now actually CAN reproduce it, like this:

$ rm -rf ~/.jbang/ && JBANG_DOWNLOAD_VERSION=0.122.0 learn/jbang/jbang learn/jbang/hello.java
Downloading JBang 0.122.0...
Installing JBang...
[jbang] Resolving dependencies...
[jbang]    dev.enola:enola:0.0.1-SNAPSHOT
[jbang] Dependencies resolved
[jbang] Building jar for hello.java...
Note: /home/vorburger/git/github.com/enola-dev/enola/learn/jbang/hello.java uses preview features of Java SE 21.
Note: Recompile with -Xlint:preview for details.
Hello World: DEVELOPMENT

$  rm -rf ~/.jbang/ && JBANG_DOWNLOAD_VERSION=0.123.0 learn/jbang/jbang learn/jbang/hello.java
Downloading JBang 0.123.0...
Installing JBang...
[jbang] Resolving dependencies...
[jbang]    dev.enola:enola:0.0.1-SNAPSHOT
[jbang] [ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT
[jbang] Run with --verbose for more details. The --verbose must be placed before the jbang command. I.e. jbang --verbose run [...]

Perhaps the Maven resolution in JBang 0.123.0 just got stricter than it used to be in 0.122.0... but I guess the //REPOS mavencentral,jitpack here is kinda wrong, because I want it to find the //DEPS dev.enola:enola:0.0.1-SNAPSHOT in the local .m2/repository repo.

vorburger · 2025-02-05T21:15:49Z

guess the //REPOS mavencentral,jitpack here is kinda wrong, because I want it to find the //DEPS dev.enola:enola:0.0.1-SNAPSHOT in the local .m2/repository repo.

//REPOS local,mavencentral,jitpack

does not work - which perhaps isn't too shocking, because I "made up" (just tried) local - it's not documented on https://www.jbang.dev/documentation/guide/latest/dependencies.html#repositories.

… build (see enola-dev#1040)

vorburger · 2025-02-05T21:38:19Z

maxandersen/jbang@8af7329 for jbangdev/jbang#431 appears to have introduced a mavenLocal, but using //REPOS mavenlocal,mavenCentral,jitpack does not solve this problem (for me here). Which is maybe not surprising, given that it's not on JBang's current main.

… build (see enola-dev#1040)

quintesse · 2025-02-05T22:02:48Z

Would it be possible to run jbang with --verbose to see what the actual error is?

… build (see #1040)

vorburger · 2025-02-05T22:08:54Z

Merging #1042 "fixed" (worked around) the problem for this project for the short term.

I'm keeping this issue open to follow-up later for both jbangdev/jbang#431 & jbangdev/jbang#1921.

vorburger · 2025-02-05T22:22:55Z

Would it be possible to run jbang with --verbose to see what the actual error is?

@quintesse sure thing:

$ rm -rf ~/.jbang/ && JBANG_DOWNLOAD_VERSION=0.123.0 learn/jbang/jbang --verbose learn/jbang/hello.java
Downloading JBang 0.123.0...
Installing JBang...
[jbang] [0:284] jbang version 0.123.0
[jbang] [0:298] Resolving resource ref: learn/jbang/hello.java
[jbang] [0:301] Resolved resource ref as: learn/jbang/hello.java (cached as: /home/vorburger/git/github.com/enola-dev/enola/learn/jbang/hello.java)
[jbang] [0:341] Build required as /home/vorburger/.jbang/cache/jars/hello.java.090302c3cc5244467fd3d3a70a35c921664a098f574b1b80b224be60c070f7b4/hello.jar not readable or not found.
[jbang] [0:351] Looking for JDK: 21
[jbang] [0:358] Using JDK: 21 (21.0.6+7, current, /usr/lib/jvm/java-21-openjdk-21.0.6.0.7-1.fc41.x86_64)
[jbang] [0:359] Looking for JDK: 21
[jbang] [0:360] Using JDK: 21 (21.0.6+7, current, /usr/lib/jvm/java-21-openjdk-21.0.6.0.7-1.fc41.x86_64)
[jbang] [0:362] Resolving artifact(s): dev.enola:enola:0.0.1-SNAPSHOT
[jbang] [0:364] Repositories: mavencentral=https://repo1.maven.org/maven2/, jitpack=https://jitpack.io/
[jbang] [0:365] Resolving dependencies...
[jbang] [0:473]    dev.enola:enola:0.0.1-SNAPSHOT
[jbang] [0:523] Deleting folder /home/vorburger/.jbang/cache/jars/hello.java.090302c3cc5244467fd3d3a70a35c921664a098f574b1b80b224be60c070f7b4/classes
[jbang] [0:525] Deleting folder /home/vorburger/.jbang/cache/jars/hello.java.090302c3cc5244467fd3d3a70a35c921664a098f574b1b80b224be60c070f7b4/generated
[jbang] [0:526] [ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT
dev.jbang.cli.ExitException: Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT
        at dev.jbang.dependencies.ArtifactResolver.resolveDescriptor(ArtifactResolver.java:374)
        at dev.jbang.dependencies.ArtifactResolver.getManagedDependencies(ArtifactResolver.java:343)
        at dev.jbang.dependencies.ArtifactResolver.lambda$resolve$1(ArtifactResolver.java:204)
        at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:273)
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1708)
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
        at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)
        at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)
        at dev.jbang.dependencies.ArtifactResolver.resolve(ArtifactResolver.java:205)
        at dev.jbang.dependencies.DependencyUtil.resolveDependencies(DependencyUtil.java:112)
        at dev.jbang.dependencies.DependencyResolver.resolve(DependencyResolver.java:66)
        at dev.jbang.source.BuildContext.resolveClassPath(BuildContext.java:118)
        at dev.jbang.source.buildsteps.CompileBuildStep.compile(CompileBuildStep.java:78)
        at dev.jbang.source.buildsteps.CompileBuildStep.build(CompileBuildStep.java:56)
        at dev.jbang.source.buildsteps.CompileBuildStep.build(CompileBuildStep.java:41)
        at dev.jbang.source.AppBuilder.build(AppBuilder.java:97)
        at dev.jbang.source.AppBuilder.build(AppBuilder.java:22)
        at dev.jbang.cli.Run.doCall(Run.java:89)
        at dev.jbang.cli.BaseCommand.call(BaseCommand.java:145)
        at dev.jbang.cli.BaseCommand.call(BaseCommand.java:21)
        at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
        at picocli.CommandLine.access$1500(CommandLine.java:148)
        at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
        at dev.jbang.cli.JBang$3.handle(JBang.java:150)
        at dev.jbang.cli.JBang$3.handle(JBang.java:145)
        at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
        at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
        at picocli.CommandLine.execute(CommandLine.java:2170)
        at dev.jbang.Main.main(Main.java:15)
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:336)
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:183)
        at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:269)
        at dev.jbang.dependencies.ArtifactResolver.resolveDescriptor(ArtifactResolver.java:372)
        ... 31 more
Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for dev.enola:enola:0.0.1-SNAPSHOT
[ERROR] 'dependencies.dependency.version' for com.github.multiformats:java-multihash:v1.3.4 is missing. @

        at org.apache.maven.model.building.DefaultModelProblemCollector.newModelBuildingException(DefaultModelProblemCollector.java:176)
        at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:550)
        at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:419)
        at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:248)
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:293)
        ... 34 more
[jbang] [0:527] If you believe this a bug in jbang, open an issue at https://github.com/jbangdev/jbang/issues

That's actually quite interesting - Thank You for suggesting --verbose to debug this!

~~My ~/.m2/repository/dev/enola/enola/0.0.1-SNAPSHOT/enola-0.0.1-SNAPSHOT.pom which is mvn install from this pom.xml looks fine, and doesn't have any missing version.~~ But I guess this:

[ERROR] 'dependencies.dependency.version' for com.github.multiformats:java-multihash:v1.3.4 is missing. @

means that a dependency of java-multihash is missing a <version>? That's curious!

The Maven dependency resolution definitely changed from JBang 0.122.0 to 0.123.0.

Looking at java-multihash:v1.3.4/pom.xml, it uses <version>${version.multibase} and <version>${version.junit} and <version>${version.hamcrest}, and those are defined... huh - nowhere?! That seems weird. I'm using java-multihash from JitPack in this project.

Next logical step here would probably be to fix those missing versions, with an upstream PR, and while awaiting that, JitPack from fork. (I love not depending on having to wait for projects releasing versions to Maven Central!)

Thank You again for having suggested --verbose, I really appreciate this tip.

vorburger · 2025-02-05T22:33:45Z

Looking at java-multihash:v1.3.4/pom.xml, it uses <version>${version.multibase} and <version>${version.junit} and <version>${version.hamcrest}, and those are defined... huh - nowhere?!

No, I'm just tired, these versions ARE defined (here).

So it seems that the Maven dependency resolution changed from JBang 0.122.0 to 0.123.0 to cause the problem above, according to @quintesse due to jbangdev/jbang#1901 by @cstamas. /CC @maxandersen

Merging #1042 "fixed" (worked around) the problem for this project for the short term.

Next Step: I'm going to give the JBang maintainers time to look further into this, and not actively further pursue this in this project.

cstamas · 2025-02-05T22:52:49Z

I don't quite follow: you installed this pom (copy pasted from your comment) and then JBang invocation fails.

I cannot reproduce as I cannot even build the Maven project (a lot of compilation errors), but what strikes me, is that the POM you installed is 1.0.0-SNAPSHOT while JBang script depends on 0.0.1-SNAPSHOT... so I don't get it.

Can you please post simple reproducer steps?

cstamas · 2025-02-05T23:01:48Z

In other words, I did:

check out this repo
tried to install mentioned POM, no go https://gist.github.com/cstamas/11af7ba27426bfdcb2d6c0372be692f7
The mentioned POM is "1.0.0-SNAPSHOT" while JBang script is //DEPS dev.enola:enola:0.0.1-SNAPSHOT

cstamas · 2025-02-05T23:16:56Z

In fact, given this tree output: https://gist.github.com/cstamas/9978178bb3072c04a34cc9b8d7dfbfef
I don't even see how mentioned artifact comes into picture?

cstamas · 2025-02-06T00:16:49Z

Finally, I'd really like to see the contents of ~/.m2/repository/dev/enola/enola/0.0.1-SNAPSHOT/enola-0.0.1-SNAPSHOT.pom POM file, as myself I cannot reproduce it.

vorburger · 2025-02-07T23:41:50Z

@cstamas Thank You for your interest in reproducing this! Very sorry for the confusion, but it's like this:

cannot even build the Maven project (a lot of compilation errors)

... this project does not actually use Maven to build, but another build tool (Bazel).

As https://docs.enola.dev/dev/jbang/ documents, the tools/maven/install.bash script builds the code, if you are fully https://docs.enola.dev/dev/setup/ - for this purpose, that would primarily need go install github.com/bazelbuild/bazelisk@latest.

But it may be a PITA to get this working locally for you (the documentation could be out of date; I'm working on fully adopting Development Containers, only), so unless you really want to build this project yourself (do feel free to file bugs for anything that's not working as documented), do read on!

but what strikes me, is that the POM you installed is 1.0.0-SNAPSHOT while JBang script depends on 0.0.1-SNAPSHOT

FYI that's because that pom.xml is not actually used for that at all... confusing, yes! 🦺

It's actually this which builds the Maven POM.

I've now added some clarifications related to this.

I'd really like to see the contents of ~/.m2/repository/dev/enola/enola/0.0.1-SNAPSHOT/enola-0.0.1-SNAPSHOT.pom

This has motivated me to pick up #970:

Voilà: https://docs.enola.dev/maven-repo/dev/enola/enola/0.0.1-SNAPSHOT/enola-0.0.1-SNAPSHOT.pom

as myself I cannot reproduce it
Can you please post simple reproducer steps?

You can (now) easily reproduce the problem that this issue is about like this; see how this works:

$ git clone https://github.com/enola-dev/enola.git
$ cd enola/learn/jbang
$ rm -rf ~/.jbang/ && JBANG_DOWNLOAD_VERSION=0.122.0 ./jbang hello.java

but how this fails, with the error shown above earlier:

$ rm -rf ~/.jbang/ && JBANG_DOWNLOAD_VERSION=0.123.0 ./jbang --verbose hello.java

cstamas · 2025-02-08T00:09:04Z

Howdy, I tried devenv, but https://gist.github.com/cstamas/126b819e3b70dbf75e64946119fd5478

cstamas · 2025-02-08T00:22:01Z

Ok, I got it reproduced.

cstamas · 2025-02-08T01:20:25Z

Got it, your pom:

        <dependency>
            <groupId>com.github.multiformats</groupId>
            <artifactId>java-multihash</artifactId>
            <version></version>
            <type>v1.3.4</type>
            <scope>runtime</scope>
        </dependency>

Has mixed version w/ type. So, JBang (Maven Resolver) is right.

vorburger · 2025-02-08T10:18:24Z

@cstamas OMG! Thank You for having pinned this down to that.

I've had a closer look (notes just for the memory of my own future self):

<dependency> (above) is ultimately generated by this
java-multihash is NOT a direct artifact here
maven_install.json shows that we get com.github.multiformats:java-multihash via com.github.ipld:java-cid
This looks...
- At least more correct than the snippet above (the <version> and <type> are not mixed up there
- Except that v1.3.4 (instead of 1.3.4) is very unusual...
- ... and technically invalid, I guess; looking at ComparableVersion.java & ComparableVersionTest.java

It seems to me that there really are sort of 2 problems and "upstream issues" here, which I will separate file, next:

A. java-multihash really should use <version>1.3.x instead of v1.3.4 (and then java-cid should use that)

B. Bazel's rules_jvm_external shouldn't "fuck up" any "not strictly compliant" <version> strings like it apparently does. I mean, sure, they are "wrong", and perhaps cannot be compared, but how about at least just treating them as opaque string?

@cstamas let me know if, with your Maven foo background & experience, you agree with this analysis?

See enola-dev/enola#1040.

cstamas · 2025-02-08T10:35:07Z

Re Maven versions: do not look at maven-artifact Versions, they are deprecated.
Instead, look here: https://github.com/apache/maven-resolver/tree/master/maven-resolver-util/src/main/java/org/eclipse/aether/util/version

Spec is fleshed out in package-info.java
https://github.com/apache/maven-resolver/blob/master/maven-resolver-util/src/main/java/org/eclipse/aether/util/version/package-info.java

[cstamas@angeleyes ~]$ jbang -m org.eclipse.aether.util.version.GenericVersionScheme org.apache.maven.resolver:maven-resolver-util:1.9.22 v1.3.4 v1.3.5
Display parameters as parsed by Maven Resolver (in canonical form and as a list of tokens) and comparison result:
1. v1.3.4 -> v1.3.4; tokens: [v, 1, 3, 4]
   v1.3.4 < v1.3.5
2. v1.3.5 -> v1.3.5; tokens: [v, 1, 3, 5]
[cstamas@angeleyes ~]$

A: So "v1.3.4" is completely okay version as Maven goes.
B: Maven does not lay down "compliant version", ultimately, it will handle it as opaque string (ordered by natural order).

cstamas · 2025-02-08T10:39:35Z

And the reason for this issue: JBang before 0.123.0 was "forgiving" re dependencies, as can be seen, it was happy to just skip non existing dependency. Starting with 0.123.0 it got more strict, and will fail if your dependencies are invalid.

One interesting thing that confused me in start: the error message emitted by Resolver: "''dependencies.dependency.version' for com.github.multiformats:java-multihash:v1.3.4 is missing." was very misleading, but what happens in reality, is that Resolver shows us GAE (groupId, artifactId, extension!), but as we see version (we "know" v1.3.4 is a version) this error makes no sense. Resolver could improve this message, as all would be clear from beginning if message would be something like "'dependencies.dependency.version' for G=com.github.multiformats; A=java-multihash; E=v1.3.4 is missing."

@ianopolous

Related to enola-dev/enola#1040. See multiformats/java-multihash#48 for multiformats/java-multihash#47. @ianopolous merge this after that?

vorburger · 2025-02-08T10:43:33Z

Resolver could improve this message, as all would be clear from beginning if message would be something like

If this has motivated you to contribute an improvement for this to, go for it! Do you want me to e.g. file an MRESOLVER about it?

A. java-multihash really should use 1.3.x instead of v1.3.4

multiformats/java-multihash#48 for multiformats/java-multihash#47, merge into fork at https://github.com/vorburger/java-multihash/tree/vorburger, now available as com.github.vorburger:java-multihash:ed14893c86 from https://jitpack.io/#vorburger/java-multihash/ed14893c86, see JitPack's build log.

(and then java-cid should use that)

ipld/java-cid#40

I'll attempt to switch this project (Enola) to using that, to confirm that it's really (Bazel's) rules_jvm_external that chokes on that v prefix.

cstamas · 2025-02-08T10:47:17Z

Oh, and one more thing: JitPack:
https://www.reddit.com/r/java/comments/1fcxaqr/jitpackio_dangerously_simple/

So personally I'd recommended to avoid it in your tooling. Better use private repo, like that of GH or even on site as you did.

cstamas · 2025-02-08T10:54:10Z

If this has motivated you to contribute an improvement for this to, go for it! Do you want me to e.g. file an MRESOLVER about it?

Sure, all issues (and PRs) are welcome!

vorburger · 2025-02-08T11:45:41Z

Sure, all issues (and PRs) are welcome!

https://issues.apache.org/jira/browse/MRESOLVER-673

Oh, and one more thing: JitPack:
https://www.reddit.com/r/java/comments/1fcxaqr/jitpackio_dangerously_simple/ So personally I'd recommended to avoid it in your tooling. Better use private repo, like that of GH or even on site as you did.

Today JitPack is the best way that I know of for how to depend on some random Java libraries from GitHub which are not or not yet released to Maven Central. Or to depend (on fixed versions of, using SHA as "version") libraries which were released, but that I had to patch - instead of having to wait for maintainers to accept patch, release new versions... that model inherently by definition just does not scale. And setting up a repo like on GH is just "not worth it" for such cases. If you know of a better way how to do this, then let me know! In the meantime I'll keep using JitPack - even though it's not perfect, sure (I don't disagree with some of the criticisms from that blog post.) But one fine day (probably next not this century) I'll build an alternative; watch #1063! LoL. 😆

vorburger · 2025-02-08T12:34:48Z

I'll attempt to switch this project (Enola) to using that, to confirm that it's really (Bazel's) rules_jvm_external that chokes on that v prefix.

Blocked by bazel-contrib/rules_jvm_external#1324.

Documented with https://github.com/enola-dev/enola/pull/1064/files for my future self.

Enough of this! 🙄 Pausing further work here, until rules_jvm_external fixed their weird handling of Maven versions.

See enola-dev/enola#1040.

vorburger added bug Something isn't working build Build, CI, etc. (w.o. #testing) dependencies Pull requests that update a dependency file help wanted Extra attention is needed labels Feb 5, 2025

vorburger self-assigned this Feb 5, 2025

vorburger mentioned this issue Feb 5, 2025

Pin JBang version (e.g. via JBANG_DOWNLOAD_VERSION or .jbangversion or jbang.properties) jbangdev/jbang#1921

Open

vorburger added a commit to vorburger/enola that referenced this issue Feb 5, 2025

fix (build): Pin JBang version to 0.122.0, because 0.123.0 breaks the…

23042ec

… build (see enola-dev#1040)

vorburger mentioned this issue Feb 5, 2025

fix (build): Pin JBang version to 0.122.0, because 0.123.0 breaks the build #1041

Closed

vorburger added a commit to vorburger/enola that referenced this issue Feb 5, 2025

fix (build): Pin JBang version to 0.122.0, because 0.123.0 breaks the…

9c6bf11

… build (see enola-dev#1040)

This was referenced Feb 5, 2025

Allow mavenlocal repository to be configured jbangdev/jbang#431

Open

fix (build): Pin JBang version to 0.122.0, because 0.123.0 breaks the build #1042

Merged

vorburger added a commit to vorburger/enola that referenced this issue Feb 5, 2025

fix (build): Pin JBang version to 0.122.0, because 0.123.0 breaks the…

c493870

… build (see enola-dev#1040)

vorburger added a commit that referenced this issue Feb 5, 2025

fix (build): Pin JBang version to 0.122.0, because 0.123.0 breaks the…

160abd2

… build (see #1040)

quintesse mentioned this issue Feb 5, 2025

fix: if no deps, avoid npe; also make sure POMs refd exist jbangdev/jbang#1901

Merged

This was referenced Feb 7, 2025

feat(build): Distribute Maven repo on docs site #1060

Merged

Make JBang script actually use Enola's brand new shiny Maven repo distro #1061

Merged

Distribute Enola JARs as Maven artefacts #970

Open

vorburger mentioned this issue Feb 8, 2025

Maven version v1.3.4 (instead of 1.3.5, without the v) breaks certain Maven based tooling multiformats/java-multihash#47

Closed

vorburger added a commit to vorburger/java-multihash that referenced this issue Feb 8, 2025

Change POM version from v1.3.4 to 1.3.5 (fixes multiformats#47)

05413d1

See enola-dev/enola#1040.

vorburger mentioned this issue Feb 8, 2025

Change POM version from v1.3.4 to 1.3.5 (fixes #47) multiformats/java-multihash#48

Merged

vorburger added a commit to vorburger/java-multihash that referenced this issue Feb 8, 2025

Change POM version from v1.3.4 to 1.3.5 (fixes multiformats#47)

ed14893

See enola-dev/enola#1040.

vorburger added a commit to vorburger/java-cid that referenced this issue Feb 8, 2025

Use <version.multihash>1.3.5 instead of v1.3.4 in POM

90d3abc

Related to enola-dev/enola#1040. See multiformats/java-multihash#48 for multiformats/java-multihash#47. @ianopolous merge this after that?

vorburger mentioned this issue Feb 8, 2025

Use <version.multihash>1.3.5 instead of v1.3.4 in POM ipld/java-cid#40

Merged

This was referenced Feb 8, 2025

MVP POC of a working MavenResolver in Enola #1062

Closed

JitPack-like (generic) alternative #1063

Open

vorburger mentioned this issue Feb 8, 2025

Maven Version string should not be assumed to necessarily start with digit! E.g. vX.Y.Z instead X.Y.Z, or JitPack.io's Git SHA as version bazel-contrib/rules_jvm_external#1324

Open

vorburger added a commit to vorburger/enola that referenced this issue Feb 8, 2025

clean(docs): Leave issue enola-dev#1040 related comment in MODULE.bazel

ed5262d

vorburger mentioned this issue Feb 8, 2025

clean(docs): Leave issue #1040 related comment in MODULE.bazel #1064

Merged

vorburger added a commit that referenced this issue Feb 8, 2025

clean(docs): Leave issue #1040 related comment in MODULE.bazel

84a5164

ianopolous pushed a commit to multiformats/java-multihash that referenced this issue Feb 8, 2025

Change POM version from v1.3.4 to 1.3.5 (fixes #47) (#48)

d40dce7

See enola-dev/enola#1040.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT #1040

[ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT #1040

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025 •

edited

Loading

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025 •

edited

Loading

quintesse commented Feb 5, 2025

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025 •

edited

Loading

vorburger commented Feb 5, 2025

cstamas commented Feb 5, 2025

cstamas commented Feb 5, 2025

cstamas commented Feb 5, 2025

cstamas commented Feb 6, 2025

vorburger commented Feb 7, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025 •

edited

Loading

vorburger commented Feb 8, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025

vorburger commented Feb 8, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025

vorburger commented Feb 8, 2025

vorburger commented Feb 8, 2025

[ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT #1040

[ERROR] Could not read artifact descriptor for dev.enola:enola:jar:0.0.1-SNAPSHOT #1040

Comments

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025 • edited Loading

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025 • edited Loading

quintesse commented Feb 5, 2025

vorburger commented Feb 5, 2025

vorburger commented Feb 5, 2025 • edited Loading

vorburger commented Feb 5, 2025

cstamas commented Feb 5, 2025

cstamas commented Feb 5, 2025

cstamas commented Feb 5, 2025

cstamas commented Feb 6, 2025

vorburger commented Feb 7, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025 • edited Loading

vorburger commented Feb 8, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025

vorburger commented Feb 8, 2025

cstamas commented Feb 8, 2025

cstamas commented Feb 8, 2025

vorburger commented Feb 8, 2025

vorburger commented Feb 8, 2025

vorburger commented Feb 5, 2025 •

edited

Loading

vorburger commented Feb 5, 2025 •

edited

Loading

vorburger commented Feb 5, 2025 •

edited

Loading

cstamas commented Feb 8, 2025 •

edited

Loading