V2.0: JSend NSCA 2.0

[GoogleCodeExporter]

Hi Jeremy, Claus

First of, Jeremy, meet Claus who has done some great work recently on 
raising and fixing bugs. Claus is currently working on a Apache Camel 
component which will use the API

http://issues.apache.org/activemq/browse/CAMEL-2347

I have started work on version 2.0. Essentially, taken the 1.3.1 codebase 
and tidied it up e.g.

* Using enums now only instead of integers which removes a load of 
validation to make sure people are setting valid levels, encryption etc

* Exposed Encryptor interface so people can roll their own encryption as 
NSCA supports a whole host of which only a subset are currently 
implemented

* Using nice features of Junit 4.7 such as expected exception rule and 
replaced IllegalArgument checks with Validate class from commons-lang

Main thing is now using Maven for build/project management. Want to 
automate as much of the release process as possible

Please feel free to check out, project is no simply called jsendnsca in trunk

If you guys have any ideas, improvements etc, can you raise issues and we 
can manage them between us to ensure they make this release

Also, Claus, any experience on getting an artifact into the maven repos, I 
understand this could take a while

Many thanks 

Raj

Original issue reported on code.google.com by rajneeshpatel on 24 Jan 2010 at 10:41

[GoogleCodeExporter]

Hi All

Just a quick note. Great work on the 2.0 so far.
I have not drilled down into this yet, I am busy currently at a business trip.

However I did notice that you have bring in new dependencies such as commons-io 
and -lang etc. If I recall 
correctly.

I would suggest to consider this move. Having a low count dependencies is a key 
thing.

Original comment by claus.ib...@gmail.com on 25 Jan 2010 at 7:27

[GoogleCodeExporter]

Hi Claus,

Thanks for taking the time to respond during your trip. 

Added dependencies as currently using quite a few classes in commons lang such 
as 
StringUtils, Validate, HashCodeBuilder, EqualsBuilder, ToStringBuilder so think 
its 
better to still have this as dependency as advantage of reusing  these classes 
in 
improving code clarity outweighs disadvantage of introducing dependency on 
commons-lang

However, only still using single class IOUtils from commons-io so have removed 
that.

Original comment by rajneeshpatel on 26 Jan 2010 at 7:56

[GoogleCodeExporter]

Original comment by rajneeshpatel on 26 Jan 2010 at 10:17

• Changed title: _V2.0: JSend NSCA 2.0 _

[GoogleCodeExporter]

Original comment by rajneeshpatel on 29 Jun 2010 at 9:18

• Changed state: Verified