alright, after having a fun time with kobalt on a ...
# kobalt
g
alright, after having a fun time with kobalt on a little fun open-source project
getoptk
, im now looking at kobalt as a replacement for
ant
at work. Some problems that I'm going to need to solve: - many semi-conventional source directories (currently
$root/Common/src/
,
$root/Front-End/src/
...) seems like I can pretty easily manually update the source sets with
sourceDirectories
- dependencies are all checked-in jars and DLL's. I guess I'll need to do some kind of clever regex or a bunch of manual effort to get them out of this checked in form and into the
compile(varargs deps: String)
build script parameter. Any thoughts here? - I need some custom JUnit and Cucumber targets. I absolutely dispise the ant targets here so my #1 goal is their replacement. Between these two runners there are a number of targets whose files are differentiated by file-name suffix (
XYZFixture
is a unit test and
ABCIntegrationTest
is an integration test) - There will be some tasks that I'd still like to leave to ant, including some stuff around
install4j
, I'm hoping kobalt has ant integration similar to gradles, is
DevCharly/kobalt-ant
the best way to do this?