This is an automated email from the ASF dual-hosted git repository.
rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new f26204ddf SLING-7935 - Move launchpad-testing module into the main
starter repository
f26204ddf is described below
commit f26204ddfc94d910f109e705ac9e623595d81fee
Author: Robert Munteanu <[email protected]>
AuthorDate: Wed May 11 14:49:34 2022 +0200
SLING-7935 - Move launchpad-testing module into the main starter repository
Remove references to the launchpad-testing module, now that the tests
are executed in the Sling Starter.
---
src/main/jbake/content/contributing.md | 12 +++++-------
src/main/jbake/content/documentation/development.md | 2 +-
2 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/src/main/jbake/content/contributing.md
b/src/main/jbake/content/contributing.md
index 8c87215a2..2c28abb1a 100644
--- a/src/main/jbake/content/contributing.md
+++ b/src/main/jbake/content/contributing.md
@@ -73,15 +73,13 @@ In case your changes are more far-reaching and the module
you are contributing t
[Sling Starter](https://github.com/apache/sling-org-apache-sling-starter), it
is a good idea to
also run the Sling Starter integration tests. This can be achieved by doing
the following:
-* Check out the [Sling
Starter](https://github.com/apache/sling-org-apache-sling-starter) and
- [Sling Starter Integration
Tests](https://github.com/apache/sling-org-apache-sling-launchpad-testing)
- projects. This step can be skipped if you have followed the steps to
checkout all Sling repositories
+* Check out the [Sling
Starter](https://github.com/apache/sling-org-apache-sling-starter) project.
+ This step can be skipped if you have followed the steps to checkout all
Sling repositories
as documented at [Getting and Building
Sling](/documentation/development/getting-and-building-sling.html#getting-the-sling-source)
* Use the latest version of the bundle(s) you changed in the Sling Starter.
Running `git grep ${ARTIFACT_ID}`
will indicate the potential places where you need to make changes
-* Run `mvn clean install` in the Sling Starter checkout. This runs a set of
Smoke tests and allows the
- integration tests to use the version of the starter that you just built
-* Run `mvn clean install` in the Sling Starter Integration Tests checkout
-
+* Run `mvn clean verify` in the Sling Starter checkout. This runs the full set
of integration tests that
+ we use for Sling modules.
+
Additionally, and PR you submit will eventually be built by Jenkins, with
additional validations on top
of the plain Maven build.
diff --git a/src/main/jbake/content/documentation/development.md
b/src/main/jbake/content/documentation/development.md
index ae7238c0f..8d41f88b5 100644
--- a/src/main/jbake/content/documentation/development.md
+++ b/src/main/jbake/content/documentation/development.md
@@ -61,4 +61,4 @@ Last but not least, here is some more information on how we
ourselves are workin
* [Deprecating Sling
Modules](/documentation/development/deprecating-sling-modules.html)
* [Maven Usage](/documentation/development/maven-usage.html)
* [Build Setup](/project-information.html#continuous-integration)
-* To run our integration tests suite see the [launchpad/testing module
README](https://github.com/apache/sling-org-apache-sling-launchpad-testing/blob/master/README.md)
and the [launchpad/integration-tests
README](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/README.md)
for how to run individual integration tests. We use the
[sling-IT](https://issues.apache.org/jira/issues/?jql=labels%20%3D%20sling-IT)
label in JIRA for known issues with our int [...]
+* To run our integration tests suite see the [Sling Starter module
README](https://github.com/apache/sling-org-apache-sling-starter/blob/master/README.md)
and the [launchpad/integration-tests
README](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/master/README.md)
for how to run individual integration tests. We use the
[sling-IT](https://issues.apache.org/jira/issues/?jql=labels%20%3D%20sling-IT)
label in JIRA for known issues with our integration tests.
