Nice!

Alex Karasulu wrote:
Hi all,

I started cleaning up and organizing the Asyncweb subproject today which
entailed:

   o moving Asyncweb out of the sandbox into the new structure discussed
here [0] with slight differences
   o moving filter-codec-http into Asyncweb as a module
   o changing package names
   o moving 3 classes of protocol-http-client into Asyncweb as a module
   o cleaning up NOTICE.txt and LICENSE.txt files
   o cleaning up problems resulting from back and forth movement of the HTTP
codec

Here's what the present directory structure of asyncweb looks like as seen
here [1]:

   ... mina/asyncweb
          .
          |-- branches
          |-- tags
          `-- trunk
              |-- LICENSE.txt
              |-- NOTICE.txt
              |-- assembly
              |-- client
              |-- common
              |-- examples
              |-- pom.xml
              |-- server
              `-- spring

There are 6 modules here.  Some points about the module migrations and name
changes: [NOTE: Below the module name based on the maven POM's <name> tag is
used.]


Module: Apache Asyncweb Common
-----------------------------------------------------

Most of a common package containing the HttpXxxxx interfaces was, as shown
earlier, re-factored and moved into the MINA subproject along with the HTTP
codec into the MINA filter-codec-http module.  Asyncweb is not concerned
with advertising that this module and it's artifact is a MINA codec which a
small part of it contains.  Furthermore this module is shared between the
http client AHC (3 classes) and the Asyncweb server. Because of these
reasons it was best called the asyncweb-common module.  Again the fact that
this module contains a codec is irrelevant.


Module: Apache Asyncweb Client
-------------------------------------------------

The Asyncweb Client module is comprised of 3 Java source files and
represents the previous protocol-http-client which was referred to as Async
HTTP Client (AHC).  This module depends on and uses the Asyncweb Common API
and the HTTP codec within it to function.  Hence as discussed and out of
common sense this protocol-http-client module in the MINA subproject was
moved under Asyncweb as the Apache Asyncweb Client module.


Module: Apache Asyncweb Server
--------------------------------------------------

This represents the old Asyncweb 'core' module from the sandbox with the
mentioned cleanups.


Module: Apache Asyncweb Spring
--------------------------------------------------

This represents the old Asyncweb 'springframework' integration module from
the sandbox with the mentioned cleanups.


Module: Apache Asyncweb Examples
-------------------------------------------------------

This represents the old Asyncweb 'example' module from the sandbox with the
mentioned cleanups.


Module: Apache Asyncweb Assembly
-------------------------------------------------------

This represents the old Asyncweb 'assembly' module from the sandbox with
minor cleanups.

I hope everyone has a chance to take a look, build etc and give feedback.
If curious and you don't have the time here's what the build run output
looks like with these names and this structure.

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Apache Asyncweb Parent
[INFO]   Apache Asyncweb Common
[INFO]   Apache Asyncweb Server
[INFO]   Apache Asyncweb Client
[INFO]   Apache Asyncweb Spring
[INFO]   Apache Asyncweb Examples
...
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] Apache Asyncweb Parent ................................ SUCCESS [
1.856s]
[INFO] Apache Asyncweb Common ................................ SUCCESS [
4.871s]
[INFO] Apache Asyncweb Server ................................ SUCCESS [
3.959s]
[INFO] Apache Asyncweb Client ................................ SUCCESS [
11.553s]
[INFO] Apache Asyncweb Spring ................................ SUCCESS [
0.668s]
[INFO] Apache Asyncweb Examples .............................. SUCCESS [
0.795s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------


I hope this report clarifies the changes and helps people get back up to
speed with Asyncweb.

Thanks,
Alex

--------

[0] Directory Restructuring Thread - http://tinyurl.com/23dclx
[1] Asynchweb in Subversion - http://svn.apache.org/repos/asf/mina/asyncweb

Reply via email to