module support

[eed3si9n]

reported by @jxstanford

http://groups.google.com/group/scalaxb/browse_frm/thread/46a6b194e655cdeb

[ChrisL]

from http://scalaxb.org/multiple-schema-files:
'To assist the user, scalaxb looks for missing references in the current directory, but only in the current directory regardless of the URI or relative path specified in schemaLocation'

My suggestion: scalaxb should find all schemas specified in include and import statements (recursive), however code shall only be generated for types within this project's schemas.

Usage (via sbt):

• [Optional, referenced .jar may already be in place]
  
  run scalaxb and compile base projects: generates code for base projects' schemas
• run scalaxb and compile further projects referencing the base projects: generates code for these further projects, however base project schema classes are suppressed when generating the code thus the scala compiler will find the case classes defined in the base projects.

This should not only allow including foreign schemas with foreign .jars but it also allows developing your own base projects with base schemas independently from referencing projects.