ruby-maven 3.0.3.0.29.0.pre → 3.0.4.0.29.0
Sign up to get free protection for your applications and to get access to all the features.
- data/LICENSE.txt +202 -202
- data/NOTICE.txt +23 -23
- data/README.txt +77 -77
- data/bin/m2.conf +2 -2
- data/bin/rmvn +0 -1
- data/conf/settings.xml +257 -257
- data/lib/aether-api-1.13.1.jar +0 -0
- data/lib/aether-connector-wagon-1.13.1.jar +0 -0
- data/lib/aether-impl-1.13.1.jar +0 -0
- data/lib/aether-spi-1.13.1.jar +0 -0
- data/lib/aether-util-1.13.1.jar +0 -0
- data/lib/ext/README.txt +2 -2
- data/lib/maven-aether-provider-3.0.4.jar +0 -0
- data/lib/maven-artifact-3.0.4.jar +0 -0
- data/lib/{maven-compat-3.0.3.jar → maven-compat-3.0.4.jar} +0 -0
- data/lib/{maven-core-3.0.3.jar → maven-core-3.0.4.jar} +0 -0
- data/lib/maven-embedder-3.0.4.jar +0 -0
- data/lib/maven-model-3.0.4.jar +0 -0
- data/lib/{maven-model-builder-3.0.3.jar → maven-model-builder-3.0.4.jar} +0 -0
- data/lib/{maven-plugin-api-3.0.3.jar → maven-plugin-api-3.0.4.jar} +0 -0
- data/lib/{maven-repository-metadata-3.0.3.jar → maven-repository-metadata-3.0.4.jar} +0 -0
- data/lib/{maven-settings-3.0.3.jar → maven-settings-3.0.4.jar} +0 -0
- data/lib/{maven-settings-builder-3.0.3.jar → maven-settings-builder-3.0.4.jar} +0 -0
- data/lib/plexus-cipher-1.7.jar +0 -0
- data/lib/ruby/ruby_maven.rb +25 -10
- data/lib/sisu-guava-0.9.9.jar +0 -0
- data/lib/sisu-guice-3.1.0-no_aop.jar +0 -0
- data/lib/sisu-inject-bean-2.3.0.jar +0 -0
- data/lib/sisu-inject-plexus-2.3.0.jar +0 -0
- data/lib/wagon-file-2.2.jar +0 -0
- data/lib/wagon-http-2.2-shaded.jar +0 -0
- data/lib/wagon-provider-api-2.2.jar +0 -0
- metadata +40 -46
- data/bin/gwt +0 -59
- data/bin/jetty-run +0 -26
- data/bin/tomcat-run +0 -26
- data/lib/aether-api-1.11.jar +0 -0
- data/lib/aether-connector-wagon-1.11.jar +0 -0
- data/lib/aether-impl-1.11.jar +0 -0
- data/lib/aether-spi-1.11.jar +0 -0
- data/lib/aether-util-1.11.jar +0 -0
- data/lib/maven-aether-provider-3.0.3.jar +0 -0
- data/lib/maven-artifact-3.0.3.jar +0 -0
- data/lib/maven-embedder-3.0.3.jar +0 -0
- data/lib/maven-model-3.0.3.jar +0 -0
- data/lib/nekohtml-1.9.6.2.jar +0 -0
- data/lib/plexus-cipher-1.4.jar +0 -0
- data/lib/ruby-maven-3.0.3.0.29.0.pre.jar +0 -0
- data/lib/ruby/maven/model/dependencies.rb +0 -281
- data/lib/ruby/maven/model/model.rb +0 -490
- data/lib/ruby/maven/model/model_utils.rb +0 -322
- data/lib/ruby/maven/tools/execute_in_phase.rb +0 -9
- data/lib/ruby/maven/tools/gem_project.rb +0 -400
- data/lib/ruby/maven/tools/gemfile_lock.rb +0 -67
- data/lib/ruby/maven/tools/pom_generator.rb +0 -63
- data/lib/ruby/maven/tools/rails_project.rb +0 -164
- data/lib/ruby/maven/tools/versions.rb +0 -12
- data/lib/sisu-guice-2.9.4-no_aop.jar +0 -0
- data/lib/sisu-inject-bean-2.1.1.jar +0 -0
- data/lib/sisu-inject-plexus-2.1.1.jar +0 -0
- data/lib/wagon-file-1.0-beta-7.jar +0 -0
- data/lib/wagon-http-lightweight-1.0-beta-7.jar +0 -0
- data/lib/wagon-http-shared-1.0-beta-7.jar +0 -0
- data/lib/wagon-provider-api-1.0-beta-7.jar +0 -0
- data/lib/xercesMinimal-1.9.6.2.jar +0 -0
data/README.txt
CHANGED
|
@@ -1,77 +1,77 @@
|
|
|
1
|
-
|
|
2
|
-
Apache Maven
|
|
3
|
-
|
|
4
|
-
What is it?
|
|
5
|
-
-----------
|
|
6
|
-
|
|
7
|
-
Maven is a software project management and comprehension tool. Based on
|
|
8
|
-
the concept of a Project Object Model (POM), Maven can manage a project's
|
|
9
|
-
build, reporting and documentation from a central piece of information.
|
|
10
|
-
|
|
11
|
-
Documentation
|
|
12
|
-
-------------
|
|
13
|
-
|
|
14
|
-
The most up-to-date documentation can be found at http://maven.apache.org/.
|
|
15
|
-
|
|
16
|
-
Release Notes
|
|
17
|
-
-------------
|
|
18
|
-
|
|
19
|
-
The full list of changes can be found at http://maven.apache.org/release-notes.html.
|
|
20
|
-
|
|
21
|
-
System Requirements
|
|
22
|
-
-------------------
|
|
23
|
-
|
|
24
|
-
JDK:
|
|
25
|
-
1.5 or above (this is to execute Maven - it still allows you to build against 1.3
|
|
26
|
-
and prior JDK's).
|
|
27
|
-
Memory:
|
|
28
|
-
No minimum requirement.
|
|
29
|
-
Disk:
|
|
30
|
-
No minimum requirement. Approximately 100MB will be used for your local repository,
|
|
31
|
-
however this will vary depending on usage and can be removed and redownloaded at
|
|
32
|
-
any time.
|
|
33
|
-
Operating System:
|
|
34
|
-
No minimum requirement. On Windows, Windows NT and above or Cygwin is required for
|
|
35
|
-
the startup scripts. Tested on Windows XP, Fedora Core and Mac OS X.
|
|
36
|
-
|
|
37
|
-
Installing Maven
|
|
38
|
-
----------------
|
|
39
|
-
|
|
40
|
-
1) Unpack the archive where you would like to store the binaries, eg:
|
|
41
|
-
|
|
42
|
-
Unix-based Operating Systems (Linux, Solaris and Mac OS X)
|
|
43
|
-
tar zxvf apache-maven-3.0.x.tar.gz
|
|
44
|
-
Windows 2000/XP
|
|
45
|
-
unzip apache-maven-3.0.x.zip
|
|
46
|
-
|
|
47
|
-
2) A directory called "apache-maven-3.0.x" will be created.
|
|
48
|
-
|
|
49
|
-
3) Add the bin directory to your PATH, eg:
|
|
50
|
-
|
|
51
|
-
Unix-based Operating Systems (Linux, Solaris and Mac OS X)
|
|
52
|
-
export PATH=/usr/local/apache-maven-3.0.x/bin:$PATH
|
|
53
|
-
Windows 2000/XP
|
|
54
|
-
set PATH="c:\program files\apache-maven-3.0.x\bin";%PATH%
|
|
55
|
-
|
|
56
|
-
4) Make sure JAVA_HOME is set to the location of your JDK
|
|
57
|
-
|
|
58
|
-
5) Run "mvn --version" to verify that it is correctly installed.
|
|
59
|
-
|
|
60
|
-
For complete documentation, see http://maven.apache.org/download.html#Installation
|
|
61
|
-
|
|
62
|
-
Licensing
|
|
63
|
-
---------
|
|
64
|
-
|
|
65
|
-
Please see the file called LICENSE.TXT
|
|
66
|
-
|
|
67
|
-
Maven URLS
|
|
68
|
-
----------
|
|
69
|
-
|
|
70
|
-
Home Page: http://maven.apache.org/
|
|
71
|
-
Downloads: http://maven.apache.org/download.html
|
|
72
|
-
Release Notes: http://maven.apache.org/release-notes.html
|
|
73
|
-
Mailing Lists: http://maven.apache.org/mail-lists.html
|
|
74
|
-
Source Code: http://svn.apache.org/repos/asf/maven/
|
|
75
|
-
Issue Tracking: http://jira.codehaus.org/browse/MNG
|
|
76
|
-
Wiki: http://docs.codehaus.org/display/MAVENUSER/
|
|
77
|
-
Available Plugins: http://maven.apache.org/plugins/index.html
|
|
1
|
+
|
|
2
|
+
Apache Maven
|
|
3
|
+
|
|
4
|
+
What is it?
|
|
5
|
+
-----------
|
|
6
|
+
|
|
7
|
+
Maven is a software project management and comprehension tool. Based on
|
|
8
|
+
the concept of a Project Object Model (POM), Maven can manage a project's
|
|
9
|
+
build, reporting and documentation from a central piece of information.
|
|
10
|
+
|
|
11
|
+
Documentation
|
|
12
|
+
-------------
|
|
13
|
+
|
|
14
|
+
The most up-to-date documentation can be found at http://maven.apache.org/.
|
|
15
|
+
|
|
16
|
+
Release Notes
|
|
17
|
+
-------------
|
|
18
|
+
|
|
19
|
+
The full list of changes can be found at http://maven.apache.org/release-notes.html.
|
|
20
|
+
|
|
21
|
+
System Requirements
|
|
22
|
+
-------------------
|
|
23
|
+
|
|
24
|
+
JDK:
|
|
25
|
+
1.5 or above (this is to execute Maven - it still allows you to build against 1.3
|
|
26
|
+
and prior JDK's).
|
|
27
|
+
Memory:
|
|
28
|
+
No minimum requirement.
|
|
29
|
+
Disk:
|
|
30
|
+
No minimum requirement. Approximately 100MB will be used for your local repository,
|
|
31
|
+
however this will vary depending on usage and can be removed and redownloaded at
|
|
32
|
+
any time.
|
|
33
|
+
Operating System:
|
|
34
|
+
No minimum requirement. On Windows, Windows NT and above or Cygwin is required for
|
|
35
|
+
the startup scripts. Tested on Windows XP, Fedora Core and Mac OS X.
|
|
36
|
+
|
|
37
|
+
Installing Maven
|
|
38
|
+
----------------
|
|
39
|
+
|
|
40
|
+
1) Unpack the archive where you would like to store the binaries, eg:
|
|
41
|
+
|
|
42
|
+
Unix-based Operating Systems (Linux, Solaris and Mac OS X)
|
|
43
|
+
tar zxvf apache-maven-3.0.x.tar.gz
|
|
44
|
+
Windows 2000/XP
|
|
45
|
+
unzip apache-maven-3.0.x.zip
|
|
46
|
+
|
|
47
|
+
2) A directory called "apache-maven-3.0.x" will be created.
|
|
48
|
+
|
|
49
|
+
3) Add the bin directory to your PATH, eg:
|
|
50
|
+
|
|
51
|
+
Unix-based Operating Systems (Linux, Solaris and Mac OS X)
|
|
52
|
+
export PATH=/usr/local/apache-maven-3.0.x/bin:$PATH
|
|
53
|
+
Windows 2000/XP
|
|
54
|
+
set PATH="c:\program files\apache-maven-3.0.x\bin";%PATH%
|
|
55
|
+
|
|
56
|
+
4) Make sure JAVA_HOME is set to the location of your JDK
|
|
57
|
+
|
|
58
|
+
5) Run "mvn --version" to verify that it is correctly installed.
|
|
59
|
+
|
|
60
|
+
For complete documentation, see http://maven.apache.org/download.html#Installation
|
|
61
|
+
|
|
62
|
+
Licensing
|
|
63
|
+
---------
|
|
64
|
+
|
|
65
|
+
Please see the file called LICENSE.TXT
|
|
66
|
+
|
|
67
|
+
Maven URLS
|
|
68
|
+
----------
|
|
69
|
+
|
|
70
|
+
Home Page: http://maven.apache.org/
|
|
71
|
+
Downloads: http://maven.apache.org/download.html
|
|
72
|
+
Release Notes: http://maven.apache.org/release-notes.html
|
|
73
|
+
Mailing Lists: http://maven.apache.org/mail-lists.html
|
|
74
|
+
Source Code: http://svn.apache.org/repos/asf/maven/
|
|
75
|
+
Issue Tracking: http://jira.codehaus.org/browse/MNG
|
|
76
|
+
Wiki: http://docs.codehaus.org/display/MAVENUSER/
|
|
77
|
+
Available Plugins: http://maven.apache.org/plugins/index.html
|
data/bin/m2.conf
CHANGED
data/bin/rmvn
CHANGED
data/conf/settings.xml
CHANGED
|
@@ -1,257 +1,257 @@
|
|
|
1
|
-
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
-
|
|
3
|
-
<!--
|
|
4
|
-
Licensed to the Apache Software Foundation (ASF) under one
|
|
5
|
-
or more contributor license agreements. See the NOTICE file
|
|
6
|
-
distributed with this work for additional information
|
|
7
|
-
regarding copyright ownership. The ASF licenses this file
|
|
8
|
-
to you under the Apache License, Version 2.0 (the
|
|
9
|
-
"License"); you may not use this file except in compliance
|
|
10
|
-
with the License. You may obtain a copy of the License at
|
|
11
|
-
|
|
12
|
-
http://www.apache.org/licenses/LICENSE-2.0
|
|
13
|
-
|
|
14
|
-
Unless required by applicable law or agreed to in writing,
|
|
15
|
-
software distributed under the License is distributed on an
|
|
16
|
-
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
17
|
-
KIND, either express or implied. See the License for the
|
|
18
|
-
specific language governing permissions and limitations
|
|
19
|
-
under the License.
|
|
20
|
-
-->
|
|
21
|
-
|
|
22
|
-
<!--
|
|
23
|
-
| This is the configuration file for Maven. It can be specified at two levels:
|
|
24
|
-
|
|
|
25
|
-
| 1. User Level. This settings.xml file provides configuration for a single user,
|
|
26
|
-
| and is normally provided in ${user.home}/.m2/settings.xml.
|
|
27
|
-
|
|
|
28
|
-
| NOTE: This location can be overridden with the CLI option:
|
|
29
|
-
|
|
|
30
|
-
| -s /path/to/user/settings.xml
|
|
31
|
-
|
|
|
32
|
-
| 2. Global Level. This settings.xml file provides configuration for all Maven
|
|
33
|
-
| users on a machine (assuming they're all using the same Maven
|
|
34
|
-
| installation). It's normally provided in
|
|
35
|
-
| ${maven.home}/conf/settings.xml.
|
|
36
|
-
|
|
|
37
|
-
| NOTE: This location can be overridden with the CLI option:
|
|
38
|
-
|
|
|
39
|
-
| -gs /path/to/global/settings.xml
|
|
40
|
-
|
|
|
41
|
-
| The sections in this sample file are intended to give you a running start at
|
|
42
|
-
| getting the most out of your Maven installation. Where appropriate, the default
|
|
43
|
-
| values (values used when the setting is not specified) are provided.
|
|
44
|
-
|
|
|
45
|
-
|-->
|
|
46
|
-
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
|
|
47
|
-
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
48
|
-
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
|
|
49
|
-
<!-- localRepository
|
|
50
|
-
| The path to the local repository maven will use to store artifacts.
|
|
51
|
-
|
|
|
52
|
-
| Default: ~/.m2/repository
|
|
53
|
-
<localRepository>/path/to/local/repo</localRepository>
|
|
54
|
-
-->
|
|
55
|
-
|
|
56
|
-
<!-- interactiveMode
|
|
57
|
-
| This will determine whether maven prompts you when it needs input. If set to false,
|
|
58
|
-
| maven will use a sensible default value, perhaps based on some other setting, for
|
|
59
|
-
| the parameter in question.
|
|
60
|
-
|
|
|
61
|
-
| Default: true
|
|
62
|
-
<interactiveMode>true</interactiveMode>
|
|
63
|
-
-->
|
|
64
|
-
|
|
65
|
-
<!-- offline
|
|
66
|
-
| Determines whether maven should attempt to connect to the network when executing a build.
|
|
67
|
-
| This will have an effect on artifact downloads, artifact deployment, and others.
|
|
68
|
-
|
|
|
69
|
-
| Default: false
|
|
70
|
-
<offline>false</offline>
|
|
71
|
-
-->
|
|
72
|
-
|
|
73
|
-
<!-- pluginGroups
|
|
74
|
-
| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
|
|
75
|
-
| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
|
|
76
|
-
| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
|
|
77
|
-
|-->
|
|
78
|
-
<pluginGroups>
|
|
79
|
-
<!-- pluginGroup
|
|
80
|
-
| Specifies a further group identifier to use for plugin lookup.
|
|
81
|
-
<pluginGroup>com.your.plugins</pluginGroup>
|
|
82
|
-
-->
|
|
83
|
-
</pluginGroups>
|
|
84
|
-
|
|
85
|
-
<!-- proxies
|
|
86
|
-
| This is a list of proxies which can be used on this machine to connect to the network.
|
|
87
|
-
| Unless otherwise specified (by system property or command-line switch), the first proxy
|
|
88
|
-
| specification in this list marked as active will be used.
|
|
89
|
-
|-->
|
|
90
|
-
<proxies>
|
|
91
|
-
<!-- proxy
|
|
92
|
-
| Specification for one proxy, to be used in connecting to the network.
|
|
93
|
-
|
|
|
94
|
-
<proxy>
|
|
95
|
-
<id>optional</id>
|
|
96
|
-
<active>true</active>
|
|
97
|
-
<protocol>http</protocol>
|
|
98
|
-
<username>proxyuser</username>
|
|
99
|
-
<password>proxypass</password>
|
|
100
|
-
<host>proxy.host.net</host>
|
|
101
|
-
<port>80</port>
|
|
102
|
-
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
|
|
103
|
-
</proxy>
|
|
104
|
-
-->
|
|
105
|
-
</proxies>
|
|
106
|
-
|
|
107
|
-
<!-- servers
|
|
108
|
-
| This is a list of authentication profiles, keyed by the server-id used within the system.
|
|
109
|
-
| Authentication profiles can be used whenever maven must make a connection to a remote server.
|
|
110
|
-
|-->
|
|
111
|
-
<servers>
|
|
112
|
-
<!-- server
|
|
113
|
-
| Specifies the authentication information to use when connecting to a particular server, identified by
|
|
114
|
-
| a unique name within the system (referred to by the 'id' attribute below).
|
|
115
|
-
|
|
|
116
|
-
| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
|
|
117
|
-
| used together.
|
|
118
|
-
|
|
|
119
|
-
<server>
|
|
120
|
-
<id>deploymentRepo</id>
|
|
121
|
-
<username>repouser</username>
|
|
122
|
-
<password>repopwd</password>
|
|
123
|
-
</server>
|
|
124
|
-
-->
|
|
125
|
-
|
|
126
|
-
<!-- Another sample, using keys to authenticate.
|
|
127
|
-
<server>
|
|
128
|
-
<id>siteServer</id>
|
|
129
|
-
<privateKey>/path/to/private/key</privateKey>
|
|
130
|
-
<passphrase>optional; leave empty if not used.</passphrase>
|
|
131
|
-
</server>
|
|
132
|
-
-->
|
|
133
|
-
</servers>
|
|
134
|
-
|
|
135
|
-
<!-- mirrors
|
|
136
|
-
| This is a list of mirrors to be used in downloading artifacts from remote repositories.
|
|
137
|
-
|
|
|
138
|
-
| It works like this: a POM may declare a repository to use in resolving certain artifacts.
|
|
139
|
-
| However, this repository may have problems with heavy traffic at times, so people have mirrored
|
|
140
|
-
| it to several places.
|
|
141
|
-
|
|
|
142
|
-
| That repository definition will have a unique id, so we can create a mirror reference for that
|
|
143
|
-
| repository, to be used as an alternate download site. The mirror site will be the preferred
|
|
144
|
-
| server for that repository.
|
|
145
|
-
|-->
|
|
146
|
-
<mirrors>
|
|
147
|
-
<!-- mirror
|
|
148
|
-
| Specifies a repository mirror site to use instead of a given repository. The repository that
|
|
149
|
-
| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
|
|
150
|
-
| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
|
151
|
-
|
|
|
152
|
-
<mirror>
|
|
153
|
-
<id>mirrorId</id>
|
|
154
|
-
<mirrorOf>repositoryId</mirrorOf>
|
|
155
|
-
<name>Human Readable Name for this Mirror.</name>
|
|
156
|
-
<url>http://my.repository.com/repo/path</url>
|
|
157
|
-
</mirror>
|
|
158
|
-
-->
|
|
159
|
-
</mirrors>
|
|
160
|
-
|
|
161
|
-
<!-- profiles
|
|
162
|
-
| This is a list of profiles which can be activated in a variety of ways, and which can modify
|
|
163
|
-
| the build process. Profiles provided in the settings.xml are intended to provide local machine-
|
|
164
|
-
| specific paths and repository locations which allow the build to work in the local environment.
|
|
165
|
-
|
|
|
166
|
-
| For example, if you have an integration testing plugin - like cactus - that needs to know where
|
|
167
|
-
| your Tomcat instance is installed, you can provide a variable here such that the variable is
|
|
168
|
-
| dereferenced during the build process to configure the cactus plugin.
|
|
169
|
-
|
|
|
170
|
-
| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
|
|
171
|
-
| section of this document (settings.xml) - will be discussed later. Another way essentially
|
|
172
|
-
| relies on the detection of a system property, either matching a particular value for the property,
|
|
173
|
-
| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
|
|
174
|
-
| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
|
|
175
|
-
| Finally, the list of active profiles can be specified directly from the command line.
|
|
176
|
-
|
|
|
177
|
-
| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
|
|
178
|
-
| repositories, plugin repositories, and free-form properties to be used as configuration
|
|
179
|
-
| variables for plugins in the POM.
|
|
180
|
-
|
|
|
181
|
-
|-->
|
|
182
|
-
<profiles>
|
|
183
|
-
<!-- profile
|
|
184
|
-
| Specifies a set of introductions to the build process, to be activated using one or more of the
|
|
185
|
-
| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
|
|
186
|
-
| or the command line, profiles have to have an ID that is unique.
|
|
187
|
-
|
|
|
188
|
-
| An encouraged best practice for profile identification is to use a consistent naming convention
|
|
189
|
-
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
|
|
190
|
-
| This will make it more intuitive to understand what the set of introduced profiles is attempting
|
|
191
|
-
| to accomplish, particularly when you only have a list of profile id's for debug.
|
|
192
|
-
|
|
|
193
|
-
| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
|
|
194
|
-
<profile>
|
|
195
|
-
<id>jdk-1.4</id>
|
|
196
|
-
|
|
197
|
-
<activation>
|
|
198
|
-
<jdk>1.4</jdk>
|
|
199
|
-
</activation>
|
|
200
|
-
|
|
201
|
-
<repositories>
|
|
202
|
-
<repository>
|
|
203
|
-
<id>jdk14</id>
|
|
204
|
-
<name>Repository for JDK 1.4 builds</name>
|
|
205
|
-
<url>http://www.myhost.com/maven/jdk14</url>
|
|
206
|
-
<layout>default</layout>
|
|
207
|
-
<snapshotPolicy>always</snapshotPolicy>
|
|
208
|
-
</repository>
|
|
209
|
-
</repositories>
|
|
210
|
-
</profile>
|
|
211
|
-
-->
|
|
212
|
-
|
|
213
|
-
<!--
|
|
214
|
-
| Here is another profile, activated by the system property 'target-env' with a value of 'dev',
|
|
215
|
-
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration
|
|
216
|
-
| might hypothetically look like:
|
|
217
|
-
|
|
|
218
|
-
| ...
|
|
219
|
-
| <plugin>
|
|
220
|
-
| <groupId>org.myco.myplugins</groupId>
|
|
221
|
-
| <artifactId>myplugin</artifactId>
|
|
222
|
-
|
|
|
223
|
-
| <configuration>
|
|
224
|
-
| <tomcatLocation>${tomcatPath}</tomcatLocation>
|
|
225
|
-
| </configuration>
|
|
226
|
-
| </plugin>
|
|
227
|
-
| ...
|
|
228
|
-
|
|
|
229
|
-
| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
|
|
230
|
-
| anything, you could just leave off the <value/> inside the activation-property.
|
|
231
|
-
|
|
|
232
|
-
<profile>
|
|
233
|
-
<id>env-dev</id>
|
|
234
|
-
|
|
235
|
-
<activation>
|
|
236
|
-
<property>
|
|
237
|
-
<name>target-env</name>
|
|
238
|
-
<value>dev</value>
|
|
239
|
-
</property>
|
|
240
|
-
</activation>
|
|
241
|
-
|
|
242
|
-
<properties>
|
|
243
|
-
<tomcatPath>/path/to/tomcat/instance</tomcatPath>
|
|
244
|
-
</properties>
|
|
245
|
-
</profile>
|
|
246
|
-
-->
|
|
247
|
-
</profiles>
|
|
248
|
-
|
|
249
|
-
<!-- activeProfiles
|
|
250
|
-
| List of profiles that are active for all builds.
|
|
251
|
-
|
|
|
252
|
-
<activeProfiles>
|
|
253
|
-
<activeProfile>alwaysActiveProfile</activeProfile>
|
|
254
|
-
<activeProfile>anotherAlwaysActiveProfile</activeProfile>
|
|
255
|
-
</activeProfiles>
|
|
256
|
-
-->
|
|
257
|
-
</settings>
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
+
|
|
3
|
+
<!--
|
|
4
|
+
Licensed to the Apache Software Foundation (ASF) under one
|
|
5
|
+
or more contributor license agreements. See the NOTICE file
|
|
6
|
+
distributed with this work for additional information
|
|
7
|
+
regarding copyright ownership. The ASF licenses this file
|
|
8
|
+
to you under the Apache License, Version 2.0 (the
|
|
9
|
+
"License"); you may not use this file except in compliance
|
|
10
|
+
with the License. You may obtain a copy of the License at
|
|
11
|
+
|
|
12
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
13
|
+
|
|
14
|
+
Unless required by applicable law or agreed to in writing,
|
|
15
|
+
software distributed under the License is distributed on an
|
|
16
|
+
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
17
|
+
KIND, either express or implied. See the License for the
|
|
18
|
+
specific language governing permissions and limitations
|
|
19
|
+
under the License.
|
|
20
|
+
-->
|
|
21
|
+
|
|
22
|
+
<!--
|
|
23
|
+
| This is the configuration file for Maven. It can be specified at two levels:
|
|
24
|
+
|
|
|
25
|
+
| 1. User Level. This settings.xml file provides configuration for a single user,
|
|
26
|
+
| and is normally provided in ${user.home}/.m2/settings.xml.
|
|
27
|
+
|
|
|
28
|
+
| NOTE: This location can be overridden with the CLI option:
|
|
29
|
+
|
|
|
30
|
+
| -s /path/to/user/settings.xml
|
|
31
|
+
|
|
|
32
|
+
| 2. Global Level. This settings.xml file provides configuration for all Maven
|
|
33
|
+
| users on a machine (assuming they're all using the same Maven
|
|
34
|
+
| installation). It's normally provided in
|
|
35
|
+
| ${maven.home}/conf/settings.xml.
|
|
36
|
+
|
|
|
37
|
+
| NOTE: This location can be overridden with the CLI option:
|
|
38
|
+
|
|
|
39
|
+
| -gs /path/to/global/settings.xml
|
|
40
|
+
|
|
|
41
|
+
| The sections in this sample file are intended to give you a running start at
|
|
42
|
+
| getting the most out of your Maven installation. Where appropriate, the default
|
|
43
|
+
| values (values used when the setting is not specified) are provided.
|
|
44
|
+
|
|
|
45
|
+
|-->
|
|
46
|
+
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
|
|
47
|
+
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
48
|
+
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
|
|
49
|
+
<!-- localRepository
|
|
50
|
+
| The path to the local repository maven will use to store artifacts.
|
|
51
|
+
|
|
|
52
|
+
| Default: ~/.m2/repository
|
|
53
|
+
<localRepository>/path/to/local/repo</localRepository>
|
|
54
|
+
-->
|
|
55
|
+
|
|
56
|
+
<!-- interactiveMode
|
|
57
|
+
| This will determine whether maven prompts you when it needs input. If set to false,
|
|
58
|
+
| maven will use a sensible default value, perhaps based on some other setting, for
|
|
59
|
+
| the parameter in question.
|
|
60
|
+
|
|
|
61
|
+
| Default: true
|
|
62
|
+
<interactiveMode>true</interactiveMode>
|
|
63
|
+
-->
|
|
64
|
+
|
|
65
|
+
<!-- offline
|
|
66
|
+
| Determines whether maven should attempt to connect to the network when executing a build.
|
|
67
|
+
| This will have an effect on artifact downloads, artifact deployment, and others.
|
|
68
|
+
|
|
|
69
|
+
| Default: false
|
|
70
|
+
<offline>false</offline>
|
|
71
|
+
-->
|
|
72
|
+
|
|
73
|
+
<!-- pluginGroups
|
|
74
|
+
| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
|
|
75
|
+
| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
|
|
76
|
+
| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
|
|
77
|
+
|-->
|
|
78
|
+
<pluginGroups>
|
|
79
|
+
<!-- pluginGroup
|
|
80
|
+
| Specifies a further group identifier to use for plugin lookup.
|
|
81
|
+
<pluginGroup>com.your.plugins</pluginGroup>
|
|
82
|
+
-->
|
|
83
|
+
</pluginGroups>
|
|
84
|
+
|
|
85
|
+
<!-- proxies
|
|
86
|
+
| This is a list of proxies which can be used on this machine to connect to the network.
|
|
87
|
+
| Unless otherwise specified (by system property or command-line switch), the first proxy
|
|
88
|
+
| specification in this list marked as active will be used.
|
|
89
|
+
|-->
|
|
90
|
+
<proxies>
|
|
91
|
+
<!-- proxy
|
|
92
|
+
| Specification for one proxy, to be used in connecting to the network.
|
|
93
|
+
|
|
|
94
|
+
<proxy>
|
|
95
|
+
<id>optional</id>
|
|
96
|
+
<active>true</active>
|
|
97
|
+
<protocol>http</protocol>
|
|
98
|
+
<username>proxyuser</username>
|
|
99
|
+
<password>proxypass</password>
|
|
100
|
+
<host>proxy.host.net</host>
|
|
101
|
+
<port>80</port>
|
|
102
|
+
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
|
|
103
|
+
</proxy>
|
|
104
|
+
-->
|
|
105
|
+
</proxies>
|
|
106
|
+
|
|
107
|
+
<!-- servers
|
|
108
|
+
| This is a list of authentication profiles, keyed by the server-id used within the system.
|
|
109
|
+
| Authentication profiles can be used whenever maven must make a connection to a remote server.
|
|
110
|
+
|-->
|
|
111
|
+
<servers>
|
|
112
|
+
<!-- server
|
|
113
|
+
| Specifies the authentication information to use when connecting to a particular server, identified by
|
|
114
|
+
| a unique name within the system (referred to by the 'id' attribute below).
|
|
115
|
+
|
|
|
116
|
+
| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
|
|
117
|
+
| used together.
|
|
118
|
+
|
|
|
119
|
+
<server>
|
|
120
|
+
<id>deploymentRepo</id>
|
|
121
|
+
<username>repouser</username>
|
|
122
|
+
<password>repopwd</password>
|
|
123
|
+
</server>
|
|
124
|
+
-->
|
|
125
|
+
|
|
126
|
+
<!-- Another sample, using keys to authenticate.
|
|
127
|
+
<server>
|
|
128
|
+
<id>siteServer</id>
|
|
129
|
+
<privateKey>/path/to/private/key</privateKey>
|
|
130
|
+
<passphrase>optional; leave empty if not used.</passphrase>
|
|
131
|
+
</server>
|
|
132
|
+
-->
|
|
133
|
+
</servers>
|
|
134
|
+
|
|
135
|
+
<!-- mirrors
|
|
136
|
+
| This is a list of mirrors to be used in downloading artifacts from remote repositories.
|
|
137
|
+
|
|
|
138
|
+
| It works like this: a POM may declare a repository to use in resolving certain artifacts.
|
|
139
|
+
| However, this repository may have problems with heavy traffic at times, so people have mirrored
|
|
140
|
+
| it to several places.
|
|
141
|
+
|
|
|
142
|
+
| That repository definition will have a unique id, so we can create a mirror reference for that
|
|
143
|
+
| repository, to be used as an alternate download site. The mirror site will be the preferred
|
|
144
|
+
| server for that repository.
|
|
145
|
+
|-->
|
|
146
|
+
<mirrors>
|
|
147
|
+
<!-- mirror
|
|
148
|
+
| Specifies a repository mirror site to use instead of a given repository. The repository that
|
|
149
|
+
| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
|
|
150
|
+
| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
|
151
|
+
|
|
|
152
|
+
<mirror>
|
|
153
|
+
<id>mirrorId</id>
|
|
154
|
+
<mirrorOf>repositoryId</mirrorOf>
|
|
155
|
+
<name>Human Readable Name for this Mirror.</name>
|
|
156
|
+
<url>http://my.repository.com/repo/path</url>
|
|
157
|
+
</mirror>
|
|
158
|
+
-->
|
|
159
|
+
</mirrors>
|
|
160
|
+
|
|
161
|
+
<!-- profiles
|
|
162
|
+
| This is a list of profiles which can be activated in a variety of ways, and which can modify
|
|
163
|
+
| the build process. Profiles provided in the settings.xml are intended to provide local machine-
|
|
164
|
+
| specific paths and repository locations which allow the build to work in the local environment.
|
|
165
|
+
|
|
|
166
|
+
| For example, if you have an integration testing plugin - like cactus - that needs to know where
|
|
167
|
+
| your Tomcat instance is installed, you can provide a variable here such that the variable is
|
|
168
|
+
| dereferenced during the build process to configure the cactus plugin.
|
|
169
|
+
|
|
|
170
|
+
| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
|
|
171
|
+
| section of this document (settings.xml) - will be discussed later. Another way essentially
|
|
172
|
+
| relies on the detection of a system property, either matching a particular value for the property,
|
|
173
|
+
| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
|
|
174
|
+
| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
|
|
175
|
+
| Finally, the list of active profiles can be specified directly from the command line.
|
|
176
|
+
|
|
|
177
|
+
| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
|
|
178
|
+
| repositories, plugin repositories, and free-form properties to be used as configuration
|
|
179
|
+
| variables for plugins in the POM.
|
|
180
|
+
|
|
|
181
|
+
|-->
|
|
182
|
+
<profiles>
|
|
183
|
+
<!-- profile
|
|
184
|
+
| Specifies a set of introductions to the build process, to be activated using one or more of the
|
|
185
|
+
| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
|
|
186
|
+
| or the command line, profiles have to have an ID that is unique.
|
|
187
|
+
|
|
|
188
|
+
| An encouraged best practice for profile identification is to use a consistent naming convention
|
|
189
|
+
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
|
|
190
|
+
| This will make it more intuitive to understand what the set of introduced profiles is attempting
|
|
191
|
+
| to accomplish, particularly when you only have a list of profile id's for debug.
|
|
192
|
+
|
|
|
193
|
+
| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
|
|
194
|
+
<profile>
|
|
195
|
+
<id>jdk-1.4</id>
|
|
196
|
+
|
|
197
|
+
<activation>
|
|
198
|
+
<jdk>1.4</jdk>
|
|
199
|
+
</activation>
|
|
200
|
+
|
|
201
|
+
<repositories>
|
|
202
|
+
<repository>
|
|
203
|
+
<id>jdk14</id>
|
|
204
|
+
<name>Repository for JDK 1.4 builds</name>
|
|
205
|
+
<url>http://www.myhost.com/maven/jdk14</url>
|
|
206
|
+
<layout>default</layout>
|
|
207
|
+
<snapshotPolicy>always</snapshotPolicy>
|
|
208
|
+
</repository>
|
|
209
|
+
</repositories>
|
|
210
|
+
</profile>
|
|
211
|
+
-->
|
|
212
|
+
|
|
213
|
+
<!--
|
|
214
|
+
| Here is another profile, activated by the system property 'target-env' with a value of 'dev',
|
|
215
|
+
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration
|
|
216
|
+
| might hypothetically look like:
|
|
217
|
+
|
|
|
218
|
+
| ...
|
|
219
|
+
| <plugin>
|
|
220
|
+
| <groupId>org.myco.myplugins</groupId>
|
|
221
|
+
| <artifactId>myplugin</artifactId>
|
|
222
|
+
|
|
|
223
|
+
| <configuration>
|
|
224
|
+
| <tomcatLocation>${tomcatPath}</tomcatLocation>
|
|
225
|
+
| </configuration>
|
|
226
|
+
| </plugin>
|
|
227
|
+
| ...
|
|
228
|
+
|
|
|
229
|
+
| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
|
|
230
|
+
| anything, you could just leave off the <value/> inside the activation-property.
|
|
231
|
+
|
|
|
232
|
+
<profile>
|
|
233
|
+
<id>env-dev</id>
|
|
234
|
+
|
|
235
|
+
<activation>
|
|
236
|
+
<property>
|
|
237
|
+
<name>target-env</name>
|
|
238
|
+
<value>dev</value>
|
|
239
|
+
</property>
|
|
240
|
+
</activation>
|
|
241
|
+
|
|
242
|
+
<properties>
|
|
243
|
+
<tomcatPath>/path/to/tomcat/instance</tomcatPath>
|
|
244
|
+
</properties>
|
|
245
|
+
</profile>
|
|
246
|
+
-->
|
|
247
|
+
</profiles>
|
|
248
|
+
|
|
249
|
+
<!-- activeProfiles
|
|
250
|
+
| List of profiles that are active for all builds.
|
|
251
|
+
|
|
|
252
|
+
<activeProfiles>
|
|
253
|
+
<activeProfile>alwaysActiveProfile</activeProfile>
|
|
254
|
+
<activeProfile>anotherAlwaysActiveProfile</activeProfile>
|
|
255
|
+
</activeProfiles>
|
|
256
|
+
-->
|
|
257
|
+
</settings>
|