Hello Oleg, We did upload all the required dependencies to the Maven Central, it includes sequence, trilead and sqljet libraries. We did sycnhronization through the sonatype OSS repository, so I'll contact them now to check why sequence library was lost (it is the only missing dependency).
The relevant issue is here: https://issues.sonatype.org/browse/OSSRH-3479 Alexander Kitaev, TMate Software, http://subgit.com/ - Svn to Git Migration! http://svnkit.com/ - Java [Sub]Versioning Library! http://hg4j.com/ - Java Mercurial Library! http://sqljet.com/ - Java SQLite Library! On 11 May 2012 08:06, Oleg Estekhin <oleg.estek...@gmail.com> wrote: > > Hi > > i am very glad to see the svnkit:1.7+ in the Maven Central, but there is a > problem that prevents its use. The following error will prevent the building > of anything that depends on svnkit:1.7.4-v1 and uses only the Maven Central > repository: > === > Could not find artifact de.regnis.q.sequence:sequence-library:jar:1.0.2 in > central (http://repo.maven.apache.org/maven2) > === > > The svnkit:1.7.4-v1 references > de.regnis.q.sequence:sequence-library:jar:1.0.2 which is not present in the > Maven Central. This effectively makes it impossible to use the > svnkit:1.7.4-v1 without referencing the additional repository > http://maven.tmatesoft.com/content/repositories/releases/. > > Please review the possible solutions in the order from the best to not so > good: > 1) find a way to upload de.regnis.q.sequence:sequence-library:jar:1.0.2 into > the Maven Central. This will allow to use the already existing > svnkit:1.7.4-v1 without any modifications or additional releases. > 2) if you can not upload de.regnis.q.sequence:sequence-library:jar:1.0.2 > under its original name, then upload it under custom svnkit-related group, > as was done with the trilead-ssh:build213-svnkit-1.3-patch before, and > release svnkit:1.7.4-v2 with the corrected dependency. > > 3) if it is not possible to upload > de.regnis.q.sequence:sequence-library:jar:1.0.2 into the Maven Central at > all due to licensing or some other issues, then svnkit:1.7.4-v1 in the Maven > Central is useless, and the only option is to stop bothering the with > Central and use the > http://maven.tmatesoft.com/content/repositories/releases/ repository. This > is sadly the worst option because it will propagate to all artifacts that > depend on the svnkit - they will not be able to release new versions into > the Maven Central too, and will have to use their own repositories, and this > will propagate to their users and so on (fail cascade =\ ) > > > > -- > View this message in context: > http://old.nabble.com/svnkit%3A1.7.4-v1-in-Central-has-unresolved-dependency-that-prevents-its-use-tp33765913p33765913.html > Sent from the SVNKit - Users mailing list archive at Nabble.com. > >
