Skip to Content

Changes for page maven-wobootstrap-plugin

Last modified by Yana Oksner on 2026/01/08 12:35
From version 20.2
edited by Lachlan Deck
on 2023/11/13 11:56
Change comment: Update document after refactoring.
To version 21.1
edited by Yana Oksner
on 2026/01/08 12:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ldeck
1 +XWiki.yanasd
Content
... ... @@ -22,22 +22,22 @@
22 22  
23 23  In most cases, wobootstrap:install doesn't need any configuration. It also doesn't need a Maven project to run.
24 24  
25 -{{noformat}}
25 +{{code}}
26 26  
27 27  mvn wobootstrap:install
28 28  
29 -{{/noformat}}
29 +{{/code}}
30 30  
31 31  === The wobootstrap:deploy Mojo ===
32 32  
33 33  The wobootstrap:deploy Mojo is used to install the WebObjects libraries to a remote repository (i.e. managed by an Enterprise Repository Manager). The full usage statement of the wobootstrap:deploy mojo can be described as:
34 34  
35 -{{noformat}}
35 +{{code}}
36 36  
37 37  mvn wobootstrap:deploy -Durl=file://C:\m2-repo \
38 38   -DrepositoryId=some.id
39 39  
40 -{{/noformat}}
40 +{{/code}}
41 41  
42 42  If the url to deploy is not specified, the goal will fail. The repositoryId points to a server section in the settings.xml file. If you don't specify a repositoryId, Maven will try to extract authentication information using the default id 'remote-repository'.
43 43  
... ... @@ -69,12 +69,12 @@
69 69  
70 70  These configurations are optional, but you have to provide both if you want to customize the search for WebObjects libraries.
71 71  
72 -{{noformat}}
72 +{{code}}
73 73  
74 74  mvn wobootstrap:install -DwebObjectsLibFolder=/a_path_to_webobjects/lib \
75 75   -DwebObjectsVersion=5.3.3
76 76  
77 -{{/noformat}}
77 +{{/code}}
78 78  
79 79  You can use these parameters with both goals: install and deploy.
80 80