Skip to Content

Changes for page WOProject-Maven

Last modified by Ulrich Köster on 2011/08/20 20:03
From version 62.1
edited by Andrus Adamchik
on 2006/09/30 18:46
Change comment: There is no comment for this version
To version 65.1
edited by Ulrich Köster
on 2006/10/27 08:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.andrus
1 +XWiki.uli
Content
... ... @@ -1,9 +1,9 @@
1 1  This is the home page for the Maven Plugins space.
2 2  
3 -== Maven Plugins ==
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]]
6 +* [[maven-woproject-plugin]]
7 7  * Maven2 WebObjects Archetypes
8 8  ** [[maven-archetype-woapplication]]
9 9  
... ... @@ -13,6 +13,7 @@
13 13  * Add ObjectStyle Maven2 repository to the project POM //(we may distribute the plugins via Ibiblio at some point too)//. E.g.:
14 14  
15 15  {{code title="pom.xml"}}
16 +
16 16  <pluginRepositories>
17 17   <pluginRepository>
18 18   <id>objectstyle</id>
... ... @@ -33,7 +33,44 @@
33 33  
34 34  {{/code}}
35 35  
36 -//(outdated - fixme)//
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:
37 37  
38 -* [[Preparing the Project]]
39 -* [[Maven Goals]]
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 +[[^examples.zip]] ecample projects.