unstick r1775795

Revision 1775795

Date:
2016/12/23 06:52:41
Author:
niclas
Revision Log:
Changing name from Zest to Polygene. Keeping the release announcement intact as well as the details of it.
Files:

Legend:

 
Added
 
Removed
 
Modified
  • zest/site/src/_data/releases.yml

     
    1 1
    2 # Apache Zest Releases
    2 # Apache Polygene Releases
    3 3 # Releases with no announcement are not rendered
    4 4
    5 5 - version: 2.1
     
    7 7 signer: Paul Merlin
    8 8 pgpId: 7D0391AC
    9 9 warning: >
    10 <strong>Apache Zest™ (Java Edition) 2.1</strong> is the first release of the Qi4j codebase under the Apache
    10 <strong>Apache Polygene™ (Java Edition) 2.1</strong> is the first release of the Qi4j codebase under the Apache
    11 11 Software Foundation umbrella.<br/>
    12 12 To keep backward compatiblity, this version still use <code>org.qi4j.*</code> Java packages and Maven
    13 13 coordinates.<br/>
  • zest/site/src/_data/texts.yml

     
    1 1
    2 2 description: >
    3 Apache Zest™ is a community based effort exploring Composite Oriented
    3 Apache Polygene™ is a community based effort exploring Composite Oriented
    4 4 Programming for domain centric application development. This includes
    5 5 evolved concepts from Aspect Oriented Programming, Dependency Injection
    6 6 and Domain Driven Design.
    7 7
    8 8 Composite Oriented Programming allows developers to work with 'fragments',
    9 9 smaller than classes, and 'compose' fragments into larger 'composites'
    10 which acts like the regular objects. Apache Zest™ also tackles the
    10 which acts like the regular objects. Apache Polygene™ also tackles the
    11 11 enforcement of application composition, i.e. composites are declared in
    12 12 modules, modules are contained in layers and access between layers are
    13 13 controlled/enforced.
    14 14
    15 author: The Apache Zest™ Project
    15 author: The Apache Polygene™ Project
    16 16
    17 17 keywords: cop, composite oriented programming, ddd, domain driven design, composite, mixin, fragment, constraint, concern, side-effect, aop, aspect oriented programming, application, layer, module, structure, java, library, toolkit, framework
  • zest/site/src/_layouts/default.html

     
    50 50 <span class="icon-bar"></span>
    51 51 <span class="icon-bar"></span>
    52 52 </a>
    53 <a class="brand" href="/"><img src="/landing-resources/img/feather.png" width="64"/> Apache <strong>Zest™</strong></a>
    53 <a class="brand" href="/"><img src="/landing-resources/img/feather.png" width="64"/> Apache <strong>Polygene™</strong></a>
    54 54 <div class="nav-collapse collapse">
    55 55 <ul class="nav">
    56 56 <li><a href="/news.html"><i class="icon-rss"></i> News</a></li>
     
    83 83 <li role="menuitem"><a href="/community/playing_field.html"><i class="icon-caret-right"></i> Playing Field</a></li>
    84 84 <li class="divider"></li>
    85 85 <li role="menuitem"><a href="/community/codebase.html"><i class="icon-caret-right"></i> Codebase</a></li>
    86 <li role="menuitem"><a href="https://builds.apache.org/view/S-Z/view/Zest/" target="_blank"><i class="icon-caret-right"></i> Continuous Integration</a></li>
    87 <li role="menuitem"><a href="https://issues.apache.org/jira/browse/ZEST" target="_blank"><i class="icon-caret-right"></i> Issues</a></li>
    86 <li role="menuitem"><a href="https://builds.apache.org/view/S-Z/view/Polygene/" target="_blank"><i class="icon-caret-right"></i> Continuous Integration</a></li>
    87 <li role="menuitem"><a href="https://issues.apache.org/jira/browse/POLYGENE" target="_blank"><i class="icon-caret-right"></i> Issues</a></li>
    88 88 <li class="divider"></li>
    89 89 <li role="menuitem"><a href="/community/maturity.html"><i class="icon-caret-right"></i> Maturity Model</a></li>
    90 <li role="menuitem"><a href="/community/contributors.html"><i class="icon-caret-right"></i> People behind Apache Zest™</a></li>
    90 <li role="menuitem"><a href="/community/contributors.html"><i class="icon-caret-right"></i> People behind Apache Polygene™</a></li>
    91 91 <li class="divider"></li>
    92 92 <li role="menuitem"><a href="http://www.apache.org/licenses/" target="_blank"><i class="icon-caret-right"></i> Licensing</a></li>
    93 93 <li role="menuitem"><a href="/community/licensing_faq.html"><i class="icon-caret-right"></i> Licensing FAQ</a></li>
     
    114 114 Copyright &copy; 2015-{{ 'now' | date: "%Y" }} The Apache Software Foundation, Licensed under the <a href="http://www.apache.org/licenses/">Apache License, Version 2.0</a>.
    115 115 <br/>
    116 116 <small>
    117 Apache Zest, Zest, Apache, the Apache feather logo, and the Apache Zest project logo are trademarks of The Apache Software Foundation.<br/>
    117 Apache Polygene, Polygene, Apache, the Apache feather logo, and the Apache Polygene project logo are trademarks of The Apache Software Foundation.<br/>
    118 118 All other marks mentioned may be trademarks or registered trademarks of their respective owners.
    119 119 </small>
    120 120 </p>
  • zest/site/src/_layouts/posts.html

     
    49 49 <span class="icon-bar"></span>
    50 50 <span class="icon-bar"></span>
    51 51 </a>
    52 <a class="brand" href="/"><img src="/landing-resources/img/feather.png" width="64"/> Apache <strong>Zest™</strong></a>
    52 <a class="brand" href="/"><img src="/landing-resources/img/feather.png" width="64"/> Apache <strong>Polygene™</strong></a>
    53 53 <div class="nav-collapse collapse">
    54 54 <ul class="nav">
    55 55 <li><a href="/news.html"><i class="icon-rss"></i> News</a></li>
     
    82 82 <li role="menuitem"><a href="/community/playing_field.html"><i class="icon-caret-right"></i> Playing Field</a></li>
    83 83 <li class="divider"></li>
    84 84 <li role="menuitem"><a href="/community/codebase.html"><i class="icon-caret-right"></i> Codebase</a></li>
    85 <li role="menuitem"><a href="https://builds.apache.org/view/S-Z/view/Zest/" target="_blank"><i class="icon-caret-right"></i> Continuous Integration</a></li>
    86 <li role="menuitem"><a href="https://issues.apache.org/jira/browse/ZEST" target="_blank"><i class="icon-caret-right"></i> Issues</a></li>
    85 <li role="menuitem"><a href="https://builds.apache.org/view/S-Z/view/Polygene/" target="_blank"><i class="icon-caret-right"></i> Continuous Integration</a></li>
    86 <li role="menuitem"><a href="https://issues.apache.org/jira/browse/POLYGENE" target="_blank"><i class="icon-caret-right"></i> Issues</a></li>
    87 87 <li class="divider"></li>
    88 88 <li role="menuitem"><a href="/community/maturity.html"><i class="icon-caret-right"></i> Maturity Model</a></li>
    89 <li role="menuitem"><a href="/community/contributors.html"><i class="icon-caret-right"></i> People behind Apache Zest™</a></li>
    89 <li role="menuitem"><a href="/community/contributors.html"><i class="icon-caret-right"></i> People behind Apache Polygene™</a></li>
    90 90 <li class="divider"></li>
    91 91 <li role="menuitem"><a href="http://www.apache.org/licenses/" target="_blank"><i class="icon-caret-right"></i> Licensing</a></li>
    92 92 <li role="menuitem"><a href="/community/licensing_faq.html"><i class="icon-caret-right"></i> Licensing FAQ</a></li>
     
    120 120 Copyright &copy; 2015-{{ 'now' | date: "%Y" }} The Apache Software Foundation, Licensed under the <a href="http://www.apache.org/licenses/">Apache License, Version 2.0</a>.
    121 121 <br/>
    122 122 <small>
    123 Apache Zest, Zest, Apache, the Apache feather logo, and the Apache Zest project logo are trademarks of The Apache Software Foundation.<br/>
    123 Apache Polygene, Polygene, Apache, the Apache feather logo, and the Apache Polygene project logo are trademarks of The Apache Software Foundation.<br/>
    124 124 All other marks mentioned may be trademarks or registered trademarks of their respective owners.
    125 125 </small>
    126 126 </p>
  • zest/site/src/atom.xml

     
    1 1 ---
    2 title : Apache Zest Atom Feed
    2 title : Apache Polygene Atom Feed
    3 3 ---
    4 4 <?xml version="1.0" encoding="utf-8"?>
    5 5 <feed xmlns="http://www.w3.org/2005/Atom">
  • zest/site/src/community/codebase.html

     
    1 1 ---
    2 title: Apache Zest™ Codebase
    2 title: Apache Polygene™ Codebase
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
    6 6 <h1>Codebase</h1>
    7 <p class="lead">Apache Zest™ codebase is hosted at the Apache Software Foundation and follow the git-flow development model.</p>
    7 <p class="lead">Apache Polygene™ codebase is hosted at the Apache Software Foundation and follow the git-flow development model.</p>
    8 8 </div>
    9 9 <div class="row-fluid">
    10 10 <div class="span2"></div>
     
    23 23 <a href="https://github.com/qi4j">Github</a>, the Qi4j community finally moved to the
    24 24 <a href="https://www.apache.org/">Apache Software Foundation</a> (ASF) on March 2015.
    25 25 The codebase history is kept in <a href="https://git-scm.com/">Git</a> repositories, mirrored to the
    26 <a href="https://github.com/apache?query=zest">ASF Github organization</a>.
    26 <a href="https://github.com/apache?query=polygene">ASF Github organization</a>.
    27 27 This should simplify the learning, as not only does developers have plenty of experience with Git, and
    28 28 tools around it, but also there are endless amount of documentation and user forums to support each
    29 29 individual, off-loading some of that burden from us.
     
    31 31 </p>
    32 32 <h2>Public Access Repository</h2>
    33 33 <p>
    34 Apache Zest™ differs slightly from the regular project, due to our specific needs and style of development. the main
    34 Apache Polygene™ differs slightly from the regular project, due to our specific needs and style of development. the main
    35 35 differences are;
    36 36 </p>
    37 37 <ul>
    38 38 <li>
    39 Apache Zest™ uses the <code>develop</code> branch for the day to day changes to the project. The
    39 Apache Polygene™ uses the <code>develop</code> branch for the day to day changes to the project. The
    40 40 <code>master</code> branch is used for the latest releases. See below about the 'Git Development Model'.
    41 41 </li>
    42 42 <li>
    43 Apache Zest™ uses a social contract to limit access to different areas of the project, instead of ACLs. The
    43 Apache Polygene™ uses a social contract to limit access to different areas of the project, instead of ACLs. The
    44 44 driving point is to relax the contribution criteria in less critical parts, to encourage a wider
    45 45 participation that otherwise would not be possible.
    46 46 </li>
    47 47 </ul>
    48 48 <p>
    49 Apache Zest™ used to have many repositories to accommodate for the authorization issue above, but eventually
    49 Apache Polygene™ used to have many repositories to accommodate for the authorization issue above, but eventually
    50 50 settled with a single Git repository, and now only have 2 repositories;
    51 51 </p>
    52 52 <ul>
    53 <li><code>zest-java</code></li>
    54 <li><code>zest-sandbox</code></li>
    53 <li><code>polygene-java</code></li>
    54 <li><code>polygene-sandbox</code></li>
    55 55 </ul>
    56 56 <p>
    57 57 The sandbox is where experimental code goes, and modules that are not ready to be shipped, or can not be
    58 58 shipped due to licensing restrictions (e.g. Oracle doesn't provide Coherence as automatic download for our
    59 59 testing, so can't really ship the coherence extension). The sandbox is a normal Git repository available
    60 to clone as; <code>git clone https://git-wip-us.apache.org/repos/asf/zest-sandbox.git</code>
    60 to clone as; <code>git clone https://git-wip-us.apache.org/repos/asf/polygene-sandbox.git</code>
    61 61 </p>
    62 62 <p>
    63 The Apache Zest™ (Java Edition) is the main development codebase, and to start working with it you simply clone it;
    64 <code>git clone https://git-wip-us.apache.org/repos/asf/zest-java.git</code>
    63 The Apache Polygene™ (Java Edition) is the main development codebase, and to start working with it you simply clone it;
    64 <code>git clone https://git-wip-us.apache.org/repos/asf/polygene-java.git</code>
    65 65 </p>
    66 66
    67 67 <h2>Web Access</h2>
     
    69 69 The two repositories can be browsed on the mirrors on the ASF Github organization;
    70 70 </p>
    71 71 <ul>
    72 <li><a href="https://github.com/apache/zest-java">https://github.com/apache/zest-java</a></li>
    73 <li><a href="https://github.com/apache/zest-sandbox">https://github.com/apache/zest-sandbox</a></li>
    72 <li><a href="https://github.com/apache/polygene-java">https://github.com/apache/polygene-java</a></li>
    73 <li><a href="https://github.com/apache/polygene-sandbox">https://github.com/apache/polygene-sandbox</a></li>
    74 74 </ul>
    75 75
    76 76 <h2>Committer Access</h2>
    77 77 <p class="lead">
    78 Apache Zest™ has a 3 level committer access system. The groups are "Core", "Platform" and "Community" and the roles
    78 Apache Polygene™ has a 3 level committer access system. The groups are "Core", "Platform" and "Community" and the roles
    79 79 are very clear.
    80 80 </p>
    81 81
    82 82 <h3>Core Developers</h3>
    83 83 <p>
    84 84 These are the guardians and stewards of the core technology and ultimate rulers of what is going on. The
    85 hope is that a small group of benevolent dictators will manage to make Apache Zest™ the best platform out there,
    86 and not listen in on the voices of features and changes that derails the vision and principles of Apache Zest™.
    85 hope is that a small group of benevolent dictators will manage to make Apache Polygene™ the best platform out there,
    86 and not listen in on the voices of features and changes that derails the vision and principles of Apache Polygene™.
    87 87 </p>
    88 88 <div class="well">
    89 89 <p>
    90 Over the course of Apache Zest™'s history, there have been several occasions where brilliant developers got
    91 caught up in 'feature improvements' which went against the fibers of Apache Zest™ philosophy and technological
    90 Over the course of Apache Polygene™'s history, there have been several occasions where brilliant developers got
    91 caught up in 'feature improvements' which went against the fibers of Apache Polygene™ philosophy and technological
    92 92 direction. IF we would have had an 'open door' policy to changes in Core, these 'improvements' would
    93 have degraded the excellence of Apache Zest™, and we are not likely to invite anyone to the Core Developer
    94 team, unless the individual shows remarkable understanding of the inner workings of Apache Zest™, the
    95 philosophy that drives Apache Zest™ and prudence in working on highly sensitive codebases. In return we will
    96 strive for making the Apache Zest™ Core as small as possible, having most features in libraries and extensions.
    93 have degraded the excellence of Apache Polygene™, and we are not likely to invite anyone to the Core Developer
    94 team, unless the individual shows remarkable understanding of the inner workings of Apache Polygene™, the
    95 philosophy that drives Apache Polygene™ and prudence in working on highly sensitive codebases. In return we will
    96 strive for making the Apache Polygene™ Core as small as possible, having most features in libraries and extensions.
    97 97 We welcome any suggestions that breaks out pluggable functionality.
    98 98 </p>
    99 99 <p>
    100 100 We apologize in advance if this comes across as elitist, but the purpose is to ensure a high quality
    101 Apache Zest™ Runtime, stable over time and not bloating with unnecessary features. Thanks for understanding.
    101 Apache Polygene™ Runtime, stable over time and not bloating with unnecessary features. Thanks for understanding.
    102 102 </p>
    103 103 </div>
    104 104
    105 105 <h3>Platform Developers</h3>
    106 106 <p>
    107 These form the work force of Apache Zest™. They will work on the Extensions and Libraries, which eventually will
    108 make Apache Zest™ the most efficient way of programming in Java.
    107 These form the work force of Apache Polygene™. They will work on the Extensions and Libraries, which eventually will
    108 make Apache Polygene™ the most efficient way of programming in Java.
    109 109 </p>
    110 110
    111 111 <h3>Community Developers</h3>
    112 112 <p>
    113 Any person who is interested in helping out with Apache Zest™ will be granted access to Sandbox, Tests, IDE
    113 Any person who is interested in helping out with Apache Polygene™ will be granted access to Sandbox, Tests, IDE
    114 114 support, Tutorials, Samples, HowTos, documentation and other (i.e. not Core, Libraries and Extensions).
    115 115 This will gauge their abilities and commitment to the project, with an aim to make them Platform Developers.
    116 116 </p>
     
    118 118 <h3>Independents</h3>
    119 119 <p>
    120 120 Of course, Git's distributed nature also allows anyone to fork our repositories, and have the patches find
    121 their way back to Apache Zest™'s official repository. And GitHub's pull-request system makes the management of this
    121 their way back to Apache Polygene™'s official repository. And GitHub's pull-request system makes the management of this
    122 122 a lot easier, and something that we encourage.
    123 123 </p>
    124 124
    125 125 <h3>How to Join?</h3>
    126 126 <p>
    127 127 To become a Community Developer, just subscribe to the
    128 <a href="mailto:dev-subscribe@zest.apache.org">dev@zest.apache.org</a> mailing list and participate,
    128 <a href="mailto:dev-subscribe@polygene.apache.org">dev@polygene.apache.org</a> mailing list and participate,
    129 129 nothing more than a desire to help is required.
    130 130 </p>
    131 131 <p>
     
    137 137
    138 138 <h2>Commit Policy</h2>
    139 139 <p class="lead">
    140 Apache Zest™ generally uses a Commit-Then-Review policy on most changes. This allows a reasonable high velocity of
    140 Apache Polygene™ generally uses a Commit-Then-Review policy on most changes. This allows a reasonable high velocity of
    141 141 development.
    142 142 </p>
    143 143 <p>
     
    154 154 tests, either to accommodate for code changes in Core or to tighten the constraints of them, MUST be
    155 155 discussed on the <code>dev@</code> mailing list, prior to committing them to the 'develop' branch. We
    156 156 recommend that a different branch is used for these changes, unless simply codesnippets are pasted to mail.
    157 This exists to ensure that we have a stable evolution of Apache Zest™ (Java Edition) Runtime, and no surprises will occur in
    157 This exists to ensure that we have a stable evolution of Apache Polygene™ (Java Edition) Runtime, and no surprises will occur in
    158 158 existing applications with new versions.
    159 159 </p>
    160 160
     
    170 170 The most important part of that excellent article can be found below.
    171 171 </p>
    172 172
    173 <h3>Git Branching Model used at Apache Zest™</h3>
    173 <h3>Git Branching Model used at Apache Polygene™</h3>
    174 174 <p>
    175 175 It looks more complicated than it is. Here are the guidelines;
    176 176 </p>
     
    185 185 </ul>
    186 186 <p>
    187 187 Day-to-day development revolves around the develop branch and it is this branch that you typically clone
    188 from our repository if you intend to contribute to Apache Zest™ itself. If you create a new feature, or make some
    188 from our repository if you intend to contribute to Apache Polygene™ itself. If you create a new feature, or make some
    189 189 larger piece of refactoring, then please create a 'feature branch' (see article for details).
    190 190 </p>
    191 191 <p>
     
    284 284 <pre><code>
    285 285 # You need to have a "remote" defined in your git configuration
    286 286 # This is only needed once
    287 git remote add github https://github.com/apache/zest-java.git
    287 git remote add github https://github.com/apache/polygene-java.git
    288 288
    289 289 # Fetch the commit
    290 290 git fetch github pull/42/head:merge-pr-42
  • zest/site/src/community/contributors.html

     
    1 1 ---
    2 title: People behind Apache Zest™
    2 title: People behind Apache Polygene™
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
    6 <h1>People behind Apache Zest™</h1>
    6 <h1>People behind Apache Polygene™</h1>
    7 7 <p class="lead">
    8 8 Qi4j was started in 2007 by Niclas Hedhman and Rickard &Ouml;berg, a.k.a "The Founders".
    9 9 <br/>
    10 In 2015, Qi4j came to the Apache Software Foundation, and is run as an Apache project named Apache Zest™.
    10 In 2015, Qi4j came to the Apache Software Foundation, and is run as an Apache project named Apache Polygene™.
    11 11 </p>
    12 12 </div>
    13 13 <div class="row-fluid">
     
    41 41
    42 42 <h2>Contributors</h2>
    43 43 <p>
    44 There has been numerous contributors to the Zest/Qi4j project over the years, and with risk of missing someone,
    44 There has been numerous contributors to the Polygene/Zest/Qi4j project over the years, and with risk of missing someone,
    45 45 we try to maintain this list to show our appreciation of these contributions.
    46 46 </p>
    47 47 <h3>Rickard &Ouml;berg</h3>
     
    60 60 </p>
    61 61 <h3>Others</h3>
    62 62 <p>
    63 The list below includes all past and present contributors to the Zest/Qi4j project. There
    63 The list below includes all past and present contributors to the Polygene/Zest/Qi4j project. There
    64 64 might be omissions, and that is purely a mistake. So if you find anyone, incl yourself,
    65 missing from the list, please contact the Zest developer list, dev@zest.apache.org
    65 missing from the list, please contact the Polygene developer list, dev@polygene.apache.org
    66 66 </p>
    67 67 <ul>
    68 68 <li>Alex Shneyderman</li>
  • zest/site/src/community/get_help.html

     
    1 1 ---
    2 title: Apache Zest™ - Get Help
    2 title: Apache Polygene™ - Get Help
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
     
    13 13 <img src="../landing-resources/img/feather.png" class="pull-right" style="height: 2em" />
    14 14 </h2>
    15 15 <p>
    16 To discuss with the Apache Zest™ community, it is easiest to do so at the
    17 <code>dev@zest.apache.org</code>
    16 To discuss with the Apache Polygene™ community, it is easiest to do so at the
    17 <code>dev@polygene.apache.org</code>
    18 18 mailing list.
    19 19 </p>
    20 20 <p class="lead">
    21 21 To subscribe simply send an email to
    22 22 <br/>
    23 <a href="mailto:dev-subscribe@zest.apache.org">dev-subscribe@zest.apache.org</a>.
    23 <a href="mailto:dev-subscribe@polygene.apache.org">dev-subscribe@polygene.apache.org</a>.
    24 24 </p>
    25 <p>Read the browsable and searchable <a href="https://lists.apache.org/list.html?dev@zest.apache.org">archives</a>.</p>
    25 <p>Read the browsable and searchable <a href="https://lists.apache.org/list.html?dev@polygene.apache.org">archives</a>.</p>
    26 26 <p>Also review general information about many <a href="https://www.apache.org/foundation/mailinglists.html">other Apache mailing lists</a></p>
    27 27 </div>
    28 28 <div class="span4">
     
    31 31 <img src="../landing-resources/img/logo-stackoverflow.png" class="pull-right" style="height: 2em" />
    32 32 </h2>
    33 33 <p>
    34 To post question to and get answers from the Apache Zest™ community, go to
    35 <a href="http://stackoverflow.com/questions/tagged/apache-zest">StackOverflow</a>.
    34 To post question to and get answers from the Apache Polygene™ community, go to
    35 <a href="http://stackoverflow.com/questions/tagged/apache-polygene">StackOverflow</a>.
    36 36 </p>
    37 37 </div>
    38 38 <div class="span4">
     
    41 41 <img src="../landing-resources/img/logo-jira.png" class="pull-right" style="height: 2em" />
    42 42 </h2>
    43 43 <p>
    44 If you found a bug or want to request a new feature, use the <a href="https://issues.apache.org/jira/browse/ZEST">issue tracker</a>.
    44 If you found a bug or want to request a new feature, use the <a href="https://issues.apache.org/jira/browse/POLYGENE">issue tracker</a>.
    45 45 </p>
    46 46 </div>
    47 47 </div>
  • zest/site/src/community/index.html

     
    1 1 ---
    2 title: Apache Zest™ Community
    2 title: Apache Polygene™ Community
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
    6 <h1>Apache Zest™ Community</h1>
    6 <h1>Apache Polygene™ Community</h1>
    7 7 <p class="lead">
    8 Apache Zest™ is an open development community effort with an Apache ver 2.0 open source license.
    8 Apache Polygene™ is an open development community effort with an Apache ver 2.0 open source license.
    9 9 </p>
    10 10 </div>
    11 11 <div class="row-fluid">
     
    14 14
    15 15 <h2>What does this really mean?</h2>
    16 16 <p>
    17 First of all, we work together to achieve the visions of Apache Zest™, based on technical merits alone in an open and
    18 friendly manner, mostly via the dev@zest.apache.org mailing list. It means that everyone in the community are stake
    17 First of all, we work together to achieve the visions of Apache Polygene™, based on technical merits alone in an open and
    18 friendly manner, mostly via the dev@polygene.apache.org mailing list. It means that everyone in the community are stake
    19 19 holders in the resulting codebase, and noone can claim it is mine.
    20 20 </p>
    21 21 <p>
    22 Secondly, all source code, artwork and documentation produced in Apache Zest™ are licensed very liberally under the Apache
    22 Secondly, all source code, artwork and documentation produced in Apache Polygene™ are licensed very liberally under the Apache
    23 23 License ver 2.0. This allows you to use our efforts in your own projects, whether they are open sourced, commercial
    24 24 or any other arrangement you like, subject to a few terms like "Must re-distribute a Notice that your product
    25 contains Apache Zest™ and such. See the License text for exact details, and please consult with IP rights lawyers about
    25 contains Apache Polygene™ and such. See the License text for exact details, and please consult with IP rights lawyers about
    26 26 this and other Open Source licenses.
    27 27 </p>
    28 28 <p>
    29 Thirdly, Apache Zest™ invites everyone to participate. There are many ways to participate, not only by writing code. See
    29 Thirdly, Apache Polygene™ invites everyone to participate. There are many ways to participate, not only by writing code. See
    30 30 list in the <a href="participate.html">Participation</a> section.
    31 31 </p>
    32 32
  • zest/site/src/community/licensing_faq.html

     
    1 1 ---
    2 title: Apache Zest™ Licensing FAQ
    2 title: Apache Polygene™ Licensing FAQ
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
     
    14 14 <dl>
    15 15
    16 16 <dt class="lead">
    17 <strong>Q</strong>: Can I use Apache Zest™ Core in my commercial applications under a closed-source, proprietary license?
    17 <strong>Q</strong>: Can I use Apache Polygene™ Core in my commercial applications under a closed-source, proprietary license?
    18 18 </dt>
    19 19 <dd>
    20 20 <strong>A</strong>: Yes. The Apache License is very business-friendly. Please observe the obligations on your part,
     
    27 27 <dl>
    28 28
    29 29 <dt class="lead">
    30 <strong>Q</strong>: My company has invested a lot of time to learn and understand the Apache Zest™ platform, and we think we
    31 are really good at writing Apache Zest™ applications and would like to start training others. Can we advertise that we are
    32 "Apache Zest™ experts" or that we conduct "Advanced Apache Zest™ training"?
    30 <strong>Q</strong>: My company has invested a lot of time to learn and understand the Apache Polygene™ platform, and we think we
    31 are really good at writing Apache Polygene™ applications and would like to start training others. Can we advertise that we are
    32 "Apache Polygene™ experts" or that we conduct "Advanced Apache Polygene™ training"?
    33 33 </dt>
    34 34 <dd>
    35 <strong>A</strong>: The Apache Software Foundation has a unified <a href="http://www.apache.org/foundation/marks/">trademarks and branding policy</a>, which covers this question. This is somewhat more strict than the pre-ASF policy in the Apache Zest™ project, and if you have any doubts, please contact the Apache Zest project for clarification. The intent of the Project Management Committee is to lean towards "permissible" rather than "exclusionary", as long as credit is given where credit is due. <strong>Also</strong> be aware that all references to "Zest" MUST be "Apache Zest™".
    35 <strong>A</strong>: The Apache Software Foundation has a unified <a href="http://www.apache.org/foundation/marks/">trademarks and branding policy</a>, which covers this question. This is somewhat more strict than the pre-ASF policy in the Apache Polygene™ project, and if you have any doubts, please contact the Apache Polygene project for clarification. The intent of the Project Management Committee is to lean towards "permissible" rather than "exclusionary", as long as credit is given where credit is due. <strong>Also</strong> be aware that all references to "Polygene" MUST be "Apache Polygene™".
    36 36 </dd>
    37 37 </dl>
    38 38
  • zest/site/src/community/maturity.html

     
    1 1 ---
    2 title: Apache Zest™ Maturity Model
    2 title: Apache Polygene™ Maturity Model
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
    6 6 <h1>Maturity Model</h1>
    7 <p class="lead">Apache Zest™ is hosted at the Apache Software Foundation and this is the
    7 <p class="lead">Apache Polygene™ is hosted at the Apache Software Foundation and this is the
    8 8 <a href="https://community.apache.org/apache-way/apache-project-maturity-model.html">Apache
    9 9 Maturity Model</a> self-declaration of its compliance..</p>
    10 10 </div>
  • zest/site/src/community/participate.html

     
    1 1 ---
    2 title: Participate to Apache Zest™
    2 title: Participate to Apache Polygene™
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
    6 6 <h1>Participate</h1>
    7 <p class="lead">Apache Zest™ is a community based on open development principles</p>
    7 <p class="lead">Apache Polygene™ is a community based on open development principles</p>
    8 8 </div>
    9 9
    10 10 <div class="row-fluid">
     
    12 12 <div class="span8">
    13 13
    14 14 <p>
    15 The Apache Zest™ community is an open source community centered around software and components for Composite Oriented
    16 Programming on Java/Scala, and related design methodologies that are enhanced by using Apache Zest™, like Domain Driven
    15 The Apache Polygene™ community is an open source community centered around software and components for Composite Oriented
    16 Programming on Java/Scala, and related design methodologies that are enhanced by using Apache Polygene™, like Domain Driven
    17 17 Design, DCI (Data, Context, Interaction) and HATEOAS REST.
    18 18 </p>
    19 19 <p>
    20 The Apache Zest™ community is an open community, in so far as it welcomes any member that accepts the basic criteria of
    20 The Apache Polygene™ community is an open community, in so far as it welcomes any member that accepts the basic criteria of
    21 21 contribution and adheres to the community's Code of Conduct.
    22 22 </p>
    23 23 <p>
    24 Note that you can contribute to Apache Zest™ also by contributing documentation or giving feedback on the current documentation.
    24 Note that you can contribute to Apache Polygene™ also by contributing documentation or giving feedback on the current documentation.
    25 25 Basically, at all the places where you can get help, there's also room for contributions.
    26 26 </p>
    27 27
    28 28 <div class="well">
    29 <h4>dev@zest.apache.org mailing list</h4>
    29 <h4>dev@polygene.apache.org mailing list</h4>
    30 30 <p>
    31 To discuss with the Apache Zest™ community, it is easiest to do so at the
    32 <a href="http://mail-archives.apache.org/mod_mbox/zest-dev/" target="_blank">dev@zest.apache.org</a> mailing list. This list is open to everyone and regular open source forum etiquette applies. Failure to be respectful may cause the poster to be
    31 To discuss with the Apache Polygene™ community, it is easiest to do so at the
    32 <a href="http://mail-archives.apache.org/mod_mbox/polygene-dev/" target="_blank">dev@polygene.apache.org</a> mailing list. This list is open to everyone and regular open source forum etiquette applies. Failure to be respectful may cause the poster to be
    33 33 expelled. The forum is a light and friendly one, where we are all friends working on a marvelous way of writing Java
    34 34 code.
    35 35 </p>
     
    39 39
    40 40 <h2>Principles of Participation <small>(not enforced yet)</small></h2>
    41 41 <p>
    42 We borrow a lot of our principles in community building from OPS4J, as OPS4J was the initial home of Apache Zest, called
    42 We borrow a lot of our principles in community building from OPS4J, as OPS4J was the initial home of Apache Polygene, called
    43 43 Qi4j back then. OPS4J is unique that it allows everyone to participate and modify the codebase
    44 44 without being voted into the community. We want to retain the spirit of this openness and low-barrier of entry, but need
    45 45 some structure to organize ourselves.
     
    55 55
    56 56 <h2>I want to help, what do I do?</h2>
    57 57 <p>
    58 First of all, subscribe to dev@zest.apache.org and introduce yourself. Secondly, take a look at the outstanding JIRA issues
    58 First of all, subscribe to dev@polygene.apache.org and introduce yourself. Secondly, take a look at the outstanding JIRA issues
    59 59 and see if there is anything that you are capable of working on. Communicate that with the community. If there is no issues,
    60 60 that you can manage, consider creating your own JIRAs, such as working on the Getting Started guide or more test cases.
    61 61 </p>
  • zest/site/src/community/playing_field.html

     
    5 5 <div class="page-header">
    6 6 <h1>Playing field</h1>
    7 7 <p class="lead">
    8 <a href="http://mail-archives.apache.org/mod_mbox/zest-dev/" target="_blank">dev@zest.apache.org</a> mailing list is a collaborative effort of open development, and we need to have some rules in place to make that work.
    8 <a href="http://mail-archives.apache.org/mod_mbox/polygene-dev/" target="_blank">dev@polygene.apache.org</a> mailing list is a collaborative effort of open development, and we need to have some rules in place to make that work.
    9 9 <br/>
    10 10 Below is an evolving list of rules and guidelines that we try to follow.
    11 11 </p>
     
    18 18
    19 19 <h2>Coding Standard</h2>
    20 20 <p>
    21 The coding standard at Apache Zest™ promotes whitespace to aid in reading the code. Opening braces are placed on new lines,
    21 The coding standard at Apache Polygene™ promotes whitespace to aid in reading the code. Opening braces are placed on new lines,
    22 22 spaces are between operators and so forth. We are following the OPS4J coding standards, as they have IDEA, Eclipse and
    23 23 Checkstyle templates prepared or in the works. These are slowly evolving, and it is likely we will evolve with them.
    24 24 The coding standards can be found in
    25 <a href="https://github.com/apache/zest-java/tree/develop/etc">https://github.com/apache/zest-java/tree/develop/etc</a>.
    25 <a href="https://github.com/apache/polygene-java/tree/develop/etc">https://github.com/apache/polygene-java/tree/develop/etc</a>.
    26 26 </p>
    27 27
    28 28 <h2>Design and Implementation work</h2>
    29 29 <p>
    30 We want all discussions around the design and implementation to happen on the dev@zest.apache.org mailing list.
    30 We want all discussions around the design and implementation to happen on the dev@polygene.apache.org mailing list.
    31 31 But we also recognize that instant messaging, voice and face-2-face are important tools to
    32 32 increase productivity. The participants are expected to convey in a comprehensible format (not just a copy/paste of
    33 33 the IM log) any new development, ideas and progress that occur during those sessions. The decisions for any multiple
    34 choices should be made on the dev@zest.apache.org mailing list only.
    34 choices should be made on the dev@polygene.apache.org mailing list only.
    35 35 </p>
    36 36 <h2>Community Structure</h2>
    37 37 <h3>Committers</h3>
    38 38 <p>
    39 The term "committer" is often used in open development efforts, and in Apache Zest™ it refers to the individuals who has commit
    40 39 rights to the codebase. Committers are invited by other committers, typically after some contribution via JIRA (Pull Requests
    40 The term "committer" is often used in open development efforts, and in Apache Polygene™ it refers to the individuals who has commit
    41 41 are not yet fully supported by the Apache infrastructure, but may change in the future. )
    42 42 </p>
    43 43
     
    48 48 that is not required from the Foundation itself, such as Licensing, Releases, Branding and source control management.
    49 49 </p>
    50 50 <p>
    51 At Apache Zest, we want to see all active committers to be part of the PMC. To have a voice of the future of the project.
    51 At Apache Polygene™, we want to see all active committers to be part of the PMC. To have a voice of the future of the project.
    52 52 Committers that are inactive are encouraged to resign from the PMC, but will retain the committer status and invited back
    53 53 to the PMC again, once activity picks up. This will not be enforced, but purely on voluntary basis.
    54 54 </p>
    55 <h3>PMC Chair & VP of Apache Zest</h3>
    55 <h3>PMC Chair & VP of Apache Polygene™</h3>
    56 56 The PMC Chair is an appointment by the Board, and acts as the link between the project and the Board, primarily for so called
    57 57 <i>oversight</i>, i.e. that the Board has knowledge of any community issues in a project. The PMC Chair is an <i>Officer</i>
    58 58 of the Foundation, but in reality the Chair is a glorified secretary, responsible for providing a short report once every
     
    72 72 <p>
    73 73 There are cases when we need to revert commits made by people. Common sense should rule, but the above cases of
    74 74 incompatibility and legal reasons are two obvious examples. Sabotage, misunderstandings and mistakes are others.
    75 When such cause arises, the issue should be brought to the dev@zest.apache.org mailing list, explained why the
    75 When such cause arises, the issue should be brought to the dev@polygene.apache.org mailing list, explained why the
    76 76 commit should be reverted, and if noone objects within 48 hours, the commit can be reverted. If the concern results
    77 77 in a debate, then the issue is resolved in a simple majority vote among the committers.
    78 78 </p>
    79 79
    80 80 <h2>Infrastructure issues</h2>
    81 81 <p>
    82 Any infrastructure requests or problems, should be directed to the dev@zest.apache.org mailing list.
    82 Any infrastructure requests or problems, should be directed to the dev@polygene.apache.org mailing list.
    83 83 </p>
    84 84
    85 85 <h2>Trademarks, Patents and Licenses</h2>
    86 86 <p>
    87 Apache Zest™ is licensed under the Apache License version 2.0. All committers agree that all their contributions are licensed
    88 under this license to Apache Zest™, other committers and the general public. The Copyright of each contribution is held by the
    87 Apache Polygene™ is licensed under the Apache License version 2.0. All committers agree that all their contributions are licensed
    88 under this license to Apache Polygene™, other committers and the general public. The Copyright of each contribution is held by the
    89 89 contributor, and no Copyright assigns are required.
    90 90 </p>
    91 91 <p>
    92 92 All committers assert that no patents are hidden within their contributions or that if such patent exists then such
    93 patent is freely licensed to Apache Zest™, other committers and the general public.
    93 patent is freely licensed to Apache Polygene™, other committers and the general public.
    94 94 </p>
    95 95 <p>
    96 All contributors agree that the Apache Zest™ project may change to a later version of the Apache License, if/when such license
    96 All contributors agree that the Apache Polygene™ project may change to a later version of the Apache License, if/when such license
    97 97 becomes available and the Core Dev Team at that time finds it appropriate.
    98 98 </p>
    99 99
  • zest/site/src/doap.rdf

     
    29 29
    30 30 =======================================================================
    31 31 -->
    32 <Project rdf:about="https://zest.apache.org/">
    32 <Project rdf:about="https://polygene.apache.org/">
    33 33 <created>2015-03-18</created>
    34 34 <license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
    35 <name>Apache Zest</name>
    36 <homepage rdf:resource="https://zest.apache.org/" />
    37 <asfext:pmc rdf:resource="https://zest.apache.org" />
    38 <shortdesc>Apache Zest is a community based effort exploring Composite Oriented Programming for domain centric application development.</shortdesc>
    39 <description>Apache Zest is a community based effort exploring Composite Oriented Programming for domain centric application development. This includes evolved concepts from Aspect Oriented Programming, Dependency Injection and Domain Driven Design. Composite Oriented Programming allows developers to work with 'fragments', smaller than classes, and 'compose' fragments into larger 'composites' which acts like the regular objects. Zest also tackles the enforcement of application composition, i.e. composites are declared in modules, modules are contained in layers and access between layers are controlled/enforced. Apache Zest™ (Java Edition), first Apache Zest sub-project, is an implementation of Composite Oriented Programming, using the standard Java platform, without the use of any pre-processors or new language elements. Everything you know from Java still applies and you can leverage both your experience and toolkits to become more productive with Composite Oriented Programming today.</description>
    40 <bug-database rdf:resource="https://issues.apache.org/jira/browse/ZEST" />
    35 <name>Apache Polygene</name>
    36 <homepage rdf:resource="https://polygene.apache.org/" />
    37 <asfext:pmc rdf:resource="https://polygene.apache.org" />
    38 <shortdesc>Apache Polygene is a community based effort exploring Composite Oriented Programming for domain centric application development.</shortdesc>
    39 <description>Apache Polygene is a community based effort exploring Composite Oriented Programming for domain centric application development. This includes evolved concepts from Aspect Oriented Programming, Dependency Injection and Domain Driven Design. Composite Oriented Programming allows developers to work with 'fragments', smaller than classes, and 'compose' fragments into larger 'composites' which acts like the regular objects. Polygene also tackles the enforcement of application composition, i.e. composites are declared in modules, modules are contained in layers and access between layers are controlled/enforced. Apache Polygene™ (Java Edition), first Apache Polygene sub-project, is an implementation of Composite Oriented Programming, using the standard Java platform, without the use of any pre-processors or new language elements. Everything you know from Java still applies and you can leverage both your experience and toolkits to become more productive with Composite Oriented Programming today.</description>
    40 <bug-database rdf:resource="https://issues.apache.org/jira/browse/POLYGENE" />
    41 41 <mailing-list rdf:resource="https://www.apache.org/foundation/mailinglists.html" />
    42 <download-page rdf:resource="https://zest.apache.org/download.html" />
    42 <download-page rdf:resource="https://polygene.apache.org/download.html" />
    43 43 <programming-language>Java</programming-language>
    44 44 <programming-language>C#</programming-language>
    45 45 <programming-language>Scala</programming-language>
     
    48 48 <category rdf:resource="http://projects.apache.org/category/library" />
    49 49 <repository>
    50 50 <SVNRepository>
    51 <location rdf:resource="http://svn.apache.org/repos/asf/zest/"/>
    52 <browse rdf:resource="http://svn.apache.org/viewcvs.cgi/zest/"/>
    51 <location rdf:resource="http://svn.apache.org/repos/asf/polygene/"/>
    52 <browse rdf:resource="http://svn.apache.org/viewcvs.cgi/polygene/"/>
    53 53 </SVNRepository>
    54 54 </repository>
    55 55 <repository>
    56 56 <GitRepository>
    57 <location rdf:resource="https://git-wip-us.apache.org/repos/asf/zest-java.git"/>
    58 <browse rdf:resource="https://github.com/apache/zest-java"/>
    57 <location rdf:resource="https://git-wip-us.apache.org/repos/asf/polygene-java.git"/>
    58 <browse rdf:resource="https://github.com/apache/polygene-java"/>
    59 59 </GitRepository>
    60 60 </repository>
    61 61 <maintainer>
  • zest/site/src/download-qi4j-legacy.html

     
    13 13 <h2>Qi4j™ SDK Releases</h2>
    14 14
    15 15 <p class="lead">
    16 Qi4j™ SDK Releases found below are <strong>not official Apache releases</strong> and were built before Qi4j™ enter the Apache Zest™ project.
    16 Qi4j™ SDK Releases found below are <strong>not official Apache releases</strong> and were built before Qi4j™ enter the Apache Polygene™ project.
    17 17 </p>
    18 18
    19 19 {% if site.data.releases[0].announcement %}
    20 20 <div class="alert alert-success">
    21 <strong>Apache Zest™ (Java Edition) {{ site.data.releases[0].version }} is out!</strong>
    21 <strong>Apache Polygene™ (Java Edition) {{ site.data.releases[0].version }} is out!</strong>
    22 22 <br/>
    23 If you are not working with legacy Qi4j™ applications you should <a href="download.html">download Apache Zest™ (Java Edition)</a> instead.
    23 If you are not working with legacy Qi4j™ applications you should <a href="download.html">download Apache Polygene™ (Java Edition)</a> instead.
    24 24 </div>
    25 25 {% endif %}
    26 26
  • zest/site/src/download.html

     
    1 1 ---
    2 title: Download Apache Zest™
    2 title: Download Apache Polygene™
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
     
    12 12 <h2>Distributions</h2>
    13 13
    14 14 <p>
    15 Apache Zest™ (Java Edition) is split in two downloads: sources and binaries. Both downloads are available in the <code>zip</code> and <code>tar.gz</code> formats. The source code is also available on <a href="https://github.com/apache/zest-java" target="_blank">Github</a>.
    15 Apache Polygene™ (Java Edition) is split in two downloads: sources and binaries. Both downloads are available in the <code>zip</code> and <code>tar.gz</code> formats. The source code is also available on <a href="https://github.com/apache/polygene-java" target="_blank">Github</a>.
    16 16 </p>
    17 17 <p>
    18 The source distributions contains the whole Apache Zest™ (Java Edition) source tree.
    18 The source distributions contains the whole Apache Polygene™ (Java Edition) source tree.
    19 19 See the included <code>README</code> for build guidance.
    20 20 </p>
    21 21 <p>
    22 The binary distributions contains Apache Zest™ (Java Edition) artifacts (classes, javadocs and sources jars), helpers to download all needed dependencies, plus a local copy of the whole documentation website including browsable javadoc.
    22 The binary distributions contains Apache Polygene™ (Java Edition) artifacts (classes, javadocs and sources jars), helpers to download all needed dependencies, plus a local copy of the whole documentation website including browsable javadoc.
    23 23 See the included <code>README</code> for details.
    24 24 </p>
    25 25
     
    29 29 <strong>Using Gradle, Maven, SBT, Ivy or any other build system that provide dependency management?</strong>
    30 30 </p>
    31 31 <p>
    32 Learn how to <a href="java/latest/howto-depend-on-zest.html">depend on Apache Zest™ (Java Edition) in your build</a>.
    32 Learn how to <a href="java/latest/howto-depend-on-polygene.html">depend on Apache Zest™ (Java Edition) in your build</a>.
    33 33 </p>
    34 34 </div>
    35 35 <div class="span2"></div>
     
    42 42 When downloading from a mirror please check the <a href="https://www.apache.org/dev/release-signing#md5">md5sum</a> and verify the <a href="https://www.apache.org/dev/release-signing#openpgp">OpenPGP</a> compatible signature from the main <a href="https://www.apache.org">Apache site</a>.
    43 43 Links are provided below.
    44 44 <br/>
    45 This <a href="https://www.apache.org/dist/zest/KEYS">KEYS</a> file contains the public keys used for signing releases.
    45 This <a href="https://www.apache.org/dist/polygene/KEYS">KEYS</a> file contains the public keys used for signing releases.
    46 46 It is recommended that (when possible) a <a href="https://www.apache.org/dev/release-signing#web-of-trust">web of trust</a> is used to confirm the identity of these keys.
    47 47 </div>
    48 48
    49 49 {% for release in site.data.releases %}
    50 50 {% if release.announcement %}
    51 <h3>Apache Zest™ (Java Edition) {{ release.version }}</h3>
    51 <h3>Apache Polygene™ (Java Edition) {{ release.version }}</h3>
    52 52 <p>Signed by {{ release.signer }}, PGP ID: <code>{{ release.pgpId }}</code>, <a href="{{ release.announcement }}.html">Announcement and Release-Notes</a></p>
    53 53 {% if release.warning %} <div class="alert warning">{{ release.warning }}</div>{% endif %}
    54 54 <h4>Source Distribution</h4>
    55 55 <table class="table table-striped">
    56 56 <tr>
    57 <td><a href="https://www.apache.org/dyn/closer.lua/zest/apache-zest-java-{{ release.version }}-src.zip"><i class="icon-download"></i> apache-zest-java-{{ release.version }}-src.zip</a></td>
    58 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-src.zip.MD5"><small>(MD5)</small></a></td>
    59 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-src.zip.SHA-512"><small>(SHA-512)</small></a></td>
    60 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-src.zip.asc"><small>(OpenPGP asc)</small></a></td>
    57 <td><a href="https://www.apache.org/dyn/closer.lua/polygene/apache-polygene-java-{{ release.version }}-src.zip"><i class="icon-download"></i> apache-polygene-java-{{ release.version }}-src.zip</a></td>
    58 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-src.zip.MD5"><small>(MD5)</small></a></td>
    59 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-src.zip.SHA-512"><small>(SHA-512)</small></a></td>
    60 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-src.zip.asc"><small>(OpenPGP asc)</small></a></td>
    61 61 </tr>
    62 62 <tr>
    63 <td><a href="https://www.apache.org/dyn/closer.lua/zest/apache-zest-java-{{ release.version }}-src.tgz"><i class="icon-download"></i> apache-zest-java-{{ release.version }}-src.tgz</a></td>
    64 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-src.tgz.MD5"><small>(MD5)</small></a></td>
    65 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-src.tgz.SHA-512"><small>(SHA-512)</small></a></td>
    66 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-src.tgz.asc"><small>(OpenPGP asc)</small></a></td>
    63 <td><a href="https://www.apache.org/dyn/closer.lua/polygene/apache-polygene-java-{{ release.version }}-src.tgz"><i class="icon-download"></i> apache-polygene-java-{{ release.version }}-src.tgz</a></td>
    64 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-src.tgz.MD5"><small>(MD5)</small></a></td>
    65 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-src.tgz.SHA-512"><small>(SHA-512)</small></a></td>
    66 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-src.tgz.asc"><small>(OpenPGP asc)</small></a></td>
    67 67 </tr>
    68 68 </table>
    69 69 <h4>Binary Distribution</h4>
    70 70 <table class="table table-striped">
    71 71 <tr>
    72 <td><a href="https://www.apache.org/dyn/closer.lua/zest/apache-zest-java-{{ release.version }}-bin.zip"><i class="icon-download"></i> apache-zest-java-{{ release.version }}-bin.zip</a></td>
    73 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-bin.zip.MD5"><small>(MD5)</small></a></td>
    74 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-bin.zip.SHA-512"><small>(SHA-512)</small></a></td>
    75 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-bin.zip.asc"><small>(OpenPGP asc)</small></a></td>
    72 <td><a href="https://www.apache.org/dyn/closer.lua/polygene/apache-polygene-java-{{ release.version }}-bin.zip"><i class="icon-download"></i> apache-polygene-java-{{ release.version }}-bin.zip</a></td>
    73 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-bin.zip.MD5"><small>(MD5)</small></a></td>
    74 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-bin.zip.SHA-512"><small>(SHA-512)</small></a></td>
    75 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-bin.zip.asc"><small>(OpenPGP asc)</small></a></td>
    76 76 </tr>
    77 77 <tr>
    78 <td><a href="https://www.apache.org/dyn/closer.lua/zest/apache-zest-java-{{ release.version }}-bin.tgz"><i class="icon-download"></i> apache-zest-java-{{ release.version }}-bin.tgz</a></td>
    79 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-bin.tgz.MD5"><small>(MD5)</small></a></td>
    80 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-bin.tgz.SHA-512"><small>(SHA-512)</small></a></td>
    81 <td><a href="https://www.apache.org/dist/zest/apache-zest-java-{{ release.version }}-bin.tgz.asc"><small>(OpenPGP asc)</small></a></td>
    78 <td><a href="https://www.apache.org/dyn/closer.lua/polygene/apache-polygene-java-{{ release.version }}-bin.tgz"><i class="icon-download"></i> apache-polygene-java-{{ release.version }}-bin.tgz</a></td>
    79 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-bin.tgz.MD5"><small>(MD5)</small></a></td>
    80 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-bin.tgz.SHA-512"><small>(SHA-512)</small></a></td>
    81 <td><a href="https://www.apache.org/dist/polygene/apache-polygene-java-{{ release.version }}-bin.tgz.asc"><small>(OpenPGP asc)</small></a></td>
    82 82 </tr>
    83 83 </table>
    84 84 {% endif %}
     
    93 93
    94 94 {% unless site.data.releases[0].announcement %}
    95 95 <p class="alert alert-warning">
    96 The Apache Zest™ project has not released any version yet.
    96 The Apache Polygene™ project has not released any version yet.
    97 97 Until then, download a <a href="download-qi4j-legacy.html">legacy Qi4j™ version</a>.
    98 98 </p>
    99 99 {% endunless %}
    100 100
    101 101 <h2>Versioning</h2>
    102 102
    103 <p>Apache Zest™ versioning tries to stick to;</p>
    103 <p>Apache Polygene™ versioning tries to stick to;</p>
    104 104 <ul>
    105 105 <li>For changes in the 3rd version digit, for instance from 1.3.1 to 1.3.2, only bug fixes have occurred.</li>
    106 106 <li>For changes in the 2nd version digit, for instance from 1.3.1 to 1.4, more features have been added.</li>
  • zest/site/src/index.html

     
    1 1 ---
    2 2 layout: default
    3 title: Apache Zest
    3 title: Apache Polygene
    4 4 ---
    5 5 <div class="row-fluid">
    6 6 <div class="span3" style="text-align: center; padding-bottom: 32px">
    7 7 <img src="graphics/Qi4j-Logo-Symbol.png"/>
    8 <img src="graphics/Apache-Zest-Logo-Text.png"/>
    8 <img src="graphics/Apache-Polygene-Logo-Text.png"/>
    9 9 </div>
    10 10 <div class="span9">
    11 11 <div class="row-fluid">
    12 12 <div class="span9">
    13 13 <div class="well">
    14 <h2>What is Apache Zest™?</h2>
    14 <h2>What is Apache Polygene™?</h2>
    15 <p>Let's create an example application. Open a terminal/console and type;</p>
    16 <code><pre>
    17 polygene create-project restapp Order my.domain.order
    18 ./gradlew assemble jettyRun
    19 </pre>
    20 </code>
    21 <p>Open <a href="http://localhost:8080/app/api/">http://localhost:8080/app/api/</a> in browser. You will get the REST API root endpoint, showing Customers and Orders.</p>
    22 <p>We can navigate to Customers <a href="http://localhost:8080/app/api/customers/">http://localhost:8080/app/api/customers/</a></p>
    23 <p>There are no Customers, but instructions how to create one.</p>
    24 <p>Open a new terminal and let's create a Customer.</p>
    25 <code><pre>
    26 curl -u admin:secret -d name="Niclas Hedhman" http://localhost:8080/app/api/customers/create
    27 </pre></code>
    28 <p>We get back a confirmation that the Customer was created and the location of </p>
    29 <code><pre>
    30 $ echo '{ "name": "Niclas Hedhman",
    31 "address": "Canary Residence",
    32 "city": "Cheras",
    33 "country": "Malaysia",
    34 "phone": "" }' | curl http://localhost:8080/app/api
    35 </pre>
    36 </code>
    15 37 <p>
    16 The short answer is that <strong>Apache Zest™</strong> is a community based effort exploring Composite Oriented Programming for domain centric application development. This includes evolved concepts from <a href="https://en.wikipedia.org/wiki/Aspect-oriented_programming">Aspect Oriented Programming</a>, <a href="https://en.wikipedia.org/wiki/Dependency_injection">Dependency Injection</a> and <a href="https://en.wikipedia.org/wiki/Domain-driven_design">Domain Driven Design</a>.
    38 The simple Order domain model is found in <code>Order/model/src/main/java/my/domain/order/model/orders</code>
    39 and we can see <code>Customer.java</code>, <code>Order.java</code> and <code>OrderItem.java</code>
    17 40 </p>
    41 <code><pre>
    42 public interface Order extends Identity
    43 {
    44 Property&lt;String&gt; orderNumber();
    45 Association&lt;Customer&gt; customer();
    46 ManyAssociation&lt;OrderItem&gt; items();
    47 Property&lt;ZonedDateTime&gt; registered();
    48 @Optional Property&lt;ZonedDateTimeOpti shipped();
    49 }
    50 </pre></code>
    51 <code><pre>
    52 public interface OrderItem extends Identity
    53 {
    54 Property&lt;String&gt; partNumber();
    55 Property&lt;BigDecimal&gt; unitPrice();
    56 Property&lt;Integer&gt; units();
    57 Property&lt;BigDecimal&gt; discount();
    58 }
    59 </pre></code>
    60 <!--
    18 61 <p>
    19 <strong>Composite Oriented Programming</strong> allows developers to work with 'fragments', smaller than classes, and 'compose' fragments into larger 'composites' which acts like the regular objects. Apache Zest™ also tackles the enforcement of application composition, i.e. composites are declared in modules, modules are contained in layers and access between layers are controlled/enforced.
    62 The short answer is that <strong>Apache Polygene™</strong> is a community based effort exploring Composite Oriented Programming for domain centric application development. This includes evolved concepts from <a href="https://en.wikipedia.org/wiki/Aspect-oriented_programming">Aspect Oriented Programming</a>, <a href="https://en.wikipedia.org/wiki/Dependency_injection">Dependency Injection</a> and <a href="https://en.wikipedia.org/wiki/Domain-driven_design">Domain Driven Design</a>.
    20 63 </p>
    21 64 <p>
    22 <strong>Apache Zest™ (Java Edition)</strong>, first Apache Zest sub-project, is an implementation of Composite Oriented Programming, using the standard Java platform, without the use of any pre-processors or new language elements. Everything you know from Java still applies and you can leverage both your experience and toolkits to become more productive with Composite Oriented Programming today.
    65 <strong>Composite Oriented Programming</strong> allows developers to work with 'fragments', smaller than classes, and 'compose' fragments into larger 'composites' which acts like the regular objects. Apache Polygene™ also tackles the enforcement of application composition, i.e. composites are declared in modules, modules are contained in layers and access between layers are controlled/enforced.
    23 66 </p>
    24 67 <p>
    25 The Apache Zest™ community welcomes any effort exploring Composite Oriented Programming for domain centric application development using any technology.
    68 <strong>Apache Polygene™ (Java Edition)</strong>, first Apache Polygene sub-project, is an implementation of Composite Oriented Programming, using the standard Java platform, without the use of any pre-processors or new language elements. Everything you know from Java still applies and you can leverage both your experience and toolkits to become more productive with Composite Oriented Programming today.
    26 69 </p>
    70 <p>
    71 The Apache Polygene™ community welcomes any effort exploring Composite Oriented Programming for domain centric application development using any technology.
    72 </p>
    73 -->
    27 74 </div>
    28 75 </div>
    29 76 <div class="span3">
    30 77 <a href="http://www.apache.org" target="_blank"><img src="landing-resources/img/asf_logo.png"/></a>
    31 78 <h3><i class="icon-group"></i> Get Help</h3>
    32 <p>Join the <a href="https://www.apache.org/foundation/mailinglists.html" target="_blank">dev@zest.apache.org</a> mailing list to discuss and get help, or help others on <a href="http://stackoverflow.com/questions/tagged/apache-zest">Stackoverflow</a>.</p>
    79 <p>Join the <a href="https://www.apache.org/foundation/mailinglists.html" target="_blank">dev@polygene.apache.org</a> mailing list to discuss and get help<!--, or help others on <a href="http://stackoverflow.com/questions/tagged/apache-polygene">Stackoverflow</a>-->.</p>
    80 You can also subscribe from here: <a href="mailto:dev-subscribe@polygene.apache.org" title="Click to subscribe to this list" style="margin: 0 auto" class="btn btn-primary">Subscribe</a>
    33 81 </div>
    34 82 </div>
    35 83 <div class="row-fluid">
    36 84 <div class="span6">
    37 85 <h3><i class="icon-briefcase"></i> Learn more</h3>
    38 <p><a href="java/latest/intro.html">Learn more</a> about problems Apache Zest™ (Java Edition) tries to solve thanks to Composite Oriented Programming and how you can confidently develop domain centric applications with it.</p>
    86 <p><a href="java/latest/intro.html">Learn more</a> about problems Apache Polygene™ (Java Edition) tries to solve thanks to Composite Oriented Programming and how you can confidently develop domain centric applications with it.</p>
    39 87 </div><!--/span-->
    40 88 <div class="span6">
    41 89 <h3><i class="icon-download"></i> Download</h3>
    42 <p><a href="download.html">Download</a> the Apache Zest™ (Java Edition) SDK binaries and sources, learn how to <a href="java/latest/howto-depend-on-qi4j.html">depend on Apache Zest™ (Java Edition) in your build</a> or simply get the <a href="community/codebase.html">source</a>.</p>
    90 <p><a href="download.html">Download</a> the Apache Polygene™ (Java Edition) SDK binaries and sources, learn how to <a href="java/latest/howto-depend-on-qi4j.html">depend on Apache Polygene™ (Java Edition) in your build</a> or simply get the <a href="community/codebase.html">source</a>.</p>
    43 91 </div><!--/span-->
    44 92 </div><!--/row-->
    45 93 <div class="row-fluid">
    46 94 <div class="span6">
    47 95 <h3><i class="icon-time"></i> Get started</h3>
    48 <p>Get a grasp on Apache Zest™ (Java Edition) in 42 minutes and then, get real through the first steps needed to get a complete application up and running. From there, work through the fundamentals of Apache Zest™ (Java Edition) development with in-depth tutorials.</p>
    96 <p>Get a grasp on Apache Polygene™ (Java Edition) in 42 minutes and then, get real through the first steps needed to get a complete application up and running. From there, work through the fundamentals of Apache Polygene™ (Java Edition) development with in-depth tutorials.</p>
    49 97 <p><a href="java/latest/tutorials.html"><i class="icon-time"></i> View details &raquo;</a></p>
    50 98 </div><!--/span-->
    51 99 <div class="span6">
    52 100 <h3><i class="icon-book"></i> Read the docs</h3>
    53 <p>Everything you need to know about internals and how to use Apache Zest™ (Java Edition). Runable samples, comprehensive documentation of the Apache Zest™ (Java Edition) Core, Libraries, Extensions and Tools.</p>
    101 <p>Everything you need to know about internals and how to use Apache Polygene™ (Java Edition). Runable samples, comprehensive documentation of the Apache Polygene™ (Java Edition) Core, Libraries, Extensions and Tools.</p>
    54 102 <p><a class="" href="java/latest/index.html"><i class="icon-book"></i> View details &raquo;</a></p>
    55 103 </div><!--/span-->
    56 104 </div><!--/row-->
  • zest/site/src/news.html

     
    1 1 ---
    2 title: Apache Zest™ News
    2 title: Apache Polygene™ News
    3 3 layout: default
    4 4 ---
    5 5 <div class="page-header">
    6 <h1>Apache Zest™ News</h1>
    6 <h1>Apache Polygene™ News</h1>
    7 7 <p class="lead"><a href="atom.xml"><i class="icon-rss"></i> Atom Feed</a></p>
    8 8 </div>
    9 9