Author: buildbot
Date: Thu Nov 3 09:00:17 2016
New Revision: 1000426
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Nov 3 09:00:17 2016
@@ -1 +1 @@
-1767843
+1767844
Modified:
websites/staging/sling/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.html
Thu Nov 3 09:00:17 2016
@@ -130,7 +130,7 @@ h2:hover > .headerlink, h3:hover > .head
</ul>
</div>
<h2 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h2>
-<p>The Sling IDE Tooling relies on the <a
href="https://wiki.eclipse.org/M2E_compatible_maven_plugins";>m2e incremental
build support</a> for the generation of the bundle's manifest, the component
descriptions as well as the metatype resources (the latter being generated
through OSGi 6 <a
href="https://osgi.org/javadoc/r6/cmpn/org/osgi/service/component/annotations/package-summary.html";>component
annotations</a> and <a
href="https://osgi.org/javadoc/r6/cmpn/org/osgi/service/metatype/annotations/package-summary.html";>metatype
annotations</a> or through <a
href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html";>Apache
Felix SCR annotations</a>. That means whenever at least one java class is
touched and the auto-build in Eclipse is enabled, the annotations on that class
should be reevaluated which may lead to a modification of the bundle's manifest
and/or generation/modification of service description XMLs and/or Metatype
resource file
s.
+<p>The Sling IDE Tooling relies on the <a
href="https://wiki.eclipse.org/M2E_compatible_maven_plugins";>m2e incremental
build support</a> for the generation of the bundle's manifest, the component
descriptions as well as the metatype resources (the latter two being generated
through OSGi 6 <a
href="https://osgi.org/javadoc/r6/cmpn/org/osgi/service/component/annotations/package-summary.html";>component
annotations</a> and <a
href="https://osgi.org/javadoc/r6/cmpn/org/osgi/service/metatype/annotations/package-summary.html";>metatype
annotations</a> or through <a
href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html";>Apache
Felix SCR annotations</a>). That means whenever at least one java class is
touched and the auto-build in Eclipse is enabled the annotations on that class
should be reevaluated. This may lead to a modification of the bundle's manifest
and/or generation/modification of service description XMLs and/or Metatype
resource
files.
Depending on which maven plugins you use you must adjust their configuration
accordingly to properly support incremental builds.</p>
<h2 id="manifest-generation">Manifest Generation<a class="headerlink"
href="#manifest-generation" title="Permanent link">¶</a></h2>
<h3 id="maven-bundle-plugin">maven-bundle-plugin<a class="headerlink"
href="#maven-bundle-plugin" title="Permanent link">¶</a></h3>
@@ -145,7 +145,7 @@ Depending on which maven plugins you use
<p>OSGi component and metatype annotations (for OSGi 6) are natively supported
through bnd (and therefore automatically generated through both
maven-bundle-plugin and bnd-maven-plugin). You don't need to configure anything
explicitly since version 3.0.0 of bnd (<a
href="https://github.com/bndtools/bnd/issues/1041";>issue 1041</a>).</p>
<p>The maven-bundle-plugin can be optionally coupled with the <a
href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-maven-scr-plugin-use.html";>maven-scr-plugin</a>.
Both maven-bundle-plugin as well as bnd-maven-plugin can be optionally coupled
with the <a
href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.html";>scr-bnd-plugin</a>.
Both approaches can be used to generate components descriptions and metatype
resources out of the <a
href="http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html";>Felix
SCR annotations</a>. The recommended way for new projects though is to rely on
OSGi 6 annotations. However if you need to rely on Felix SCR annotations though
it is recommended to rather use the scr-bnd-plugin over the maven-scr-plugin,
as the former is nicely integrated into bnd and therefore means less overhead
during the build.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1767843 by kwin on Thu, 3 Nov 2016 08:59:16 +0000
+ Rev. 1767844 by kwin on Thu, 3 Nov 2016 09:00:07 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
