------
 Managing Project Classloader
 ------
 Nicolas De loof
 ------
18 May 2009
 ------

~~ Licensed to the Apache Software Foundation (ASF) under one
~~ or more contributor license agreements.  See the NOTICE file
~~ distributed with this work for additional information
~~ regarding copyright ownership.  The ASF licenses this file
~~ to you under the Apache License, Version 2.0 (the
~~ "License"); you may not use this file except in compliance
~~ with the License.  You may obtain a copy of the License at
~~
~~   http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing,
~~ software distributed under the License is distributed on an
~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~~ KIND, either express or implied.  See the License for the
~~ specific language governing permissions and limitations
~~ under the License.

~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html


Managing project classloader

  Many plugins have to lauch a class using a custom classloader that mixes a plugin dependency (the tool) with the
  project dependencies and classpath elements.

* Usage

   ProjectClassLoaderUtil has static methods to created the required URLClassLoader using the MavenProject. The
   classpath is built depending on standard Artifact scopes, and may include project source roots.

   Optionnaly, the constructed ClassLoader can include some more artifacts, for example the one obtained from 
   Maven with expression <<<${plugin.artifacts}>>>.