#Made Github repository for JAudioTagger 2.2.6 in order to use with Maven , Gradle etc.
#Made Github repository for JAudioTagger 2.2.6 in order to use with Maven , Gradle etc.
From the repository read me ...
Fake Repository in order to use JAudioTagger 2.2.6 with Gradle and Maven
Use it with Maven , Gradle etc via https://jitpack.io/#goxr3plus/jaudiotagger
Example with Maven :
<repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories>
<dependency>
<groupId>com.github.goxr3plus</groupId>
<artifactId>jaudiotagger</artifactId>
<version>V2.2.6</version>
</dependency>
This repository is a fork (though not complete from [ https://bitbucket.org/ijabz/jaudiotagger ]
So don't use the code from here ... :)
Comments (12)
-
repo owner -
reporter I am using Maven and Gradle build , i can't find anywhere JAudioTagger 2.2.6 . So i am proposing this temporary solution :
Every repository from Bitbucket and Github which has releases can use JitPack.io in order to get Libraries with Maven , Gradle etc .
For example : https://jitpack.io/#goxr3plus/jaudiotagger takes the release from that GitHub repository and can be used with Maven .
The same should happen with JAudioTagger 2.2.6 via BitBucket but there is a problem here as you can see : https://jitpack.io/#org.bitbucket.ijabz/jaudiotagger the 2.2.6 doesn't appear at all . Only until 2.2.5 .
That's my point :) .
Finally i want to ask , is there any other way you have done it that i don't know :) . I would be happy if there is .
-
repo owner Cant you fix in bitbucket rather than puttoin on github, I dont really want your version to be the version shown in maven, I havent done a final release of jaudioatgger 2.2.6, I guess it is overdue but Im not sure how to do it.
-
reporter Yes i agree it is a bad solution but it works ... i did that because i have applications like which need JAudioTagger 2.2.6 in order to work ...
Alright please read the below , it will work :)
What you need to do is create a new Tag (https://bitbucket.org/ijabz/jaudiotagger/downloads/?tab=tags ) with name 2.2.6 or whatever version you release on future and JitPack.io will automatically make it Maven and Gradle importable . That's it .
Like you did for 2.2.5 for example :) . If you do it i will be more than grateful :)
So it will be shown here -> https://jitpack.io/#org.bitbucket.ijabz/jaudiotagger if you do it correctly .
-
reporter Also be sure that the report of Maven is Build Success :) like for your version 2.2.5 -> https://jitpack.io/org/bitbucket/ijabz/jaudiotagger/v2.2.5/build.log
-
FYI jitpack.io can directly consume from this repo hosted on bitbucket.io. See: https://jitpack.io/#org.bitbucket.ijabz/jaudiotagger
(IJabz, thanks for all your work! I'm a customer and a user of your library.)
-
reporter @kgilmer Hello :) Of course it can but it doesn't have the latest version 2.6 . That's the problem .
-
Hi @GOXR3PLUS :) Well that's because 2.2.6 hasn't been released yet and that release is at the discretion of the library maintainer. It would be a source of confusion to fork a library and produce new versions under the name of the original IMHO. In any case you can also consume from a commit as opposed to a release/tag so assuming the commit you need has been pushed publicly you can consume it like this (ex has latest commit from repo):
compile 'org.bitbucket.ijabz:jaudiotagger:90533d4'
This lets you consume whichever version of the library you like without putting pressure on the library maintainer to create a release. I see above that you have already referenced jitpack.io...I did not see that until now.
-
Hi Roman,
Sure, check here: https://jitpack.io/#org.bitbucket.ijabz/jaudiotagger. You can specify a commit as a release on the 'commits' tab.
HTH ken
-
repo owner Im trying to get published on Maven central again with Sonatype - https://issues.sonatype.org/browse/OSSRH-73942
-
repo owner now on maven central jaudiotagger 3.0.0
-
repo owner - changed status to resolved
Done.
- Log in to comment
I dont understand what the point of this is.