Complete Maven POM so Ant not required.

[GoogleCodeExporter]

Submitting complete pom.xml which can perform compile, package, sign and deploy.

Original issue reported on code.google.com by cw10...@gmail.com on 23 Jan 2013 at 4:24

Attachments:

• pom.xml

[GoogleCodeExporter]

Forgot about OSGi bundle and inclusion/relocation of ASM, so refer to the 
attached, revised pom.xml

  -Chris

Original comment by cw10...@gmail.com on 23 Jan 2013 at 6:55

Attachments:

• pom.xml

[GoogleCodeExporter]

BTW, I meant to file this as "enhancement" - not "defect".

Original comment by cw10...@gmail.com on 23 Jan 2013 at 11:15

[GoogleCodeExporter]

Thanks for this!  I'll try it out for the next release...

Original comment by kevin.s...@gmail.com on 31 Jan 2013 at 3:15

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

The reason I re-did it using Maven is because I was having a lot of 
trouble debugging a stream/group configuration and was surprised that 
BeanIO code has no logging.  I modified some code to add logging, 
specifically, SLF4J, which has multiple pluggable backends and low 
overhead.  e.g. I needed to trace parsing and unmarshalling.  I will 
submit my changes as suggested enhancements.

Oh, so with Maven, the dependencies are automatically maintained, as I 
was too lazy to manually locate and download slf4j to ./lib ;)

Thanks and regards,

   -Chris

Original comment by cw10...@gmail.com on 31 Jan 2013 at 3:06

[GoogleCodeExporter]

BeanIO 2.1.0 will be built using Gradle.

Thanks again for the Maven pom, but its complexity just reaffirmed my dislike 
for Maven.

Original comment by kevin.s...@gmail.com on 21 Apr 2013 at 2:27

• Changed state: WontFix

[GoogleCodeExporter]

There's no question that Maven can be tough, but for many projects with 
complex dependencies,
it's a life-saver, compared to Ant.  That Gradle looks promising....

Original comment by cw10...@gmail.com on 22 Apr 2013 at 2:32