Downloading and installing maven artifacts as modules

[Mandy Chung]

On 09/19/11 05:09, Alan Bateman wrote:
>
> The migration and interop section of the requirements document has a 
> requirement to be able to download, install and resolve Maven 
> artifacts as if they were modules. I've hacked up a prototype, as a 
> demo module, that downloads artifacts and their transitive 
> dependencies and installs them as modules. The idea is to make it easy 
> to use popular libraries as modules and to tease out the issues that 
> such interop would bring. The webrev is here:
>
> http://cr.openjdk.java.net/~alanb/MavenDemo/webrev.01/
>
I went through the webrev which looks good as a demo. It's okay
for now to install this module demo as part of make/modules in
the post-processing step.  The modules build will be clean up
at some point in time and include to build the demo/sample modules
in the proper place.  Also this demo might be just temporary
and could be replaced by the future work.  Some comments below.

README.txt
   [-L library] option is an option to the demo.MavenImport.  Since
   demo.MavenImport a module and it can be installed in a module
  library, it would be confusing:

    $ java -L mlib -m demo.MavenImport -L maven-module-lib

     where mlib is the library where demo.MavenImport is installed
     and maven-module-lib is the library to install the modules
     imported from maven into.

Main.java
    L48: typo "comamnd-line" should be "command-line"
    L140: You can call Library.systemLibraryPath() or Library.openSystemLibrary()|
    to get the system module library rather than hardcoding the pathname.
|

|Pom.java|
    L190: I think it's a typo {@code jar}?

Mandy