You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, first of all, this is open source, the way I see it you're always welcome to copy features you like. Copying code as well when licenses are the same as in our case. Still my code is in Java vs yours in Go, so straight copying won't work very well :-)
The other thing is that I strongly feel that Java tools should be written in Java :-)
If for some reason it's easier to write things in X, then we should try to fix that and make it as easy (or easier/better/nicer) in Java.
So although your project certainly looks very interesting and scratches much of the same itch as mine, I do not see myself delving into Go right now.
A question, your examples all seem very *nix centered, have you taken into account that people will want this to work on Windows as well?
Btw, thinking about it some more I also feel there's a "philosophical" difference between our tools. You want yours to be a full build tool, a full replacement of the entire build chain. That's not what I want with my jpm, in fact it's the opposite, I want it to help me, but not get in my way. I want to keep using the tool chain the language gives me (eg. javac/java/kotlinc/etc) but make the dependency management easier because for me that's the most important part that's missing.
This also means that my jpm works with Kotlin, Groovy, Scala and others just as easily as with Java exactly because users keep using their respective tool chains. No need to change anything. In contrast your jpm needs special built-in support for each language. That makes yours a much more powerful tool, but it's just not what I'm looking to do with mine.
I just directly hit the Maven Central search API: https://central.sonatype.org/search/rest-api-guide/ .
It's all pretty limited TBH.
If there's one thing I would really love for the Java ecosystem to copy from npmjs is the excellent search results when looking for packages/artifacts. In the Maven world search results have always been extremely limited, especially when compared to npmjs.
Activity
quintesse commentedon Oct 7, 2025
Hi, first of all, this is open source, the way I see it you're always welcome to copy features you like. Copying code as well when licenses are the same as in our case. Still my code is in Java vs yours in Go, so straight copying won't work very well :-)
The other thing is that I strongly feel that Java tools should be written in Java :-)
If for some reason it's easier to write things in X, then we should try to fix that and make it as easy (or easier/better/nicer) in Java.
So although your project certainly looks very interesting and scratches much of the same itch as mine, I do not see myself delving into Go right now.
A question, your examples all seem very *nix centered, have you taken into account that people will want this to work on Windows as well?
quintesse commentedon Oct 7, 2025
Btw, thinking about it some more I also feel there's a "philosophical" difference between our tools. You want yours to be a full build tool, a full replacement of the entire build chain. That's not what I want with my jpm, in fact it's the opposite, I want it to help me, but not get in my way. I want to keep using the tool chain the language gives me (eg. javac/java/kotlinc/etc) but make the dependency management easier because for me that's the most important part that's missing.
This also means that my jpm works with Kotlin, Groovy, Scala and others just as easily as with Java exactly because users keep using their respective tool chains. No need to change anything. In contrast your jpm needs special built-in support for each language. That makes yours a much more powerful tool, but it's just not what I'm looking to do with mine.
jpm-hub commentedon Oct 7, 2025
Yeah mine is programmed in go and I do create the tool to replace java, javac, kotlinc . I wish I was as good in Java as I am in go.
I wanted know specifically how do you search for packages?
quintesse commentedon Oct 7, 2025
I just directly hit the Maven Central search API: https://central.sonatype.org/search/rest-api-guide/ .
It's all pretty limited TBH.
If there's one thing I would really love for the Java ecosystem to copy from npmjs is the excellent search results when looking for packages/artifacts. In the Maven world search results have always been extremely limited, especially when compared to npmjs.
quintesse commentedon Oct 10, 2025
Btw, do you know about JeKa? https://jeka.dev/
It seems to have similar intentions as your project, although with a different design.
jpm-hub commentedon Oct 11, 2025
I do know about Jeka, but I see that they're more repository based, I was more inspired by npm.
Also, Jeka still kinda depends on other build tools according to what I understand. I don't want to depend on any build tool.