You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2026/08/22 15:33:23 UTC

(maven-doxia-site) branch master updated: Doxia Site merged into Maven Site

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-doxia-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 9fafc9c  Doxia Site merged into Maven Site
9fafc9c is described below

commit 9fafc9c3005bc08b944c0a41c55bbe1585a0da1e
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sat Aug 22 17:31:09 2026 +0200

    Doxia Site merged into Maven Site
---
 Jenkinsfile | 73 -------------------------------------------------------------
 README.md   | 60 +-------------------------------------------------
 2 files changed, 1 insertion(+), 132 deletions(-)

diff --git a/Jenkinsfile b/Jenkinsfile
deleted file mode 100644
index 20ad7db..0000000
--- a/Jenkinsfile
+++ /dev/null
@@ -1,73 +0,0 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
- pipeline {
-    agent {
-        label 'svn-websites'
-    }
-    stages {
-        stage('Checkout') {
-            steps {
-                // Clean before build
-                cleanWs()
-                // We need to explicitly checkout from SCM here
-                checkout scm
-            }
-        }
-        stage('Build only') {
-            when {
-                not { branch 'master' }
-            }
-            steps {
-                withEnv(["JAVA_HOME=${ tool "jdk_17_latest" }",
-                         "PATH+MAVEN=${ tool "jdk_17_latest" }/bin:${tool "maven_3_latest"}/bin",
-                         "MAVEN_OPTS=-Xms2g -Xmx4g -Djava.awt.headless=true"]) {
-                    sh "mvn -U -ntp clean site -Dmaven.repo.local=.repository"
-                }
-            }
-        }
-        stage('Site Deploy') {
-            when {
-                branch 'master'
-            }
-            steps {
-                withEnv(["JAVA_HOME=${ tool "jdk_17_latest" }",
-                         "PATH+MAVEN=${ tool "jdk_17_latest" }/bin:${tool "maven_3_latest"}/bin",
-                         "MAVEN_OPTS=-Xms2g -Xmx4g -Djava.awt.headless=true"]) {
-                    sh "mvn -U -ntp clean site-deploy -Dmaven.repo.local=.repository"
-                }
-            }
-        }
-    }
-    post {
-        always {
-            jenkinsNotify()
-        }
-    }
-    options {
-        buildDiscarder(logRotator(numToKeepStr:'15'))
-        timeout(time: 10, unit: 'MINUTES')
-        skipStagesAfterUnstable()
-        //timestamps()
-        disableConcurrentBuilds()
-        ansiColor('xterm')
-        // This is required if you want to clean before build
-        skipDefaultCheckout(true)
-    }
-}
diff --git a/README.md b/README.md
index e069474..c96ea94 100644
--- a/README.md
+++ b/README.md
@@ -20,62 +20,4 @@ Contributing to [Apache Maven Doxia Site](https://maven.apache.org/doxia/)
 [![Apache License, Version 2.0, January 2004](https://img.shields.io/github/license/apache/maven.svg?label=License)][license]
 [![Jenkins Status](https://img.shields.io/jenkins/s/https/ci-maven.apache.org/job/Maven/job/maven-box/job/maven-doxia-site/job/master.svg)][build]
 
-
-You have found a bug, or you have an idea for a cool new feature? Contributing
-code is a great way to give something back to the open source community. Before
-you dig right into the code, there are a few guidelines that we need
-contributors to follow so that we can have a chance of keeping on top of
-things.
-
-Getting Started
----------------
-
-+ Make sure you have a [GitHub account](https://github.com/signup/free).
-+ If you're planning to implement a new feature, it makes sense to discuss your changes 
-  on the [dev list][ml-list] first. 
-  This way you can make sure you're not wasting your time on something that isn't 
-  considered to be in Apache Maven's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
-  + Clearly describe the issue, including steps to reproduce when it is a bug.
-  + Make sure you fill in the earliest version that you know has the issue.
-+ Fork the repository on GitHub.
-
-Making and Submitting Changes
---------------
-
-We accept Pull Requests via GitHub. The [developer mailing list][ml-list] is the
-main channel of communication for contributors.  
-There are some guidelines which will make applying PRs easier for us:
-+ Create a topic branch from where you want to base your work (this is usually the master branch).
-  Push your changes to a topic branch in your fork of the repository.
-+ Make commits of logical units.
-+ Respect the original code style: by using the same [codestyle][code-style],
-  patches should only highlight the actual difference, not being disturbed by any formatting issues:
-  + Only use spaces for indentation.
-  + Create minimal diffs - disable on save actions like reformat source code or organize imports. 
-    If you feel the source code should be reformatted, create a separate PR for this change.
-  + Check for unnecessary whitespace with `git diff --check` before committing.
-+ Make sure your commit messages are in the proper format. Your commit message should contain the key of the JIRA issue.
-+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
-+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was accidentally broken.
-+ Submit a pull request to the repository in the Apache organization.
-
-If you plan to contribute on a regular basis, please consider filing a [contributor license agreement][cla].
-
-Additional Resources
---------------------
-
-+ [Contributing patches](https://maven.apache.org/guides/development/guide-maven-development.html#Creating_and_submitting_a_patch)
-+ [Contributor License Agreement][cla]
-+ [General GitHub documentation](https://help.github.com/)
-+ [GitHub pull request documentation](https://help.github.com/send-pull-requests/)
-+ [Apache Maven X Account](https://x.com/ASFMavenProject)
-+ [Apache Maven Bluesky Account](https://bsky.app/profile/maven.apache.org)
-+ [Apache Maven Mastodon Account](https://mastodon.social/deck/@ASFMavenProject@fosstodon.org)
-
-[license]: https://www.apache.org/licenses/LICENSE-2.0
-[ml-list]: https://maven.apache.org/mailing-lists.html
-[code-style]: https://maven.apache.org/developers/conventions/code.html
-[cla]: https://www.apache.org/licenses/#clas
-[maven-wiki]: https://cwiki.apache.org/confluence/display/MAVEN/Index
-[build]: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-doxia-site/job/master/
+content moved to [Maven Site](/apache/maven-site.git)