Refactor java folder to follow Maven/Gradle convention

[magreenblatt]

Original report by Paul Furbacher (Bitbucket: Paul Furbacher).

---

There's a widely adopted, standard way of setting up Java source and test directories/folders, first specified by Maven and continued in Gradle.

java-cef doesn't honor this convention, but it there's no reason it shouldn't.

The current folder structure:

java-cef/
    java/
        org/
        tests/

should be refactored to

java-cef
    src/
        main/
            java/
                org/...
        test/
            java/
                tests/...

In addition, the tests folder should be refactored to

java-cef/
    src/
        test/
            org/
                cef/
                    demos/
                        detailed/ 
                        simple/

Given the nature of the "tests" (they don't run in a test harness), I'd favor either "demos" or "examples".

[magreenblatt]

Why is this necessary? Is there some tooling you're trying to use that does not work with the current directory layout?

[magreenblatt]

Original comment by Paul Furbacher (Bitbucket: Paul Furbacher).

---

It's not necessary, that's why I set the issue type to "proposal" and priority to "minor".

Reasons:

1. Convention
2. Tooling

I don't know, I've been doing Java development since 1997. I have found it's generally good to follow conventions. Most Java developers use the Maven/Gradle project structure, even when it includes building native libs, etc.

And it's not that for example, Gradle won't work with this folder structure:

sourceSets { 
    // Make allowance for unconventional folder hierarchy ...
    main {
        java {
            srcDir 'java'
        }
    }
}

accommodates it.

And there is a Java project convention around "tests". They are run in a test harness (e.g., JUnit, Selenium). What you present are examples, demos, uses. Hence the proposal to align the naming and project structure accordingly in this regard.

Just suggestions; you can close this issue if you don't feel I've made a compelling enough case.

[magreenblatt]

If we proceed with Maven support then we should roll in issue #262 and issue #189 which discuss distribution.

[magreenblatt]

Proposed PR here: https://bitbucket.org/chromiumembedded/java-cef/pull-requests/20

[magreenblatt]

Maven build/config is now available at https://github.com/jcefmaven/jcefmaven