Skip to content
Dan Dudley edited this page Jun 13, 2014 · 2 revisions

Why did I call the project "flapjack"?

When I thought about parsing a flat file I imagined a stack of pancakes on a plate.

Why did I make the parsing and mapping to the model separate?

Well, that's the way I think it should be. Also, it allows multiple developers to use the same record layouts, but use totally different domain models. Why should someone have to duplicate the record definitions?! This leads to mistakes re-implementing the record layouts and it's also duplication. Plus from my experience it's sometimes hard to get others to agree on the same domain model design.

How to use Flapjack?

Checkout the examples on how to use flapjack.

How to access Flapjack as a Maven dependency?

Checkout how to setup your pom to access the flapjack repository

I see there is a new release of flapjack. What features or bug fixes are in the new release?

Checkout the release notes.

I have encountered a bug or I see a missing feature. What should I do?

Create an issue here.

How can I be notified of updates or new releases?

Checkout the project feeds here. Follow us on twitter

I have a question, but it is not answered here?

Post a question on the Google Group.