jinject 0.1.0__py3-none-any.whl

jinject/_version.py

@@ -0,0 +1,24 @@
+# file generated by vcs-versioning
+# don't change, don't track in version control
+from __future__ import annotations
+
+__all__ = [
+    "__version__",
+    "__version_tuple__",
+    "version",
+    "version_tuple",
+    "__commit_id__",
+    "commit_id",
+]
+
+version: str
+__version__: str
+__version_tuple__: tuple[int | str, ...]
+version_tuple: tuple[int | str, ...]
+commit_id: str | None
+__commit_id__: str | None
+
+__version__ = version = '0.1.0'
+__version_tuple__ = version_tuple = (0, 1, 0)
+
+__commit_id__ = commit_id = None

jinject/cli.py

@@ -0,0 +1,209 @@
+import argparse
+import json
+import logging
+import os
+import importlib.metadata
+import importlib.resources
+import subprocess
+import jinja2
+
+logger = logging.getLogger(__name__)
+
+
+def _build_command_args(args: tuple, kwargs: dict) -> list[str]:
+    """Convert positional and keyword arguments into a flat command list.
+
+    Positional args become command tokens in order.
+    Keyword args are appended as --key=value flags (or --key for boolean True).
+    Boolean False kwargs are omitted entirely.
+    """
+    cmd: list[str] = [str(a) for a in args]
+    for key, value in kwargs.items():
+        flag = f"--{key.replace('_', '-')}"
+        if isinstance(value, bool):
+            if value:
+                cmd.append(flag)
+        else:
+            cmd.append(f"{flag}={value}")
+    return cmd
+
+
+def shell(*args: str, **kwargs: str) -> str:
+    """Execute a command and return its stdout as a stripped string.
+
+    Positional arguments form the command tokens. Keyword arguments are
+    appended as --key=value flags (underscores become hyphens).
+
+    Raises subprocess.CalledProcessError on non-zero exit.
+
+    Examples (from Jinja):
+        {{ shell("echo", "hello") }}
+        {{ shell("uv", "run", "my_tool", config="/path/to/cfg") }}
+    """
+    cmd = _build_command_args(args, kwargs)
+    logger.debug("shell: executing %s", cmd)
+    result = subprocess.run(cmd, capture_output=True, text=True, check=True)
+    return result.stdout.strip()
+
+
+def shell_json(*args: str, **kwargs: str):
+    """Execute a command and parse its stdout as JSON.
+
+    Same argument conventions as shell(). Returns the parsed Python object
+    (dict, list, str, etc.) for use in templates.
+
+    Raises subprocess.CalledProcessError on non-zero exit.
+    Raises json.JSONDecodeError if stdout is not valid JSON.
+
+    Examples (from Jinja):
+        {% set data = shell_json("uv", "run", "my_tool", output="json") %}
+        {{ data.some_field }}
+    """
+    raw = shell(*args, **kwargs)
+    return json.loads(raw)
+
+
+class PackageTemplateLoader(jinja2.BaseLoader):
+    """Dynamically routes template lookup calls directly to entry point packages."""
+    def __init__(self):
+        self.providers = {}
+        # Discover all registration blocks listed under 'jinject.templates'
+        for ep in importlib.metadata.entry_points(group="jinject.templates"):
+            # ep.value looks like 'theme_core:templates' -> split package and subfolder
+            pkg, _, resource_dir = ep.value.partition(":")
+            self.providers[ep.name] = (pkg, resource_dir or "templates")
+
+    def get_source(self, environment, template):
+        # Expects explicit namespacing format: "namespace/file.html"
+        if "/" not in template:
+            raise jinja2.TemplateNotFound(template)
+            
+        prefix, _, target_path = template.partition("/")
+        if prefix not in self.providers:
+            raise jinja2.TemplateNotFound(template)
+            
+        package_name, base_dir = self.providers[prefix]
+        full_resource_path = f"{base_dir}/{target_path}"
+        
+        try:
+            # Safely stream asset records directly out of the target package distribution
+            ref = importlib.resources.files(package_name).joinpath(full_resource_path)
+            if not ref.is_file():
+                raise jinja2.TemplateNotFound(template)
+                
+            source = ref.read_text(encoding="utf-8")
+            return source, None, lambda: True
+        except Exception:
+            raise jinja2.TemplateNotFound(template)
+
+
+def _build_env_path_loader() -> jinja2.BaseLoader | None:
+    """Build a PrefixLoader from the JINJECT_TEMPLATE_PATH environment variable.
+
+    Each entry on the path (separated by os.pathsep) takes one of two forms:
+
+      namespace=/absolute/path/to/templates
+        Registers the directory under the given namespace explicitly.
+
+      /absolute/path/to/directory
+        Uses the directory's basename as the namespace.
+
+    Returns None if the variable is unset/empty or yields no valid directories.
+    """
+    raw = os.environ.get("JINJECT_TEMPLATE_PATH", "")
+    if not raw:
+        return None
+
+    mapping: dict[str, jinja2.FileSystemLoader] = {}
+
+    for entry in raw.split(os.pathsep):
+        entry = entry.strip()
+        if not entry:
+            continue
+
+        # Determine namespace and directory
+        if "=" in entry:
+            namespace, _, directory = entry.partition("=")
+            namespace = namespace.strip()
+            directory = directory.strip()
+        else:
+            directory = entry
+            namespace = os.path.basename(directory.rstrip(os.sep))
+
+        if not namespace:
+            logger.debug("Skipping JINJECT_TEMPLATE_PATH entry with empty namespace: %s", entry)
+            continue
+
+        if not os.path.isdir(directory):
+            logger.debug("Skipping JINJECT_TEMPLATE_PATH entry (not a directory): %s", directory)
+            continue
+
+        # Later entries for the same namespace are ignored (first wins)
+        if namespace not in mapping:
+            mapping[namespace] = jinja2.FileSystemLoader(directory)
+            logger.debug("JINJECT_TEMPLATE_PATH: registered namespace '%s' -> %s", namespace, directory)
+
+    if not mapping:
+        return None
+
+    return jinja2.PrefixLoader(mapping, delimiter="/")
+
+
+def main() -> None:
+    parser = argparse.ArgumentParser(description="Explicit Entry-Point Jinja Preprocessor")
+    parser.add_argument("input", help="Path to the primary local Jinja layout template.")
+    parser.add_argument("-o", "--output", required=True, help="Destination payload filepath.")
+    parser.add_argument("-v", "--var", action="append", default=[], help="Variables in key=value format.")
+    args = parser.parse_args()
+
+    if not os.path.exists(args.input):
+        raise FileNotFoundError(f"Source file not found: {args.input}")
+
+    context = {}
+    for var in args.var:
+        if "=" in var:
+            key, value = var.split("=", 1)
+            context[key.strip()] = value.strip()
+
+    # Absolute path execution bound entirely to immediate compilation target directory
+    local_dir = os.path.dirname(os.path.abspath(args.input))
+    
+    # Build loader chain: local files > env-path namespaces > entry-point packages
+    loaders: list[jinja2.BaseLoader] = [jinja2.FileSystemLoader(local_dir)]
+
+    env_loader = _build_env_path_loader()
+    if env_loader is not None:
+        loaders.append(env_loader)
+
+    loaders.append(PackageTemplateLoader())
+
+    env = jinja2.Environment(
+        loader=jinja2.ChoiceLoader(loaders),
+        trim_blocks=True,
+        lstrip_blocks=True
+    )
+
+    # Register built-in shell execution globals
+    env.globals["shell"] = shell
+    env.globals["shell_json"] = shell_json
+    
+    # Track core extensions and strictly namespace them by their actual package name
+    for ep in importlib.metadata.entry_points(group="jinject.plugins"):
+        pkg_name = ep.dist.name  # Extracts the source package name, e.g., 'theme_core'
+        
+        # Ensure the package has its own sub-dictionary namespace in globals
+        if pkg_name not in env.globals:
+            env.globals[pkg_name] = {}
+            
+        # Bind the function to its declared entry point key inside that package block
+        env.globals[pkg_name][ep.name] = ep.load()
+
+    template_filename = os.path.basename(args.input)
+    template = env.get_template(template_filename)
+    rendered_content = template.render(**context)
+
+    output_dir = os.path.dirname(os.path.abspath(args.output))
+    os.makedirs(output_dir, exist_ok=True)
+
+    with open(args.output, "w") as f:
+        f.write(rendered_content)

jinject-0.1.0.dist-info/METADATA

@@ -0,0 +1,190 @@
+Metadata-Version: 2.5
+Name: jinject
+Version: 0.1.0
+Summary: Jinja templating with bundled Python
+Project-URL: Repository, https://github.com/seantfish/jinja.git
+Author-email: Sean Fish <seantfish@gmail.com>
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: jinja2>=3.0.0
+Description-Content-Type: text/markdown
+
+# jinject
+
+`jinject` is a Jinja2 layout preprocessor designed to enable inclusion of templates with Python packages and dynamic injection of Python utility functions at runtime.
+
+## Installation
+
+In order to use `jinject` with compatible installed system packages, you can run:
+```
+uv tool install ./jinject
+```
+This works well for packages installed to your base global environment (such as via `apt`, `pip --break-system-packages`, or a sourced ROS 2 workspace).
+
+## Creating Jinjectable Python Packages
+
+Packages can expose both templates and executable Python helper macros directly to the `jinject` processor via standard entry points.
+
+### Registering template directories
+
+Registered templates must reside inside your Python package directory structure (e.g., src/my_asset_package/templates/) and added as a `"jinject.templates"` entry-point. Here is an example of a `pyproject.toml`:
+
+```
+[project]
+name = "my_asset_package"
+version = "1.0.0"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project.entry-points."jinject.templates"]
+# Maps the prefix "core_layouts/" to the package's templates/ folder
+core_layouts = "my_asset_package:templates"
+
+# Ensure Hatchling sweeps up non-Python (e.g. *.jinja) files
+[tool.hatch.build.targets.wheel]
+packages = ["src/my_asset_package"]
+
+Downstream files can now import these assets explicitly using the defined namespace key:
+{% import 'core_layouts/base.html' as theme %}
+```
+
+
+### Registering functions
+Functions must behave as pure interfaces—accepting standard primitives (str, int, float) and returning structures Jinja can cleanly process or unpack (such as a generic dict or list or string).
+```
+# located inside: src/my_asset_package/core.py
+
+def metadata_combiner(prefix: str, count: int) -> dict:
+    """Computes layout tag strings and parity flags."""
+    return {
+        "id_tag": f"{prefix}_{count}",
+        "is_even": count % 2 == 0
+    }
+```
+Map this function path under the jinject.plugins entry point namespace inside your pyproject.toml:
+```
+[project.entry-points."jinject.plugins"]
+get_meta = "my_asset_package.core:metadata_combiner"
+```
+
+#### Register the Entry Point
+Map the python method path within the distribution `pyproject.toml` configuration block:
+
+```toml
+[project.entry-points."jinject.plugins"]
+get_meta = "my_asset_package.core:metadata_combiner"
+```
+
+## Writing Templates
+
+### Python functions in the template
+
+`jinject` automatically wires `get_meta()` into the global execution block, making it instantly executable within layout templates:
+
+```text
+{# Inside template context #}
+{% set layout_state = my_asset_package.get_meta("node", 4) %}
+<div id="{{ layout_state.id_tag }}">Parity Event Status: {{ layout_state.is_even }}</div>
+```
+
+### Shell Command Execution in the template
+
+`jinject` provides built-in `shell()` and `shell_json()` functions available in all templates. These allow calling external command-line tools during template rendering — no entry points required.
+
+#### `shell(*args, **kwargs)` → `str`
+
+Executes a command and returns its stdout as a stripped string. Raises on non-zero exit.
+
+Positional arguments form the command tokens. Keyword arguments are appended as `--key=value` flags (underscores in kwarg names become hyphens). Boolean `True` kwargs emit the flag alone; `False` kwargs are omitted.
+
+```jinja
+{# Simple command #}
+{{ shell("echo", "hello") }}
+
+{# Command with flags via kwargs #}
+{% set version = shell("uv", "run", "my_tool", config="/etc/app.yaml") %}
+{# Equivalent to: uv run my_tool --config=/etc/app.yaml #}
+
+{# Boolean flags #}
+{{ shell("ros2", "param", "get", "/node", "use_sim_time", verbose=True) }}
+{# Equivalent to: ros2 param get /node use_sim_time --verbose #}
+```
+
+#### `shell_json(*args, **kwargs)` → `dict | list | ...`
+
+Same calling convention as `shell()`, but parses stdout as JSON and returns the resulting Python object for structured access in templates.
+
+```jinja
+{% set info = shell_json("uv", "run", "get_sensor_config", output_format="json") %}
+<sensor name="{{ info.name }}" rate="{{ info.rate_hz }}" />
+```
+
+### Error Handling
+
+- **Non-zero exit code:** Raises `subprocess.CalledProcessError`, halting template rendering with a clear error message.
+- **Invalid JSON** (for `shell_json`): Raises `json.JSONDecodeError`.
+- **Command not found:** Raises `FileNotFoundError`.
+
+These are intentionally loud failures — jinject is a build-time tool, and silent corruption is worse than a failed build.
+
+## Template Discovery via Environment Variable
+
+For packages that cannot use Python entry points, `jinject` supports the `JINJECT_TEMPLATE_PATH` environment variable as a template discovery mechanism.
+
+### Format
+
+`JINJECT_TEMPLATE_PATH` is a path-separator-delimited list (`:` on Unix, `;` on Windows) of entries. Each entry takes one of two forms:
+
+```bash
+# Explicit namespace mapping
+JINJECT_TEMPLATE_PATH="calibration_description=/opt/share/calibration_description/templates"
+
+# Basename inference (directory basename becomes the namespace)
+JINJECT_TEMPLATE_PATH="/opt/share/calibration_description"
+# → namespace = "calibration_description"
+```
+
+Multiple entries can be combined:
+
+```bash
+export JINJECT_TEMPLATE_PATH="calibration_description=/opt/share/calibration_description/templates:/opt/share/robot_description"
+```
+
+### Behavior
+
+- Each entry registers a directory under a namespace. Templates are then resolvable as `namespace/path/to/template.jinja`.
+- Non-existent directories are silently skipped.
+- If the same namespace appears multiple times, the **first** entry wins.
+- **Precedence:** Environment variable paths are searched **before** entry-point-registered packages. If both provide the same namespace, the env var wins.
+- Entry points remain fully supported — this is additive.
+
+### Example: CMake-Installed Templates
+
+A CMake package installs templates to a known prefix:
+
+```cmake
+install(DIRECTORY templates/ DESTINATION share/${PROJECT_NAME}/templates)
+```
+
+At runtime, set the path to make them discoverable:
+
+```bash
+export JINJECT_TEMPLATE_PATH="calibration_description=/opt/ros/install/share/calibration_description/templates"
+```
+
+Then any Jinja template can import from that namespace:
+
+```jinja
+{% from "calibration_description/velo2cam.sdf.jinja" import velo2cam_model %}
+{{ velo2cam_model("lidar_front") }}
+```
+
+## Background
+
+`jinject` was originally created to generate highly parameterized simulation environments for Gazebo. The workflow maps directly to a modular robotic ecosystem:
+
+* World Containers: ROS 2 packages define overall Gazebo world environments as top-level Jinja files.
+* Asset Containers: Independent hardware/robot packages bundle parameterized SDF templates alongside python procedural helpers (e.g., generating dynamic collision hulls, specific wheel configurations, or customized meshes).
+ 

jinject-0.1.0.dist-info/RECORD

@@ -0,0 +1,8 @@
+jinject/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+jinject/_version.py,sha256=n_5vdJsPNu7wZ57LGuRL585uvll-hiuvZUBWzdG0RQU,520
+jinject/cli.py,sha256=7T8B_BanxrIYMTA74TOSQYl-edaGFpxaU5xyI7ePNj8,7644
+jinject-0.1.0.dist-info/METADATA,sha256=kkOcCVOjSriycMuNIbutiEC8tZT5mpuMq4qTdUoolv8,7175
+jinject-0.1.0.dist-info/WHEEL,sha256=W3fkpkm7-wf9vBI5Z-7s0eWkeM-spu78I8Neb98DeEg,87
+jinject-0.1.0.dist-info/entry_points.txt,sha256=Avc8TzY6qa4DKH3fgtVp9Jt5sb_H8xT8Aw2unKgV11U,45
+jinject-0.1.0.dist-info/licenses/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
+jinject-0.1.0.dist-info/RECORD,,

jinject-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.4
+Root-Is-Purelib: true
+Tag: py3-none-any

jinject-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+jinject = jinject.cli:main

jinject-0.1.0.dist-info/licenses/LICENSE

@@ -0,0 +1,201 @@
+                                 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.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.