Changes for page WOProject-Maven

Summary

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

Details

Page properties

Content

...	...	@@ -1,74 +1,60 @@
1	1	This is the home page for the Maven Plugins space.
2	2
	3	+[[Maven 2.0.9>>http://maven.apache.org/download.html]] is recommended.
	4	+
3	3	== WOProject Maven2 Plugins ==
4	4
5	5	* [[maven-japplication-plugin]]: A Maven plugin for assembling native launchers of Java applications for a number of OS platforms.
6		-* [[maven-woproject-plugin]]
	8	+* [[maven-wobootstrap-plugin]]:
	9	+* [[maven-wolifecycle-plugin]]:
7	7	* Maven2 WebObjects Archetypes
8		-** [[maven-archetype-woapplication]]
	11	+** [[woapplication-archetype]] (new)
	12	+** [[maven-archetype-woapplication]] (deprecated)
9	9
10		-== Getting Started ==
	14	+== Why use Maven? ==
11	11
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.:
	16	+* http:~/~/www.oreillynet.com/onjava/blog/2007/11/why_maven.html
	17	+* http:~/~/www.infoq.com/news/2008/01/maven-debate
14	14
15		-{{code title="pom.xml"}}
	19	+== Maven Principles ==
16	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>
	21	+* http:~/~/maven.apache.org/what-is-maven.html
34	34
35		-{{/code}}
	23	+== Getting Started ==
36	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:
	25	+* http:~/~/maven.apache.org/guides/getting-started/index.html
	26	+* http:~/~/www.developer.com/lang/article.php/10924_3510331_1
	27	+* http:~/~/www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven.html?lsrc=jwrss
	28	+* Maven: The Definitive Guide (book): http:~/~/www.sonatype.com/book/
	29	+* Better Builds with Maven (book): http:~/~/www.devzuz.com/web/guest/products/resources#BBWM
38	38
39		-{{code title="pom.xml"}}
	31	+== Repository Managers ==
40	40
41		-<build>
42		- <plugins>
43		- <plugin>
44		- <groupId>org.objectstyle.woproject.maven2</groupId>
	33	+=== What is a Repository Manager? ===
45	45
46		- plugin specific information goes here...
	35	+* http:~/~/maven.apache.org/repository-management.html
47	47
48		- </plugin>
49		- </plugins>
50		-</build>
	37	+=== Available Repository Managers ===
51	51
52		-{{/code}}
	39	+* Archiva: http:~/~/maven.apache.org/archiva/
	40	+* Artifactory: http:~/~/www.jfrog.org/sites/artifactory/latest/
	41	+* Nexus: http:~/~/nexus.sonatype.org/
53	53
54		-{{info title="Useful Information"}}
	43	+== Enterprise Super POM ==
55	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.
	45	+* http:~/~/www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html
	46	+* http:~/~/maven.apache.org/guides/introduction/introduction-to-the-pom.html
	47	+* http:~/~/maven.apache.org/pom.html
57	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:
	49	+== IDE Integration ==
59	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}
	51	+* M2Eclipse: http:~/~/m2eclipse.codehaus.org/
	52	+* Q4E: http:~/~/code.google.com/p/q4e/
69	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*.
	54	+== Building woproject with maven ==
71	71
72		-Reference: http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html.
	56	+[[Building the woproject source code with maven]]
73	73
74		-{{/info}}
	58	+== Building wonder with maven ==
	59	+
	60	+[[Building the wonder source code with maven]]