OpenSearch

Commit Graph

Author	SHA1	Message	Date
Simon Willnauer	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
David Pilato	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
Colin Goodheart-Smithe	772d0cc6e7	Build: Make rest-spec-api a project so eclipse build works The change makes rest-spec-api a project in the same way as we build dev-tools. it packages the tests and api in a bundle using the maven-remote-resources-plugin and uses the same plugin in the plugins and core pom to unpack the rest-api-spec into the target directory and references the rest tests there in the test resources. The main stimulus for this change is that for those using Eclipse the current build does not work. After running `mvn eclipse:eclipse` the Eclipse IDE errors because the rest-api-spec is outside of the project scope, meaning that every time the command is run (required whenever any dependencies change), the class path of all the projects has to be manually fixed.	2015-06-22 11:41:44 +01:00

Author

SHA1

Message

Date

Simon Willnauer

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

David Pilato

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

Colin Goodheart-Smithe

772d0cc6e7

Build: Make rest-spec-api a project so eclipse build works

The change makes rest-spec-api a project in the same way as we build dev-tools. it packages the tests and api in a bundle using the maven-remote-resources-plugin and uses the same plugin in the plugins and core pom to unpack the rest-api-spec into the target directory and references the rest tests there in the test resources.

The main stimulus for this change is that for those using Eclipse the current build does not work. After running `mvn eclipse:eclipse` the Eclipse IDE errors because the rest-api-spec is outside of the project scope, meaning that every time the command is run (required whenever any dependencies change), the class path of all the projects has to be manually fixed.

2015-06-22 11:41:44 +01:00

3 Commits