Maven is not updated #37

New Issue

open-autonomous-connection · 2019-03-24T08:16:32Z

SuSeu1414 commented

2019-03-24 08:16:32 +00:00

(Migrated from github.com)

This doesn't work

<dependency>
    <groupId>org.luaj</groupId>
    <artifactId>luaj-jse</artifactId>
    <version>3.0.2</version>
</dependency>

But this one does

<dependency>
    <groupId>org.luaj</groupId>
    <artifactId>luaj-jse</artifactId>
    <version>3.0.1</version>
</dependency>

This doesn't work ``` <dependency> <groupId>org.luaj</groupId> <artifactId>luaj-jse</artifactId> <version>3.0.2</version> </dependency> ``` But this one does ``` <dependency> <groupId>org.luaj</groupId> <artifactId>luaj-jse</artifactId> <version>3.0.1</version> </dependency> ```

lagagain commented

2019-03-31 12:58:01 +00:00

(Migrated from github.com)

I guess because this repo is not total same with original (host on SourceForge), and this repo maintain can't contact the maintain of original. (There are an explanation on README)

But, this repo has released jar file (luaj-jme-3.0.2.jar and luaj-jse-3.0.2.jar) on release page. I think you can download the jar files to your maven project (directly use jar file).

I guess because this repo is not total same with original (host on [SourceForge](https://sourceforge.net/projects/luaj/)), and this repo maintain can't contact the maintain of original. (There are an explanation on README) But, this repo has released jar file (luaj-jme-3.0.2.jar and luaj-jse-3.0.2.jar) on [release page](https://github.com/luaj/luaj/releases). I think you can download the jar files to your maven project (directly use jar file).

👍 2

Mikhael-Danilov commented

2019-04-03 15:52:32 +00:00

(Migrated from github.com)

Maybe it worth to introduce new package?

binkley commented

2019-12-23 14:25:48 +00:00

(Migrated from github.com)

Confirming that 3.0.1 is most recent version in Maven Central: https://search.maven.org/artifact/org.luaj/luaj-jse

After looking through README.md, I see the ownership issues. Does this prevent publishing to 3.0.2 to Maven Central? Since one may download 3.0.2 jar directly, it isn't clear to me how one is ok (downloading the jar), and the other isn't (downloading from Maven Central). I'm not up-to-date on how such matters work.

Perhaps it would be helpful in the GitHub README.md to include instructions and/or link for using local jars as dependencies.

This StackOverflow answer seems relevant: https://stackoverflow.com/a/22300875

Also, the download link(s) on README.md seem to point to 3.0.1. Does this mean 3.0.2 needs to be built from source to use it?

Confirming that 3.0.1 is most recent version in Maven Central: https://search.maven.org/artifact/org.luaj/luaj-jse After looking through `README.md`, I see the ownership issues. Does this prevent publishing to 3.0.2 to Maven Central? Since one may download 3.0.2 jar directly, it isn't clear to me how one is ok (downloading the jar), and the other isn't (downloading from Maven Central). I'm not up-to-date on how such matters work. Perhaps it would be helpful in the GitHub `README.md` to include instructions and/or link for using local jars as dependencies. This StackOverflow answer seems relevant: https://stackoverflow.com/a/22300875 Also, the download link(s) on `README.md` seem to point to 3.0.1. Does this mean 3.0.2 needs to be built from source to use it?

acanthite1855 commented

2020-07-15 15:08:25 +00:00

(Migrated from github.com)

Hey. How about jitpack.io? It works the way, that it downloads the source from repo, builds it somewhere on their servers. It supports sources and javadoc. You can use the built lib by specifying dependency like this:

<dependency>
    <!-- user -->
    <groupId>com.github.luaj</groupId> 
    <!-- repo -->
    <artifactId>luaj</artifactId>
    <!-- tag or branch -->
    <version>3.0.2</version> 
</dependency>

Unfortunately it cannot build jar from 3.0.2 tag for some reason. It May be related to the build script/tests. I'm not really sure what's going on by just looking at the logs.

Hey. How about [jitpack.io](https://jitpack.io/)? It works the way, that it downloads the source from repo, builds it somewhere on their servers. It supports sources and javadoc. You can use the built lib by specifying dependency like this: ```xml <dependency>  <groupId>com.github.luaj</groupId>  <artifactId>luaj</artifactId>  <version>3.0.2</version> </dependency> ``` Unfortunately it cannot build jar from 3.0.2 tag for some reason. It May be related to the build script/tests. I'm not really sure what's going on by just looking at the logs.

lorenzos commented

2023-02-09 14:34:44 +00:00

(Migrated from github.com)

Using jitpack.io would be a nice solution, but the reason it doesn't work with 3.0.2 is that JitPack encounters an error while trying to build it, here's the log: https://jitpack.io/com/github/luaj/luaj/v3.0.2/build.log

Also, beware that the release tag in this repository is named v3.0.2, so you have to use it exactly as it is:

<dependency>
    <groupId>com.github.luaj</groupId> 
    <artifactId>luaj</artifactId>
    <version>v3.0.2</version> 
</dependency>

implementation 'com.github.luaj:luaj:v3.0.2'

Using [jitpack.io](https://jitpack.io/) would be a nice solution, but the reason it doesn't work with 3.0.2 is that JitPack encounters an error while trying to build it, here's the log: https://jitpack.io/com/github/luaj/luaj/v3.0.2/build.log Also, beware that the release tag in this repository is named `v3.0.2`, so you have to use it exactly as it is: ``` <dependency> <groupId>com.github.luaj</groupId> <artifactId>luaj</artifactId> <version>v3.0.2</version> </dependency> ``` ``` implementation 'com.github.luaj:luaj:v3.0.2' ```

open-autonomous-connection closed this issue

2026-03-01 18:00:07 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: open-autonomous-connection/luaj#37