Merge lp:~snappy-dev/snapcraft/core into lp:snapcraft

[roland wisdom]

That’s good

Perfect

Unmerged revisions

261. By Sergio Schvezov on 2015-10-29

Release changelog for 0.4

260. By Sergio Schvezov on 2015-10-29

Support combinations of --version, -v and version. Also order help by sergiusens approved by chipaca

259. By Sergio Schvezov on 2015-10-29

stat and chmod the actual file and not the target when removing suid/guid bits by sergiusens approved by elopio

258. By Sergio Schvezov on 2015-10-28

Fix path to binaries in the ros example by sergiusens approved by elopio

257. By Sergio Schvezov on 2015-10-28

Support --version with small note on snapcraft help by sergiusens approved by chipaca

256. By Sergio Schvezov on 2015-10-28

Listing plugins on help should not raise an exception by sergiusens approved by dholbach

255. By Daniel Holbach on 2015-10-28

Integrate all relevant information from https://developer.ubuntu.com/snappy/tutorials/build-snaps/ so it will be easier to maintain the docs for us. Fixed some other small issues along the way. by dholbach approved by sergiusens

254. By Sergio Schvezov on 2015-10-27

Adding a help command to get snapcraft help from the cli. by sergiusens approved by chipaca

253. By Sergio Schvezov on 2015-10-26

Add list-plugins by sergiusens approved by elopio,chipaca

252. By Sergio Schvezov on 2015-10-26

Plugins raise exception instead of true/false by sergiusens approved by elopio

=== added file '.bzrignore'
--- .bzrignore	1970-01-01 00:00:00 +0000
+++ .bzrignore	2022-05-19 22:01:22 +0000
@@ -0,0 +1,14 @@
+examples/*/parts/
+examples/*/snap/
+examples/*/stage/
+examples/**/*.snap
+tests/unit/parts/
+tests/unit/snap/
+tests/unit/stage/
+build
+dist
+*.egg-info
+.coverage**
+htmlcov
+__pycache__
+docs/**.html

=== added symlink '.gitignore'
=== target is '.bzrignore'
=== added file '.tarmac.sh'
--- .tarmac.sh	1970-01-01 00:00:00 +0000
+++ .tarmac.sh	2022-05-19 22:01:22 +0000
@@ -0,0 +1,2 @@
+#!/bin/sh
+./runtests.sh

=== added file 'COPYING'
--- COPYING	1970-01-01 00:00:00 +0000
+++ COPYING	2022-05-19 22:01:22 +0000
@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.

=== added file 'HACKING.md'
--- HACKING.md	1970-01-01 00:00:00 +0000
+++ HACKING.md	2022-05-19 22:01:22 +0000
@@ -0,0 +1,48 @@
+# Snapcraft
+
+## Running
+
+To see all the commands and options, run `snapcraft --help`.
+
+## Testing
+
+Simply run the top level testing script:
+
+    ./runtests.sh
+
+- If you want to get a test coverage report, install python3-coverage before running the tests:
+
+    sudo apt-get install python3-coverage
+
+
+- If you don't want to run the plainbox integration tests, you can skip them by setting SNAPCRAFT_TESTS_SKIP_PLAINBOX=1 in your environment.
+
+- If you are on 15.04 or earlier, you will need to run:
+
+    sudo add-apt-repository ppa:hardware-certification/public
+
+### PPA
+
+You can install the daily build PPA by running:
+
+    sudo add-apt-repository ppa:snappy-dev/snapcraft-daily
+
+## Hacking
+
+We'd love the help!
+
+- Submit merge requests against lp:snapcraft
+- Our mailing list is [e-mail]
+- We can also be found on the #snappy IRC channel on Freenode
+
+### Project Layout
+
+- **bin:** Holds the main snapcraft script. Putting this bin in your PATH or directly running scripts from it will find the rest of the source tree automatically.
+
+- **examples:** Entering the subdirectories and running `../../bin/snapcraft snap` will generally yield interesting results. These examples will give you an idea of what snapcraft can do. These examples are not used during automated testing, they are simply for experimenting.
+
+- **plugins:** Holds yaml metadata for the current snapcraft plugins.
+
+- **tests:** Tests, obviously. `unit` holds Python unit tests and `plainbox` holds plainbox integration tests.
+
+- **snapcraft:** The Python module that houses the core snapcraft logic. The `plugins` subdirectory holds the code for each plugin.

=== added file 'README.md'
--- README.md	1970-01-01 00:00:00 +0000
+++ README.md	2022-05-19 22:01:22 +0000
@@ -0,0 +1,7 @@
+# Snapcraft
+
+Snapcraft allows easy crafting of snap packages for the Ubuntu Core
+transactional system.
+
+See docs/intro.md for details about the concepts behind
+snapcraft. There is also a tutorial in docs/tutorial.md.
\ No newline at end of file

=== added directory 'bin'
=== added file 'bin/snapcraft'
--- bin/snapcraft	1970-01-01 00:00:00 +0000
+++ bin/snapcraft	2022-05-19 22:01:22 +0000
@@ -0,0 +1,33 @@
+#!/usr/bin/python3
+# -*- Mode:Python; indent-tabs-mode:nil; tab-width:4 -*-
+#
+# Copyright (C) 2015 Canonical Ltd
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 3 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+import os
+import sys
+
+# make running from bzr snapshot easy
+topdir = os.path.abspath(os.path.join(__file__, "..", ".."))
+if os.path.exists(os.path.join(topdir, 'setup.py')):
+    sys.path = [topdir] + sys.path
+
+# now import
+import snapcraft.main
+import snapcraft.dirs
+
+
+if __name__ == "__main__":
+    snapcraft.dirs.setup_dirs()
+    snapcraft.main.main()

=== added file 'bin/snapcraft-coverage'
--- bin/snapcraft-coverage	1970-01-01 00:00:00 +0000
+++ bin/snapcraft-coverage	2022-05-19 22:01:22 +0000
@@ -0,0 +1,44 @@
+#!/usr/bin/python3
+# -*- Mode:Python; indent-tabs-mode:nil; tab-width:4 -*-
+#
+# Copyright (C) 2015 Canonical Ltd
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 3 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+import os
+import sys
+
+import coverage
+
+# make running from bzr snapshot easy
+topdir = os.path.abspath(os.path.join(__file__, "..", ".."))
+if os.path.exists(os.path.join(topdir, 'setup.py')):
+    sys.path = [topdir] + sys.path
+
+# now import
+import snapcraft.main
+import snapcraft.dirs
+
+
+if __name__ == "__main__":
+    cov = coverage.coverage(
+        data_file=os.path.join(topdir, '.coverage'), data_suffix=True,
+        branch=True, source=['snapcraft'])
+    cov.start()
+    try:
+        snapcraft.dirs.setup_dirs()
+        snapcraft.main.main()
+    except:
+        cov.stop()
+        cov.save()
+        raise

=== added directory 'debian'
=== added file 'debian/changelog'
--- debian/changelog	1970-01-01 00:00:00 +0000
+++ debian/changelog	2022-05-19 22:01:22 +0000
@@ -0,0 +1,119 @@
+snapcraft (0.4) xenial; urgency=medium
+
+  * Core:
+    - Install build packages if package is removed but not purged
+      (LP: #1507814)
+    - Don't crash on help for unexisting plugin (LP: #1510954)
+    - Don't follow links when checking for suid/guid for unpacked
+      debian package contents (LP: #1511161)
+    - Raise exceptions for plugin errors (LP: #1481122)
+    - Exit cleanly with an error when using the source keyword with a local
+      file (LP: #1499424)
+    - Add version flags to cli (LP: #1501222)
+    - Search the wiki for a part if the 'plugin' keyword is missing
+      (LP: #1506205)
+    - Developer documentation for the plugin base class added (LP: #1507075)
+    - Add subcommand to list plugins (LP: #1510160)
+    - Add subcommand for help (LP: #1510683)
+  * Plugins:
+    - autotools: use autoreconf if needed (LP: #1507648)
+    - maven: support maven flags (LP: #1502031)
+    - catkin: new plugin for building ros projects (LP: #1506201)
+  * Packaging:
+    - Run tests on package build (LP: #1506096)
+    - debian/control: python3-fixtures and python3-testscenarios build deps
+      (LP: #1507573)
+
+ -- Sergio Schvezov <[e-mail]>  Thu, 29 Oct 2015 12:52:04 -0300
+
+snapcraft (0.3) wily; urgency=medium
+
+  * Core imprevements:
+    - Add deprecation messages for deprecated keywords (LP: #1501494)
+    - Remove suid/guid from staged packages (LP: #1503495)
+    - Autodetect tar sources (LP: #1500726)
+    - Better logging if output is not a tty (LP: #1500887)
+    - Improved error message when a plugin is not found (LP: #1501980)
+  * Plugin improvements:
+    - Types instead of plugin as a keyword (LP: #1500857)
+    - Plugin names no longer have '-project' as a suffix (LP: #1501496)
+    - Local plugins can override built-in ones with x-[plugin].py
+      (LP: #1500873)
+  * New plugins:
+    - Scons support added (LP: #1500758)
+  * Bug fixes:
+    - Multi python3 install support (LP: #1499429)
+    - Use the system series for stage-packages (LP: #1501035)
+    - Handle framework policies (LP: #1501037).
+    - Don't infer a plugin name from a part name (LP: #1501413)
+    - Installation errors during build-package's setup now errors
+      (LP: #1502449)
+    - When a dangling symlink is found, try and satisfy it with a
+      package on the host (LP: #1500505)
+    - Support reextraction when using tar sources (LP: #1500728)
+    - Do not require geoip (LP: #1499158)
+  * Examples:
+    - Fix build requirements issue with python2 project (LP: #1501997)
+    - Add missing plugin keyword for the python2 example (LP: #1501977)
+    - Updated the upstream tarball for tomcat (LP: #1504174)
+
+ -- Sergio Schvezov <[e-mail]>  Fri, 25 Sep 2015 12:46:23 +0200
+
+snapcraft (0.2.1) wily; urgency=medium
+
+  * New upstream release (LP: #1499265)
+  * Brown-paper bag release:
+    - Fix install path of examples. Thanks Martin Pitt for noticing.
+    - Allow using local sources through an env var (mostly useful for
+      Launchpad building).
+
+ -- Daniel Holbach <[e-mail]>  Thu, 24 Sep 2015 11:37:36 +0200
+
+snapcraft (0.2) wily; urgency=medium
+
+  * Better setuptools support:
+    - Better support python-setuptools (LP: #1481864),
+    - Used builddir as a base for setup.py overrides (LP: #1498212),
+    - Fix build (LP: #1494825),
+  * Plugin fixes:
+    - Add demo.qml back to the snapcraft.yaml for the QML Demo (LP: #1491301),
+    - stage package libgudev-1.0-0, which makes the godd snap actually 
+      work (LP: #1498347),
+    - Wrap setup.py calls to configure the shebang writer (LP: #1486680),
+    - Update tomcat upstream URL, fixes example again (LP: #1491303),
+    - Add libgudev-1.0-dev as build-tools for godd example,
+      Ensure C library configuration tools don't use system 
+      paths (LP: #1496789),
+  * Snapcraft cli:
+    - On clean, check the contents of the parts dir only if it 
+      exists. (LP: #1497371)
+    - Load the config before trying to run (LP: #1498140),
+    - Notify user why the password is being requested (LP: #1481499),
+    - Fix numerous issues in snapcraft run (LP: #1486659),
+  * Snapcraft stage-packages:
+    - Enable ports for architectures that are not amd64 or 
+      i386 (LP: #1498157),
+    - Improving stage-package handling (LP: #1497453, LP: #1497582)
+    - Fetch all packages in a single download run with proper 
+      progress (LP: #1498333),
+  * Snapcraft wiki queries excessive (LP: #1496381),
+  * Snapcraft internals:
+    - Add 'simple' and 'has-leftovers' flags to all integration tests job
+      units. (LP: #1484596),
+    - Regex for binary and service names (LP: #1495662),
+    - Provide a nice error when tabs found in snapcraft.yaml (LP: #1477875),
+    - Use relative paths for image creation (LP: #1497108),
+    - Use the python logger (LP: #1476452),
+    - snapcraft now has less exit points (LP: #1477639),
+    - Depend and Build-Depend on python3-requests (LP: #1496363),
+    - Add autopkgtest, reshuffle build-deps accordingly (LP: #1496392),
+    - Fix "snapcraft run" (LP: #1484720),
+  * Examples packaged (LP: #1498189).
+
+ -- Sergio Schvezov <[e-mail]>  Wed, 24 Sep 2015 14:23:24 -0300
+
+snapcraft (0.1) wily; urgency=low
+
+  * Initial release
+
+ -- Michael Terry <[e-mail]>  Mon, 6 Jul 2015 21:55:21 -0500

=== added file 'debian/compat'
--- debian/compat	1970-01-01 00:00:00 +0000
+++ debian/compat	2022-05-19 22:01:22 +0000
@@ -0,0 +1,1 @@
+9

=== added file 'debian/control'
--- debian/control	1970-01-01 00:00:00 +0000
+++ debian/control	2022-05-19 22:01:22 +0000
@@ -0,0 +1,59 @@
+Source: snapcraft
+Section: utils
+Priority: extra
+Maintainer: Snapcraft Team <[e-mail]>
+Build-Depends: bzr,
+               cmake,
+               debhelper (>= 9),
+               dh-python,
+               python3 (>= 3.4),
+               python3-apt,
+               python3-fixtures,
+               python3-jsonschema,
+               python3-lxml,
+               python3-pkg-resources,
+               python3-requests,
+               python3-setuptools,
+               python3-testscenarios,
+               python3-yaml,
+               ubuntu-snappy-cli,
+               wget,
+               xz-utils
+Homepage: https://launchpad.net/snapcraft
+Vcs-Bzr: lp:snapcraft
+Standards-Version: 3.9.6
+
+Package: snapcraft
+Architecture: all
+Depends: bzr,
+         dpkg-dev,
+         git,
+         mercurial,
+         python3-apt,
+         python3-jsonschema,
+         python3-lxml,
+         python3-pkg-resources,
+         python3-requests,
+         python3-yaml,
+         sudo,
+         ubuntu-snappy-cli,
+         wget,
+         xz-utils,
+         ${misc:Depends},
+         ${python3:Depends}
+Description: easily craft snaps
+ Snapcraft aims to make upstream developers' lives easier and as such is not
+ a single toolset, but instead is a collection of tools that enable the
+ natural workflow of an upstream to be extended with a simple release step
+ into Snappy.
+
+Package: snapcraft-examples
+Architecture: all
+Depends: snapcraft (= ${binary:Version}), ${misc:Depends}, ${python3:Depends}
+Description: examples for snapcraft
+ Snapcraft aims to make upstream developers' lives easier and as such is not
+ a single toolset, but instead is a collection of tools that enable the
+ natural workflow of an upstream to be extended with a simple release step
+ into Snappy.
+ .
+ This package contains examples for snapcraft.

=== added file 'debian/copyright'
--- debian/copyright	1970-01-01 00:00:00 +0000
+++ debian/copyright	2022-05-19 22:01:22 +0000
@@ -0,0 +1,22 @@
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: Snapcraft
+Upstream-Contact: Snapcraft Team <[e-mail]>
+Source: https://launchpad.net/snapcraft
+
+Files: *
+Copyright: 2015 Canonical Ltd
+License: GPL-3
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License version 3 as
+ published by the Free Software Foundation.
+ .
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this program.  If not, see <http://www.gnu.org/licenses/>.
+ .
+ On Debian systems, the full text of the GNU General Public License
+ version 3 can be found in the file /usr/share/common-licenses/GPL-3.

=== added file 'debian/rules'
--- debian/rules	1970-01-01 00:00:00 +0000
+++ debian/rules	2022-05-19 22:01:22 +0000
@@ -0,0 +1,8 @@
+#!/usr/bin/make -f
+# -*- Mode:Makefile; indent-tabs-mode:t; tab-width:4 -*-
+
+%:
+	dh $@ --with python3 --buildsystem=pybuild
+
+override_dh_compress:
+	dh_compress -Xusr/share/doc/snapcraft-examples/examples

=== added file 'debian/snapcraft-examples.examples'
--- debian/snapcraft-examples.examples	1970-01-01 00:00:00 +0000
+++ debian/snapcraft-examples.examples	2022-05-19 22:01:22 +0000
@@ -0,0 +1,1 @@
+examples/*

=== added file 'debian/snapcraft.install'
--- debian/snapcraft.install	1970-01-01 00:00:00 +0000
+++ debian/snapcraft.install	2022-05-19 22:01:22 +0000
@@ -0,0 +1,3 @@
+/usr/bin
+/usr/lib/python*
+/usr/share/snapcraft

=== added directory 'debian/source'
=== added file 'debian/source/format'
--- debian/source/format	1970-01-01 00:00:00 +0000
+++ debian/source/format	2022-05-19 22:01:22 +0000
@@ -0,0 +1,1 @@
+3.0 (native)

=== added file 'debian/source/options'
--- debian/source/options	1970-01-01 00:00:00 +0000
+++ debian/source/options	2022-05-19 22:01:22 +0000
@@ -0,0 +1,2 @@
+# Ignore standard files (like .bzr)
+tar-ignore

=== added directory 'debian/tests'
=== added file 'debian/tests/control'
--- debian/tests/control	1970-01-01 00:00:00 +0000
+++ debian/tests/control	2022-05-19 22:01:22 +0000
@@ -0,0 +1,11 @@
+Tests: runtests
+       runexamples
+Restrictions: allow-stderr, isolation-container, rw-build-tree
+Depends: @,
+         build-essential,
+         pep8,
+         plainbox,
+         pyflakes,
+         python3-fixtures,
+         python3-mccabe,
+         python3-testscenarios

=== added file 'debian/tests/runexamples'
--- debian/tests/runexamples	1970-01-01 00:00:00 +0000
+++ debian/tests/runexamples	2022-05-19 22:01:22 +0000
@@ -0,0 +1,2 @@
+#!/bin/sh
+./runtests.sh plainbox examples

=== added file 'debian/tests/runtests'
--- debian/tests/runtests	1970-01-01 00:00:00 +0000
+++ debian/tests/runtests	2022-05-19 22:01:22 +0000
@@ -0,0 +1,2 @@
+#!/bin/sh
+./runtests.sh

=== added directory 'docs'
=== added file 'docs/intro.md'
--- docs/intro.md	1970-01-01 00:00:00 +0000
+++ docs/intro.md	2022-05-19 22:01:22 +0000
@@ -0,0 +1,95 @@
+# Intro
+
+Snapcraft is a build and packaging tool which helps you package your software
+as a snap. It makes it easy to incorporate components from different sources 
+and build technologies or solutions.
+
+# Key concepts
+
+A `.snap` package for the Ubuntu Core system contains all its
+dependencies. This has a couple of advantages over traditional `deb` or
+`rpm` based dependency handling, the most important being that a
+developer can always be assured that there are no regressions triggered by
+changes to the system underneath their app.
+
+Snapcraft makes bundling these dependencies easy by allowing you to
+specify them as "parts" in the `snapcraft.yaml` file.
+
+# Snappy
+
+Snappy Ubuntu Core is a new rendition of Ubuntu with transactional updates - a
+minimal server image with the same libraries as today's Ubuntu, but
+applications are provided through a simpler mechanism.
+
+Snappy apps and Ubuntu Core itself can be upgraded atomically and rolled back
+if needed. Apps are also strictly confined and sandboxed to safeguard your
+data and system.
+
+## Parts
+
+A central aspect of a snapcraft recipe is a "part". A part is a piece
+of software or data that the snap package requires to work or to
+build other parts. Each part is managed by a snapcraft plugin and parts
+are usually independent of each other.
+
+## Plugin
+
+Each part has a `plugin` associated to it, this `plugin` provides the mechanism
+to handle it. Parts are driven through plugins, there are a variety of plugins
+already included for python 2 and 3, go, java, and cmake or autotools based
+projects.
+
+## Lifecycle
+
+Each part goes through the following steps:
+
+### Pull
+
+The first is that each part is pulled. This step will download
+content, e.g. checkout a git repository or download a binary component
+like the Java SDK. Snapcraft will create a `parts/` directory with
+sub-directories like `parts/part-name/src` for each part that contains
+the downloaded content.
+
+### Build
+
+The next step is that each part is built in its `parts/part-name/build`
+directory and installs itself into `parts/part-name/install`.
+
+### Stage
+
+After the build of each part the parts are combined into a single
+directory tree that is called the "staging area". It can be found
+under the `./stage` directory.
+
+This `./stage` directory is useful for building outside code that isn't in the
+`snapcraft.yaml` recipe against the snap contents. For example, you might 
+build a local project against the libraries in `./stage` by running `snapcraft 
+shell make`. Though in general, you are encouraged to add even local
+projects to snapcraft.yaml with a local `source:` path.
+
+### Snap
+
+The snap step moves the data into a `./snap` directory. It contains only
+the content that will be put into the final snap package, unlike the staging
+area which may include some development files not destined for your package.
+
+The Snappy metadata information about your project will also now be placed in
+`./snap/meta`. Snapcraft takes care of generating all the meta-data Snappy
+expects. For a breakdown of what this is, have a look at our [Snappy developer
+reference](https://developer.ubuntu.com/snappy/guides/packaging-format-apps/).
+
+This `./snap` directory is useful for inspecting what is going into your snap
+and to make any final post-processing on snapcraft's output.
+
+### Assemble
+
+The final step builds a snap package out of the `snap` directory. This `.snap` 
+file can be uploaded to the Ubuntu Store and published directly to Snappy 
+users.
+
+# Next
+
+After introducing the key concept of snapcraft it is probably a good
+time to look at [the tutorial](your-first-snap.md) to create your first snap
+with snapcraft.

=== added file 'docs/snapcraft-advanced-features.md'
--- docs/snapcraft-advanced-features.md	1970-01-01 00:00:00 +0000
+++ docs/snapcraft-advanced-features.md	2022-05-19 22:01:22 +0000
@@ -0,0 +1,188 @@
+# Snapcraft: Advanced features
+
+Once you have built [your first snap](your-first-snap.md), you will probably
+want to learn more about snapcraft's more advanced features. Having a look at
+our selection of examples is a good idea, as we want it to be a good showcase
+of what is possible and generally relevant.
+
+## Examples
+
+Our showcase can be found in the actual source of `snapcraft` itself. Check
+it out by simply running:
+
+	bzr branch lp:snapcraft
+	cd snapcraft/examples
+
+Inspecting the source locally will make easier to build the examples and
+play around with them. (You can
+[view them online](https://bazaar.launchpad.net/~snappy-dev/snapcraft/core/files/head:/examples/)
+as well.)
+
+### Playing around with the examples
+
+If you just checked out the `snapcraft` source and inspect the examples, you
+can start off your explorations by reading the accompanying `snapcraft.yaml`
+file and running:
+
+	../../bin/snapcraft
+
+This will inform you of all the steps taken during the creation of the snap.
+
+## Defining your parts
+
+Once you have noted down all the general information about your snap
+(like description, vendor information and everything else), naming
+the individual parts will define the stucture of your `snapcraft.yaml` file.
+Think of parts as individual components of your snap: Where do you pull them
+from? How are they built?
+
+### Prerequisites during the build
+
+The example named `downloader-with-wiki-parts` shows how very easy you can
+make sure that the relevant build dependencies are installed:
+
+	build-packages: [libssl-dev]
+
+The above will install the `libssl-dev` package from the Ubuntu archive before
+an attempted build. If you need a specific version of libssl-dev or a custom
+build, you will need to specify a separate part.
+
+Also note that the above will not define which libraries are shipped with the
+app. It merely makes sure you have all the relevant build tools installed.
+
+
+### Pulling and building
+
+If you just intend to pull and build the source, take a look at the `gopaste`
+example. In its `snapcraft.yaml` file you can find just this one `parts`
+paragraph:
+
+	parts:
+ 	  gopaste:
+    	    plugin: go
+            source: git://github.com/wisnij/gopaste/gopasted
+
+It starts off with the name of the specific part (`gopaste` here), the origin
+of the part (it's a `git` URL) and how to build it (plugin: `go`).
+Other possible scenarios would be Bazaar or Mercurial branches, or local
+directories.
+
+### Mixing and matching plugins
+
+An interesting example is `py2-project` because it defines only one part
+(`spongeshaker`), but uses two different plugins (`python2` and `make`) to
+assemble and build the snap:
+
+	parts:
+  	  spongeshaker:
+	    plugin: python2
+	    source: git://github.com/markokr/spongeshaker.git
+	  make-project:
+	    plugin: make
+	    source: .
+
+The example above mixes and matches parts of different origin. Locally it
+provides a binary we intend to ship (the `sha3sum.py` script) and a
+`Makefile` (to install our script in the right place).
+
+`spongeshaker` is a python library we will need to pull from git, build as
+a python project and bundle along with our script.
+
+A possible use-case for the above would be if you just intend to ship a small
+binary which you maintain, but require a library you need to build from git
+as opposed to simply including it from the Ubuntu archives.
+
+What's happening during the `snapcraft` run is:
+
+1. Get `spongeshaker` from `git`.
+1. Build it as a python project (which will include installing the python
+   library in the right place).
+1. Running `make` (from the local `Makefile`) and thus installing our
+   `sha3sum.py` script in the right place.
+
+### Putting your parts in order
+
+If your app is comprised of multiple parts, it might be necessary to build
+and stage parts in a particular order. This can be done by using the `after`
+keyword:
+
+	parts:
+	    pipelinetest:
+	        plugin: make
+	        source: lp:~mterry/+junk/pipelinetest
+	        after:
+	            - libpipeline
+	    libpipeline:
+	        plugin: autotools
+	        source: lp:~mterry/libpipeline/printf
+
+
+In the case of the `libpipeline` example above, the part named `pipelinetest`
+will be built after `libpipeline`. Especially if you need specific
+functionality during a build or as part of checks during the `snap` phase,
+this will be handy.
+
+### Re-using parts
+
+With snapcraft we want to make it easy to learn from other app vendors and
+re-use parts which have worked well for them.
+
+In the `downloader-with-wiki-parts` example, you can see that the `main`
+part is built:
+
+	        after:
+	            - curl
+
+As we never define the `curl` part in the above example, `snapcraft` will
+check the Ubuntu Wiki, which is where we currently host examples of
+successful snapcraft parts. The build order in this case would be `curl`,
+then `main`.
+
+
+## Finishing steps
+
+### Individual files
+
+If you are planning to provide binaries and services to the users of your
+apps, you need to specify them in your definition first. It's just a matter
+of enumerating them.
+
+The `godd` example has one binary:
+
+	binaries:
+	  godd:
+	    exec: ./bin/godd
+
+The above will take care of making the script executable, adding it to the
+user's path and install it in the right place.
+
+For a simple service we can take a look at `gopaste`:
+
+	services:
+	  gopaste:
+	    description: "gopaste"
+	    start: bin/gopasted
+
+You define a name for the service, describe it (so log messages are more
+descriptive), declare how to run the service and that's it. For more
+thoughts on services and their security, visit the
+[snappy policy](https://developer.ubuntu.com/en/snappy/guides/security-policy/).
+
+
+### Limiting the number of installed files
+
+To check the list of files included in your snap, you can use `dpkg -c` on
+the resulting `.snap` file. If you find that certain files should not be
+shipped to the user (download size being just one factor), you can
+explicitly tell `snapcraft` which files to snap:
+
+	    snap:
+	     - usr/lib/x86_64-linux-gnu/libgudev-1.0.so*
+	     - usr/lib/x86_64-linux-gnu/libobject-2.0.so*
+	     - usr/lib/x86_64-linux-gnu/libglib-2.0.so*
+	     - bin/godd*
+
+Here `godd` further defines the list of files to be placed in the app
+during the `snap` phase. As you can see above, globs (using asterisks as
+wildcard characters) are a good way of handling complexities within the
+directory structure.

=== added file 'docs/your-first-snap.md'
--- docs/your-first-snap.md	1970-01-01 00:00:00 +0000
+++ docs/your-first-snap.md	2022-05-19 22:01:22 +0000
@@ -0,0 +1,328 @@
+# Snapcraft Tutorial
+
+Let's make a snap from scratch using Snapcraft! We'll pick something a little
+interesting: a webcam server.
+
+## Preparation
+
+You'll want a webcam and a Snappy device. We'll assume you have those,
+but if you need help setting up a Snappy install, there is help
+[online](https://developer.ubuntu.com/en/snappy/start/).
+
+(Even if you don't have either of those, you can still follow along. You just
+won't be able to use the final snap package you create. But you'll get to see
+how Snapcraft works, which is still super rewarding.)
+
+You should also install Snapcraft:
+
+    $ sudo add-apt-repository ppa:snappy-dev/tools
+    $ sudo apt-get update
+    $ sudo apt-get install snapcraft
+
+## Approach
+
+This example is easy because we won't be doing much of the heavy lifting
+ourselves. We're going to integrate a couple pieces of code together to make
+an interesting app.
+
+Namely, we'll combine a web server with a webcam program and combine
+them to serve a new frame every ten seconds.
+
+> The resulting package is also part of the examples directory in the
+> [snapcraft sources](http://bazaar.launchpad.net/~snappy-dev/snapcraft/core/files/head:/examples/webcam-webui/)
+
+### The Web Server
+
+Go has a simple web server in its standard libraries. So let's just use that.
+
+It's trivial to write a complete (but basic) web server in a few lines:
+
+    package main
+    import "net/http"
+    func main() {
+        panic(http.ListenAndServe(":8080", http.FileServer(http.Dir("."))))
+    }
+
+This will serve the current directory on port `:8080`. If there is an
+`index.html` in the current directory, it will be served. Otherwise a
+directory listing will be shown.
+
+This code is hosted on a simple GitHub
+[repository](https://github.com/mikix/golang-static-http).
+
+### The Webcam Program
+
+There is a webcam program provided in the Ubuntu archives called `fswebcam`.
+It has a lot of neat features. But all we'll be needing for now is its ability
+to take a webcam freeze frame and drop it to a file by calling it like so:
+
+    $ fswebcam output.jpg
+
+## Snapcraft Recipe
+
+OK, let's create a Snapcraft recipe that combines the above programs into a
+useful snap.
+
+Snapcraft reads a single file, `snapcraft.yaml`, which tells it how to combine
+code. It contains a list of `parts`, or pieces of code, and some metadata for
+the final snap it will create. But let's not worry about the metadata yet.
+
+### Initializing a project
+
+To get started with a base template create a folder that will hold your
+project, and initialize it:
+
+    $ mkdir webcam-webui
+    $ cd webcam-webui
+    $ snapcraft init
+
+then open the created snapcraft.yaml and edit the templated values for `name`,
+`version`, `vendor`, `summary` and `description`. You can make it look like
+this:
+
+    name: webcam-webui
+    version: 1
+    vendor: You <[e-mail]>
+    summary: Webcam web UI
+    description: Exposes your webcam over a web UI
+    icon: icon.png
+
+and copy over an icon to `icon.png` or change the path accordingly (if you
+change the path just make sure it is part of your project directory and that
+the path is relative to be able to share your snapcrafting):
+
+    $ cp /usr/share/icons/hicolor/64/mimetypes/text-x-apport.png ./icon.png
+
+If you run `snapcraft` now, it will complain about not having any `parts`.
+
+We will look more into this metadata in a bit, but first let's look at adding
+some `parts`.
+
+### Web Server Part
+
+Let's start with the web server.
+
+    parts:
+      cam:
+        plugin: go
+        source: git://github.com/mikix/golang-static-http
+
+You've just defined a `part` inside `parts` named `cam`, but you
+could call it anything. That part has a two options: A `plugin` option that
+tells Snapcraft how to interpret the part (in this case, it's a Go project),
+and a `source` option telling Snapcraft where to download the code.
+
+Go ahead and append the above contents to your recently created
+`snapcraft.yaml`.
+
+Now we can build and "stage" this recipe. Staging just means putting the output
+of the parts in a common folder that has the same layout as the snap we'll
+eventually create. It lets you look at how the snap is constructed and make
+sure everything is in place.
+
+    $ snapcraft stage
+
+You'll see a bunch of output, including Snapcraft downloading the Go compiler
+if not already installed on your host build environment.
+It will use this to compile the code found on GitHub. Eventually when it is
+done, you'll be able to inspect the `./stage` folder and see the web server
+executable sitting in `./stage/bin`:
+
+    $ ls stage/bin
+    golang-static-http
+
+### Adding an Ubuntu dependency to a part.
+
+Now let's add the webcam program `fswebcam` to our snap. Edit `snapcraft.yaml`
+to make the `cam` part look like:
+
+    parts:
+      cam:
+        plugin: go
+        source: git://github.com/mikix/golang-static-http
+        stage-packages:
+          - fswebcam
+
+We've just added a new property to the `cam` part called `stage-packages` which
+contains a yaml list with any supporting Ubuntu package we want; in this case
+our list has one element with an entry for the `fswebcam` Ubuntu `deb` based
+package.
+
+Now let's stage our recipe again (and force it to go through the lifecycle).
+
+    $ snapcraft stage --force
+
+You'll also see Snapcraft downloading and unpacking all the Ubuntu packages
+into your snap. If you look at `./stage`, you'll see a lot more files now:
+
+    $ ls stage
+    bin  etc  lib  usr  var
+
+### A copy Part
+
+OK, so we have the two programs in our staging area. But how do we make them
+work together?
+
+We'll write a tiny little script that runs the server and `fswebcam` together:
+
+    #!/bin/sh
+    set -e
+
+    cd "$SNAP_APP_DATA_PATH"
+
+    golang-static-http &
+
+    while :; do
+        fswebcam shot.jpeg
+        sleep 10
+    done
+
+Save the above as `webcam-webui` and make it executable:
+
+    $ chmod a+x webcam-webui
+
+Alright, let's put this script in our snap too:
+
+    parts:
+      cam:
+        plugin: go
+        source: git://github.com/mikix/golang-static-http
+        stage-packages:
+          - fswebcam
+      glue:
+        plugin: copy
+        files:
+          webcam-webui: bin/webcam-webui
+
+The `copy` plugin takes a list of files to just directly copy without
+building or downloading anything. In this case, we just want to put our glue
+script in the `bin/` directory.
+
+If we run Snapcraft again, we won't be surprised:
+
+    $ snapcraft stage
+
+We should now see both the web server and our script in stage/bin (the webcam
+program is in stage/usr/bin since it came from Ubuntu):
+
+    $ ls stage/bin
+    golang-static-http  webcam-webui
+
+### Filesets
+
+Some files in `./stage` could be needed for building dependent parts during the
+staging phase and some of these would be useful for the resulting snap. In
+this case we don't need some of these for either staging or the resulting snap,
+so let's add some filesets for the snap.
+
+Edit `snapcraft.yaml` once more to make the `cam` part in `parts` to look like:
+
+    parts:
+      cam:
+        plugin: go
+        source: git://github.com/mikix/golang-static-http
+        stage-packages:
+          - fswebcam
+        filesets:
+          fswebcam:
+            - usr/bin/fswebcam
+            - lib
+            - usr/lib
+          go-server:
+            - bin/golang-*
+        snap:
+          - $fswebcam
+          - $go-server
+      glue:
+        plugin: copy
+        files:
+          webcam-webui: bin/webcam-webui
+
+What we did was add two `filesets`, one named `fswebcam` and another one named
+`go-server` and then added a `snap` entry referencing these two filesets with
+`$`. All these filesets are inclusion based filesets, you can use `*` to glob
+many files and directories (if `*` is the first character, it needs to be
+quoted e.g.; `'*'`). An exclusion can be added by prefixing the file
+with a `-`. Additionally, you don't need to define a fileset, you can explicitly
+mention the file, directory or match under `snap` or `stage`.
+
+### Extending the Metadata
+
+The defined values in `snapcraft.yaml` are used to build the corresponding
+`meta` directory that holds all the package information.
+
+You can read all about the resulting [format of this metadata](https://developer.ubuntu.com/en/snappy/guides/packaging-format-apps/),
+but we'll assume here that you're already familiar.
+
+The templated values when `snapcraft init` was run did not hold any `parts`
+which we've filled along the way. It also did not define any `services` or
+`binaries` which we will be adding now
+
+Edit `snapcraft.yaml` once more and add the `services` and `binaries` entry,
+your resulting `snapcraft.yaml` should look very similar to:
+
+    name: webcam-webui
+    version: 1
+    vendor: You <[e-mail]>
+    summary: Webcam web UI
+    description: Exposes your webcam over a web UI
+    icon: icon.png
+    services:
+      webcam-webui:
+        start: bin/webcam-webui
+
+    parts:
+      golang-static-http:
+        plugin: go
+        source: git://github.com/mikix/golang-static-http
+        stage-packages:
+         - fswebcam
+      glue:
+        plugin: copy
+        files:
+          webcam-webui: bin/webcam-webui
+
+and tell Snapcraft to actually make the snap package:
+
+    $ snapcraft
+
+You should now have a `webcam-webui_1_amd64.snap` file sitting in your
+directory (assuming you are running on amd64). Congratulations!
+
+
+## Next steps
+
+Well done, your first snap using snapcraft is ready. If you want to check out
+a few examples for reference or to get inspired, have a look at the
+`examples` directory in the source directory of snapcraft:
+
+    bzr branch lp:snapcraft
+    cd snapcraft/examples
+
+In `examples/` you can find a diverse set of examples which should help you
+get started on your own projects. To get a good overview of the snapcraft 
+features used in these examples, check out 
+[this article](snapcraft-advanced-features.md).
+
+If you should have any more questions, ask us on
+
+ * `#snappy` on `irc.freenode.net` or
+ * the 
+   [snappy-app-devel](https://lists.ubuntu.com/mailman/listinfo/snappy-app-devel)
+   mailing list.
+   We recommend you subscribe to this mailing list where discussions around 
+   snap apps take place, this will keep you up to date with new capabilities 
+   for your snappy app, and best practices from fellow developers.
+
+### Publish your app to snappy users
+
+We'll be happy to help you on the mailing list to build a snappy package of 
+anything that you are interested in. Choose a good name for it, and you can
+very easily share it in 
+[ubuntu myapps](https://myapps.developer.ubuntu.com/dev/click-apps/?format=snap)
+where you go to share it with other snappy users.
+
+This is the same underlying hub that we use for Ubuntu phone apps, but 
+snappy is a new iteration of that system. It only takes minutes from time of 
+upload to being available to end users. The goal is to deliver your app 
+directly to users instantly — you push a new version, they get it.

=== added directory 'examples'
=== added directory 'examples/downloader-with-wiki-parts'
=== added file 'examples/downloader-with-wiki-parts/Makefile'
--- examples/downloader-with-wiki-parts/Makefile	1970-01-01 00:00:00 +0000
+++ examples/downloader-with-wiki-parts/Makefile	2022-05-19 22:01:22 +0000
@@ -0,0 +1,11 @@
+# -*- Mode:Makefile; indent-tabs-mode:t; tab-width:4 -*-
+
+all:
+	gcc -Wall -Wextra -Werror -pedantic -o test ./test.c $(CFLAGS) $(LDFLAGS) -lcurl -lssl -lcrypto -lssl -lcrypto -lz
+
+install:
+	install -d -m755  $(DESTDIR)/bin/
+	install -m755 ./test $(DESTDIR)/bin/test
+
+clean:
+	rm -f test

=== added file 'examples/downloader-with-wiki-parts/icon.png'
Binary files examples/downloader-with-wiki-parts/icon.png and examples/downloader-with-wiki-parts/icon.png differ
=== added file 'examples/downloader-with-wiki-parts/snapcraft.yaml'
--- examples/downloader-with-wiki-parts/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/downloader-with-wiki-parts/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,17 @@
+name: downloader
+version: 1.0
+vendor: "Sergio Schvezov <[e-mail]>"
+summary: curl based downloader
+description: this is an example package
+icon: icon.png
+binaries:
+    test:
+        exec: bin/test
+
+parts:
+    main:
+        plugin: make
+        source: .
+        after:
+            - curl
+build-packages: [libssl-dev]

=== added file 'examples/downloader-with-wiki-parts/test.c'
--- examples/downloader-with-wiki-parts/test.c	1970-01-01 00:00:00 +0000
+++ examples/downloader-with-wiki-parts/test.c	2022-05-19 22:01:22 +0000
@@ -0,0 +1,17 @@
+#include <stdio.h>
+#include <curl/curl.h>
+
+int main(void)
+{
+  CURL *curl;
+
+  curl = curl_easy_init();
+  if(curl) {
+    curl_easy_setopt(curl, CURLOPT_URL, "ubuntu.com");
+    curl_easy_perform(curl);
+
+    curl_easy_cleanup(curl);
+  }
+
+  return 0;
+}

=== added directory 'examples/godd'
=== added file 'examples/godd/icon.png'
Binary files examples/godd/icon.png and examples/godd/icon.png differ
=== added file 'examples/godd/snapcraft.yaml'
--- examples/godd/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/godd/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,20 @@
+name: godd
+version: 1.0
+vendor: Michael Vogt <[e-mail]>
+binaries:
+  godd:
+    exec: ./bin/godd
+summary: Simple dd like tool
+description: Written in go with support for device auto-detection via libgudev, you would need to use hw-assign to access devices.
+icon: icon.png
+
+parts:
+  godd:
+    plugin: go
+    source: git://github.com/mvo5/godd
+    stage-packages: [libgudev-1.0-dev]
+    snap:
+     - usr/lib/x86_64-linux-gnu/libgudev-1.0.so*
+     - usr/lib/x86_64-linux-gnu/libobject-2.0.so*
+     - usr/lib/x86_64-linux-gnu/libglib-2.0.so*
+     - bin/godd*

=== added directory 'examples/gopaste'
=== added file 'examples/gopaste/Makefile'
--- examples/gopaste/Makefile	1970-01-01 00:00:00 +0000
+++ examples/gopaste/Makefile	2022-05-19 22:01:22 +0000
@@ -0,0 +1,8 @@
+# -*- Mode: Makefile; indent-tabs-mode:t; tab-width: 4 -*-
+
+all:
+	cp parts/gopaste/src/github.com/wisnij/gopaste/web.template snap/
+	cp -r parts/gopaste/src/github.com/wisnij/gopaste/static snap/
+	cp -r meta snap/
+	cp gopaste snap/bin/
+

=== added file 'examples/gopaste/gopaste'
--- examples/gopaste/gopaste	1970-01-01 00:00:00 +0000
+++ examples/gopaste/gopaste	2022-05-19 22:01:22 +0000
@@ -0,0 +1,10 @@
+#!/bin/sh
+
+set -x
+
+cd $SNAP_APP_DATA_PATH
+cp $SNAP_APP_PATH/web.template .
+cp -r $SNAP_APP_PATH/static .
+export HOME=$SNAP_APP_DATA_PATH
+
+exec $SNAP_APP_PATH/bin/gopasted

=== added file 'examples/gopaste/icon.png'
Binary files examples/gopaste/icon.png and examples/gopaste/icon.png differ
=== added file 'examples/gopaste/snapcraft.yaml'
--- examples/gopaste/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/gopaste/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,15 @@
+name: gopaste
+version: 1.0
+vendor: Michael Terry <[e-mail]>
+services:
+  gopaste:
+    description: "gopaste"
+    start: bin/gopasted
+summary: Simple pasting tool
+description: Runs a service that allows you to paste to and share.
+icon: icon.png
+
+parts:
+  gopaste:
+    plugin: go
+    source: git://github.com/wisnij/gopaste/gopasted

=== added directory 'examples/java-hello-world'
=== added file 'examples/java-hello-world/Makefile'
--- examples/java-hello-world/Makefile	1970-01-01 00:00:00 +0000
+++ examples/java-hello-world/Makefile	2022-05-19 22:01:22 +0000
@@ -0,0 +1,7 @@
+# -*- Mode:Makefile; indent-tabs-mode:t; tab-width:4 -*-
+
+all:
+
+install:
+	install -d -m755  $(DESTDIR)/bin/
+	install -m755 wrapper $(DESTDIR)/bin/wrapper

=== added file 'examples/java-hello-world/build.xml'
--- examples/java-hello-world/build.xml	1970-01-01 00:00:00 +0000
+++ examples/java-hello-world/build.xml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,39 @@
+<project name="HelloWorld" basedir="." default="main">
+
+    <property name="src.dir"     value="src"/>
+
+    <property name="build.dir"   value="build"/>
+    <property name="classes.dir" value="${build.dir}/classes"/>
+    <property name="jar.dir"     value="target"/>
+
+    <property name="main-class"  value="oata.HelloWorld"/>
+
+
+
+    <target name="clean">
+        <delete dir="${build.dir}"/>
+    </target>
+
+    <target name="compile">
+        <mkdir dir="${classes.dir}"/>
+        <javac srcdir="${src.dir}" destdir="${classes.dir}"/>
+    </target>
+
+    <target name="jar" depends="compile">
+        <mkdir dir="${jar.dir}"/>
+        <jar destfile="${jar.dir}/${ant.project.name}.jar" basedir="${classes.dir}">
+            <manifest>
+                <attribute name="Main-Class" value="${main-class}"/>
+            </manifest>
+        </jar>
+    </target>
+
+    <target name="run" depends="jar">
+        <java jar="${jar.dir}/${ant.project.name}.jar" fork="true"/>
+    </target>
+
+    <target name="clean-build" depends="clean,jar"/>
+
+    <target name="main" depends="clean,run"/>
+
+</project>

=== added file 'examples/java-hello-world/icon.png'
Binary files examples/java-hello-world/icon.png and examples/java-hello-world/icon.png differ
=== added file 'examples/java-hello-world/snapcraft.yaml'
--- examples/java-hello-world/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/java-hello-world/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,17 @@
+name: java-hello-world
+version: 0
+vendor: Michael Terry <[e-mail]>
+binaries:
+ hello:
+   exec: bin/wrapper
+summary: A java example
+description: this is not much more than an example
+icon: icon.png
+
+parts:
+    local:
+        plugin: ant
+        source: .
+    wrapper:
+        plugin: make
+        source: .

=== added directory 'examples/java-hello-world/src'
=== added directory 'examples/java-hello-world/src/oata'
=== added file 'examples/java-hello-world/src/oata/HelloWorld.java'
--- examples/java-hello-world/src/oata/HelloWorld.java	1970-01-01 00:00:00 +0000
+++ examples/java-hello-world/src/oata/HelloWorld.java	2022-05-19 22:01:22 +0000
@@ -0,0 +1,10 @@
+// https://ant.apache.org/manual/tutorial-HelloWorldWithAnt.html
+
+package oata;
+
+public class HelloWorld {
+    public static void main(String[] args) {
+        System.out.println("Hello World");
+    }
+}
+

=== added file 'examples/java-hello-world/wrapper'
--- examples/java-hello-world/wrapper	1970-01-01 00:00:00 +0000
+++ examples/java-hello-world/wrapper	2022-05-19 22:01:22 +0000
@@ -0,0 +1,2 @@
+#!/bin/sh
+java oata.HelloWorld

=== added directory 'examples/libpipeline'
=== added file 'examples/libpipeline/Makefile'
--- examples/libpipeline/Makefile	1970-01-01 00:00:00 +0000
+++ examples/libpipeline/Makefile	2022-05-19 22:01:22 +0000
@@ -0,0 +1,11 @@
+# -*- Mode:Makefile; indent-tabs-mode:t; tab-width:4 -*-
+
+all:
+	gcc -o test ./test.c $(CFLAGS) $(LDFLAGS) -lpipeline
+
+install:
+	install -d -m755  $(DESTDIR)/bin/
+	install -m755 ./test $(DESTDIR)/bin/test
+
+clean:
+	rm -f test

=== added file 'examples/libpipeline/icon.png'
Binary files examples/libpipeline/icon.png and examples/libpipeline/icon.png differ
=== added file 'examples/libpipeline/snapcraft.yaml'
--- examples/libpipeline/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/libpipeline/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,19 @@
+name: pipelinetest
+version: 1.0
+vendor: Mike Terry <[e-mail]>
+binaries:
+  pipelinetest:
+    exec: ./bin/pipelinetest
+summary: Libpipeline example
+description: this is an example package of an autotools project built with snapcraft using
+icon: icon.png
+
+parts:
+    pipelinetest:
+        plugin: make
+        source: lp:~mterry/+junk/pipelinetest
+        after:
+            - libpipeline
+    libpipeline:
+        plugin: autotools
+        source: lp:~mterry/libpipeline/printf

=== added file 'examples/libpipeline/test.c'
--- examples/libpipeline/test.c	1970-01-01 00:00:00 +0000
+++ examples/libpipeline/test.c	2022-05-19 22:01:22 +0000
@@ -0,0 +1,18 @@
+#include <pipeline.h>
+#include <stdio.h>
+
+int main()
+{
+    pipeline *p;
+    int status;
+
+    printf("running ls | grep s | grep t\n");
+
+    p = pipeline_new ();
+    pipeline_command_args (p, "ls", NULL);
+    pipeline_command_args (p, "grep", "s", NULL);
+    pipeline_command_args (p, "grep", "t", NULL);
+    status = pipeline_run (p);
+
+    return status;
+}

=== added directory 'examples/py2-project'
=== added file 'examples/py2-project/Makefile'
--- examples/py2-project/Makefile	1970-01-01 00:00:00 +0000
+++ examples/py2-project/Makefile	2022-05-19 22:01:22 +0000
@@ -0,0 +1,8 @@
+# -*- Mode: Makefile; indent-tabs-mode:t; tab-width: 4 -*-
+
+all:
+
+install:
+	mkdir -p $(DESTDIR)/bin
+	cp -a sha3sum.py $(DESTDIR)/bin/sha3sum
+	chmod a+x $(DESTDIR)/bin/sha3sum

=== added file 'examples/py2-project/icon.png'
Binary files examples/py2-project/icon.png and examples/py2-project/icon.png differ
=== added file 'examples/py2-project/sha3sum.py'
--- examples/py2-project/sha3sum.py	1970-01-01 00:00:00 +0000
+++ examples/py2-project/sha3sum.py	2022-05-19 22:01:22 +0000
@@ -0,0 +1,14 @@
+#!/usr/bin/env python2
+
+import sys
+
+import spongeshaker.sha3
+
+
+if __name__ == "__main__":
+    # 224 is the default from sha3sum
+    h = spongeshaker.sha3.sha3_224()
+    with open(sys.argv[1], "rb") as fp:
+        data = fp.read()
+    h.update(data)
+    print(h.hexdigest())

=== added file 'examples/py2-project/snapcraft.yaml'
--- examples/py2-project/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/py2-project/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,20 @@
+name: spongeshaker
+version: 0
+vendor: Michael Vogt <[e-mail]>
+binaries:
+  sha3sum:
+    exec: ./bin/sha3sum
+summary: A python sha3 implementation
+description: A python2 project using snapcraft
+icon: icon.png
+
+build-packages:
+  - libpython2.7-dev
+
+parts:
+  spongeshaker:
+    plugin: python2
+    source: git://github.com/markokr/spongeshaker.git
+  make-project:
+    plugin: make
+    source: .

=== added directory 'examples/py3-project'
=== added file 'examples/py3-project/icon.png'
Binary files examples/py3-project/icon.png and examples/py3-project/icon.png differ
=== added file 'examples/py3-project/sha3sum.py'
--- examples/py3-project/sha3sum.py	1970-01-01 00:00:00 +0000
+++ examples/py3-project/sha3sum.py	2022-05-19 22:01:22 +0000
@@ -0,0 +1,14 @@
+#!/usr/bin/env python3
+
+import sys
+
+import spongeshaker.sha3
+
+
+if __name__ == "__main__":
+    # 224 is the default from sha3sum
+    h = spongeshaker.sha3.sha3_224()
+    with open(sys.argv[1], "rb") as fp:
+        data = fp.read()
+    h.update(data)
+    print(h.hexdigest())

=== added file 'examples/py3-project/snapcraft.yaml'
--- examples/py3-project/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/py3-project/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,18 @@
+name: spongeshaker
+version: 0
+vendor: Michael Vogt <[e-mail]>
+binaries:
+  sha3sum:
+    exec: bin/sha3sum
+summary: A python sha3 implementation
+description: A python2 project using snapcraft
+icon: icon.png
+
+parts:
+  spongeshaker:
+    plugin: python3
+    source: git://github.com/markokr/spongeshaker.git
+  sha3:
+    plugin: copy
+    files:
+     sha3sum.py: bin/sha3sum

=== added directory 'examples/qmldemo'
=== added file 'examples/qmldemo/demo.qml'
--- examples/qmldemo/demo.qml	1970-01-01 00:00:00 +0000
+++ examples/qmldemo/demo.qml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,9 @@
+import QtQuick 2.2
+import QtQuick.Controls 1.1
+
+ApplicationWindow {
+	Label {
+		anchors.centerIn: parent
+		text: "QML Example"
+	}
+}

=== added file 'examples/qmldemo/icon.png'
Binary files examples/qmldemo/icon.png and examples/qmldemo/icon.png differ
=== added directory 'examples/qmldemo/meta'
=== added file 'examples/qmldemo/meta/package.yaml'
--- examples/qmldemo/meta/package.yaml	1970-01-01 00:00:00 +0000
+++ examples/qmldemo/meta/package.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,10 @@
+name: qmldemo
+version: 1
+vendor: Ted Gould <[e-mail]>
+frameworks: [mir]
+binaries:
+  - name: qmldemo
+    exec: qmlscene demo.qml --
+    caps:
+      - mir_client
+      - network-client

=== added file 'examples/qmldemo/meta/readme.md'
--- examples/qmldemo/meta/readme.md	1970-01-01 00:00:00 +0000
+++ examples/qmldemo/meta/readme.md	2022-05-19 22:01:22 +0000
@@ -0,0 +1,4 @@
+
+== QML Demo ==
+
+An example of shipping a usable QML file in a snap using the QML plugin.

=== added file 'examples/qmldemo/snapcraft.yaml'
--- examples/qmldemo/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/qmldemo/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,22 @@
+name: qmldemo
+version: 1
+vendor: Ted Gould <[e-mail]>
+frameworks:
+  - mir
+binaries:
+  qmldemo:
+    exec: qmlscene demo.qml --
+    caps:
+      - mir_client
+      - network-client
+summary: qml demo
+description: An example of shipping a usable QML file in a snap using the QML plugin.
+icon: icon.png
+
+parts:
+  qml:
+    plugin: qml
+  qmldemo:
+    plugin: copy
+    files:
+      demo.qml: demo.qml

=== added directory 'examples/ros'
=== added file 'examples/ros/icon.svg'
--- examples/ros/icon.svg	1970-01-01 00:00:00 +0000
+++ examples/ros/icon.svg	2022-05-19 22:01:22 +0000
@@ -0,0 +1,1 @@
+<svg />

=== added file 'examples/ros/snapcraft.yaml'
--- examples/ros/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/ros/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,27 @@
+name: ros-example
+version: 1.0
+vendor: Number Five <[e-mail]>
+summary: A robot example
+icon: icon.svg
+description: A really small ROS example
+
+binaries:
+  listener:
+    exec: opt/ros/indigo/beginner_tutorials/lib/beginner_tutorials/listener
+  talker:
+    exec: opt/ros/indigo/beginner_tutorials/lib/beginner_tutorials/talker
+
+services:
+  rosmaster:
+    start: bin/roscore-rosmaster-service
+    description: ROS Master Service
+
+parts:
+  roscore:
+    plugin: roscore
+  catkin-tutorials:
+    plugin: catkin
+    source: .
+    catkin-packages:
+      - beginner_tutorials
+

=== added directory 'examples/ros/src'
=== added file 'examples/ros/src/CMakeLists.txt'
--- examples/ros/src/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/ros/src/CMakeLists.txt	2022-05-19 22:01:22 +0000
@@ -0,0 +1,47 @@
+# toplevel CMakeLists.txt for a catkin workspace
+# catkin/cmake/toplevel.cmake
+
+cmake_minimum_required(VERSION 2.8.3)
+
+# optionally provide a cmake file in the workspace to override arbitrary stuff
+include(workspace.cmake OPTIONAL)
+
+set(CATKIN_TOPLEVEL TRUE)
+
+# include catkin directly or via find_package()
+if(EXISTS "${CMAKE_SOURCE_DIR}/catkin/cmake/all.cmake" AND EXISTS "${CMAKE_SOURCE_DIR}/catkin/CMakeLists.txt")
+  set(catkin_EXTRAS_DIR "${CMAKE_SOURCE_DIR}/catkin/cmake")
+  # include all.cmake without add_subdirectory to let it operate in same scope
+  include(catkin/cmake/all.cmake NO_POLICY_SCOPE)
+  add_subdirectory(catkin)
+
+else()
+  # use either CMAKE_PREFIX_PATH explicitly passed to CMake as a command line argument
+  # or CMAKE_PREFIX_PATH from the environment
+  if(NOT DEFINED CMAKE_PREFIX_PATH)
+    if(NOT "$ENV{CMAKE_PREFIX_PATH}" STREQUAL "")
+      string(REPLACE ":" ";" CMAKE_PREFIX_PATH $ENV{CMAKE_PREFIX_PATH})
+    endif()
+  endif()
+
+  # list of catkin workspaces
+  set(catkin_search_path "")
+  foreach(path ${CMAKE_PREFIX_PATH})
+    if(EXISTS "${path}/.CATKIN_WORKSPACE")
+      list(FIND catkin_search_path ${path} _index)
+      if(_index EQUAL -1)
+        list(APPEND catkin_search_path ${path})
+      endif()
+    endif()
+  endforeach()
+
+  # search for catkin in all workspaces
+  set(CATKIN_TOPLEVEL_FIND_PACKAGE TRUE)
+  find_package(catkin REQUIRED
+    NO_POLICY_SCOPE
+    PATHS ${catkin_search_path}
+    NO_DEFAULT_PATH NO_CMAKE_FIND_ROOT_PATH)
+  unset(CATKIN_TOPLEVEL_FIND_PACKAGE)
+endif()
+
+catkin_workspace()

=== added directory 'examples/ros/src/beginner_tutorials'
=== added file 'examples/ros/src/beginner_tutorials/CMakeLists.txt'
--- examples/ros/src/beginner_tutorials/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/CMakeLists.txt	2022-05-19 22:01:22 +0000
@@ -0,0 +1,39 @@
+# %Tag(FULLTEXT)%
+cmake_minimum_required(VERSION 2.8.3)
+project(beginner_tutorials)
+
+## Find catkin and any catkin packages
+find_package(catkin REQUIRED COMPONENTS roscpp rospy std_msgs genmsg)
+
+## Declare ROS messages and services
+add_message_files(FILES Num.msg)
+add_service_files(FILES AddTwoInts.srv)
+
+## Generate added messages and services
+generate_messages(DEPENDENCIES std_msgs)
+
+## Declare a catkin package
+catkin_package()
+
+## Build talker and listener
+include_directories(include ${catkin_INCLUDE_DIRS})
+
+add_executable(talker src/talker.cpp)
+target_link_libraries(talker ${catkin_LIBRARIES})
+
+add_executable(listener src/listener.cpp)
+target_link_libraries(listener ${catkin_LIBRARIES})
+
+## Build service client and server
+# %Tag(SRVCLIENT)%
+add_executable(add_two_ints_server src/add_two_ints_server.cpp)
+target_link_libraries(add_two_ints_server ${catkin_LIBRARIES})
+add_dependencies(add_two_ints_server beginner_tutorials_gencpp)
+
+add_executable(add_two_ints_client src/add_two_ints_client.cpp)
+target_link_libraries(add_two_ints_client ${catkin_LIBRARIES})
+add_dependencies(add_two_ints_client beginner_tutorials_gencpp)
+
+# %EndTag(SRVCLIENT)%
+
+# %EndTag(FULLTEXT)%
\ No newline at end of file

=== added directory 'examples/ros/src/beginner_tutorials/msg'
=== added file 'examples/ros/src/beginner_tutorials/msg/Num.msg'
--- examples/ros/src/beginner_tutorials/msg/Num.msg	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/msg/Num.msg	2022-05-19 22:01:22 +0000
@@ -0,0 +1,1 @@
+int64 num

=== added file 'examples/ros/src/beginner_tutorials/package.xml'
--- examples/ros/src/beginner_tutorials/package.xml	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/package.xml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,42 @@
+<?xml version="1.0"?>
+<!-- %Tag(FULLTEXT,-1)% -->
+<package>
+  <!-- %Tag(NAME)% -->
+  <name>beginner_tutorials</name>
+  <!-- %EndTag(NAME)% -->
+  <!-- %Tag(VERSION)% -->
+  <version>0.1.0</version>
+  <!-- %EndTag(VERSION)% -->
+  <!-- %Tag(DESC)% -->
+  <description>The beginner_tutorials package</description>
+  <!-- %EndTag(DESC)% -->
+
+  <!-- %Tag(MAINTAINER)% -->
+  <maintainer email="[e-mail]">Your Name</maintainer>
+  <!-- %EndTag(MAINTAINER)% -->
+  <!-- %Tag(LICENSE)% -->
+  <license>BSD</license>
+  <!-- %EndTag(LICENSE)% -->
+  <!-- %Tag(URLS)% -->
+  <url type="website">http://wiki.ros.org/beginner_tutorials</url>
+  <!-- %EndTag(URLS)% -->
+  <!-- %Tag(AUTHORS)% -->
+  <author email="[e-mail]">Jane Doe</author>
+  <!-- %EndTag(AUTHORS)% -->
+
+  <!-- %Tag(DEPS)% -->
+  <buildtool_depend>catkin</buildtool_depend>
+
+  <build_depend>roscpp</build_depend>
+  <build_depend>rospy</build_depend>
+  <build_depend>std_msgs</build_depend>
+
+  <run_depend>roscpp</run_depend>
+  <run_depend>rospy</run_depend>
+  <run_depend>std_msgs</run_depend>
+  <!-- %EndTag(DEPS)% -->
+
+  <!-- %Tag(EXPORT)% -->
+  <!-- %EndTag(EXPORT)% -->
+</package>
+<!-- %EndTag(FULLTEXT)% -->
\ No newline at end of file

=== added directory 'examples/ros/src/beginner_tutorials/src'
=== added file 'examples/ros/src/beginner_tutorials/src/add_two_ints_client.cpp'
--- examples/ros/src/beginner_tutorials/src/add_two_ints_client.cpp	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/src/add_two_ints_client.cpp	2022-05-19 22:01:22 +0000
@@ -0,0 +1,30 @@
+#include "ros/ros.h"
+#include "beginner_tutorials/AddTwoInts.h"
+#include <cstdlib>
+
+int main(int argc, char **argv)
+{
+  ros::init(argc, argv, "add_two_ints_client");
+  if (argc != 3)
+  {
+    ROS_INFO("usage: add_two_ints_client X Y");
+    return 1;
+  }
+
+  ros::NodeHandle n;
+  ros::ServiceClient client = n.serviceClient<beginner_tutorials::AddTwoInts>("add_two_ints");
+  beginner_tutorials::AddTwoInts srv;
+  srv.request.a = atoll(argv[1]);
+  srv.request.b = atoll(argv[2]);
+  if (client.call(srv))
+  {
+    ROS_INFO("Sum: %ld", (long int)srv.response.sum);
+  }
+  else
+  {
+    ROS_ERROR("Failed to call service add_two_ints");
+    return 1;
+  }
+
+  return 0;
+}

=== added file 'examples/ros/src/beginner_tutorials/src/add_two_ints_server.cpp'
--- examples/ros/src/beginner_tutorials/src/add_two_ints_server.cpp	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/src/add_two_ints_server.cpp	2022-05-19 22:01:22 +0000
@@ -0,0 +1,23 @@
+#include "ros/ros.h"
+#include "beginner_tutorials/AddTwoInts.h"
+
+bool add(beginner_tutorials::AddTwoInts::Request  &req,
+         beginner_tutorials::AddTwoInts::Response &res)
+{
+  res.sum = req.a + req.b;
+  ROS_INFO("request: x=%ld, y=%ld", (long int)req.a, (long int)req.b);
+  ROS_INFO("sending back response: [%ld]", (long int)res.sum);
+  return true;
+}
+
+int main(int argc, char **argv)
+{
+  ros::init(argc, argv, "add_two_ints_server");
+  ros::NodeHandle n;
+
+  ros::ServiceServer service = n.advertiseService("add_two_ints", add);
+  ROS_INFO("Ready to add two ints.");
+  ros::spin();
+
+  return 0;
+}

=== added file 'examples/ros/src/beginner_tutorials/src/listener.cpp'
--- examples/ros/src/beginner_tutorials/src/listener.cpp	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/src/listener.cpp	2022-05-19 22:01:22 +0000
@@ -0,0 +1,60 @@
+#include "ros/ros.h"
+#include "std_msgs/String.h"
+
+/**
+ * This tutorial demonstrates simple receipt of messages over the ROS system.
+ */
+void chatterCallback(const std_msgs::String::ConstPtr& msg)
+{
+  ROS_INFO("I heard: [%s]", msg->data.c_str());
+}
+
+int main(int argc, char **argv)
+{
+  /**
+   * The ros::init() function needs to see argc and argv so that it can
+   * perform any ROS arguments and name remapping that were provided
+   * at the command line. For programmatic remappings you can use a
+   * different version of init() which takes remappings directly, but
+   * for most command-line programs, passing argc and argv is the easiest
+   * way to do it.  The third argument to init() is the name of the node.
+   *
+   * You must call one of the versions of ros::init() before using any other
+   * part of the ROS system.
+   */
+  ros::init(argc, argv, "listener");
+
+  /**
+   * NodeHandle is the main access point to communications with the
+   * ROS system. The first NodeHandle constructed will fully initialize
+   * this node, and the last NodeHandle destructed will close down the node.
+   */
+  ros::NodeHandle n;
+
+  /**
+   * The subscribe() call is how you tell ROS that you want to receive
+   * messages on a given topic.  This invokes a call to the ROS master
+   * node, which keeps a registry of who is publishing and who is subscribing.
+   * Messages are passed to a callback function, here called chatterCallback.  
+   * subscribe() returns a Subscriber object that you must hold on to
+   * until you want to unsubscribe. When all copies of the Subscriber
+   * object go out of scope, this callback will automatically be
+   * unsubscribed from this topic.
+   *
+   * The second parameter to the subscribe() function is the size of
+   * the message queue.  If messages are arriving faster than they are
+   * being processed, this is the number of messages that will be
+   * buffered up before beginning to throw away the oldest ones.
+   */
+  ros::Subscriber sub = n.subscribe("chatter", 1000, chatterCallback);
+
+  /**
+   * ros::spin() will enter a loop, pumping callbacks.  With this
+   * version, all callbacks will be called from within this thread
+   * (the main one).  ros::spin() will exit when Ctrl-C is pressed,
+   * or the node is shutdown by the master.
+   */
+  ros::spin();
+
+  return 0;
+}

=== added file 'examples/ros/src/beginner_tutorials/src/talker.cpp'
--- examples/ros/src/beginner_tutorials/src/talker.cpp	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/src/talker.cpp	2022-05-19 22:01:22 +0000
@@ -0,0 +1,87 @@
+#include "ros/ros.h"
+#include "std_msgs/String.h"
+
+#include <sstream>
+
+/**
+ * This tutorial demonstrates simple sending of messages over the ROS system.
+ */
+int main(int argc, char **argv)
+{
+  /**
+   * The ros::init() function needs to see argc and argv so that it can 
+   * perform any ROS arguments and name remapping that were provided at
+   * the command line. For programmatic remappings you can use a
+   * different version of init() which takes remappings directly, but
+   * for most command-line programs, passing argc and argv is the easiest
+   * way to do it.  The third argument to init() is the name of the node.
+   *
+   * You must call one of the versions of ros::init() before using any
+   * other part of the ROS system.
+   */
+  ros::init(argc, argv, "talker");
+
+  /**
+   * NodeHandle is the main access point to communications with the
+   * ROS system. The first NodeHandle constructed will fully initialize
+   * this node, and the last NodeHandle destructed will close down
+   * the node.
+   */
+  ros::NodeHandle n;
+
+  /**
+   * The advertise() function is how you tell ROS that you want to
+   * publish on a given topic name. This invokes a call to the ROS
+   * master node, which keeps a registry of who is publishing and who
+   * is subscribing. After this advertise() call is made, the master
+   * node will notify anyone who is trying to subscribe to this topic name,
+   * and they will in turn negotiate a peer-to-peer connection with this
+   * node.  advertise() returns a Publisher object which allows you to
+   * publish messages on that topic through a call to publish().  Once
+   * all copies of the returned Publisher object are destroyed, the topic
+   * will be automatically unadvertised.
+   *
+   * The second parameter to advertise() is the size of the message queue
+   * used for publishing messages.  If messages are published more quickly
+   * than we can send them, the number here specifies how many messages to
+   * buffer up before throwing some away.
+   */
+  ros::Publisher chatter_pub = n.advertise<std_msgs::String>("chatter", 1000);
+
+  ros::Rate loop_rate(10);
+
+  /**
+   * A count of how many messages we have sent. This is used to create
+   * a unique string for each message.
+   */
+  int count = 0;
+  while (ros::ok())
+  {
+    /**
+     * This is a message object. You stuff it with data, and then publish it.
+     */
+    std_msgs::String msg;
+
+    std::stringstream ss;
+    ss << "hello world " << count;
+    msg.data = ss.str();
+
+    ROS_INFO("%s", msg.data.c_str());
+
+    /**
+     * The publish() function is how you send messages. The parameter
+     * is the message object. The type of this object must agree with the type
+     * given as a template parameter to the advertise<>() call, as was done
+     * in the constructor above.
+     */
+    chatter_pub.publish(msg);
+
+    ros::spinOnce();
+
+    loop_rate.sleep();
+    ++count;
+  }
+
+
+  return 0;
+}

=== added directory 'examples/ros/src/beginner_tutorials/srv'
=== added file 'examples/ros/src/beginner_tutorials/srv/AddTwoInts.srv'
--- examples/ros/src/beginner_tutorials/srv/AddTwoInts.srv	1970-01-01 00:00:00 +0000
+++ examples/ros/src/beginner_tutorials/srv/AddTwoInts.srv	2022-05-19 22:01:22 +0000
@@ -0,0 +1,4 @@
+int64 a
+int64 b
+---
+int64 sum

=== added directory 'examples/tomcat-maven-webapp'
=== added file 'examples/tomcat-maven-webapp/Makefile'
--- examples/tomcat-maven-webapp/Makefile	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/Makefile	2022-05-19 22:01:22 +0000
@@ -0,0 +1,6 @@
+all:
+
+install:
+	cp -a tomcat-conf/ $(DESTDIR)/
+	install -D -m755 wrapper $(DESTDIR)/bin/wrapper
+

=== added file 'examples/tomcat-maven-webapp/icon.png'
Binary files examples/tomcat-maven-webapp/icon.png and examples/tomcat-maven-webapp/icon.png differ
=== added file 'examples/tomcat-maven-webapp/snapcraft.yaml'
--- examples/tomcat-maven-webapp/snapcraft.yaml	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/snapcraft.yaml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,25 @@
+name: tomcat-webapp-demo
+vendor: Loïc Minier <[e-mail]>
+version: 1.0
+architectures:
+ - amd64
+services:
+ tomcat:
+   start: bin/wrapper
+   caps:
+   - networking
+   - network-service
+summary: Demo of Tomcat-hosted Webapp
+description: This is a demo snap of a Tomcat-hosted webapp produced by snapcraft with maven.
+icon: icon.png
+
+parts:
+    webapp:
+        plugin: maven
+        source: git://github.com/lool/snappy-mvn-demo.git
+    tomcat:
+        plugin: tar-content
+        source: http://mirrors.ircam.fr/pub/apache/tomcat/tomcat-8/v8.0.28/bin/apache-tomcat-8.0.28.tar.gz
+    local-files:
+        plugin: make
+        source: .

=== added directory 'examples/tomcat-maven-webapp/tomcat-conf'
=== added file 'examples/tomcat-maven-webapp/tomcat-conf/catalina.policy'
--- examples/tomcat-maven-webapp/tomcat-conf/catalina.policy	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/catalina.policy	2022-05-19 22:01:22 +0000
@@ -0,0 +1,250 @@
+// Licensed to the Apache Software Foundation (ASF) under one or more
+// contributor license agreements.  See the NOTICE file distributed with
+// this work for additional information regarding copyright ownership.
+// The ASF licenses this file to You under the Apache License, Version 2.0
+// (the "License"); you may not use this file except in compliance with
+// the License.  You may obtain a copy of the License at
+//
+//     http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+
+// ============================================================================
+// catalina.policy - Security Policy Permissions for Tomcat
+//
+// This file contains a default set of security policies to be enforced (by the
+// JVM) when Catalina is executed with the "-security" option.  In addition
+// to the permissions granted here, the following additional permissions are
+// granted to each web application:
+//
+// * Read access to the web application's document root directory
+// * Read, write and delete access to the web application's working directory
+// ============================================================================
+
+
+// ========== SYSTEM CODE PERMISSIONS =========================================
+
+
+// These permissions apply to javac
+grant codeBase "file:${java.home}/lib/-" {
+        permission java.security.AllPermission;
+};
+
+// These permissions apply to all shared system extensions
+grant codeBase "file:${java.home}/jre/lib/ext/-" {
+        permission java.security.AllPermission;
+};
+
+// These permissions apply to javac when ${java.home] points at $JAVA_HOME/jre
+grant codeBase "file:${java.home}/../lib/-" {
+        permission java.security.AllPermission;
+};
+
+// These permissions apply to all shared system extensions when
+// ${java.home} points at $JAVA_HOME/jre
+grant codeBase "file:${java.home}/lib/ext/-" {
+        permission java.security.AllPermission;
+};
+
+
+// ========== CATALINA CODE PERMISSIONS =======================================
+
+
+// These permissions apply to the daemon code
+grant codeBase "file:${catalina.home}/bin/commons-daemon.jar" {
+        permission java.security.AllPermission;
+};
+
+// These permissions apply to the logging API
+// Note: If tomcat-juli.jar is in ${catalina.base} and not in ${catalina.home},
+// update this section accordingly.
+//  grant codeBase "file:${catalina.base}/bin/tomcat-juli.jar" {..}
+grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
+        permission java.io.FilePermission
+         "${java.home}${file.separator}lib${file.separator}logging.properties", "read";
+
+        permission java.io.FilePermission
+         "${catalina.base}${file.separator}conf${file.separator}logging.properties", "read";
+        permission java.io.FilePermission
+         "${catalina.base}${file.separator}logs", "read, write";
+        permission java.io.FilePermission
+         "${catalina.base}${file.separator}logs${file.separator}*", "read, write";
+
+        permission java.lang.RuntimePermission "shutdownHooks";
+        permission java.lang.RuntimePermission "getClassLoader";
+        permission java.lang.RuntimePermission "setContextClassLoader";
+
+        permission java.lang.management.ManagementPermission "monitor";
+
+        permission java.util.logging.LoggingPermission "control";
+
+        permission java.util.PropertyPermission "java.util.logging.config.class", "read";
+        permission java.util.PropertyPermission "java.util.logging.config.file", "read";
+        permission java.util.PropertyPermission "org.apache.juli.AsyncLoggerPollInterval", "read";
+        permission java.util.PropertyPermission "org.apache.juli.AsyncMaxRecordCount", "read";
+        permission java.util.PropertyPermission "org.apache.juli.AsyncOverflowDropType", "read";
+        permission java.util.PropertyPermission "org.apache.juli.ClassLoaderLogManager.debug", "read";
+        permission java.util.PropertyPermission "catalina.base", "read";
+
+        // Note: To enable per context logging configuration, permit read access to
+        // the appropriate file. Be sure that the logging configuration is
+        // secure before enabling such access.
+        // E.g. for the examples web application (uncomment and unwrap
+        // the following to be on a single line):
+        // permission java.io.FilePermission "${catalina.base}${file.separator}
+        //  webapps${file.separator}examples${file.separator}WEB-INF
+        //  ${file.separator}classes${file.separator}logging.properties", "read";
+};
+
+// These permissions apply to the server startup code
+grant codeBase "file:${catalina.home}/bin/bootstrap.jar" {
+        permission java.security.AllPermission;
+};
+
+// These permissions apply to the servlet API classes
+// and those that are shared across all class loaders
+// located in the "lib" directory
+grant codeBase "file:${catalina.home}/lib/-" {
+        permission java.security.AllPermission;
+};
+
+
+// If using a per instance lib directory, i.e. ${catalina.base}/lib,
+// then the following permission will need to be uncommented
+// grant codeBase "file:${catalina.base}/lib/-" {
+//         permission java.security.AllPermission;
+// };
+
+
+// ========== WEB APPLICATION PERMISSIONS =====================================
+
+
+// These permissions are granted by default to all web applications
+// In addition, a web application will be given a read FilePermission
+// for all files and directories in its document root.
+grant {
+    // Required for JNDI lookup of named JDBC DataSource's and
+    // javamail named MimePart DataSource used to send mail
+    permission java.util.PropertyPermission "java.home", "read";
+    permission java.util.PropertyPermission "java.naming.*", "read";
+    permission java.util.PropertyPermission "javax.sql.*", "read";
+
+    // OS Specific properties to allow read access
+    permission java.util.PropertyPermission "os.name", "read";
+    permission java.util.PropertyPermission "os.version", "read";
+    permission java.util.PropertyPermission "os.arch", "read";
+    permission java.util.PropertyPermission "file.separator", "read";
+    permission java.util.PropertyPermission "path.separator", "read";
+    permission java.util.PropertyPermission "line.separator", "read";
+
+    // JVM properties to allow read access
+    permission java.util.PropertyPermission "java.version", "read";
+    permission java.util.PropertyPermission "java.vendor", "read";
+    permission java.util.PropertyPermission "java.vendor.url", "read";
+    permission java.util.PropertyPermission "java.class.version", "read";
+    permission java.util.PropertyPermission "java.specification.version", "read";
+    permission java.util.PropertyPermission "java.specification.vendor", "read";
+    permission java.util.PropertyPermission "java.specification.name", "read";
+
+    permission java.util.PropertyPermission "java.vm.specification.version", "read";
+    permission java.util.PropertyPermission "java.vm.specification.vendor", "read";
+    permission java.util.PropertyPermission "java.vm.specification.name", "read";
+    permission java.util.PropertyPermission "java.vm.version", "read";
+    permission java.util.PropertyPermission "java.vm.vendor", "read";
+    permission java.util.PropertyPermission "java.vm.name", "read";
+
+    // Required for OpenJMX
+    permission java.lang.RuntimePermission "getAttribute";
+
+    // Allow read of JAXP compliant XML parser debug
+    permission java.util.PropertyPermission "jaxp.debug", "read";
+
+    // All JSPs need to be able to read this package
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.tomcat";
+
+    // Precompiled JSPs need access to these packages.
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.jasper.el";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.jasper.runtime";
+    permission java.lang.RuntimePermission
+     "accessClassInPackage.org.apache.jasper.runtime.*";
+
+    // Precompiled JSPs need access to these system properties.
+    permission java.util.PropertyPermission
+     "org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER", "read";
+    permission java.util.PropertyPermission
+     "org.apache.el.parser.COERCE_TO_ZERO", "read";
+
+    // The cookie code needs these.
+    permission java.util.PropertyPermission
+     "org.apache.catalina.STRICT_SERVLET_COMPLIANCE", "read";
+    permission java.util.PropertyPermission
+     "org.apache.tomcat.util.http.ServerCookie.STRICT_NAMING", "read";
+    permission java.util.PropertyPermission
+     "org.apache.tomcat.util.http.ServerCookie.FWD_SLASH_IS_SEPARATOR", "read";
+
+    // Applications using Comet need to be able to access this package
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.comet";
+
+    // Applications using WebSocket need to be able to access these packages
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.tomcat.websocket";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.tomcat.websocket.server";
+};
+
+
+// The Manager application needs access to the following packages to support the
+// session display functionality. These settings support the following
+// configurations:
+// - default CATALINA_HOME == CATALINA_BASE
+// - CATALINA_HOME != CATALINA_BASE, per instance Manager in CATALINA_BASE
+// - CATALINA_HOME != CATALINA_BASE, shared Manager in CATALINA_HOME
+grant codeBase "file:${catalina.base}/webapps/manager/-" {
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.ha.session";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.manager";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.manager.util";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.util";
+};
+grant codeBase "file:${catalina.home}/webapps/manager/-" {
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.ha.session";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.manager";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.manager.util";
+    permission java.lang.RuntimePermission "accessClassInPackage.org.apache.catalina.util";
+};
+
+// You can assign additional permissions to particular web applications by
+// adding additional "grant" entries here, based on the code base for that
+// application, /WEB-INF/classes/, or /WEB-INF/lib/ jar files.
+//
+// Different permissions can be granted to JSP pages, classes loaded from
+// the /WEB-INF/classes/ directory, all jar files in the /WEB-INF/lib/
+// directory, or even to individual jar files in the /WEB-INF/lib/ directory.
+//
+// For instance, assume that the standard "examples" application
+// included a JDBC driver that needed to establish a network connection to the
+// corresponding database and used the scrape taglib to get the weather from
+// the NOAA web server.  You might create a "grant" entries like this:
+//
+// The permissions granted to the context root directory apply to JSP pages.
+// grant codeBase "file:${catalina.base}/webapps/examples/-" {
+//      permission java.net.SocketPermission "dbhost.mycompany.com:5432", "connect";
+//      permission java.net.SocketPermission "*.noaa.gov:80", "connect";
+// };
+//
+// The permissions granted to the context WEB-INF/classes directory
+// grant codeBase "file:${catalina.base}/webapps/examples/WEB-INF/classes/-" {
+// };
+//
+// The permission granted to your JDBC driver
+// grant codeBase "jar:file:${catalina.base}/webapps/examples/WEB-INF/lib/driver.jar!/-" {
+//      permission java.net.SocketPermission "dbhost.mycompany.com:5432", "connect";
+// };
+// The permission granted to the scrape taglib
+// grant codeBase "jar:file:${catalina.base}/webapps/examples/WEB-INF/lib/scrape.jar!/-" {
+//      permission java.net.SocketPermission "*.noaa.gov:80", "connect";
+// };
+

=== added file 'examples/tomcat-maven-webapp/tomcat-conf/catalina.properties'
--- examples/tomcat-maven-webapp/tomcat-conf/catalina.properties	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/catalina.properties	2022-05-19 22:01:22 +0000
@@ -0,0 +1,145 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+#
+# List of comma-separated packages that start with or equal this string
+# will cause a security exception to be thrown when
+# passed to checkPackageAccess unless the
+# corresponding RuntimePermission ("accessClassInPackage."+package) has
+# been granted.
+package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.jasper.,org.apache.tomcat.
+#
+# List of comma-separated packages that start with or equal this string
+# will cause a security exception to be thrown when
+# passed to checkPackageDefinition unless the
+# corresponding RuntimePermission ("defineClassInPackage."+package) has
+# been granted.
+#
+# by default, no packages are restricted for definition, and none of
+# the class loaders supplied with the JDK call checkPackageDefinition.
+#
+package.definition=sun.,java.,org.apache.catalina.,org.apache.coyote.,\
+org.apache.jasper.,org.apache.naming.,org.apache.tomcat.
+
+#
+#
+# List of comma-separated paths defining the contents of the "common"
+# classloader. Prefixes should be used to define what is the repository type.
+# Path may be relative to the CATALINA_HOME or CATALINA_BASE path or absolute.
+# If left as blank,the JVM system loader will be used as Catalina's "common"
+# loader.
+# Examples:
+#     "foo": Add this folder as a class repository
+#     "foo/*.jar": Add all the JARs of the specified folder as class
+#                  repositories
+#     "foo/bar.jar": Add bar.jar as a class repository
+#
+# Note: Values are enclosed in double quotes ("...") in case either the
+#       ${catalina.base} path or the ${catalina.home} path contains a comma.
+#       Because double quotes are used for quoting, the double quote character
+#       may not appear in a path.
+common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar"
+
+#
+# List of comma-separated paths defining the contents of the "server"
+# classloader. Prefixes should be used to define what is the repository type.
+# Path may be relative to the CATALINA_HOME or CATALINA_BASE path or absolute.
+# If left as blank, the "common" loader will be used as Catalina's "server"
+# loader.
+# Examples:
+#     "foo": Add this folder as a class repository
+#     "foo/*.jar": Add all the JARs of the specified folder as class
+#                  repositories
+#     "foo/bar.jar": Add bar.jar as a class repository
+#
+# Note: Values may be enclosed in double quotes ("...") in case either the
+#       ${catalina.base} path or the ${catalina.home} path contains a comma.
+#       Because double quotes are used for quoting, the double quote character
+#       may not appear in a path.
+server.loader=
+
+#
+# List of comma-separated paths defining the contents of the "shared"
+# classloader. Prefixes should be used to define what is the repository type.
+# Path may be relative to the CATALINA_BASE path or absolute. If left as blank,
+# the "common" loader will be used as Catalina's "shared" loader.
+# Examples:
+#     "foo": Add this folder as a class repository
+#     "foo/*.jar": Add all the JARs of the specified folder as class
+#                  repositories
+#     "foo/bar.jar": Add bar.jar as a class repository
+# Please note that for single jars, e.g. bar.jar, you need the URL form
+# starting with file:.
+#
+# Note: Values may be enclosed in double quotes ("...") in case either the
+#       ${catalina.base} path or the ${catalina.home} path contains a comma.
+#       Because double quotes are used for quoting, the double quote character
+#       may not appear in a path.
+shared.loader=
+
+# Default list of JAR files that should not be scanned using the JarScanner
+# functionality. This is typically used to scan JARs for configuration
+# information. JARs that do not contain such information may be excluded from
+# the scan to speed up the scanning process. This is the default list. JARs on
+# this list are excluded from all scans. The list must be a comma separated list
+# of JAR file names.
+# The list of JARs to skip may be over-ridden at a Context level for individual
+# scan types by configuring a JarScanner with a nested JarScanFilter.
+# The JARs listed below include:
+# - Tomcat Bootstrap JARs
+# - Tomcat API JARs
+# - Catalina JARs
+# - Jasper JARs
+# - Tomcat JARs
+# - Common non-Tomcat JARs
+# - Test JARs (JUnit, Cobertura and dependencies)
+tomcat.util.scan.StandardJarScanFilter.jarsToSkip=\
+bootstrap.jar,commons-daemon.jar,tomcat-juli.jar,\
+annotations-api.jar,el-api.jar,jsp-api.jar,servlet-api.jar,websocket-api.jar,\
+catalina.jar,catalina-ant.jar,catalina-ha.jar,catalina-storeconfig.jar,\
+catalina-tribes.jar,\
+jasper.jar,jasper-el.jar,ecj-*.jar,\
+tomcat-api.jar,tomcat-util.jar,tomcat-util-scan.jar,tomcat-coyote.jar,\
+tomcat-dbcp.jar,tomcat-jni.jar,tomcat-websocket.jar,\
+tomcat-i18n-en.jar,tomcat-i18n-es.jar,tomcat-i18n-fr.jar,tomcat-i18n-ja.jar,\
+tomcat-juli-adapters.jar,catalina-jmx-remote.jar,catalina-ws.jar,\
+tomcat-jdbc.jar,\
+tools.jar,\
+commons-beanutils*.jar,commons-codec*.jar,commons-collections*.jar,\
+commons-dbcp*.jar,commons-digester*.jar,commons-fileupload*.jar,\
+commons-httpclient*.jar,commons-io*.jar,commons-lang*.jar,commons-logging*.jar,\
+commons-math*.jar,commons-pool*.jar,\
+jstl.jar,taglibs-standard-spec-*.jar,\
+geronimo-spec-jaxrpc*.jar,wsdl4j*.jar,\
+ant.jar,ant-junit*.jar,aspectj*.jar,jmx.jar,h2*.jar,hibernate*.jar,httpclient*.jar,\
+jmx-tools.jar,jta*.jar,log4j*.jar,mail*.jar,slf4j*.jar,\
+xercesImpl.jar,xmlParserAPIs.jar,xml-apis.jar,\
+junit.jar,junit-*.jar,ant-launcher.jar,\
+cobertura-*.jar,asm-*.jar,dom4j-*.jar,icu4j-*.jar,jaxen-*.jar,jdom-*.jar,\
+jetty-*.jar,oro-*.jar,servlet-api-*.jar,tagsoup-*.jar,xmlParserAPIs-*.jar,\
+xom-*.jar
+
+# Default list of JAR files that should be scanned that overrides the default
+# jarsToSkip list above. This is typically used to include a specific JAR that
+# has been excluded by a broad file name pattern in the jarsToSkip list.
+# The list of JARs to scan may be over-ridden at a Context level for individual
+# scan types by configuring a JarScanner with a nested JarScanFilter.
+tomcat.util.scan.StandardJarScanFilter.jarsToScan=log4j-core*.jar,log4j-taglib*.jar
+
+# String cache configuration.
+tomcat.util.buf.StringCache.byte.enabled=true
+#tomcat.util.buf.StringCache.char.enabled=true
+#tomcat.util.buf.StringCache.trainThreshold=500000
+#tomcat.util.buf.StringCache.cacheSize=5000

=== added file 'examples/tomcat-maven-webapp/tomcat-conf/context.xml'
--- examples/tomcat-maven-webapp/tomcat-conf/context.xml	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/context.xml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,36 @@
+<?xml version='1.0' encoding='utf-8'?>
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<!-- The contents of this file will be loaded for each web application -->
+<Context>
+
+    <!-- Default set of monitored resources. If one of these changes, the    -->
+    <!-- web application will be reloaded.                                   -->
+    <WatchedResource>WEB-INF/web.xml</WatchedResource>
+    <WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
+
+    <!-- Uncomment this to disable session persistence across Tomcat restarts -->
+    <!--
+    <Manager pathname="" />
+    -->
+
+    <!-- Uncomment this to enable Comet connection tacking (provides events
+         on session expiration as well as webapp lifecycle) -->
+    <!--
+    <Valve className="org.apache.catalina.valves.CometConnectionManagerValve" />
+    -->
+</Context>

=== added file 'examples/tomcat-maven-webapp/tomcat-conf/logging.properties'
--- examples/tomcat-maven-webapp/tomcat-conf/logging.properties	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/logging.properties	2022-05-19 22:01:22 +0000
@@ -0,0 +1,64 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+handlers = 1catalina.org.apache.juli.AsyncFileHandler, 2localhost.org.apache.juli.AsyncFileHandler, 3manager.org.apache.juli.AsyncFileHandler, 4host-manager.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler
+
+.handlers = 1catalina.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler
+
+############################################################
+# Handler specific properties.
+# Describes specific configuration info for Handlers.
+############################################################
+
+1catalina.org.apache.juli.AsyncFileHandler.level = FINE
+1catalina.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
+1catalina.org.apache.juli.AsyncFileHandler.prefix = catalina.
+
+2localhost.org.apache.juli.AsyncFileHandler.level = FINE
+2localhost.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
+2localhost.org.apache.juli.AsyncFileHandler.prefix = localhost.
+
+3manager.org.apache.juli.AsyncFileHandler.level = FINE
+3manager.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
+3manager.org.apache.juli.AsyncFileHandler.prefix = manager.
+
+4host-manager.org.apache.juli.AsyncFileHandler.level = FINE
+4host-manager.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs
+4host-manager.org.apache.juli.AsyncFileHandler.prefix = host-manager.
+
+java.util.logging.ConsoleHandler.level = FINE
+java.util.logging.ConsoleHandler.formatter = org.apache.juli.OneLineFormatter
+
+
+############################################################
+# Facility specific properties.
+# Provides extra control for each logger.
+############################################################
+
+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = INFO
+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers = 2localhost.org.apache.juli.AsyncFileHandler
+
+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level = INFO
+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].handlers = 3manager.org.apache.juli.AsyncFileHandler
+
+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level = INFO
+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].handlers = 4host-manager.org.apache.juli.AsyncFileHandler
+
+# For example, set the org.apache.catalina.util.LifecycleBase logger to log
+# each component that extends LifecycleBase changing state:
+#org.apache.catalina.util.LifecycleBase.level = FINE
+
+# To see debug messages in TldLocationsCache, uncomment the following line:
+#org.apache.jasper.compiler.TldLocationsCache.level = FINE

=== added file 'examples/tomcat-maven-webapp/tomcat-conf/server.xml'
--- examples/tomcat-maven-webapp/tomcat-conf/server.xml	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/server.xml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,142 @@
+<?xml version='1.0' encoding='utf-8'?>
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<!-- Note:  A "Server" is not itself a "Container", so you may not
+     define subcomponents such as "Valves" at this level.
+     Documentation at /docs/config/server.html
+ -->
+<Server port="8005" shutdown="SHUTDOWN">
+  <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
+  <!-- Security listener. Documentation at /docs/config/listeners.html
+  <Listener className="org.apache.catalina.security.SecurityListener" />
+  -->
+  <!--APR library loader. Documentation at /docs/apr.html -->
+  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
+  <!-- Prevent memory leaks due to use of particular java/javax APIs-->
+  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
+  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
+  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
+
+  <!-- Global JNDI resources
+       Documentation at /docs/jndi-resources-howto.html
+  -->
+  <GlobalNamingResources>
+    <!-- Editable user database that can also be used by
+         UserDatabaseRealm to authenticate users
+    -->
+    <Resource name="UserDatabase" auth="Container"
+              type="org.apache.catalina.UserDatabase"
+              description="User database that can be updated and saved"
+              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
+              pathname="conf/tomcat-users.xml" />
+  </GlobalNamingResources>
+
+  <!-- A "Service" is a collection of one or more "Connectors" that share
+       a single "Container" Note:  A "Service" is not itself a "Container",
+       so you may not define subcomponents such as "Valves" at this level.
+       Documentation at /docs/config/service.html
+   -->
+  <Service name="Catalina">
+
+    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
+    <!--
+    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
+        maxThreads="150" minSpareThreads="4"/>
+    -->
+
+
+    <!-- A "Connector" represents an endpoint by which requests are received
+         and responses are returned. Documentation at :
+         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
+         Java AJP  Connector: /docs/config/ajp.html
+         APR (HTTP/AJP) Connector: /docs/apr.html
+         Define a non-SSL/TLS HTTP/1.1 Connector on port 8080
+    -->
+    <Connector port="8080" protocol="HTTP/1.1"
+               connectionTimeout="20000"
+               redirectPort="8443" />
+    <!-- A "Connector" using the shared thread pool-->
+    <!--
+    <Connector executor="tomcatThreadPool"
+               port="8080" protocol="HTTP/1.1"
+               connectionTimeout="20000"
+               redirectPort="8443" />
+    -->
+    <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
+         This connector uses the NIO implementation that requires the JSSE
+         style configuration. When using the APR/native implementation, the
+         OpenSSL style configuration is required as described in the APR/native
+         documentation -->
+    <!--
+    <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
+               maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
+               clientAuth="false" sslProtocol="TLS" />
+    -->
+
+    <!-- Define an AJP 1.3 Connector on port 8009 -->
+    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
+
+
+    <!-- An Engine represents the entry point (within Catalina) that processes
+         every request.  The Engine implementation for Tomcat stand alone
+         analyzes the HTTP headers included with the request, and passes them
+         on to the appropriate Host (virtual host).
+         Documentation at /docs/config/engine.html -->
+
+    <!-- You should set jvmRoute to support load-balancing via AJP ie :
+    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
+    -->
+    <Engine name="Catalina" defaultHost="localhost">
+
+      <!--For clustering, please take a look at documentation at:
+          /docs/cluster-howto.html  (simple how to)
+          /docs/config/cluster.html (reference documentation) -->
+      <!--
+      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
+      -->
+
+      <!-- Use the LockOutRealm to prevent attempts to guess user passwords
+           via a brute-force attack -->
+      <Realm className="org.apache.catalina.realm.LockOutRealm">
+        <!-- This Realm uses the UserDatabase configured in the global JNDI
+             resources under the key "UserDatabase".  Any edits
+             that are performed against this UserDatabase are immediately
+             available for use by the Realm.  -->
+        <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
+               resourceName="UserDatabase"/>
+      </Realm>
+
+      <Host name="localhost"  appBase="webapps"
+            unpackWARs="true" autoDeploy="true">
+
+        <!-- SingleSignOn valve, share authentication between web applications
+             Documentation at: /docs/config/valve.html -->
+        <!--
+        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
+        -->
+
+        <!-- Access log processes all example.
+             Documentation at: /docs/config/valve.html
+             Note: The pattern used is equivalent to using pattern="common" -->
+        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
+               prefix="localhost_access_log" suffix=".txt"
+               pattern="%h %l %u %t &quot;%r&quot; %s %b" />
+
+      </Host>
+    </Engine>
+  </Service>
+</Server>

=== added file 'examples/tomcat-maven-webapp/tomcat-conf/tomcat-users.xml'
--- examples/tomcat-maven-webapp/tomcat-conf/tomcat-users.xml	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/tomcat-users.xml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,39 @@
+<?xml version='1.0' encoding='utf-8'?>
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<tomcat-users xmlns="http://tomcat.apache.org/xml"
+              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+              xsi:schemaLocation="http://tomcat.apache.org/xml tomcat-users.xsd"
+              version="1.0">
+<!--
+  NOTE:  By default, no user is included in the "manager-gui" role required
+  to operate the "/manager/html" web application.  If you wish to use this app,
+  you must define such a user - the username and password are arbitrary.
+-->
+<!--
+  NOTE:  The sample user and role entries below are wrapped in a comment
+  and thus are ignored when reading this file. Do not forget to remove
+  <!.. ..> that surrounds them.
+-->
+<!--
+  <role rolename="tomcat"/>
+  <role rolename="role1"/>
+  <user username="tomcat" password="tomcat" roles="tomcat"/>
+  <user username="both" password="tomcat" roles="tomcat,role1"/>
+  <user username="role1" password="tomcat" roles="role1"/>
+-->
+</tomcat-users>

=== added file 'examples/tomcat-maven-webapp/tomcat-conf/tomcat-users.xsd'
--- examples/tomcat-maven-webapp/tomcat-conf/tomcat-users.xsd	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/tomcat-users.xsd	2022-05-19 22:01:22 +0000
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<xs:schema xmlns="http://www.w3.org/2001/XMLSchema"
+           targetNamespace="http://tomcat.apache.org/xml"
+           xmlns:users="http://tomcat.apache.org/xml"
+           xmlns:xs="http://www.w3.org/2001/XMLSchema"
+           elementFormDefault="qualified"
+           attributeFormDefault="unqualified"
+           version="1.0">
+  <xs:element name="tomcat-users">
+    <xs:complexType>
+      <xs:sequence>
+        <xs:element name="role" minOccurs="0" maxOccurs="unbounded">
+          <xs:complexType>
+            <xs:attribute name="rolename" use="required" type="users:entityname" />
+            <xs:attribute name="description" type="xs:string" />
+          </xs:complexType>
+        </xs:element>
+        <xs:element name="group" minOccurs="0" maxOccurs="unbounded">
+          <xs:complexType>
+            <xs:attribute name="groupname" use="required" type="users:entityname" />
+            <xs:attribute name="description" type="xs:string" />
+            <xs:attribute name="roles" type="xs:string" />
+          </xs:complexType>
+        </xs:element>
+        <xs:element name="user" minOccurs="0" maxOccurs="unbounded">
+          <xs:complexType>
+            <xs:attribute name="username" use="required" type="users:entityname" />
+            <xs:attribute name="fullname" type="xs:string" />
+            <xs:attribute name="password" type="xs:string" />
+            <xs:attribute name="roles" type="xs:string" />
+            <xs:attribute name="groups" type="xs:string" />
+          </xs:complexType>
+        </xs:element>
+      </xs:sequence>
+      <xs:attribute name="version" type="xs:string" />
+    </xs:complexType>
+  </xs:element>
+  <xs:simpleType name="entityname">
+    <xs:restriction base="xs:string">
+      <xs:minLength value="1"/>
+    </xs:restriction>
+  </xs:simpleType>
+</xs:schema>
\ No newline at end of file

=== added file 'examples/tomcat-maven-webapp/tomcat-conf/web.xml'
--- examples/tomcat-maven-webapp/tomcat-conf/web.xml	1970-01-01 00:00:00 +0000
+++ examples/tomcat-maven-webapp/tomcat-conf/web.xml	2022-05-19 22:01:22 +0000
@@ -0,0 +1,4664 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
+                      http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
+  version="3.1">
+
+  <!-- ======================== Introduction ============================== -->
+  <!-- This document defines default values for *all* web applications      -->
+  <!-- loaded into this instance of Tomcat.  As each application is         -->
+  <!-- deployed, this file is processed, followed by the                    -->
+  <!-- "/WEB-INF/web.xml" deployment descriptor from your own               -->
+  <!-- applications.                                                        -->
+  <!--                                                                      -->
+  <!-- WARNING:  Do not configure application-specific resources here!      -->
+  <!-- They should go in the "/WEB-INF/web.xml" file in your application.   -->
+
+
+  <!-- ================== Built In Servlet Definitions ==================== -->
+
+
+  <!-- The default servlet for all web applications, that serves static     -->
+  <!-- resources.  It processes all requests that are not mapped to other   -->
+  <!-- servlets with servlet mappings (defined either here or in your own   -->
+  <!-- web.xml file).  This servlet supports the following initialization   -->
+  <!-- parameters (default values are in square brackets):                  -->
+  <!--                                                                      -->
+  <!--   debug               Debugging detail level for messages logged     -->
+  <!--                       by this servlet.  [0]                          -->
+  <!--                                                                      -->
+  <!--   fileEncoding        Encoding to be used to read static resources   -->
+  <!--                       [platform default]                             -->
+  <!--                                                                      -->
+  <!--   input               Input buffer size (in bytes) when reading      -->
+  <!--                       resources to be served.  [2048]                -->
+  <!--                                                                      -->
+  <!--   listings            Should directory listings be produced if there -->
+  <!--                       is no welcome file in this directory?  [false] -->
+  <!--                       WARNING: Listings for directories with many    -->
+  <!--                       entries can be slow and may consume            -->
+  <!--                       significant proportions of server resources.   -->
+  <!--                                                                      -->
+  <!--   output              Output buffer size (in bytes) when writing     -->
+  <!--                       resources to be served.  [2048]                -->
+  <!--                                                                      -->
+  <!--   readonly            Is this context "read only", so HTTP           -->
+  <!--                       commands like PUT and DELETE are               -->
+  <!--                       rejected?  [true]                              -->
+  <!--                                                                      -->
+  <!--   readmeFile          File to display together with the directory    -->
+  <!--                       contents. [null]                               -->
+  <!--                                                                      -->
+  <!--   sendfileSize        If the connector used supports sendfile, this  -->
+  <!--                       represents the minimal file size in KB for     -->
+  <!--                       which sendfile will be used. Use a negative    -->
+  <!--                       value to always disable sendfile.  [48]        -->
+  <!--                                                                      -->
+  <!--   useAcceptRanges     Should the Accept-Ranges header be included    -->
+  <!--                       in responses where appropriate? [true]         -->
+  <!--                                                                      -->
+  <!--  For directory listing customization. Checks localXsltFile, then     -->
+  <!--  globalXsltFile, then defaults to original behavior.                 -->
+  <!--                                                                      -->
+  <!--   localXsltFile       Make directory listings an XML doc and         -->
+  <!--                       pass the result to this style sheet residing   -->
+  <!--                       in that directory. This overrides              -->
+  <!--                       contextXsltFile and globalXsltFile[null]       -->
+  <!--                                                                      -->
+  <!--   contextXsltFile     Make directory listings an XML doc and         -->
+  <!--                       pass the result to this style sheet which is   -->
+  <!--                       relative to the context root. This overrides   -->
+  <!--                       globalXsltFile[null]                           -->
+  <!--                                                                      -->
+  <!--   globalXsltFile      Site wide configuration version of             -->
+  <!--                       localXsltFile. This argument must either be an -->
+  <!--                       absolute or relative (to either                -->
+  <!--                       $CATALINA_BASE/conf or $CATALINA_HOME/conf)    -->
+  <!--                       path that points to a location below either    -->
+  <!--                       $CATALINA_BASE/conf (checked first) or         -->
+  <!--                       $CATALINA_HOME/conf (checked second).[null]    -->
+  <!--                                                                      -->
+  <!--   showServerInfo      Should server information be presented in the  -->
+  <!--                       response sent to clients when directory        -->
+  <!--                       listings is enabled? [true]                    -->
+
+    <servlet>
+        <servlet-name>default</servlet-name>
+        <servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
+        <init-param>
+            <param-name>debug</param-name>
+            <param-value>0</param-value>
+        </init-param>
+        <init-param>
+            <param-name>listings</param-name>
+            <param-value>false</param-value>
+        </init-param>
+        <load-on-startup>1</load-on-startup>
+    </servlet>
+
+
+  <!-- The JSP page compiler and execution servlet, which is the mechanism  -->
+  <!-- used by Tomcat to support JSP pages.  Traditionally, this servlet    -->
+  <!-- is mapped to the URL pattern "*.jsp".  This servlet supports the     -->
+  <!-- following initialization parameters (default values are in square    -->
+  <!-- brackets):                                                           -->
+  <!--                                                                      -->
+  <!--   checkInterval       If development is false and checkInterval is   -->
+  <!--                       greater than zero, background compilations are -->
+  <!--                       enabled. checkInterval is the time in seconds  -->
+  <!--                       between checks to see if a JSP page (and its   -->
+  <!--                       dependent files) needs to  be recompiled. [0]  -->
+  <!--                                                                      -->
+  <!--   classdebuginfo      Should the class file be compiled with         -->
+  <!--                       debugging information?  [true]                 -->
+  <!--                                                                      -->
+  <!--   classpath           What class path should I use while compiling   -->
+  <!--                       generated servlets?  [Created dynamically      -->
+  <!--                       based on the current web application]          -->
+  <!--                                                                      -->
+  <!--   compiler            Which compiler Ant should use to compile JSP   -->
+  <!--                       pages.  See the jasper documentation for more  -->
+  <!--                       information.                                   -->
+  <!--                                                                      -->
+  <!--   compilerSourceVM    Compiler source VM. [1.7]                      -->
+  <!--                                                                      -->
+  <!--   compilerTargetVM    Compiler target VM. [1.7]                      -->
+  <!--                                                                      -->
+  <!--   development         Is Jasper used in development mode? If true,   -->
+  <!--                       the frequency at which JSPs are checked for    -->
+  <!--                       modification may be specified via the          -->
+  <!--                       modificationTestInterval parameter. [true]     -->
+  <!--                                                                      -->
+  <!--   displaySourceFragment                                              -->
+  <!--                       Should a source fragment be included in        -->
+  <!--                       exception messages? [true]                     -->
+  <!--                                                                      -->
+  <!--   dumpSmap            Should the SMAP info for JSR45 debugging be    -->
+  <!--                       dumped to a file? [false]                      -->
+  <!--                       False if suppressSmap is true                  -->
+  <!--                                                                      -->
+  <!--   enablePooling       Determines whether tag handler pooling is      -->
+  <!--                       enabled. This is a compilation option. It will -->
+  <!--                       not alter the behaviour of JSPs that have      -->
+  <!--                       already been compiled. [true]                  -->
+  <!--                                                                      -->
+  <!--   engineOptionsClass  Allows specifying the Options class used to    -->
+  <!--                       configure Jasper. If not present, the default  -->
+  <!--                       EmbeddedServletOptions will be used.           -->
+  <!--                                                                      -->
+  <!--   errorOnUseBeanInvalidClassAttribute                                -->
+  <!--                       Should Jasper issue an error when the value of -->
+  <!--                       the class attribute in an useBean action is    -->
+  <!--                       not a valid bean class?  [true]                -->
+  <!--                                                                      -->
+  <!--   fork                Tell Ant to fork compiles of JSP pages so that -->
+  <!--                       a separate JVM is used for JSP page compiles   -->
+  <!--                       from the one Tomcat is running in. [true]      -->
+  <!--                                                                      -->
+  <!--   genStringAsCharArray                                               -->
+  <!--                       Should text strings be generated as char       -->
+  <!--                       arrays, to improve performance in some cases?  -->
+  <!--                       [false]                                        -->
+  <!--                                                                      -->
+  <!--   ieClassId           The class-id value to be sent to Internet      -->
+  <!--                       Explorer when using <jsp:plugin> tags.         -->
+  <!--                       [clsid:8AD9C840-044E-11D1-B3E9-00805F499D93]   -->
+  <!--                                                                      -->
+  <!--   javaEncoding        Java file encoding to use for generating java  -->
+  <!--                       source files. [UTF8]                           -->
+  <!--                                                                      -->
+  <!--   keepgenerated       Should we keep the generated Java source code  -->
+  <!--                       for each page instead of deleting it? [true]   -->
+  <!--                                                                      -->
+  <!--   mappedfile          Should we generate static content with one     -->
+  <!--                       print statement per input line, to ease        -->
+  <!--                       debugging?  [true]                             -->
+  <!--                                                                      -->
+  <!--   maxLoadedJsps       The maximum number of JSPs that will be loaded -->
+  <!--                       for a web application. If more than this       -->
+  <!--                       number of JSPs are loaded, the least recently  -->
+  <!--                       used JSPs will be unloaded so that the number  -->
+  <!--                       of JSPs loaded at any one time does not exceed -->
+  <!--                       this limit. A value of zero or less indicates  -->
+  <!--                       no limit. [-1]                                 -->
+  <!--                                                                      -->
+  <!--   jspIdleTimeout      The amount of time in seconds a JSP can be     -->
+  <!--                       idle before it is unloaded. A value of zero    -->
+  <!--                       or less indicates never unload. [-1]           -->
+  <!--                                                                      -->
+  <!--   modificationTestInterval                                           -->
+  <!--                       Causes a JSP (and its dependent files) to not  -->
+  <!--                       be checked for modification during the         -->
+  <!--                       specified time interval (in seconds) from the  -->
+  <!--                       last time the JSP was checked for              -->
+  <!--                       modification. A value of 0 will cause the JSP  -->
+  <!--                       to be checked on every access.                 -->
+  <!--                       Used in development mode only. [4]             -->
+  <!--                                                                      -->
+  <!--   recompileOnFail     If a JSP compilation fails should the          -->
+  <!--                       modificationTestInterval be ignored and the    -->
+  <!--                       next access trigger a re-compilation attempt?  -->
+  <!--                       Used in development mode only and is disabled  -->
+  <!--                       by default as compilation may be expensive and -->
+  <!--                       could lead to excessive resource usage.        -->
+  <!--                       [false]                                        -->
+  <!--                                                                      -->
+  <!--   scratchdir          What scratch directory should we use when      -->
+  <!--                       compiling JSP pages?  [default work directory  -->
+  <!--                       for the current web application]               -->
+  <!--                                                                      -->
+  <!--   suppressSmap        Should the generation of SMAP info for JSR45   -->
+  <!--                       debugging be suppressed?  [false]              -->
+  <!--                                                                      -->
+  <!--   trimSpaces          Should white spaces in template text between   -->
+  <!--                       actions or directives be trimmed?  [false]     -->
+  <!--                                                                      -->
+  <!--   xpoweredBy          Determines whether X-Powered-By response       -->
+  <!--                       header is added by generated servlet.  [false] -->
+
+    <servlet>
+        <servlet-name>jsp</servlet-name>
+        <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
+        <init-param>
+            <param-name>fork</param-name>
+            <param-value>false</param-value>
+        </init-param>
+        <init-param>
+            <param-name>xpoweredBy</param-name>
+            <param-value>false</param-value>
+        </init-param>
+        <load-on-startup>3</load-on-startup>
+    </servlet>
+
+
+  <!-- NOTE: An SSI Filter is also available as an alternative SSI          -->
+  <!-- implementation. Use either the Servlet or the Filter but NOT both.   -->
+  <!--                                                                      -->
+  <!-- Server Side Includes processing servlet, which processes SSI         -->
+  <!-- directives in HTML pages consistent with similar support in web      -->
+  <!-- servers like Apache.  Traditionally, this servlet is mapped to the   -->
+  <!-- URL pattern "*.shtml".  This servlet supports the following          -->
+  <!-- initialization parameters (default values are in square brackets):   -->
+  <!--                                                                      -->
+  <!--   buffered            Should output from this servlet be buffered?   -->
+  <!--                       (0=false, 1=true)  [0]                         -->
+  <!--                                                                      -->
+  <!--   debug               Debugging detail level for messages logged     -->
+  <!--                       by this servlet.  [0]                          -->
+  <!--                                                                      -->
+  <!--   expires             The number of seconds before a page with SSI   -->
+  <!--                       directives will expire.  [No default]          -->
+  <!--                                                                      -->
+  <!--   isVirtualWebappRelative                                            -->
+  <!--                       Should "virtual" paths be interpreted as       -->
+  <!--                       relative to the context root, instead of       -->
+  <!--                       the server root? [false]                       -->
+  <!--                                                                      -->
+  <!--   inputEncoding       The encoding to assume for SSI resources if    -->
+  <!--                       one is not available from the resource.        -->
+  <!--                       [Platform default]                             -->
+  <!--                                                                      -->
+  <!--   outputEncoding      The encoding to use for the page that results  -->
+  <!--                       from the SSI processing. [UTF-8]               -->
+  <!--                                                                      -->
+  <!--   allowExec           Is use of the exec command enabled? [false]    -->
+
+<!--
+    <servlet>
+        <servlet-name>ssi</servlet-name>
+        <servlet-class>
+          org.apache.catalina.ssi.SSIServlet
+        </servlet-class>
+        <init-param>
+          <param-name>buffered</param-name>
+          <param-value>1</param-value>
+        </init-param>
+        <init-param>
+          <param-name>debug</param-name>
+          <param-value>0</param-value>
+        </init-param>
+        <init-param>
+          <param-name>expires</param-name>
+          <param-value>666</param-value>
+        </init-param>
+        <init-param>
+          <param-name>isVirtualWebappRelative</param-name>
+          <param-value>false</param-value>
+        </init-param>
+        <load-on-startup>4</load-on-startup>
+    </servlet>
+-->
+
+
+  <!-- Common Gateway Includes (CGI) processing servlet, which supports     -->
+  <!-- execution of external applications that conform to the CGI spec      -->
+  <!-- requirements.  Typically, this servlet is mapped to the URL pattern  -->
+  <!-- "/cgi-bin/*", which means that any CGI applications that are         -->
+  <!-- executed must be present within the web application.  This servlet   -->
+  <!-- supports the following initialization parameters (default values     -->
+  <!-- are in square brackets):                                             -->
+  <!--                                                                      -->
+  <!--   cgiPathPrefix        The CGI search path will start at             -->
+  <!--                        webAppRootDir + File.separator + this prefix. -->
+  <!--                        If not set, then webAppRootDir is used.       -->
+  <!--                        Recommended value: WEB-INF/cgi                -->
+  <!--                                                                      -->
+  <!--   debug                Debugging detail level for messages logged    -->
+  <!--                        by this servlet.  [0]                         -->
+  <!--                                                                      -->
+  <!--   executable           Name of the executable used to run the        -->
+  <!--                        script. [perl]                                -->
+  <!--                                                                      -->
+  <!--   parameterEncoding    Name of parameter encoding to be used with    -->
+  <!--                        CGI servlet.                                  -->
+  <!--                        [System.getProperty("file.encoding","UTF-8")] -->
+  <!--                                                                      -->
+  <!--   passShellEnvironment Should the shell environment variables (if    -->
+  <!--                        any) be passed to the CGI script? [false]     -->
+  <!--                                                                      -->
+  <!--   stderrTimeout        The time (in milliseconds) to wait for the    -->
+  <!--                        reading of stderr to complete before          -->
+  <!--                        terminating the CGI process. [2000]           -->
+
+<!--
+    <servlet>
+        <servlet-name>cgi</servlet-name>
+        <servlet-class>org.apache.catalina.servlets.CGIServlet</servlet-class>
+        <init-param>
+          <param-name>debug</param-name>
+          <param-value>0</param-value>
+        </init-param>
+        <init-param>
+          <param-name>cgiPathPrefix</param-name>
+          <param-value>WEB-INF/cgi</param-value>
+        </init-param>
+         <load-on-startup>5</load-on-startup>
+    </servlet>
+-->
+
+
+  <!-- ================ Built In Servlet Mappings ========================= -->
+
+
+  <!-- The servlet mappings for the built in servlets defined above.  Note  -->
+  <!-- that, by default, the CGI and SSI servlets are *not* mapped.  You    -->
+  <!-- must uncomment these mappings (or add them to your application's own -->
+  <!-- web.xml deployment descriptor) to enable these services              -->
+
+    <!-- The mapping for the default servlet -->
+    <servlet-mapping>
+        <servlet-name>default</servlet-name>
+        <url-pattern>/</url-pattern>
+    </servlet-mapping>
+
+    <!-- The mappings for the JSP servlet -->
+    <servlet-mapping>
+        <servlet-name>jsp</servlet-name>
+        <url-pattern>*.jsp</url-pattern>
+        <url-pattern>*.jspx</url-pattern>
+    </servlet-mapping>
+
+    <!-- The mapping for the SSI servlet -->
+<!--
+    <servlet-mapping>
+        <servlet-name>ssi</servlet-name>
+        <url-pattern>*.shtml</url-pattern>
+    </servlet-mapping>
+-->
+
+    <!-- The mapping for the CGI Gateway servlet -->
+
+<!--
+    <servlet-mapping>
+        <servlet-name>cgi</servlet-name>
+        <url-pattern>/cgi-bin/*</url-pattern>
+    </servlet-mapping>
+-->
+
+
+  <!-- ================== Built In Filter Definitions ===================== -->
+
+  <!-- A filter that sets various security related HTTP Response headers.   -->
+  <!-- This filter supports the following initialization parameters         -->
+  <!-- (default values are in square brackets):                             -->
+  <!--                                                                      -->
+  <!--   hstsEnabled         Should the HTTP Strict Transport Security      -->
+  <!--                       (HSTS) header be added to the response? See    -->
+  <!--                       RFC 6797 for more information on HSTS. [true]  -->
+  <!--                                                                      -->
+  <!--   hstsMaxAgeSeconds   The max age value that should be used in the   -->
+  <!--                       HSTS header. Negative values will be treated   -->
+  <!--                       as zero. [0]                                   -->
+  <!--                                                                      -->
+  <!--   hstsIncludeSubDomains                                              -->
+  <!--                       Should the includeSubDomains parameter be      -->
+  <!--                       included in the HSTS header.                   -->
+  <!--                                                                      -->
+  <!--   antiClickJackingEnabled                                            -->
+  <!--                       Should the anti click-jacking header           -->
+  <!--                       X-Frame-Options be added to every response?    -->
+  <!--                       [true]                                         -->
+  <!--                                                                      -->
+  <!--   antiClickJackingOption                                             -->
+  <!--                       What value should be used for the header. Must -->
+  <!--                       be one of DENY, SAMEORIGIN, ALLOW-FROM         -->
+  <!--                       (case-insensitive). [DENY]                     -->
+  <!--                                                                      -->
+  <!--   antiClickJackingUri IF ALLOW-FROM is used, what URI should be      -->
+  <!--                       allowed? []                                    -->
+  <!--                                                                      -->
+  <!--   blockContentTypeSniffingEnabled                                    -->
+  <!--                       Should the header that blocks content type     -->
+  <!--                       sniffing be added to every response? [true]    -->
+<!--
+    <filter>
+        <filter-name>httpHeaderSecurity</filter-name>
+        <filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class>
+        <async-supported>true</async-supported>
+    </filter>
+-->
+
+  <!-- A filter that sets character encoding that is used to decode -->
+  <!-- parameters in a POST request -->
+<!--
+    <filter>
+        <filter-name>setCharacterEncodingFilter</filter-name>
+        <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
+        <init-param>
+            <param-name>encoding</param-name>
+            <param-value>UTF-8</param-value>
+        </init-param>
+        <async-supported>true</async-supported>
+    </filter>
+-->
+
+  <!-- A filter that triggers request parameters parsing and rejects the    -->
+  <!-- request if some parameters were skipped because of parsing errors or -->
+  <!-- request size limitations.                                            -->
+<!--
+    <filter>
+        <filter-name>failedRequestFilter</filter-name>
+        <filter-class>
+          org.apache.catalina.filters.FailedRequestFilter
+        </filter-class>
+        <async-supported>true</async-supported>
+    </filter>
+-->
+
+
+  <!-- NOTE: An SSI Servlet is also available as an alternative SSI         -->
+  <!-- implementation. Use either the Servlet or the Filter but NOT both.   -->
+  <!--                                                                      -->
+  <!-- Server Side Includes processing filter, which processes SSI          -->
+  <!-- directives in HTML pages consistent with similar support in web      -->
+  <!-- servers like Apache.  Traditionally, this filter is mapped to the    -->
+  <!-- URL pattern "*.shtml", though it can be mapped to "*" as it will     -->
+  <!-- selectively enable/disable SSI processing based on mime types. For   -->
+  <!-- this to work you will need to uncomment the .shtml mime type         -->
+  <!-- definition towards the bottom of this file.                          -->
+  <!-- The contentType init param allows you to apply SSI processing to JSP -->
+  <!-- pages, javascript, or any other content you wish.  This filter       -->
+  <!-- supports the following initialization parameters (default values are -->
+  <!-- in square brackets):                                                 -->
+  <!--                                                                      -->
+  <!--   contentType         A regex pattern that must be matched before    -->
+  <!--                       SSI processing is applied.                     -->
+  <!--                       [text/x-server-parsed-html(;.*)?]              -->
+  <!--                                                                      -->
+  <!--   debug               Debugging detail level for messages logged     -->
+  <!--                       by this servlet.  [0]                          -->
+  <!--                                                                      -->
+  <!--   expires             The number of seconds before a page with SSI   -->
+  <!--                       directives will expire.  [No default]          -->
+  <!--                                                                      -->
+  <!--   isVirtualWebappRelative                                            -->
+  <!--                       Should "virtual" paths be interpreted as       -->
+  <!--                       relative to the context root, instead of       -->
+  <!--                       the server root? [false]                       -->
+  <!--                                                                      -->
+  <!--   allowExec           Is use of the exec command enabled? [false]    -->
+
+<!--
+    <filter>
+        <filter-name>ssi</filter-name>
+        <filter-class>
+          org.apache.catalina.ssi.SSIFilter
+        </filter-class>
+        <init-param>
+          <param-name>contentType</param-name>
+          <param-value>text/x-server-parsed-html(;.*)?</param-value>
+        </init-param>
+        <init-param>
+          <param-name>debug</param-name>
+          <param-value>0</param-value>
+        </init-param>
+        <init-param>
+          <param-name>expires</param-name>
+          <param-value>666</param-value>
+        </init-param>
+        <init-param>
+          <param-name>isVirtualWebappRelative</param-name>
+          <param-value>false</param-value>
+        </init-param>
+    </filter>
+-->
+
+
+  <!-- ==================== Built In Filter Mappings ====================== -->
+
+  <!-- The mapping for the HTTP header security Filter -->
+<!--
+    <filter-mapping>
+        <filter-name>httpHeaderSecurity</filter-name>
+        <url-pattern>/*</url-pattern>
+        <dispatcher>REQUEST</dispatcher>
+    </filter-mapping>
+-->
+
+  <!-- The mapping for the Set Character Encoding Filter -->
+<!--
+    <filter-mapping>
+        <filter-name>setCharacterEncodingFilter</filter-name>
+        <url-pattern>/*</url-pattern>
+    </filter-mapping>
+-->
+
+  <!-- The mapping for the Failed Request Filter -->
+<!--
+    <filter-mapping>
+        <filter-name>failedRequestFilter</filter-name>
+        <url-pattern>/*</url-pattern>
+    </filter-mapping>
+-->
+
+  <!-- The mapping for the SSI Filter -->
+<!--
+    <filter-mapping>
+        <filter-name>ssi</filter-name>
+        <url-pattern>*.shtml</url-pattern>
+    </filter-mapping>
+-->
+
+
+  <!-- ==================== Default Session Configuration ================= -->
+  <!-- You can set the default session timeout (in minutes) for all newly   -->
+  <!-- created sessions by modifying the value below.                       -->
+
+    <session-config>
+        <session-timeout>30</session-timeout>
+    </session-config>
+
+
+  <!-- ===================== Default MIME Type Mappings =================== -->
+  <!-- When serving static resources, Tomcat will automatically generate    -->
+  <!-- a "Content-Type" header based on the resource's filename extension,  -->
+  <!-- based on these mappings.  Additional mappings can be added here (to  -->
+  <!-- apply to all web applications), or in your own application's web.xml -->
+  <!-- deployment descriptor.                                               -->
+  <!-- Note: Extensions are always matched in a case-insensitive manner.    -->
+
+    <mime-mapping>
+        <extension>123</extension>
+        <mime-type>application/vnd.lotus-1-2-3</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>3dml</extension>
+        <mime-type>text/vnd.in3d.3dml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>3ds</extension>
+        <mime-type>image/x-3ds</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>3g2</extension>
+        <mime-type>video/3gpp2</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>3gp</extension>
+        <mime-type>video/3gpp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>7z</extension>
+        <mime-type>application/x-7z-compressed</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aab</extension>
+        <mime-type>application/x-authorware-bin</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aac</extension>
+        <mime-type>audio/x-aac</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aam</extension>
+        <mime-type>application/x-authorware-map</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aas</extension>
+        <mime-type>application/x-authorware-seg</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>abs</extension>
+        <mime-type>audio/x-mpeg</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>abw</extension>
+        <mime-type>application/x-abiword</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ac</extension>
+        <mime-type>application/pkix-attr-cert</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>acc</extension>
+        <mime-type>application/vnd.americandynamics.acc</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ace</extension>
+        <mime-type>application/x-ace-compressed</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>acu</extension>
+        <mime-type>application/vnd.acucobol</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>acutc</extension>
+        <mime-type>application/vnd.acucorp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>adp</extension>
+        <mime-type>audio/adpcm</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aep</extension>
+        <mime-type>application/vnd.audiograph</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>afm</extension>
+        <mime-type>application/x-font-type1</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>afp</extension>
+        <mime-type>application/vnd.ibm.modcap</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ahead</extension>
+        <mime-type>application/vnd.ahead.space</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ai</extension>
+        <mime-type>application/postscript</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aif</extension>
+        <mime-type>audio/x-aiff</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aifc</extension>
+        <mime-type>audio/x-aiff</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aiff</extension>
+        <mime-type>audio/x-aiff</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aim</extension>
+        <mime-type>application/x-aim</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>air</extension>
+        <mime-type>application/vnd.adobe.air-application-installer-package+zip</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ait</extension>
+        <mime-type>application/vnd.dvb.ait</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ami</extension>
+        <mime-type>application/vnd.amiga.ami</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>anx</extension>
+        <mime-type>application/annodex</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>apk</extension>
+        <mime-type>application/vnd.android.package-archive</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>appcache</extension>
+        <mime-type>text/cache-manifest</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>application</extension>
+        <mime-type>application/x-ms-application</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>apr</extension>
+        <mime-type>application/vnd.lotus-approach</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>arc</extension>
+        <mime-type>application/x-freearc</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>art</extension>
+        <mime-type>image/x-jg</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>asc</extension>
+        <mime-type>application/pgp-signature</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>asf</extension>
+        <mime-type>video/x-ms-asf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>asm</extension>
+        <mime-type>text/x-asm</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aso</extension>
+        <mime-type>application/vnd.accpac.simply.aso</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>asx</extension>
+        <mime-type>video/x-ms-asf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>atc</extension>
+        <mime-type>application/vnd.acucorp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>atom</extension>
+        <mime-type>application/atom+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>atomcat</extension>
+        <mime-type>application/atomcat+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>atomsvc</extension>
+        <mime-type>application/atomsvc+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>atx</extension>
+        <mime-type>application/vnd.antix.game-component</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>au</extension>
+        <mime-type>audio/basic</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>avi</extension>
+        <mime-type>video/x-msvideo</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>avx</extension>
+        <mime-type>video/x-rad-screenplay</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>aw</extension>
+        <mime-type>application/applixware</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>axa</extension>
+        <mime-type>audio/annodex</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>axv</extension>
+        <mime-type>video/annodex</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>azf</extension>
+        <mime-type>application/vnd.airzip.filesecure.azf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>azs</extension>
+        <mime-type>application/vnd.airzip.filesecure.azs</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>azw</extension>
+        <mime-type>application/vnd.amazon.ebook</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bat</extension>
+        <mime-type>application/x-msdownload</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bcpio</extension>
+        <mime-type>application/x-bcpio</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bdf</extension>
+        <mime-type>application/x-font-bdf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bdm</extension>
+        <mime-type>application/vnd.syncml.dm+wbxml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bed</extension>
+        <mime-type>application/vnd.realvnc.bed</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bh2</extension>
+        <mime-type>application/vnd.fujitsu.oasysprs</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bin</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>blb</extension>
+        <mime-type>application/x-blorb</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>blorb</extension>
+        <mime-type>application/x-blorb</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bmi</extension>
+        <mime-type>application/vnd.bmi</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bmp</extension>
+        <mime-type>image/bmp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>body</extension>
+        <mime-type>text/html</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>book</extension>
+        <mime-type>application/vnd.framemaker</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>box</extension>
+        <mime-type>application/vnd.previewsystems.box</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>boz</extension>
+        <mime-type>application/x-bzip2</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bpk</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>btif</extension>
+        <mime-type>image/prs.btif</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bz</extension>
+        <mime-type>application/x-bzip</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>bz2</extension>
+        <mime-type>application/x-bzip2</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c</extension>
+        <mime-type>text/x-c</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c11amc</extension>
+        <mime-type>application/vnd.cluetrust.cartomobile-config</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c11amz</extension>
+        <mime-type>application/vnd.cluetrust.cartomobile-config-pkg</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c4d</extension>
+        <mime-type>application/vnd.clonk.c4group</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c4f</extension>
+        <mime-type>application/vnd.clonk.c4group</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c4g</extension>
+        <mime-type>application/vnd.clonk.c4group</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c4p</extension>
+        <mime-type>application/vnd.clonk.c4group</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>c4u</extension>
+        <mime-type>application/vnd.clonk.c4group</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cab</extension>
+        <mime-type>application/vnd.ms-cab-compressed</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>caf</extension>
+        <mime-type>audio/x-caf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cap</extension>
+        <mime-type>application/vnd.tcpdump.pcap</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>car</extension>
+        <mime-type>application/vnd.curl.car</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cat</extension>
+        <mime-type>application/vnd.ms-pki.seccat</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cb7</extension>
+        <mime-type>application/x-cbr</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cba</extension>
+        <mime-type>application/x-cbr</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cbr</extension>
+        <mime-type>application/x-cbr</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cbt</extension>
+        <mime-type>application/x-cbr</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cbz</extension>
+        <mime-type>application/x-cbr</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cc</extension>
+        <mime-type>text/x-c</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cct</extension>
+        <mime-type>application/x-director</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ccxml</extension>
+        <mime-type>application/ccxml+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdbcmsg</extension>
+        <mime-type>application/vnd.contact.cmsg</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdf</extension>
+        <mime-type>application/x-cdf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdkey</extension>
+        <mime-type>application/vnd.mediastation.cdkey</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdmia</extension>
+        <mime-type>application/cdmi-capability</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdmic</extension>
+        <mime-type>application/cdmi-container</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdmid</extension>
+        <mime-type>application/cdmi-domain</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdmio</extension>
+        <mime-type>application/cdmi-object</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdmiq</extension>
+        <mime-type>application/cdmi-queue</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdx</extension>
+        <mime-type>chemical/x-cdx</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdxml</extension>
+        <mime-type>application/vnd.chemdraw+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cdy</extension>
+        <mime-type>application/vnd.cinderella</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cer</extension>
+        <mime-type>application/pkix-cert</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cfs</extension>
+        <mime-type>application/x-cfs-compressed</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cgm</extension>
+        <mime-type>image/cgm</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>chat</extension>
+        <mime-type>application/x-chat</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>chm</extension>
+        <mime-type>application/vnd.ms-htmlhelp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>chrt</extension>
+        <mime-type>application/vnd.kde.kchart</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cif</extension>
+        <mime-type>chemical/x-cif</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cii</extension>
+        <mime-type>application/vnd.anser-web-certificate-issue-initiation</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cil</extension>
+        <mime-type>application/vnd.ms-artgalry</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cla</extension>
+        <mime-type>application/vnd.claymore</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>class</extension>
+        <mime-type>application/java</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>clkk</extension>
+        <mime-type>application/vnd.crick.clicker.keyboard</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>clkp</extension>
+        <mime-type>application/vnd.crick.clicker.palette</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>clkt</extension>
+        <mime-type>application/vnd.crick.clicker.template</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>clkw</extension>
+        <mime-type>application/vnd.crick.clicker.wordbank</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>clkx</extension>
+        <mime-type>application/vnd.crick.clicker</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>clp</extension>
+        <mime-type>application/x-msclip</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cmc</extension>
+        <mime-type>application/vnd.cosmocaller</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cmdf</extension>
+        <mime-type>chemical/x-cmdf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cml</extension>
+        <mime-type>chemical/x-cml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cmp</extension>
+        <mime-type>application/vnd.yellowriver-custom-menu</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cmx</extension>
+        <mime-type>image/x-cmx</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cod</extension>
+        <mime-type>application/vnd.rim.cod</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>com</extension>
+        <mime-type>application/x-msdownload</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>conf</extension>
+        <mime-type>text/plain</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cpio</extension>
+        <mime-type>application/x-cpio</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cpp</extension>
+        <mime-type>text/x-c</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cpt</extension>
+        <mime-type>application/mac-compactpro</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>crd</extension>
+        <mime-type>application/x-mscardfile</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>crl</extension>
+        <mime-type>application/pkix-crl</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>crt</extension>
+        <mime-type>application/x-x509-ca-cert</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cryptonote</extension>
+        <mime-type>application/vnd.rig.cryptonote</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>csh</extension>
+        <mime-type>application/x-csh</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>csml</extension>
+        <mime-type>chemical/x-csml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>csp</extension>
+        <mime-type>application/vnd.commonspace</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>css</extension>
+        <mime-type>text/css</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cst</extension>
+        <mime-type>application/x-director</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>csv</extension>
+        <mime-type>text/csv</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cu</extension>
+        <mime-type>application/cu-seeme</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>curl</extension>
+        <mime-type>text/vnd.curl</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cww</extension>
+        <mime-type>application/prs.cww</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cxt</extension>
+        <mime-type>application/x-director</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>cxx</extension>
+        <mime-type>text/x-c</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dae</extension>
+        <mime-type>model/vnd.collada+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>daf</extension>
+        <mime-type>application/vnd.mobius.daf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dart</extension>
+        <mime-type>application/vnd.dart</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dataless</extension>
+        <mime-type>application/vnd.fdsn.seed</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>davmount</extension>
+        <mime-type>application/davmount+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dbk</extension>
+        <mime-type>application/docbook+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dcr</extension>
+        <mime-type>application/x-director</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dcurl</extension>
+        <mime-type>text/vnd.curl.dcurl</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dd2</extension>
+        <mime-type>application/vnd.oma.dd2+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ddd</extension>
+        <mime-type>application/vnd.fujixerox.ddd</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>deb</extension>
+        <mime-type>application/x-debian-package</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>def</extension>
+        <mime-type>text/plain</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>deploy</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>der</extension>
+        <mime-type>application/x-x509-ca-cert</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dfac</extension>
+        <mime-type>application/vnd.dreamfactory</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dgc</extension>
+        <mime-type>application/x-dgc-compressed</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dib</extension>
+        <mime-type>image/bmp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dic</extension>
+        <mime-type>text/x-c</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dir</extension>
+        <mime-type>application/x-director</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dis</extension>
+        <mime-type>application/vnd.mobius.dis</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dist</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>distz</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>djv</extension>
+        <mime-type>image/vnd.djvu</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>djvu</extension>
+        <mime-type>image/vnd.djvu</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dll</extension>
+        <mime-type>application/x-msdownload</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dmg</extension>
+        <mime-type>application/x-apple-diskimage</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dmp</extension>
+        <mime-type>application/vnd.tcpdump.pcap</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dms</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dna</extension>
+        <mime-type>application/vnd.dna</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>doc</extension>
+        <mime-type>application/msword</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>docm</extension>
+        <mime-type>application/vnd.ms-word.document.macroenabled.12</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>docx</extension>
+        <mime-type>application/vnd.openxmlformats-officedocument.wordprocessingml.document</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dot</extension>
+        <mime-type>application/msword</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dotm</extension>
+        <mime-type>application/vnd.ms-word.template.macroenabled.12</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dotx</extension>
+        <mime-type>application/vnd.openxmlformats-officedocument.wordprocessingml.template</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dp</extension>
+        <mime-type>application/vnd.osgi.dp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dpg</extension>
+        <mime-type>application/vnd.dpgraph</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dra</extension>
+        <mime-type>audio/vnd.dra</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dsc</extension>
+        <mime-type>text/prs.lines.tag</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dssc</extension>
+        <mime-type>application/dssc+der</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dtb</extension>
+        <mime-type>application/x-dtbook+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dtd</extension>
+        <mime-type>application/xml-dtd</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dts</extension>
+        <mime-type>audio/vnd.dts</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dtshd</extension>
+        <mime-type>audio/vnd.dts.hd</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dump</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dv</extension>
+        <mime-type>video/x-dv</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dvb</extension>
+        <mime-type>video/vnd.dvb.file</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dvi</extension>
+        <mime-type>application/x-dvi</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dwf</extension>
+        <mime-type>model/vnd.dwf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dwg</extension>
+        <mime-type>image/vnd.dwg</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dxf</extension>
+        <mime-type>image/vnd.dxf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dxp</extension>
+        <mime-type>application/vnd.spotfire.dxp</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>dxr</extension>
+        <mime-type>application/x-director</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ecelp4800</extension>
+        <mime-type>audio/vnd.nuera.ecelp4800</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ecelp7470</extension>
+        <mime-type>audio/vnd.nuera.ecelp7470</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ecelp9600</extension>
+        <mime-type>audio/vnd.nuera.ecelp9600</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ecma</extension>
+        <mime-type>application/ecmascript</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>edm</extension>
+        <mime-type>application/vnd.novadigm.edm</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>edx</extension>
+        <mime-type>application/vnd.novadigm.edx</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>efif</extension>
+        <mime-type>application/vnd.picsel</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ei6</extension>
+        <mime-type>application/vnd.pg.osasli</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>elc</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>emf</extension>
+        <mime-type>application/x-msmetafile</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>eml</extension>
+        <mime-type>message/rfc822</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>emma</extension>
+        <mime-type>application/emma+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>emz</extension>
+        <mime-type>application/x-msmetafile</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>eol</extension>
+        <mime-type>audio/vnd.digital-winds</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>eot</extension>
+        <mime-type>application/vnd.ms-fontobject</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>eps</extension>
+        <mime-type>application/postscript</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>epub</extension>
+        <mime-type>application/epub+zip</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>es3</extension>
+        <mime-type>application/vnd.eszigno3+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>esa</extension>
+        <mime-type>application/vnd.osgi.subsystem</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>esf</extension>
+        <mime-type>application/vnd.epson.esf</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>et3</extension>
+        <mime-type>application/vnd.eszigno3+xml</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>etx</extension>
+        <mime-type>text/x-setext</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>eva</extension>
+        <mime-type>application/x-eva</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>evy</extension>
+        <mime-type>application/x-envoy</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>exe</extension>
+        <mime-type>application/octet-stream</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>exi</extension>
+        <mime-type>application/exi</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ext</extension>
+        <mime-type>application/vnd.novadigm.ext</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ez</extension>
+        <mime-type>application/andrew-inset</mime-type>
+    </mime-mapping>
+    <mime-mapping>
+        <extension>ez2</extension>