You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by cz...@apache.org on 2004/02/24 15:19:28 UTC
cvs commit: avalon-excalibur/lifecycle/api project.xml
cziegeler 2004/02/24 06:19:28
Modified: lifecycle/src/xdocs extension.xml book.xml interfaces.xml
fortress.xml tabs.xml merlin.xml index.xml
lifecycle/site maven.xml project.xml project.properties
lifecycle/api/src/java/org/apache/avalon/lifecycle
Creator.java Accessor.java
lifecycle/impl/src/java/org/apache/avalon/lifecycle
AbstractAccessor.java AbstractCreator.java
lifecycle/impl project.xml
lifecycle maven.xml project.properties LICENSE.TXT build.xml
project.xml
lifecycle/api project.xml
Log:
Moving to license 2.0
Revision Changes Path
1.5 +298 -283 avalon-excalibur/lifecycle/src/xdocs/extension.xml
Index: extension.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/src/xdocs/extension.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- extension.xml 7 Jul 2003 16:52:44 -0000 1.4
+++ extension.xml 24 Feb 2004 14:19:27 -0000 1.5
@@ -1,283 +1,298 @@
-<?xml version="1.0"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
-
-<document>
- <header>
- <title>Lifecycle Extensions</title>
- <authors>
- <person name="Avalon Development Team" email="dev@avalon.apache.org"/>
- </authors>
- </header>
- <body>
-
- <section><title>What are lifecycle extensions ?</title>
- <p>
- Lifecycle extensions are additional stages a component can traverse through during
- it's lifetime. Lifecycle extensions allow a container to provide extra functionality
- to components in addition to the standard stages defined by Avalon Framework.
- </p>
-
- <p>
- Avalon Framework defines a set of standard interfaces often termed as Lifecycle
- stages that can be used by a container to determine the components requirements
- during deployment and subsequent decommissioning.
- </p>
-
- <p>
- These interfaces allows the developer to separate the various concerns involved when
- writing a component. Often termed SoC and IoC (Separation of Concerns and Inversion of
- Control), these concepts represent one of the primary advantages of using Avalon.
- </p>
-
- <p>
- Sometimes it's useful to extend this development paradigm from the framework level
- into the application domain, to create customized lifecycle extensions that are called
- upon in addition to the standard set defined by the Avalon Framework.
- </p>
-
- <p>
- Such custom lifecycle stages can further enable domain specific logic across many,
- perhaps even unrelated components, can reduce code duplication, and allows the developer
- to reuse the same development and thinking paradigm as the standard lifecycle stages.
- </p>
-
- <p>
- For example, you might want to pass a specialized SecurityManager to some of your
- components before they are initialized, or have their internal state persistently cached
- during system shutdown and restored at during startup. You might want to pass user
- dependent decryption keys to your component, or give components the opportunity to
- recycle themselves before being disposed or returned to a pooled component handler.
- </p>
-
- <p>
- The possibilities and number of extensions are only limited by the requirements of your
- particular application domain.
- </p>
-
- <p>
- This document describes how to add new lifecycle extensions using <strong>Fortress</strong>
- and <strong>Merlin</strong> containers.
- This document assumes a knowledge of what an Avalon lifecycle is, and a basic understanding
- of the standard lifecycle interfaces Avalon Framework defines. References in this document to
- Service and ServiceManager can also be freely interpreted as Component and ComponentManager
- by the reader.
- </p>
-
- <note>As at the time of writing, Fortress and Merlin is the only Avalon container that
- supports lifecycle extensions, which means components that use this feature will not work
- with the other Avalon containers (ExcaliburComponentManager, Phoenix, Tweety, etc)</note>
-
- <p>
- Support for lifecycle extensions in the other Avalon containers is technically possible but
- has not yet been discussed. Please check with the Avalon developer mailing list if you use
- one of these containers and would like to use lifecycle extensions.
- </p>
-
- </section>
-
- <section><title>How do I extend a Component's lifecycle ?</title>
- <p>
- Extending a Component's lifecycle is straightforward. An overview of the process
- follows:
- </p>
-
- <ol>
- <li>Define the new component interface
-
- <br/><br/>
- Create the new interface defining the operations that should be called upon components
- that implement this interface. Using the previously mentioned examples, this would be
- your <code>SecurityManageable</code>, <code>Cacheable</code>, <code>Decryptable</code>,
- <code>Recycleable</code> interfaces.
- </li>
-
- <li>Define an extension object that calls upon the methods defined in the new interface,
- during one or more of the pre-defined phases of component's lifecycle
-
- <br/><br/>
- Create a class that implements the <code>Creator</code> and/or <code>Accessor</code>
- interfaces and implemets the interaction with target components supplied under the
- create, destroy, access and relase operations.
- </li>
-
- <li>Register your extension object
-
- <br/><br/>
- This depends on the container you are using. In
- Merlin you need to include the <extensions> tag in the component .xinfo file and
- Merlin will automatically recognize it. In Fortress you register the extension object
- with a <code>LifecycleExtensionManager</code>
- </li>
-
- <li>Implement the new component interface on your component
- <br/><br/>
-
- Add the new <code>implements</code> clause to your Component, or Component implementation,
- and write any methods defined in the implemented interface.
- <br/><br/>
-
- Proceed as normal. Checking for extensions is done implicitly within both Fortress and
- Merlin. Once lifecycle extensions are registered they will be activated during the 4
- phases defined later in this document.
- </li>
- </ol>
- </section>
-
- <section><title>When can a Component's lifecycle be extended ?</title>
- <p>
- The life of any component can be broken down to the following phases:
- </p>
-
- <ol>
- <li>Creation
-
- <br/><br/>
- When the component is instantiated.
- </li>
-
- <li>Access
-
- <br/><br/>
- When the component is accessed via a ServiceManager/Selector
- (<code>lookup()/select()</code>).
- </li>
-
- <li>Release
-
- <br/><br/>
- When the component is released via a ServiceManager/Selector (<code>release()</code>).
- </li>
-
- <li>Destruction
-
- <br/><br/>
- When the component is decommissioned, ready for garbage collection.
-
- </li>
-
- </ol>
-
- <note>A component will go through it's Creation and Destruction phase only once. Since
- extension classes can implement different handling strategies (Poolable, ThreadSafe,
- etc), the access and release phases of a component can be applied multiple times.</note>
-
- <p>
- Lifecycle extensions can be added to any of the above defined phases. This allows
- you to control the interception point your particular extension will be applied under.
- </p>
-
- <p>
- For example, thread or user dependent extensions would be added at the access and release
- levels (ie. when the component is retrieved and returned to the ServiceManager) as they
- depend on runtime data not available until they are actually used.
- </p>
-
- <p>
- More static, or global extensions would be added at the creation or destruction level, since
- they do not depend on any external data that change during runtime, nor are they particular
- to any one context of use.
- </p>
-
- </section>
-
- <section><title>Lifestyle Extension Interfaces</title>
-
- <p>
- A container manages extensions using an extension handler. Handlers may implement
- the <code>Creator</code> and/or <code>Accessor</code> interfaces. A creator extension
- will be activated during the create and destroy stages of a component lifecycle. A
- accessor extension will be activated during the access and release stages.
- </p>
-
- <section><title>The Creator Interface</title>
-
-<p>The <code>Creator</code> interface describes the create and destroy
-stages that occur between a component and a container
-during service management. Lifecycle extensions supporting create
-and destroy stages must implement this interface.</p>
-
- <source>
- package org.apache.avalon.lifecycle;
-
- import org.apache.avalon.framework.context.Context;
-
- public interface Creator
- {
- /**
- * Create stage handler.
- *
- * @param object the object that is being created
- * @param context the context instance required by the create handler
- * implementation
- * @exception Exception if an error occurs
- */
- void create( Object object, Context context )
- throws Exception;
-
- /**
- * Destroy stage handler.
- *
- * @param object the object that is being destroyed
- * @param context the context instance required by the handler
- * implementation
- */
- void destroy( Object object, Context context );
-
- }
- </source>
- </section>
-
- <section><title>Accessor Interface</title>
-<p>
-The <code>Accessor</code> interface describes the access and release
-stages that occur between a service or component manager and a container
-during service deployment. Lifecycle extensions supporting access
-and release stages must implement this interface.
-</p>
-<source>
- package org.apache.avalon.lifecycle;
-
- import org.apache.avalon.framework.context.Context;
-
- public interface Accessor
- {
- /**
- * Access stage handler.
- *
- * @param object the object that is being accessed
- * @param context the context instance required by the access handler
- * implementation
- * @exception Exception if an error occurs
- */
- void access( Object object, Context context )
- throws Exception;
-
- /**
- * Release stage handler.
- *
- * @param object the object that is being released
- * @param context the context instance required by the release handler
- * implementation
- */
- void release( Object object, Context context );
-
- }
-</source>
- </section>
- </section>
-
- <section><title>Need more information ?</title>
- <p>
- If you have any particular questions, comments, etc, please send an email to the Avalon
- developer mailing <link href="mailto:dev@avalon.apache.org">list</link>.
- </p>
- </section>
-
- </body>
- <footer>
- <legal>
- Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision$ $Date$
- </legal>
- </footer>
-</document>
+<?xml version="1.0"?>
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
+<!--
+ 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>
+ <header>
+ <title>Lifecycle Extensions</title>
+ <authors>
+ <person name="Avalon Development Team" email="dev@avalon.apache.org"/>
+ </authors>
+ </header>
+ <body>
+
+ <section><title>What are lifecycle extensions ?</title>
+ <p>
+ Lifecycle extensions are additional stages a component can traverse through during
+ it's lifetime. Lifecycle extensions allow a container to provide extra functionality
+ to components in addition to the standard stages defined by Avalon Framework.
+ </p>
+
+ <p>
+ Avalon Framework defines a set of standard interfaces often termed as Lifecycle
+ stages that can be used by a container to determine the components requirements
+ during deployment and subsequent decommissioning.
+ </p>
+
+ <p>
+ These interfaces allows the developer to separate the various concerns involved when
+ writing a component. Often termed SoC and IoC (Separation of Concerns and Inversion of
+ Control), these concepts represent one of the primary advantages of using Avalon.
+ </p>
+
+ <p>
+ Sometimes it's useful to extend this development paradigm from the framework level
+ into the application domain, to create customized lifecycle extensions that are called
+ upon in addition to the standard set defined by the Avalon Framework.
+ </p>
+
+ <p>
+ Such custom lifecycle stages can further enable domain specific logic across many,
+ perhaps even unrelated components, can reduce code duplication, and allows the developer
+ to reuse the same development and thinking paradigm as the standard lifecycle stages.
+ </p>
+
+ <p>
+ For example, you might want to pass a specialized SecurityManager to some of your
+ components before they are initialized, or have their internal state persistently cached
+ during system shutdown and restored at during startup. You might want to pass user
+ dependent decryption keys to your component, or give components the opportunity to
+ recycle themselves before being disposed or returned to a pooled component handler.
+ </p>
+
+ <p>
+ The possibilities and number of extensions are only limited by the requirements of your
+ particular application domain.
+ </p>
+
+ <p>
+ This document describes how to add new lifecycle extensions using <strong>Fortress</strong>
+ and <strong>Merlin</strong> containers.
+ This document assumes a knowledge of what an Avalon lifecycle is, and a basic understanding
+ of the standard lifecycle interfaces Avalon Framework defines. References in this document to
+ Service and ServiceManager can also be freely interpreted as Component and ComponentManager
+ by the reader.
+ </p>
+
+ <note>As at the time of writing, Fortress and Merlin is the only Avalon container that
+ supports lifecycle extensions, which means components that use this feature will not work
+ with the other Avalon containers (ExcaliburComponentManager, Phoenix, Tweety, etc)</note>
+
+ <p>
+ Support for lifecycle extensions in the other Avalon containers is technically possible but
+ has not yet been discussed. Please check with the Avalon developer mailing list if you use
+ one of these containers and would like to use lifecycle extensions.
+ </p>
+
+ </section>
+
+ <section><title>How do I extend a Component's lifecycle ?</title>
+ <p>
+ Extending a Component's lifecycle is straightforward. An overview of the process
+ follows:
+ </p>
+
+ <ol>
+ <li>Define the new component interface
+
+ <br/><br/>
+ Create the new interface defining the operations that should be called upon components
+ that implement this interface. Using the previously mentioned examples, this would be
+ your <code>SecurityManageable</code>, <code>Cacheable</code>, <code>Decryptable</code>,
+ <code>Recycleable</code> interfaces.
+ </li>
+
+ <li>Define an extension object that calls upon the methods defined in the new interface,
+ during one or more of the pre-defined phases of component's lifecycle
+
+ <br/><br/>
+ Create a class that implements the <code>Creator</code> and/or <code>Accessor</code>
+ interfaces and implemets the interaction with target components supplied under the
+ create, destroy, access and relase operations.
+ </li>
+
+ <li>Register your extension object
+
+ <br/><br/>
+ This depends on the container you are using. In
+ Merlin you need to include the <extensions> tag in the component .xinfo file and
+ Merlin will automatically recognize it. In Fortress you register the extension object
+ with a <code>LifecycleExtensionManager</code>
+ </li>
+
+ <li>Implement the new component interface on your component
+ <br/><br/>
+
+ Add the new <code>implements</code> clause to your Component, or Component implementation,
+ and write any methods defined in the implemented interface.
+ <br/><br/>
+
+ Proceed as normal. Checking for extensions is done implicitly within both Fortress and
+ Merlin. Once lifecycle extensions are registered they will be activated during the 4
+ phases defined later in this document.
+ </li>
+ </ol>
+ </section>
+
+ <section><title>When can a Component's lifecycle be extended ?</title>
+ <p>
+ The life of any component can be broken down to the following phases:
+ </p>
+
+ <ol>
+ <li>Creation
+
+ <br/><br/>
+ When the component is instantiated.
+ </li>
+
+ <li>Access
+
+ <br/><br/>
+ When the component is accessed via a ServiceManager/Selector
+ (<code>lookup()/select()</code>).
+ </li>
+
+ <li>Release
+
+ <br/><br/>
+ When the component is released via a ServiceManager/Selector (<code>release()</code>).
+ </li>
+
+ <li>Destruction
+
+ <br/><br/>
+ When the component is decommissioned, ready for garbage collection.
+
+ </li>
+
+ </ol>
+
+ <note>A component will go through it's Creation and Destruction phase only once. Since
+ extension classes can implement different handling strategies (Poolable, ThreadSafe,
+ etc), the access and release phases of a component can be applied multiple times.</note>
+
+ <p>
+ Lifecycle extensions can be added to any of the above defined phases. This allows
+ you to control the interception point your particular extension will be applied under.
+ </p>
+
+ <p>
+ For example, thread or user dependent extensions would be added at the access and release
+ levels (ie. when the component is retrieved and returned to the ServiceManager) as they
+ depend on runtime data not available until they are actually used.
+ </p>
+
+ <p>
+ More static, or global extensions would be added at the creation or destruction level, since
+ they do not depend on any external data that change during runtime, nor are they particular
+ to any one context of use.
+ </p>
+
+ </section>
+
+ <section><title>Lifestyle Extension Interfaces</title>
+
+ <p>
+ A container manages extensions using an extension handler. Handlers may implement
+ the <code>Creator</code> and/or <code>Accessor</code> interfaces. A creator extension
+ will be activated during the create and destroy stages of a component lifecycle. A
+ accessor extension will be activated during the access and release stages.
+ </p>
+
+ <section><title>The Creator Interface</title>
+
+<p>The <code>Creator</code> interface describes the create and destroy
+stages that occur between a component and a container
+during service management. Lifecycle extensions supporting create
+and destroy stages must implement this interface.</p>
+
+ <source>
+ package org.apache.avalon.lifecycle;
+
+ import org.apache.avalon.framework.context.Context;
+
+ public interface Creator
+ {
+ /**
+ * Create stage handler.
+ *
+ * @param object the object that is being created
+ * @param context the context instance required by the create handler
+ * implementation
+ * @exception Exception if an error occurs
+ */
+ void create( Object object, Context context )
+ throws Exception;
+
+ /**
+ * Destroy stage handler.
+ *
+ * @param object the object that is being destroyed
+ * @param context the context instance required by the handler
+ * implementation
+ */
+ void destroy( Object object, Context context );
+
+ }
+ </source>
+ </section>
+
+ <section><title>Accessor Interface</title>
+<p>
+The <code>Accessor</code> interface describes the access and release
+stages that occur between a service or component manager and a container
+during service deployment. Lifecycle extensions supporting access
+and release stages must implement this interface.
+</p>
+<source>
+ package org.apache.avalon.lifecycle;
+
+ import org.apache.avalon.framework.context.Context;
+
+ public interface Accessor
+ {
+ /**
+ * Access stage handler.
+ *
+ * @param object the object that is being accessed
+ * @param context the context instance required by the access handler
+ * implementation
+ * @exception Exception if an error occurs
+ */
+ void access( Object object, Context context )
+ throws Exception;
+
+ /**
+ * Release stage handler.
+ *
+ * @param object the object that is being released
+ * @param context the context instance required by the release handler
+ * implementation
+ */
+ void release( Object object, Context context );
+
+ }
+</source>
+ </section>
+ </section>
+
+ <section><title>Need more information ?</title>
+ <p>
+ If you have any particular questions, comments, etc, please send an email to the Avalon
+ developer mailing <link href="mailto:dev@avalon.apache.org">list</link>.
+ </p>
+ </section>
+
+ </body>
+ <footer>
+ <legal>
+ Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
+ $Revision$ $Date$
+ </legal>
+ </footer>
+</document>
1.2 +16 -1 avalon-excalibur/lifecycle/src/xdocs/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/src/xdocs/book.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- book.xml 11 Mar 2003 15:55:15 -0000 1.1
+++ book.xml 24 Feb 2004 14:19:27 -0000 1.2
@@ -1,6 +1,21 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "book-cocoon-v10.dtd">
-
+<!--
+ 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.
+-->
<book software="Excalibur Lifecycle Extensions" title="Excalibur Lifecycle Extensions" copyright="@year@ The Apache Software Foundation" xmlns:xlink="http://www.w3.org/1999/xlink">
1.3 +17 -2 avalon-excalibur/lifecycle/src/xdocs/interfaces.xml
Index: interfaces.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/src/xdocs/interfaces.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- interfaces.xml 11 Mar 2003 15:53:56 -0000 1.2
+++ interfaces.xml 24 Feb 2004 14:19:27 -0000 1.3
@@ -1,6 +1,21 @@
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
-
+<!--
+ 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>
<header>
<title>Extension Interfaces</title>
1.3 +17 -2 avalon-excalibur/lifecycle/src/xdocs/fortress.xml
Index: fortress.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/src/xdocs/fortress.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fortress.xml 11 Mar 2003 15:53:56 -0000 1.2
+++ fortress.xml 24 Feb 2004 14:19:27 -0000 1.3
@@ -1,6 +1,21 @@
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
-
+<!--
+ 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>
<header>
<title>Fortress Lifecycle Extensions</title>
1.3 +16 -1 avalon-excalibur/lifecycle/src/xdocs/tabs.xml
Index: tabs.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/src/xdocs/tabs.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- tabs.xml 16 Apr 2003 08:25:34 -0000 1.2
+++ tabs.xml 24 Feb 2004 14:19:27 -0000 1.3
@@ -1,6 +1,21 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN" "tab-cocoon-v10.dtd">
-
+<!--
+ 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.
+-->
<tabs software="Excalibur collections"
title="Excalibur collections"
copyright="Foo"
1.3 +17 -2 avalon-excalibur/lifecycle/src/xdocs/merlin.xml
Index: merlin.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/src/xdocs/merlin.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- merlin.xml 11 Mar 2003 15:53:56 -0000 1.2
+++ merlin.xml 24 Feb 2004 14:19:27 -0000 1.3
@@ -1,6 +1,21 @@
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
-
+<!--
+ 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>
<header>
<title>Lifecycle Extensions</title>
1.3 +17 -2 avalon-excalibur/lifecycle/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/src/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 11 Mar 2003 15:53:56 -0000 1.2
+++ index.xml 24 Feb 2004 14:19:27 -0000 1.3
@@ -1,6 +1,21 @@
<?xml version="1.0"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
-
+<!--
+ 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>
<header>
1.2 +16 -0 avalon-excalibur/lifecycle/site/maven.xml
Index: maven.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/site/maven.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- maven.xml 2 Oct 2003 03:07:21 -0000 1.1
+++ maven.xml 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,3 +1,19 @@
+<!--
+ 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.
+-->
<project default="site" xmlns:maven="jelly:maven" xmlns:j="jelly:core" xmlns:util="jelly:util" xmlns:ant="jelly:ant">
<property file="${basedir}/build.properties"/>
1.2 +16 -1 avalon-excalibur/lifecycle/site/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/site/project.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.xml 2 Oct 2003 03:07:21 -0000 1.1
+++ project.xml 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,5 +1,20 @@
<?xml version="1.0" encoding="UTF-8"?>
-
+<!--
+ 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.
+-->
<project>
<extend>${basedir}/../project.xml</extend>
1.2 +17 -0 avalon-excalibur/lifecycle/site/project.properties
Index: project.properties
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/site/project.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.properties 2 Oct 2003 03:07:21 -0000 1.1
+++ project.properties 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,3 +1,20 @@
+#
+# 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.
+#
+#
#
# Banner background and foreground colors.
1.2 +17 -50 avalon-excalibur/lifecycle/api/src/java/org/apache/avalon/lifecycle/Creator.java
Index: Creator.java
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/api/src/java/org/apache/avalon/lifecycle/Creator.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Creator.java 2 Oct 2003 03:07:21 -0000 1.1
+++ Creator.java 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,52 +1,19 @@
-/*
-
- ============================================================================
- The Apache Software License, Version 1.1
- ============================================================================
-
- Copyright (C) 1999-2002 The Apache Software Foundation. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modifica-
- tion, are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- 3. The end-user documentation included with the redistribution, if any, must
- include the following acknowledgment: "This product includes software
- developed by the Apache Software Foundation (http://www.apache.org/)."
- Alternately, this acknowledgment may appear in the software itself, if
- and wherever such third-party acknowledgments normally appear.
-
- 4. The names "Jakarta", "Apache Avalon", "Avalon Framework" and
- "Apache Software Foundation" must not be used to endorse or promote
- products derived from this software without prior written
- permission. For written permission, please contact apache@apache.org.
-
- 5. Products derived from this software may not be called "Apache", nor may
- "Apache" appear in their name, without prior written permission of the
- Apache Software Foundation.
-
- THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
- INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
- INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
- DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
- ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
- THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- This software consists of voluntary contributions made by many individuals
- on behalf of the Apache Software Foundation. For more information on the
- Apache Software Foundation, please see <http://www.apache.org/>.
-
-*/
+/*
+ * Copyright 2003-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.
+ */
package org.apache.avalon.lifecycle;
import org.apache.avalon.framework.context.Context;
1.2 +17 -50 avalon-excalibur/lifecycle/api/src/java/org/apache/avalon/lifecycle/Accessor.java
Index: Accessor.java
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/api/src/java/org/apache/avalon/lifecycle/Accessor.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Accessor.java 2 Oct 2003 03:07:21 -0000 1.1
+++ Accessor.java 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,52 +1,19 @@
-/*
-
- ============================================================================
- The Apache Software License, Version 1.1
- ============================================================================
-
- Copyright (C) 1999-2002 The Apache Software Foundation. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modifica-
- tion, are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- 3. The end-user documentation included with the redistribution, if any, must
- include the following acknowledgment: "This product includes software
- developed by the Apache Software Foundation (http://www.apache.org/)."
- Alternately, this acknowledgment may appear in the software itself, if
- and wherever such third-party acknowledgments normally appear.
-
- 4. The names "Jakarta", "Apache Avalon", "Avalon Framework" and
- "Apache Software Foundation" must not be used to endorse or promote
- products derived from this software without prior written
- permission. For written permission, please contact apache@apache.org.
-
- 5. Products derived from this software may not be called "Apache", nor may
- "Apache" appear in their name, without prior written permission of the
- Apache Software Foundation.
-
- THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
- INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
- INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
- DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
- ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
- THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- This software consists of voluntary contributions made by many individuals
- on behalf of the Apache Software Foundation. For more information on the
- Apache Software Foundation, please see <http://www.apache.org/>.
-
-*/
+/*
+ * Copyright 2003-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.
+ */
package org.apache.avalon.lifecycle;
import org.apache.avalon.framework.context.Context;
1.2 +16 -50 avalon-excalibur/lifecycle/impl/src/java/org/apache/avalon/lifecycle/AbstractAccessor.java
Index: AbstractAccessor.java
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/impl/src/java/org/apache/avalon/lifecycle/AbstractAccessor.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AbstractAccessor.java 2 Oct 2003 03:07:21 -0000 1.1
+++ AbstractAccessor.java 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,53 +1,19 @@
-/*
-
- ============================================================================
- The Apache Software License, Version 1.1
- ============================================================================
-
- Copyright (C) 1999-2002 The Apache Software Foundation. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modifica-
- tion, are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- 3. The end-user documentation included with the redistribution, if any, must
- include the following acknowledgment: "This product includes software
- developed by the Apache Software Foundation (http://www.apache.org/)."
- Alternately, this acknowledgment may appear in the software itself, if
- and wherever such third-party acknowledgments normally appear.
-
- 4. The names "Jakarta", "Apache Avalon", "Avalon Framework" and
- "Apache Software Foundation" must not be used to endorse or promote
- products derived from this software without prior written
- permission. For written permission, please contact apache@apache.org.
-
- 5. Products derived from this software may not be called "Apache", nor may
- "Apache" appear in their name, without prior written permission of the
- Apache Software Foundation.
-
- THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
- INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
- INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
- DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
- ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
- THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- This software consists of voluntary contributions made by many individuals
- on behalf of the Apache Software Foundation. For more information on the
- Apache Software Foundation, please see <http://www.apache.org/>.
-
-*/
-
+/*
+ * Copyright 2003-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.
+ */
package org.apache.avalon.lifecycle;
import org.apache.avalon.framework.context.Context;
1.2 +16 -50 avalon-excalibur/lifecycle/impl/src/java/org/apache/avalon/lifecycle/AbstractCreator.java
Index: AbstractCreator.java
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/impl/src/java/org/apache/avalon/lifecycle/AbstractCreator.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AbstractCreator.java 2 Oct 2003 03:07:21 -0000 1.1
+++ AbstractCreator.java 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,53 +1,19 @@
-/*
-
- ============================================================================
- The Apache Software License, Version 1.1
- ============================================================================
-
- Copyright (C) 1999-2002 The Apache Software Foundation. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modifica-
- tion, are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- 3. The end-user documentation included with the redistribution, if any, must
- include the following acknowledgment: "This product includes software
- developed by the Apache Software Foundation (http://www.apache.org/)."
- Alternately, this acknowledgment may appear in the software itself, if
- and wherever such third-party acknowledgments normally appear.
-
- 4. The names "Jakarta", "Apache Avalon", "Avalon Framework" and
- "Apache Software Foundation" must not be used to endorse or promote
- products derived from this software without prior written
- permission. For written permission, please contact apache@apache.org.
-
- 5. Products derived from this software may not be called "Apache", nor may
- "Apache" appear in their name, without prior written permission of the
- Apache Software Foundation.
-
- THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
- INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
- INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
- DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
- ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
- THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- This software consists of voluntary contributions made by many individuals
- on behalf of the Apache Software Foundation. For more information on the
- Apache Software Foundation, please see <http://www.apache.org/>.
-
-*/
-
+/*
+ * Copyright 2003-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.
+ */
package org.apache.avalon.lifecycle;
import org.apache.avalon.framework.context.Context;
1.3 +16 -1 avalon-excalibur/lifecycle/impl/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/impl/project.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- project.xml 22 Oct 2003 00:52:02 -0000 1.2
+++ project.xml 24 Feb 2004 14:19:28 -0000 1.3
@@ -1,5 +1,20 @@
<?xml version="1.0" encoding="UTF-8"?>
-
+<!--
+ 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.
+-->
<project>
<extend>${basedir}/../project.xml</extend>
1.2 +16 -0 avalon-excalibur/lifecycle/maven.xml
Index: maven.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/maven.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- maven.xml 2 Oct 2003 03:07:20 -0000 1.1
+++ maven.xml 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,3 +1,19 @@
+<!--
+ 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.
+-->
<project default="avalon:build" xmlns:maven="jelly:maven" xmlns:j="jelly:core" xmlns:util="jelly:util" xmlns:ant="jelly:ant">
<ant:property name="maven.dist.assembly.dir"
1.2 +17 -0 avalon-excalibur/lifecycle/project.properties
Index: project.properties
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/project.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.properties 14 Nov 2003 14:47:41 -0000 1.1
+++ project.properties 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,3 +1,20 @@
+#
+# 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.
+#
+#
# gump integration
project.name = excalibur-lifecycle
1.3 +176 -46 avalon-excalibur/lifecycle/LICENSE.TXT
Index: LICENSE.TXT
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/LICENSE.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LICENSE.TXT 2 Oct 2003 03:07:20 -0000 1.2
+++ LICENSE.TXT 24 Feb 2004 14:19:28 -0000 1.3
@@ -1,46 +1,176 @@
- ============================================================================
- The Apache Software License, Version 1.1
- ============================================================================
-
- Copyright (C) 1997-2003 The Apache Software Foundation.
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without modifica-
- tion, are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- 3. The end-user documentation included with the redistribution, if any, must
- include the following acknowledgment: "This product includes software
- developed by the Apache Software Foundation (http://www.apache.org/)."
- Alternately, this acknowledgment may appear in the software itself, if
- and wherever such third-party acknowledgments normally appear.
-
- 4. The names "Apache", "Avalon", "Excalibur", "Fortress", "Phoenix",
- "Merlin" and "Apache Software Foundation" must not be used to endorse or
- promote products derived from this software without prior written
- permission. For written permission, please contact apache@apache.org.
-
- 5. Products derived from this software may not be called "Apache", nor may
- "Apache" appear in their name, without prior written permission of the
- Apache Software Foundation.
-
- THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
- INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
- INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
- DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
- ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
- THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- This software consists of voluntary contributions made by many individuals
- on behalf of the Apache Software Foundation. For more information on the
- Apache Software Foundation, please see http://www.apache.org/.
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
1.14 +16 -1 avalon-excalibur/lifecycle/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/build.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- build.xml 13 Nov 2003 12:39:27 -0000 1.13
+++ build.xml 24 Feb 2004 14:19:28 -0000 1.14
@@ -1,5 +1,20 @@
<?xml version="1.0" encoding="UTF-8"?>
-
+<!--
+ 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.
+-->
<project default="warning" name="Gump Build Support - DO NOT HAND-EDIT!!!" basedir=".">
<property file="${basedir}/project.properties"/>
1.2 +16 -1 avalon-excalibur/lifecycle/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/project.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.xml 2 Oct 2003 03:07:20 -0000 1.1
+++ project.xml 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,5 +1,20 @@
<?xml version="1.0" encoding="UTF-8"?>
-
+<!--
+ 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.
+-->
<project>
<name>Excalibur Lifecycle</name>
1.2 +16 -1 avalon-excalibur/lifecycle/api/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/lifecycle/api/project.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.xml 2 Oct 2003 03:07:21 -0000 1.1
+++ project.xml 24 Feb 2004 14:19:28 -0000 1.2
@@ -1,5 +1,20 @@
<?xml version="1.0" encoding="UTF-8"?>
-
+<!--
+ 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.
+-->
<project>
<extend>${basedir}/../project.xml</extend>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org