Use new maven rules

[steve-hb]

Hey,

I'm back from my business trip. This & next week I'm going to try migrating one of our large projects to Bazel using this plugin. If everything works fine, I'll write a comment below, otherwise I submit a patch or start a discussion.

#1

[steve-hb]

Today I tried it the first time:

• 1. I think I'll implement an option to provide custom templates (I'm using wrapper rules for some things).
• 2. The plugin identifies some of the modules as external maven dependencies. It's clear that this won't work.
• 3. We should use glob(["src/main/java/**/*.java"]) instead of writing hundreds of lines.
• 4. Modules only containing resources are not handled correctly: The Build files are empty
• 5. Local modules specified as dependencies are not resolved correctly: //:module_name won't work for modules located at //moduleGroup/group1/module_name .
  This could be solved by defining the complete path in every dependency or by providing aliases/wrappers in our root BUILD file.
• 6. The rule-names are too complex and long: We should provide options to use custom formats. (e.g. <fomat>%artifactId%</format> <fomat>%groupId_%artifactId%</format>

Next week (Tuesday or later) I'm looking forward to evaluate these things and maybe create Issues for them or implement them directly in this PR. @OrhanKupusoglu What do u think? New issues or not?

[OrhanKupusoglu]

New issues = too much bureaucracy
I think you can implement them in this PR with atomic commits (one and only one thing at a time)

[steve-hb]

New issues = too much bureaucracy

I'm a German - we know how bureaucracy works! :P

I started implementing all the things, but it will take about a week. I'm currently a little bit too busy.

// A week... nope. Too busy currently, will continue next months, maybe 2020

[OrhanKupusoglu]

Cheers