You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by mc...@apache.org on 2004/06/16 03:57:06 UTC

svn commit: rev 21336 - in avalon/trunk/central/site/src/xdocs/central: about about/cop about/docs about/installation about/tutorials/advanced about/tutorials/basic tools tools/magic/model tools/maven

Author: mcconnell
Date: Tue Jun 15 18:57:06 2004
New Revision: 21336

Added:
   avalon/trunk/central/site/src/xdocs/central/about/cop/
      - copied from rev 21332, avalon/trunk/central/site/src/xdocs/central/about/docs/cop/
   avalon/trunk/central/site/src/xdocs/central/about/installation/
      - copied from rev 21332, avalon/trunk/central/site/src/xdocs/central/about/docs/installation/
   avalon/trunk/central/site/src/xdocs/central/about/installation/svn.xml
   avalon/trunk/central/site/src/xdocs/central/about/tutorials/advanced/
      - copied from rev 21332, avalon/trunk/central/site/src/xdocs/central/about/docs/advanced/
   avalon/trunk/central/site/src/xdocs/central/about/tutorials/basic/
      - copied from rev 21332, avalon/trunk/central/site/src/xdocs/central/about/docs/basic/
Removed:
   avalon/trunk/central/site/src/xdocs/central/about/docs/
Modified:
   avalon/trunk/central/site/src/xdocs/central/about/index.xml
   avalon/trunk/central/site/src/xdocs/central/about/installation/index.xml
   avalon/trunk/central/site/src/xdocs/central/about/installation/navigation.xml
   avalon/trunk/central/site/src/xdocs/central/about/navigation.xml
   avalon/trunk/central/site/src/xdocs/central/tools/magic/model/index.xml
   avalon/trunk/central/site/src/xdocs/central/tools/maven/navigation.xml
   avalon/trunk/central/site/src/xdocs/central/tools/navigation.xml
Log:
backing out the changes to central/about based on the overriding priority to focus of the flow of activity - download, evalutate, go back and read the background - and all of this info needs to availble on page 2 ... + plus some addition to magic documentation

Modified: avalon/trunk/central/site/src/xdocs/central/about/index.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/about/index.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/about/index.xml	Tue Jun 15 18:57:06 2004
@@ -10,7 +10,7 @@
       <p>
       Avalon Central is the place you can find 
       <a href="download.cgi">downloads</a> of the latest Avalon
-      products, <a href="docs/index.html">tutorials</a> to get 
+      products, <a href="tutorials/index.html">tutorials</a> to get 
       you up-to-speed as quickly as possible, together with information 
       about the <a href="../community/who/index.html">people</a> 
       who make up this community, and the latest 

Modified: avalon/trunk/central/site/src/xdocs/central/about/installation/index.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/about/docs/installation/index.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/about/installation/index.xml	Tue Jun 15 18:57:06 2004
@@ -41,6 +41,17 @@
             </td>
           </tr>
           <tr>
+            <td><a href="svn.html">Building Merlin from SVN</a></td>
+            <td>
+              <p>
+                Instruction on how to build the latest greatest version
+                of the Avalon platform.  These instructions are target towards
+                bleeding edge developers that are interested in tracking and 
+                contributing to the day to development and platform evolution.
+              </p>
+            </td>
+          </tr>
+          <tr>
             <td><a href="nt.html">Merlin NT Service</a></td>
             <td>
               <p>

Modified: avalon/trunk/central/site/src/xdocs/central/about/installation/navigation.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/about/docs/installation/navigation.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/about/installation/navigation.xml	Tue Jun 15 18:57:06 2004
@@ -23,6 +23,7 @@
 
   <body>
     <menu>
+      <item name="Source" href="svn.html"/>
       <item name="Binary" href="binary.html"/>
       <item name="NT Service" href="nt.html"/>
       <item name="Other Versions" href="archive/index.html"/>

Added: avalon/trunk/central/site/src/xdocs/central/about/installation/svn.xml
==============================================================================
--- (empty file)
+++ avalon/trunk/central/site/src/xdocs/central/about/installation/svn.xml	Tue Jun 15 18:57:06 2004
@@ -0,0 +1,40 @@
+<?xml version="1.0"?>
+
+<!-- 
+ Copyright 2004 Apache Software Foundation
+ Licensed  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.
+-->
+
+<document>
+
+  <properties>
+    <author email="dev@avalon.apache.org">Avalon Documentation Team</author>
+    <title>Avalon Central</title>
+  </properties> 
+
+  <body>
+    <section name="Building from SVN">
+
+      <p>IN PREPARATION BUT IN THE MEANTIME POST THE QUESTION TO dev@avalon.apache.org</p>
+
+    </section>
+  </body>
+
+</document>
+
+
+
+
+

Modified: avalon/trunk/central/site/src/xdocs/central/about/navigation.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/about/navigation.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/about/navigation.xml	Tue Jun 15 18:57:06 2004
@@ -25,15 +25,13 @@
     <menu>
       <item name="License" href="license.html"/>
       <item name="Downloads" href="download.cgi"/>
-      <item name="Documentation" href="docs/index.html"/>
-      <!--
       <item name="Installation" href="installation/index.html"/>
-      <item name="Component Oriented" href="cop/index.html"/>
-      <item name="Tutorials" href="tutorials/index.html"/>
-      -->
+      <item name="Concepts" href="cop/index.html"/>
+      <item name="Tutorials" href="tutorials/index.html"/>
       <item name="Resources" href="resources/index.html"/>
       <item name="News" href="news/index.html"/>
+      <item name="FAQ" href="faq.html"/>
     </menu>
- </body>
+ </body>
 
-</project>
+</project>

Modified: avalon/trunk/central/site/src/xdocs/central/tools/magic/model/index.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/tools/magic/model/index.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/tools/magic/model/index.xml	Tue Jun 15 18:57:06 2004
@@ -16,12 +16,100 @@
       for transitive inheritance of dependency information.
       </p>
       <p>
-      An example of a Magic project defintion is shown below:
+      An example of a Magic project defintion:
       </p>
-<source>
-</source>
+<source><![CDATA[
+<project basedir="../../runtime/framework/impl">
+  <info>
+    <group>avalon/framework</group>
+    <name>avalon-framework-impl</name>
+    <version>4.2.0</version>
+  </info>
+  <dependencies>
+    <include key="avalon-framework-api"/>
+  </dependencies>
+</project>
+]]></source>
+
+      <p>
+      The above XML fragment is taken from a index.xml file.  The index.xml 
+      contains the resource, project, and plugin defintions for a suite of 
+      interconnected systems.  Within magic, plugins and projects are derived
+      from the notion of a resouce.  A resource can be viewed as a logical 
+      artifact accessible from a repository cache using group, name and version 
+      information.  A project extends this concept to include a local basedir 
+      refernce (the root of the project directory) and a set of dependencies.
+      Plugins extend the concept of project to include the delcaration of 
+      the Ant tasks they provide to the classic ant build environment. 
+      </p>
+
+      <p>
+      Dependendency declarations within a project refernce the name of another 
+      another project within the scope of an index.xml file.  As such, a 
+      dependency declaration can be resolved to an artifact group, name, version
+      and type, and from this information, a repository based resource can be 
+      resolved, or in the case of a project or plugin reference, a target can be 
+      built as part of a higher-level build scenario. 
+      </p>
+
+      <p>
+      The declaration of dependendency implicitly introduced a dependency 
+      by the dependee on the dependent of the dependency. In other words, dependency
+      declarations are transative.  Magic provides support for the qualification of 
+      transativate dependency inheritance relative to the following four policies: 
+      </p>
+
+      <ul>
+        <li>ANY</li>
+        <li>BUILD</li>
+        <li>TEST</li>
+        <li>RUNTIME</li>
+      </ul>
+
+      <p>
+      A set of ant tasks use magic dependency information to construct respective  
+      classpaths and classloaders when executing classic ant tasks such as 
+      javac, junit, or custom tasks dealing with runtime artifacts (e.g. dynamic plugin
+      loading, plugin data generators, deployment meta-data, etc., etc. )
+      </p>
+
+      <p>
+      In the case of RUNTIME dependencies, Magic differntiates between the following
+      classloader categories.
+      </p>
+
+      <ul>
+        <li>ANY</li>
+        <li>API</li>
+        <li>SPI</li>
+        <li>IMPL</li>
+      </ul>
+
+      <p>
+      A dependency declared as RUNTIME enabled with a tag API
+      will result in the aggreggation of all of the dependents of the dependant within
+      an API path scope.  The same principal holds true for SPI and IMPL tags with 
+      the exception of non-repition of path entires in lower-level path declarations.
+      In the impication of the term "lower-level" is realtive to the ordering of classloaders
+      resolved from API, SPI and IMPL path declarations.  An IMPL classloader has a SPI
+      classloader as parent, and in turn an SPI classloader has an API as parent. This
+      chaining of classloaders provides the posibility for embedded applications to 
+      control which classloader is supplied to their runtime sub-systems.  For example, 
+      a plugin executing withing a particular environment can cotrol which classloader is 
+      used (typically an API or SPI loader) when deployed child units (plugins, components, 
+      etc.).
+      </p>
+
+      <p>
+      While technically duanting, the above classloader chaining strategy delivers
+      the potential for applications to take control over the management of resourse 
+      isolation - a fundamental security principal in component-based-development.
+      Secondly, the actual implementation of classloader chaining becomes 
+      strait-forward once a declarative model is put in place.
+      </p> 
+
+    </section>
 
-    </section>
   </body>
 
 </document>

Modified: avalon/trunk/central/site/src/xdocs/central/tools/maven/navigation.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/tools/maven/navigation.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/tools/maven/navigation.xml	Tue Jun 15 18:57:06 2004
@@ -23,8 +23,8 @@
 
   <body>
     <menu>
-      <item name="Meta" href="meta/index.html"/>
-      <item name="Merlin" href="merlin/index.html"/>
+      <item name="Maven Meta Plugin" href="meta/index.html"/>
+      <item name="Maven Merlin Plugin" href="merlin/index.html"/>
     </menu>
   </body>
 

Modified: avalon/trunk/central/site/src/xdocs/central/tools/navigation.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/tools/navigation.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/tools/navigation.xml	Tue Jun 15 18:57:06 2004
@@ -24,8 +24,8 @@
  <body>
     <menu>
       <item name="Magic" href="magic/index.html"/>
-      <item name="Optional Plugins" href="plugins/index.html"/>
-      <item name="Legacy Support" href="maven/index.html"/>
+      <item name="Plugins" href="plugins/index.html"/>
+      <item name="Legacy" href="maven/index.html"/>
     </menu>
  </body>
 

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org


Re: svn commit: rev 21336 -

Posted by J Aaron Farr <fa...@apache.org>.
J Aaron Farr wrote:
> mcconnell@apache.org wrote:
> 
>>
>> backing out the changes to central/about based on the overriding 
>> priority to focus of the flow of activity - download, evalutate, go 
>> back and read the background - and all of this info needs to availble 
>> on page 2 ... + plus some addition to magic documentation
>>
> 
> Stephen,
> 
> You asked for help and suggestions.  If you're going to rollback 
> someone's changes, it works a lot better if you mention something on the 
> mailing list first so we can discuss the whys and wherefores.  You might 
> even find out that the author will agree with your rollback reasons and 
> will feel less brushed aside than simply JFDI without any attempt at 
> collaboration.

Stephen,

Sorry for the flame.  I didn't see or get your other response on the 
mailing list until after I had sent this.  However, I still think the 
best policy on rollbacks is to send to the mailing list first and then 
commit.

jaaron


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: svn commit: rev 21336 -

Posted by J Aaron Farr <fa...@apache.org>.
mcconnell@apache.org wrote:
>
> backing out the changes to central/about based on the overriding priority to focus of the flow of activity - download, evalutate, go back and read the background - and all of this info needs to availble on page 2 ... + plus some addition to magic documentation
> 

Stephen,

You asked for help and suggestions.  If you're going to rollback 
someone's changes, it works a lot better if you mention something on the 
mailing list first so we can discuss the whys and wherefores.  You might 
even find out that the author will agree with your rollback reasons and 
will feel less brushed aside than simply JFDI without any attempt at 
collaboration.

jaaron

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org