I mean, I have an ant script, ant ant script expresses our entire build system, what I want to do is something like write a task in kobalt that depends on a target from an ant build script. I have no interest in writing ant in kotlin, at least at this time

but honestly if i just have to drop down to my own

process-builder.exec

call I'd be OK with that

or actually, I say that now... the ability ot query the XML dom might also be helpful...

and actually, completely unrelated, but I'm looking at pipelining my build on teamcity so as to avoid re-compilation. But like many projects we have a

compile-src

and

compile-tests&src

targets... is there any way I can combine those into a single step, such that I dont have to re-compile my production code but also have a folder that contains only production-code binaries?

Looks like a TeamCity related question…

I mean its a javac/kobalt/teamcity question, I really just want one call to javac that will do some special formatting of the output

well

javac+kotlinc

I'm wondering if its possible to compile our production code and our test code at the same time and still produce a production jar file

@cedric there is something wrong with kobalt-plugin-api-1.0.100.jar on JCentral because the package "com.beust.kobalt" is NOT in that jar

mmh

Ah yeah I remember accidentally uploading it and then interrupting because there was no need

but I’ll fix it right now hold on

I fixed .100 and uploaded .101 also

many thx for the super quick fix 👍

Sure thing. I’m curious why you need this dependency though, are you trying to write a plug-in?

trying to update my kobalt-ant plugin

Ah alright. Let me know if you need help, if I recall, you wrote your plug-in with an old

0.x

version

yes,

0.839

...

@ethauvin For some reason,

--resolve

of versionless artifacts is working again for me, can you try on your end?

./kobaltw  --resolve com.beust:kobalt:

@cedric Yeah, same here.

I wonder what caused it. It lasted a few days.

A repo side glitch I suppose. Or maybe they screwed up their

metadata

files for a few days so version ranges could no longer be resolved…

That could be, especially that it was complaning about not finding something on

MavenCenteral

which should have been on

JCenter

.

Hmm, seems that the

fatJar

option is broken. When I build https://github.com/DevCharly/kobalt-ant then

kobalt-ant-0.4.jar

is only 18k, but it should be ~2500k

@devcharly Can I reproduce the issue if I clone your repo?

@cedric yes, the repo is up-to-date.

assemble

builds to JARs: *

kobaltBuild/libs/kobalt-ant-0.4.jar

should be "fat" *

kobaltBuild/libs/kobalt-ant-core-0.4.jar

is "non-fat"

I'm getting errors:

| |/ /   ___   | |__     __ _  | | | |_
           | ' /   / _ \  | '_ \   / _` | | | | __|
           | . \  | (_) | | |_) | | (_| | | | | |_
           |_|\_\  \___/  |_.__/   \__,_| |_|  \__|  1.0.100

Parallel build starting
     ╔═════════════════════╗
     ║ Building kobalt-ant ║
     ╚═════════════════════╝
───── kobalt-ant:compile
Downloaded artifact com.devcharly:kotlin-ant-dsl:pom:0.6 from JCenter (<https://jcenter.bintray.com/>, default, releases+snapshots)
Downloaded artifact org.apache.ant:ant:pom:1.10.1 from Maven (<http://repo1.maven.org/maven2/>, default, releases+snapshots)
Downloaded artifact org.apache.ant:ant-parent:pom:1.10.1 from Maven (<http://repo1.maven.org/maven2/>, default, releases+snapshots)
Downloaded artifact org.apache.ant:ant-launcher:pom:1.10.1 from Maven (<http://repo1.maven.org/maven2/>, default, releases+snapshots)
Downloaded artifact org.apache.ant:ant:jar:1.10.1 from Maven (<http://repo1.maven.org/maven2/>, default, releases+snapshots)
Downloaded artifact org.apache.ant:ant-launcher:jar:1.10.1 from Maven (<http://repo1.maven.org/maven2/>, default, releases+snapshots)
Downloaded artifact com.devcharly:kotlin-ant-dsl:jar:0.6 from JCenter (<https://jcenter.bintray.com/>, default, releases+snapshots)
  Kotlin 1.2.0 compiling 1 file
*****
***** ERROR warning: some JAR files in the classpath have the Kotlin Runtime library bundled into them. This may cause difficult to debug problems if there's a different version of the Kotlin Runtime library in the classpath. Consider removing these libraries from the classpath or use '-Xskip-runtime-version-check' to suppress this warning
       C:\Users\erik\.kobalt\cache\com\beust\kobalt-plugin-api\1.0.100\kobalt-plugin-api-1.0.100.jar: warning: library has Kotlin runtime bundled into it
       src\main\kotlin\com\devcharly\kobalt\plugin\ant\AntTaskPlugin.kt:19:18: error: unresolved reference: kobalt
       import com.beust.kobalt.IncrementalTaskInfo

@cedric It's back:

$ k8 --resolve com.beust:kobalt:
              __ __           __              __   __
             / //_/  ____    / /_   ____ _   / /  / /_
            / ,<    / __ \  / __ \ / __ `/  / /  / __/
           / /| |  / /_/ / / /_/ // /_/ /  / /  / /_
          /_/ |_|  \____/ /_.___/ \__,_/  /_/   \__/  1.0.100

*****
***** ERROR Could not find artifact com.beust:kobalt-wrapper:jar:1.0.100 in Maven (<http://repo1.maven.org/maven2/>)
*****

@devcharly I was able to compile changing:

dependencies {
		compileOnly("com.beust:kobalt-plugin-api:")
        compileOnly("org.jetbrains.kotlin:kotlin-stdlib:1.2.10")
		compile("com.devcharly:kotlin-ant-dsl:${Versions.kotlinAntDSL}")
		compile("org.apache.ant:ant:${Versions.ant}")
	}

But the jars are the same size, as you're seeing.