0014728a0d
[maven] rename maven names for parent, dev-tools and rest spec
...
Follow up for previous commit:
```
[INFO] Build Tools and Resources .......................... SUCCESS [ 0.158 s]
[INFO] Rest API Specification ............................. SUCCESS [ 0.002 s]
[INFO] Elasticsearch Parent POM ........................... SUCCESS [ 0.122 s]
```
2015-08-18 13:38:49 +02:00
d1c93fb573
Release: Remove aws-maven plugin/improve release docs
...
In order to have consistent deploys across several repositories,
we should deploy to sonatype first, then mirror those contents,
and then upload to s3.
This means, the aws wagon is not needed anymore.
2015-08-17 15:39:22 +02:00
b447e2ae99
Move master to [2.1.0-SNAPSHOT]
2015-08-14 23:44:06 +02:00
e869c87119
Build: Adding aws-maven extension to dev-tools and rest-api-spec
2015-08-14 17:30:00 +02:00
c1405d26b5
fixtypo
2015-08-14 15:27:23 +02:00
dd1b0d84a6
Also deploy top level artifacts to S3
...
This commit adds the S3 wagon release profile also to dev-tools
and rest-api-spec and makes the actual repository path / bucket
configurable.
2015-08-14 15:21:06 +02:00
605253a39f
Cut over master to 2.0.0-SNAPSHOT
2015-08-12 21:16:08 +02:00
6abc69c488
Packaging: Makes sure all POMs contain a description
...
Adds an explicit description the RPM package so it doesn't inherit the description from the POM.
Closes #12550
Also, modified descriptions for deb and rpm packages to be the same and to reference the documentation rather than listing features that are out of date.
2015-08-10 15:21:24 +01:00
6f9a067197
Change master branch back to 2.0-beta1
2015-08-04 15:38:21 -04:00
6753f7f03e
Cut over master to 2.0.0-SNAPSHOT
2015-08-04 10:54:12 +02:00
b40186652c
updated the elasticsearch versioning format
...
Moving to from `X.Y.Z.beta1`/`X.Y.Z.RC1` to `X.Y.Z-beta1`/`X.Y.Z-rc1`
2015-07-13 20:26:37 +02:00
e0708813a9
Make 2.0.0.beta1-SNAPSHOT the current version.
...
Today everything is tight to having the next version as the latest.
In order to work towards 2.0.0.beta1 we need to fix all the usage of
2.0.0-SNAPSHOT to reflect the version we will release soon.
Usually we do this on the release branch but to simplify things I wanna
keep this on master for now and move to 2.1.0-SNAPSHOT on master once
we created a 2.0 branch.
Closes #12148
2015-07-09 21:24:32 +02:00
e7a6b51bab
[maven] change groupId / artifactId
...
When we generate our project, we can get something like:
```
├── dev-tools
├── elasticsearch
├── elasticsearch-parent
├── elasticsearch-plugin
├── plugin
│ ├── elasticsearch-analysis-icu
│ ├── elasticsearch-analysis-kuromoji
│ ├── elasticsearch-analysis-phonetic
│ ├── elasticsearch-analysis-smartcn
│ ├── elasticsearch-analysis-stempel
│ ├── elasticsearch-cloud-aws
│ ├── elasticsearch-cloud-azure
│ ├── elasticsearch-cloud-gce
│ ├── elasticsearch-delete-by-query
│ ├── elasticsearch-lang-javascript
│ └── elasticsearch-lang-python
├── rest-api-spec
└── securemock
```
I propose here to use a common naming for artifacts: start always with `elasticsearch-`.
Also, move `elasticsearch-plugin` to `org.elasticsearch.plugin` groupId.
So we could have:
```
├── elasticsearch
├── elasticsearch-dev-tools
├── elasticsearch-parent
├── elasticsearch-rest-api-spec
├── elasticsearch-securemock
├── plugin
│ ├── elasticsearch-analysis-icu
│ ├── elasticsearch-analysis-kuromoji
│ ├── elasticsearch-analysis-phonetic
│ ├── elasticsearch-analysis-smartcn
│ ├── elasticsearch-analysis-stempel
│ ├── elasticsearch-cloud-aws
│ ├── elasticsearch-cloud-azure
│ ├── elasticsearch-cloud-gce
│ ├── elasticsearch-delete-by-query
│ ├── elasticsearch-lang-javascript
│ ├── elasticsearch-lang-python
│ └── elasticsearch-plugin
```
2015-07-06 17:17:07 +02:00
05db5dc2c8
create parent pom project from its original location
2015-06-05 13:12:05 +02:00
David Pilato
Alexander Reelsen
Simon Willnauer
Colin Goodheart-Smithe
Robert Muir
uboness