implement a random graph generator : layer by layer method

.editorconfig

@@ -0,0 +1,10 @@
+root = true
+
+[*]
+charset = utf-8
+ident_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.md]
+trim_trailing_whitespace = false

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,19 @@
+
+```
+ * JGraphT version:
+ * Java version (java -version)/platform:  
+```
+
+**Issue**
+
+
+
+**Steps to reproduce (small coding example)**
+
+
+
+**Expected behaviour**
+
+
+
+**Other information**

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+<!-- describe the changes you have made here: what, why, …
+     Link issues by using the following pattern: [#333](https://github.com/jgrapht/jgrapht/issues/333).
+     The title of the PR must not reference an issue, because GitHub does not support autolinking there. -->
+
+----
+
+- [ ] I read and understood <https://github.com/jgrapht/jgrapht/wiki/Become-a-Contributor>
+- [ ] I read and understood <https://github.com/jgrapht/jgrapht/wiki/How-to-make-your-first-%28code%29-contribution>
+- [ ] I added [unit tests](https://github.com/jgrapht/jgrapht/wiki/Unit-testing)
+- [ ] I added [documentation](https://github.com/jgrapht/jgrapht/wiki/How-to-write-documentation)
+- [ ] I followed the [Coding and Style Conventions](https://github.com/jgrapht/jgrapht/wiki/Coding-and-Style-Conventions)
+- [ ] I **have not** modified `HISTORY.md` or `CONTRIBUTORS.md`
+- [ ] I ensured that [the git commit message is a good one](https://github.com/joelparkerhenderson/git_commit_message)

.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "maven"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/PR-workflow.yaml

@@ -0,0 +1,34 @@
+name: JGrapht Pull Request build
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+    branches:
+      - master
+
+jobs:
+  build:
+    strategy:
+      fail-fast: false
+      matrix:
+        os:
+        - name: Windows
+          tag: windows-latest
+        - name: macOS
+          tag: macos-latest
+        - name: Ubuntu
+          tag: ubuntu-latest
+    name: Build (${{ matrix.os.name }})
+    runs-on: ${{ matrix.os.tag }}
+    steps:
+      - uses: actions/checkout@v7
+      - name: Set up JDK 21
+        uses: actions/setup-java@v5
+        with:
+          java-version: 21
+          distribution: 'temurin'
+          cache: 'maven'
+      - name: Build with Maven
+        shell: bash
+        run: |
+          set -e
+          mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V && mvn verify -B && mvn javadoc:aggregate && mvn checkstyle:check -P checkstyle

.github/workflows/master-workflow.yaml

@@ -0,0 +1,83 @@
+name: JGrapht Master build
+on:
+  push:
+    branches:
+      - master
+    paths-ignore:
+      - 'CONTRIBUTORS.md'
+      - 'HISTORY.md'
+
+concurrency:
+  group: ${{ github.workflow }}
+  cancel-in-progress: true
+
+jobs:
+  build:
+    strategy:
+      matrix:
+        os:
+        - name: Windows
+          tag: windows-latest
+        - name: macOS
+          tag: macos-latest
+        - name: Ubuntu
+          tag: ubuntu-latest
+    name: Build (${{ matrix.os.name }})
+    runs-on: ${{ matrix.os.tag }}
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-java@v5
+        with:
+          java-version: 21
+          distribution: 'temurin'
+          cache: 'maven'
+
+      - name: Build with Maven
+        shell: bash
+        run: |
+          set -e
+          mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V && mvn verify -B && mvn javadoc:aggregate && mvn checkstyle:check -P checkstyle
+
+  snapshot-publish:
+    name: Publish Snapshot
+    needs: build
+    if: github.repository == 'jgrapht/jgrapht'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-java@v5
+        with:
+          java-version: 21
+          distribution: 'temurin'
+          cache: 'maven'
+      - run: |
+          set -e
+          mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V && mvn javadoc:aggregate
+      - uses: actions/setup-node@v7
+        with:
+          node-version: 14
+      - run: npm install -g hercule@5.0.0
+
+      - name: Run prepareDocs script
+        run: ./etc/prepareDocs.sh
+        shell: bash
+
+      - name: Deploy snapshot to Sonatype
+        env:
+          CENTRAL_USER: ${{ secrets.CI_DEPLOY_USERNAME }}
+          CENTRAL_PASSWORD: ${{ secrets.CI_DEPLOY_PASSWORD }}
+        run: mvn package org.sonatype.central:central-publishing-maven-plugin:publish -DskipTests=true --settings etc/snapshot-settings.xml
+        shell: bash
+
+      - name: Publish Github Pages
+        uses: JamesIves/github-pages-deploy-action@v4.8.0
+        with:
+          token: ${{ secrets.PAGES_TOKEN }}
+          branch: gh-pages
+          folder: docs
+          clean: true

.gitignore

@@ -26,3 +26,17 @@ build
 .kdev4
 .buildpath
 .svn
+.idea/*
+*.iml
+out/*
+**/out/*
+**/bin/*
+pom.xml.releaseBackup
+**/pom.xml.releaseBackup
+**/dependency-reduced-pom.xml
+.classpath
+docs/javadoc*
+docs/_site
+
+# allow checked-in jgrapht-osm sample fixture
+!jgrapht-osm/src/test/resources/perf/osm/sample-*.csv.gz

CODE_OF_CONDUCT.md

@@ -0,0 +1,90 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and committers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+* Proactively reading, following, and improving community guidelines
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project committers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project committers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Contribution Model
+
+In the JGraphT project, we use the term "committers" rather than "maintainers".
+
+This is because other than release management, most project maintenance is done through contributions,
+rather than through work carried out by a dedicated team.  Committers
+help contributors carry this out through processes such as issue discussions
+and code review.  Committers generally do not even commit their own work directly;
+instead, they wait for another committer to review and merge their contributions.
+
+Understanding and respecting these roles is an important aspect of our
+code of conduct.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project committers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at admin@jgrapht.org. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project committers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,5 @@
+Thanks for your interest in improving JGraphT.:+1::tada:
+
+Before preparing your first pull request, please take a look at our
+[developer guidelines wiki](https://github.com/jgrapht/jgrapht/wiki#developer-pages) page, and in particular the [how to make your first contribution page](https://github.com/jgrapht/jgrapht/wiki/How-to-make-your-first-%28code%29-contribution). The probability that your PR gets accepted increases exponentially when your submission complies with these guidelines. Please do **not** submit PRs that are partially finished: each time you push new commits we get e-mail notifications. If you want feedback or have a dev question, please post an a message to [jgrapht-dev](https://groups.google.com/forum/#!forum/jgrapht-dev) containing a URL to your branch/repository.
+