Hi,

as bootstrapping maven progresses (see my other post), the need for help
from Java-developers arises.

To finish all the work to be done after maven bootstrapping, some
experienced Java developers are needed. The following questions need to
be answered.

  * Designing the maven-build-system as follows:
      o How to maven commands map to our build phases? Should they map,
        should there be new ones?
      o Is there a need to clean up the pom-files prior to building,
        e.g. remove version numbers?
      o How to make the maven-build-system to never ever include other
        jar? Perhaps we need to post-process the generated jars.
      o How to handle pom-files (see below)

  * Which naming conventions should be used for packages? Maven has the
    notion of "group-id" and "atrtifact". Should this be kept? OTOH,
    there are very common packages like "commons-io" aka
    "apache-commons-io".

  * Where should the repo-files be kept in Guix? Debian seems to bot
    them into a dir-structure which I assume is leaned on some
    file-structure in the maven central repository. See
    <https://wiki.debian.org/Java/MavenRepoSpec>
    <https://wiki.debian.org/Java/MavenRepoHelper> and
    <https://packages.debian.org/jessie/maven-repo-helper>

  * Where to keep the pom-files? Are there other files we need (I've
    seen "effective pom", and "maven-fragments" in other distros)? Can
    or should we strip these files, like Debian seems to to with the
    maven-repo-helper? If so: What do we need? can this be done in guix,
    is there a maven-plugin, or …?

  * Help finding official sources, homepages, etc. for all packages. For
    many packages the data in the pom is outdated, since e.b.
    codehaus.org and code.google.com are gone.


Please comment!

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |