and the jars from the devPackage directory. I believe that providing proper maven dependencies/repository would remove unnecessary obstacle for developers who want to develop/experiment with teamcity plugin development and are used to maven...
Thank you for your effort devising a pom for the TeamCity libraries. Totrally agree: we should publish the libraries ourselves into a public Maven repo. BTW, here is an issue to vote for / watch: TW-10625.
In absence of locating an online maven repository, what are the dependencies that we should use? I had to guess at the following for 6.5.1:
<dependency>
<groupId>com.jetbrains.teamcity</groupId>
<artifactId>server-api</artifactId>
<version>6.5.1</version>
</dependency>
<dependency>
<groupId>com.jetbrains.teamcity</groupId>
<artifactId>runtime-util</artifactId>
<version>6.5.1</version>
</dependency>
<dependency>
<groupId>com.jetbrains.teamcity</groupId>
<artifactId>common-api</artifactId>
<version>6.5.1</version>
</dependency>
<dependency>
<groupId>com.jetbrains.teamcity</groupId>
<artifactId>annotations</artifactId>
<version>6.5.1</version>
</dependency>
<dependency>
<groupId>com.jetbrains.teamcity</groupId>
<artifactId>agent-api</artifactId>
<version>6.5.1</version>
</dependency>
<dependency>
<groupId>com.jetbrains.teamcity</groupId>
<artifactId>util</artifactId>
<version>6.5.1</version>
</dependency>
I copied these files from my installation directory at /usr/local/teamcity:
/usr/local/teamcity/devPackage/agent-api.jar
/usr/local/teamcity/devPackage/common-api.jar
/usr/local/teamcity/devPackage/server-api.jar
/usr/local/teamcity/devPackage/runtime/runtime-util.jar
/usr/local/teamcity/webapps/ROOT/WEB-INF/lib/annotations.jar
/usr/local/teamcity/webapps/ROOT/WEB-INF/lib/util.jar
I took inspiration in:
http://vcsupdate.googlecode.com/svn/trunk/pom.xml
Hence using:
and the jars from the devPackage directory. I believe that providing proper maven dependencies/repository would remove unnecessary obstacle for developers who want to develop/experiment with teamcity plugin development and are used to maven...
Guys,
Thank you for your effort devising a pom for the TeamCity libraries.
Totrally agree: we should publish the libraries ourselves into a public Maven repo.
BTW, here is an issue to vote for / watch: TW-10625.
Hi, here's a Gradle example: