@@ -9,8 +9,8 @@ deploy \<repository-name>
9
9
10
10
##DESCRIPTION
11
11
12
- Deploy transmits ** target/splunk-1.9.2 .jar** , ** target/splunk-1.9.2 -javadoc.jar** , and
13
- ** target/splunk-1.9.2 -sources.jar** to the ** local** , ** staging** , or ** production**
12
+ Deploy transmits ** target/splunk-1.9.3 .jar** , ** target/splunk-1.9.3 -javadoc.jar** , and
13
+ ** target/splunk-1.9.3 -sources.jar** to the ** local** , ** staging** , or ** production**
14
14
maven repository. Repository names are mapped to locations as follows.
15
15
16
16
| repository-name | location |
@@ -21,18 +21,18 @@ maven repository. Repository names are mapped to locations as follows.
21
21
22
22
After deployment you should find this tree structure at the location of your repository
23
23
24
- com/splunk/splunk/1.9.2 /
25
- ├── splunk-1.9.2 -javadoc.jar
26
- ├── splunk-1.9.2 -javadoc.jar.md5
27
- ├── splunk-1.9.2 -javadoc.jar.sha1
28
- ├── splunk-1.9.2 -sources.jar
29
- ├── splunk-1.9.2 -sources.jar.md5
30
- ├── splunk-1.9.2 -sources.jar.sha1
31
- ├── splunk-1.9.2 .jar
32
- ├── splunk-1.9.2 .jar.md5
33
- ├── splunk-1.9.2 .jar.sha1
34
- ├── splunk-1.9.2 .pom
35
- ├── splunk-1.9.2 .pom.md5
36
- └── splunk-1.9.2 .pom.sha1
24
+ com/splunk/splunk/1.9.3 /
25
+ ├── splunk-1.9.3 -javadoc.jar
26
+ ├── splunk-1.9.3 -javadoc.jar.md5
27
+ ├── splunk-1.9.3 -javadoc.jar.sha1
28
+ ├── splunk-1.9.3 -sources.jar
29
+ ├── splunk-1.9.3 -sources.jar.md5
30
+ ├── splunk-1.9.3 -sources.jar.sha1
31
+ ├── splunk-1.9.3 .jar
32
+ ├── splunk-1.9.3 .jar.md5
33
+ ├── splunk-1.9.3 .jar.sha1
34
+ ├── splunk-1.9.3 .pom
35
+ ├── splunk-1.9.3 .pom.md5
36
+ └── splunk-1.9.3 .pom.sha1
37
37
38
38
Verify this structure prior to release.
0 commit comments