Create project structure

[edeandrea]

We need to create a basic project skeleton. This is what I'm thinking for starters. We can always evolve it as needed.

.  # root will be the parent project - not sure we need a bom artifact yet
+-- .github
       +-- dependabot.yml
       +-- workflows
              +-- dependabot-automerge.yml
              # Other GH action workflows
+-- api
       # Java project - Code in here is part of the public api. Mostly interfaces/definitions. Separate artifact published to maven central.
       +-- src/main/java/ai/docling
              +-- api  
                     # Code/subpackages in here
+-- docs  
       # Antora documentation - we should theme it to be consistent with the rest of the Docling projects
+-- impl  
       # Java project (I'm not crazy about the name but its something we need), but this will be the reference implementation
       +-- src/main/java/ai/docling 
              # Code/subpackages in here
+-- testing  
       # Java project - Any testing-related code (i.e. testcontainers/etc), or any test resources . Separate artifact published to maven central
       +-- src/main/java/ai/docling
              +-- test  # Code/subpackages in here

@ThomasVitale @lordofthejars thoughts?

Also, any preference on using Maven vs Gradle? I don't have a preference.

[lordofthejars]

For me, Maven (as I don't have a lot of Gradle experience) , but at the end, I will only use it for resolving dependencies, so I really don't care

[ThomasVitale]

Looks good! How about client instead of impl? I guess that will be the default client implementation, right? So the main packages published to Maven Central can be docling-api and docling-client. Thoughts?

About testing, I would consider having a testcontainers module which can be published by itself, separate from other testing utilities.

Regarding the build tool, I'm more familiar with Gradle, but I'm fine either way.

[edeandrea]

Looks good! How about client instead of impl? I guess that will be the default client implementation, right? So the main packages published to Maven Central can be docling-api and docling-client. Thoughts?

I'm fine with that. Naming things is still the hardest thing to do in computer science :)

About testing, I would consider having a testcontainers module which can be published by itself, separate from other testing utilities.

Sure we can do that too.

Regarding the build tool, I'm more familiar with Gradle, but I'm fine either way.

I'm fine with Gradle. Its been a while since I used it, but I always thought it was a better tool than Maven :) (I'm sure I'll get some flack internally about saying that :) )

I'll get this set up today so that I'm not blocking anyone and we can start to work asynchronously. I probably won't have much time this week to work on this. I need to finish up something else before I can devote my full attention to this.