r2032 - in trunk: . main

mcconnell at BerliOS mcconnell at mail.berlios.de
Mon Sep 10 14:27:29 EDT 2007

Author: mcconnell
Date: 2007-09-10 20:27:28 +0200 (Mon, 10 Sep 2007)
New Revision: 2032

update file locations (resolving nsi installer generation on windows platform)

Copied: trunk/LICENSE.TXT (from rev 2028, trunk/main/LICENSE.TXT)

Copied: trunk/MIGRATION.TXT (from rev 2028, trunk/main/MIGRATION.TXT)

Copied: trunk/NOTICE.TXT (from rev 2028, trunk/main/NOTICE.TXT)

Copied: trunk/README.TXT (from rev 2028, trunk/main/README.TXT)

Deleted: trunk/main/LICENSE.TXT
--- trunk/main/LICENSE.TXT	2007-09-10 18:19:30 UTC (rev 2031)
+++ trunk/main/LICENSE.TXT	2007-09-10 18:27:28 UTC (rev 2032)
@@ -1,176 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-   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,
-      implied, including, without limitation, any warranties or conditions
-      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.

Deleted: trunk/main/MIGRATION.TXT
--- trunk/main/MIGRATION.TXT	2007-09-10 18:19:30 UTC (rev 2031)
+++ trunk/main/MIGRATION.TXT	2007-09-10 18:27:28 UTC (rev 2032)
@@ -1,75 +0,0 @@
-DPML SDK 2.0 Migration Notes
-The notes deal with migration from DPML 1.1.0 to DPML 2.0.0.
-1. Changes to the Depot index schema and namespace.
-1.1 Namespace changes
-The XML namespace for index files, imported module and imported project files has changed from "link:xsd:dpml/lang/dpml-lang#1.0" to the new namespace "dpml:library".  This change has been 
-brought about a simpler architecture for new namespace resolution.  Instead of the namespace 
-serving as an implicit resource identifier, version 2.0.0 leverages the java.util.ServiceLoader
-to load a schema validator for any unknown schema references.
-1.2 Schema Changes
-The schema definition has been simplified with the removal of inline declaration of product 
-type data structures.  For example, under version 1.1 you could define a project using the 
-following in-line component type declaration:
-  <project name="foo" basedir="foo">
-    <types>
-      <type id="jar"/>
-      <part:plugin class="org.acme.Foo" alias="true"/>
-    </types>
-  </project>
-In the above XML sample the declaration of '<part:plugin .../>' is an example of an inline 
-declaration.  Under version 2.0.0 the equivalent definition is handled by a part type 
-production statement using the new 'source' attribute referencing an XML defining a 
-part deployment strategy.
-  <project name="foo" basedir="foo">
-    <types>
-      <type id="jar"/>
-      <type id="part" alias="true" source="component.xml"/>
-    </types>
-  </project>
-2. Part data type management changes
-2.1 Separation of part schema from strategy schemas.
-The schema definition for the 'part' data type has been updated such that it no longer defines any concrete deployment strategies (version 1.1 include resource and plugin definitions).  Instead, resource declarations may defined under an XML file with a root <resource> element with the namespace "dpml:antlib".  Plugin definitions have been removed as these are now redundant in that all plugin functionality is fully supported by a <component> definition under the "dpml:metro" namespace.  Under this revised structure the introduction of new schemas is much simpler because new alternative strategy schemas can be loaded dynamically, as are handlers for the strategy type.
-3. Metro component strategy
-3.1 Component annotations
-Version 1 provided support for the declaration of component meta-data via a collocated .type data file.  This concept has been replaced under version 2.0 with class annotations that provide for the declaration of component features and policies.  This change eliminates a substantial area of code dealing with component type data structure generation.
-3.2 Enhancements to the <context> definition
-The <context> nested element can now include nested context entries, and entries that resolve to map-based structures. The nested context support is of particular interest when dealing with 'standard' context interfaces declared as return types within an enclosing context interface.  In addition, Metro 2.0.0 includes a Context annotation enabling the declaration of an interface as a context definition - enabling the use of alternative interface names and improving overall flexibility in context contract specification and use.
-3.3 Bundled deployment defaults
-A deployment profile can be collocated with a class file under the name <classname>.xprofile. The deployment profile contains the declaration of the default context and any other component data to be applied on the establishment of a component model before subsequent customization based on a component directive within a part data structure.  In addition, component policy (such as lifecycle, lifestyle, etc.) can also be associated with a component class via respective annotations.  Collectively these enhancement eliminate the need for the metro component ant task (which in turn eliminates a significant amount of code and provides a marked performance improvement related to component loading and deployment).
-4. Embedded Component Deployment Enhancements
-4.1 Content Handlers abstraction
-Introduction of artifact content handlers into the Transit resource management layer has enabled the separation of all 'part' content handling to an external system.  In the case of the 'part' content hander a part definition is analysed and a strategy element loaded via a dedicated strategy handler.  This approach simplifies both the Transit and Metro codebase while introducing some breaking API changes.  Generally speaking the changes are minor in nature and will normally be limited to test cases that reference directly DPML part management APIS.  In most cases these API changes will not impact client code.
-4.2 Modularization
-Under the 1.X series of distributions all classes were packaged under the net.dpml namespace.  Under 2.X public classes (i.e. classes making up the public SDK API) remain in the net.dpml namespace whereas private classes have been moved to the dpml namespace.  This change resolves issues related to public classes that were public in order to support inter-module visibility but which were not designed for inclusion within the public API.  As a consequence - the public API for component management within embedded applications has shrunk dramatically (37 public packages reduced down to 9). This change to some extent is pre-emptive of the changes that would be brought about by an implementation based on the JSR 294 Modularization specification.
\ No newline at end of file

Deleted: trunk/main/NOTICE.TXT
--- trunk/main/NOTICE.TXT	2007-09-10 18:19:30 UTC (rev 2031)
+++ trunk/main/NOTICE.TXT	2007-09-10 18:27:28 UTC (rev 2032)
@@ -1,22 +0,0 @@
-==  NOTICE file corresponding to the section 4 d of                    ==
-==  the Apache License, Version 2.0,                                   ==
-This product is developed by the members of the Digital Product Meta 
-Library (DPML) http://www.dpml.net.
-Except as provided for in this notice, all Resources are copyright
-DPML and/or its members. All rights reserved.
-Resources developed by the DPML includes products and resources developed 
-by the Apache Software Foundation (http://www.apache.org).
-The Janel application launcher copyright Timothy Kil used within the Windows 
-distribution of Depot includes a binary distribution licensed to the DPML 
-under ASL 2.0 by Timothy Kil.
-Permission to use icons and graphics from the CystalXP Alien collection 
-and subsequent redistribution under ASL 2.0 has been granted by the author 

Deleted: trunk/main/README.TXT
--- trunk/main/README.TXT	2007-09-10 18:19:30 UTC (rev 2031)
+++ trunk/main/README.TXT	2007-09-10 18:27:28 UTC (rev 2032)
@@ -1,49 +0,0 @@
-DPML Platform Installation README.
-The DPML SDK distribution comes in three flavours:
-  1. a automatic installer for Windows
-  2. an alternative zip file for a windows installation
-  3. a tar.gz file for nix installation
-If your not using the Windows installer then you will need to unpack the 
-archive in your preferred location.  This result in the creation of a 
-single directory named 'dpml'.
-To complete the installation:
-  1. define the DPML_HOME environment variable pointing to the 
-     'dpml' directory
-  2. add the [the-dpml-home-path]/share/bin directory into 
-     your system path
-To verify your installation you can validate the installed Metro version 
-using the following command:
-  $ metro -version
-Win32 users can install the Station as a NT service by executing the 
-install-DPML-SCM.bat command file (note that this is automatically 
-installed as a manually activated service by the Windows installer).  
-After installation you can start the station manually using the 
-following command:
-  $ net start dpml
-Alternatively, Windows users can modify the DPML service settings using 
-the Control Panel / Administrative Tools / Service control panel.
-The equivalent functionality on UNIX platforms is achieved using the 
-station commands within machine start-up and shutdown scripts.
-  $ station startup
-  $ station shutdown
-If you encounter any problems please consult relevant online documentation 
-and/or post a note to the DPML support list.
-  http://www.dpml.net/about/resources/lists.html
-Stephen McConnell, DPML

More information about the notify-dpml mailing list