Closed GoogleCodeExporter closed 9 years ago
Hi
You make a very good point. I used maven for to get a build up and running
quickly
but was thinking about using ant+ivy for 1.1. Also thinking about splitting
this up
into two jars
1. jsend-nsca.jar - the main API
2. jsend-nsca-cli.jar - the cli wrapper code
Any thoughts?
Original comment by rajneeshpatel
on 26 Nov 2008 at 9:29
Hi 2 :)
I've tested ivy for a while - but I don't feel comfortable with :
"new magic behaviour through just another xmlfile". One place more to hunt down
bugs.
I'm currently using the ant-maven-task only. One additional task for
dependencies is
just quite right for me.
( I'm not a real purist btw: My default-build.xml is getting bigger + complexer
every-day :o )
In case of the splitting up : i would personally use the cli only for testing -
send_nsca is available for unix + windows. But a "ant-jsendnsca-task" would be
more
practiable ( hmmmm ).
cu
jens
... googles away to find more about this "ant-jsendnsca-task" ...
Original comment by jens.rit...@gmail.com
on 26 Nov 2008 at 10:27
Hi Jens
Youre right about the cli for testing, my thinking around it was as follows:
1. Multi-platform
2. Integration test for the core API and testing a NSCA/Nagios setup
So far as splitting out, ive created a jsendnsca-core project for the core API
using
a simple ant build.xml
Ill also create a jsendnsca-cli project which uses the core API, again using a
simple
ant build script.
It will take me a day or two to upload to SVN and will update issue once done.
For the ant-jsendnsca-task, interesting idea.
Thanks for the comments/ideas, will be in touch soon.
Regards
Raj
Original comment by rajneeshpatel
on 26 Nov 2008 at 11:22
Original comment by rajneeshpatel
on 26 Nov 2008 at 11:24
Code has now been split into two parts
1. jsendnsca-core: Core API
2. jsendnsca-cli : Command line tool
Now using Ant as build tool
Original comment by rajneeshpatel
on 30 Nov 2008 at 3:22
Original issue reported on code.google.com by
jens.rit...@gmail.com
on 26 Nov 2008 at 8:20