Author: buildbot
Date: Wed Mar 4 15:32:47 2015
New Revision: 942318
Log:
Staging update by buildbot for aries
Modified:
websites/staging/aries/trunk/content/ (props changed)
websites/staging/aries/trunk/content/modules/blueprint-maven-plugin.html
Propchange: websites/staging/aries/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 4 15:32:47 2015
@@ -1 +1 @@
-1664044
+1664045
Modified:
websites/staging/aries/trunk/content/modules/blueprint-maven-plugin.html
==============================================================================
--- websites/staging/aries/trunk/content/modules/blueprint-maven-plugin.html
(original)
+++ websites/staging/aries/trunk/content/modules/blueprint-maven-plugin.html
Wed Mar 4 15:32:47 2015
@@ -271,8 +271,8 @@
<!-- Content -->
<div class="wiki-content"><p>Writing blueprint xml is quite
verbose and large blueprint xmls are difficult to keep in sync with code
changes and especially refactorings.
So you would like to do most declarations using annoations and ideally these
annotations should be standardized.</p>
-<h2 id="maven-blueprint-plugin">Maven-blueprint-plugin</h2>
-<p>The maven-blueprint-plugin allows to configure blueprint using annotations.
It scans one or more paths for annotated classes and creates a blueprint.xml in
target/generated-resources. So at runtime the bundle behaves like a normal
blueprint bundle.
+<h2 id="blueprint-maven-plugin">blueprint-maven-plugin</h2>
+<p>The blueprint-maven-plugin allows to configure blueprint using annotations.
It scans one or more paths for annotated classes and creates a blueprint.xml in
target/generated-resources. So at runtime the bundle behaves like a normal
blueprint bundle.
The generated blueprint can also be used together with a manually created
blueprint file. So for example property placeholder configurations
or cxf services can be created in xml while most of the beans are
automatically generated.</p>
<p>Usage:</p>
