Changes for page WOProject-Maven

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -9,4 +9,69 @@
9	9
10	10	== Getting Started ==
11	11
12		-It makes take more then five minutes to get you startet but it's worth to take the ride. [[Guided Maven Example]]
	12	+* Install [[Maven2>>http://maven.apache.org]] on a local machine.
	13	+* Add ObjectStyle Maven2 repository to the project POM //(we may distribute the plugins via Ibiblio at some point too)//. E.g.:
	14	+
	15	+{{code title="pom.xml"}}
	16	+
	17	+<pluginRepositories>
	18	+ <pluginRepository>
	19	+ <id>objectstyle</id>
	20	+ <name>ObjectStyle Public Maven2 repo</name>
	21	+ <url>http://objectstyle.org/maven2</url>
	22	+ <layout>default</layout>
	23	+ <snapshots>
	24	+ <enabled>true</enabled>
	25	+ <updatePolicy>daily</updatePolicy>
	26	+ <checksumPolicy>ignore</checksumPolicy>
	27	+ </snapshots>
	28	+ <releases>
	29	+ <enabled>true</enabled>
	30	+ </releases>
	31	+ </pluginRepository>
	32	+...
	33	+</pluginRepositories>
	34	+
	35	+{{/code}}
	36	+
	37	+* Plugins are bound to the build lifecycle via "project/build/plugins" section of the POM. Here is a general example, for more details see documentation of individual plugins:
	38	+
	39	+{{code title="pom.xml"}}
	40	+
	41	+<build>
	42	+ <plugins>
	43	+ <plugin>
	44	+ <groupId>org.objectstyle.woproject.maven2</groupId>
	45	+
	46	+ plugin specific information goes here...
	47	+
	48	+ </plugin>
	49	+ </plugins>
	50	+</build>
	51	+
	52	+{{/code}}
	53	+
	54	+{{info title="Useful Information"}}
	55	+
	56	+By default, Maven will search the groupId org.apache.maven.plugins for prefix-to-artifactId mappings for the plug-ins it needs to perform a given build. However, WOProject maven plug-ins belong to a different group: *org.objectstyle.woproject.maven2*. Since the Maven project is assumed to have control over the default plug-in groupId, we can configure Maven to search other groupId locations for plugin-prefix mappings.
	57	+
	58	+In the Maven settings file (per-user: ~/.m2/settings.xml; global: $M2_HOME/conf/settings.xml), you can provide a custom pluginGroups section, listing the plugin groupIds you want to search (each groupId goes in its own pluginGroup sub-element). For example, if your projects use a WOProject maven plug-in, you might have the following in your settings:
	59	+
	60	+{code:xml|title=settings.xml}
	61	+<settings>
	62	+...
	63	+ <pluginGroups>
	64	+ <pluginGroup>org.objectstyle.woproject.maven2</pluginGroup>
	65	+ </pluginGroups>
	66	+...
	67	+</settings>
	68	+{code}
	69	+
	70	+Now you can directly execute plug-ins, i.e. *mvn woproject:goal* instead of *mvn org.objectstyle.woproject.maven2:maven-woproject-plugin:goal*.
	71	+
	72	+Reference: http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html.
	73	+
	74	+{{/info}}
	75	+
	76	+[[^settings.xml]] ecample settings.xml.
	77	+[[^MavenHelloWorldExamples.zip]] MavenHelloWorldExamples projects.