Hello Josef, I apologize for delay with the answer - we had mailing list issues and it looked like replies were sent while they were not :( So I'm resending these lost messages.
There are good reasons why we've decided to use Gradle. Before starting to use it we have investigated other options, and we've found Gradle most suitable for our needs. It's pity to know that you are not satisfied with this change. Here is an outline of our building framework: Server side: 1) Maven Repository at http://maven.tmatesoft.com/, Snapshots repository URL is http://maven.tmatesoft.com/content/repositories/snapshots/ Releases repository URL is http://maven.tmatesoft.com/content/repositories/releases/ This is standard Maven repository and all nightly builds of SVNKit goes to snapshots repository. In particular there are following artifacts, that you may refer from your maven poms: <groupId>org.tmatesoft.svnkit</groupId> <artifactId>svnkit</artifactId> <version>1.3.6-SNAPSHOT</version> <groupId>org.tmatesoft.svnkit</groupId> <artifactId>svnkit-cli</artifactId> <version>1.3.6-SNAPSHOT</version> So, if you use Maven, then you should have no problems introducing dependency on SVNKit artifacts. 2) Teamcity continuous integration at http://teamcity.tmatesoft.com/ This is the place where you may download binaries of SVNKit that are buit daily. Binaries includes command line client, OSGi update site and plain SVNKit jars. Binaries are kept for the last ten continuous builds on this server. Client side: 3) On the client side we use Gradle (http://gradle.org/). You only need it if you're going to build SVNKit from sources. Gradle is Open Source, but I do not know if it works on OpenVMS. In general, you shouldn't need to build SVNKit from sources. Why would you need to do that and not just use artifacts from maven or binaries from the web site or continuous integration server? Would it help if we put complete command line client as an artifact to maven? But if you do need to build from sources anyway, you may, write ant script of your own, that would use ant maven tasks to fetch SVNKit artifact dependencies from the maven repository and then compile svnkit sources putting these dependencies on classpath. Alexander Kitaev, TMate Software, http://svnkit.com/ - Java [Sub]Versioning Library! http://hg4j.com/ - Java Mercurial Library! http://sqljet.com/ - Java SQLite Library! On 16 August 2011 09:32, Stadelmann Josef <[email protected]> wrote: > Why did gradle substitute ant build.xml or even maven? > > Nothing against gradle but you guys bring us into a bad situation, in > troubles. > > I could successfully build in the past svnkit on OpenVMS using ant –f > build.xml > > I was hoping that one day maven will substitute ant build.xml but now I find > that gradle was that substitut > > If two build optioins gradle and ant or maven would be suported I would not > claim. BUT > > Gradle may work nicely under Windows and all those *ux* boxes but I have no > information about a gradle running on OpenVMS yet. > > Is that Open Source behaviour? > > We are trying hard to get svnkit and maven running on OpenVMS as close as > possible at a main development line. > > But with every introduction of new build systems we feel further away and > allone from our target to have maven and svnkit doing well. > > Josef
