Skip to content

Commit

Permalink
Merge pull request #40 from rikkarth/dev
Browse files Browse the repository at this point in the history
ZipBuilder Base Implementation
  • Loading branch information
rikkarth authored Mar 19, 2024
2 parents cbddcba + 080f95d commit 056049a
Show file tree
Hide file tree
Showing 26 changed files with 1,283 additions and 698 deletions.
2 changes: 1 addition & 1 deletion .editorconfig
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ insert_final_newline = true

# Java-specific settings
[*.java]
indent_size = 4
max_line_length = 120

# Ignore some files and directories
[**.md]
Expand Down
33 changes: 19 additions & 14 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,15 +1,10 @@
target/
!.mvn/wrapper/maven-wrapper.jar
!**/src/main/**/target/
!**/src/test/**/target/

### IntelliJ IDEA ###
# IntelliJ IDEA
.idea/
*.iws
*.iml
*.ipr

### Eclipse ###
# Eclipse
.apt_generated
.classpath
.factorypath
Expand All @@ -18,24 +13,34 @@ target/
.springBeans
.sts4-cache

### NetBeans ###
# NetBeans
/nbproject/private/
/nbbuild/
/dist/
/nbdist/
/.nb-gradle/
build/
!**/src/main/**/build/
!**/src/test/**/build/

### VS Code ###
# VS Code
.vscode/

### Mac OS ###
# Mac OS
.DS_Store

### Project ###
# Maven
/dependency-reduced-pom.xml
/javadoc
/release.properties
target/
!.mvn/wrapper/maven-wrapper.jar
!**/src/main/**/target/
!**/src/test/**/target/

# Node.js
/node_modules/

# Project specific
build/
src/test/resources/output/*
!**/src/main/**/build/
!**/src/test/**/build/
!src/test/resources/output/.gitkeep
6 changes: 3 additions & 3 deletions .versionrc.json
Original file line number Diff line number Diff line change
Expand Up @@ -37,10 +37,10 @@
"hidden": true
},
{
"tpe": "build",
"type": "build",
"hidden": true
}
],
"commitUrlFormat": "https://github.com/mokkapps/changelog-generator-demo/commits/{{hash}}",
"compareUrlFormat": "https://github.com/mokkapps/changelog-generator-demo/compare/{{previousTag}}...{{currentTag}}"
"commitUrlFormat": "https://github.com/rikkarth/tooler-tools/commits/{{hash}}",
"compareUrlFormat": "https://github.com/rikkarth/tooler-tools/compare/{{previousTag}}...{{currentTag}}"
}
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,14 @@

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

## [0.1.0](https://github.com/rikkarth/tooler-tools/compare/0.0.8...0.1.0) (2024-03-19)


### Features

* **XmlHandler:** get element from xpath ([00fc2a0](https://github.com/rikkarth/tooler-tools/commits/00fc2a04f91fa448ea59e25441d477b7736e39fe))
* **ZipBuilder:** base implementation ([aa8cceb](https://github.com/rikkarth/tooler-tools/commits/aa8cceb6b599dfd7dee6492fabdbfeb0a5ef3f36))

### 0.0.8 (2023-12-14)


Expand Down
132 changes: 132 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,132 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall
community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or advances of
any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email address,
without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders 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, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official email address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[INSERT CONTACT METHOD].
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of
actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the
community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
[https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations
49 changes: 49 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
# Contributing Guidelines

Thank you for considering contributing to our project! We welcome contributions from anyone interested in improving the project. Before making a contribution, please take a moment to review the following guidelines.

## Code of Conduct

Please review our [Code of Conduct](CODE_OF_CONDUCT.md) before contributing to ensure a positive and inclusive environment for everyone.

## How to Contribute

1. Fork the repository to your GitHub account.
2. Clone the forked repository to your local machine:
```sh
git clone https://github.com/your-username/tooler-tools.git
```
3. Create a new branch for your contribution:
```sh
git checkout -b feat/your-feature-name
```
4. Make your changes and commit them with a descriptive commit message:
```sh
git commit -m 'feat(#001): Add a descriptive commit message'
```
5. Push your changes to your fork:
```sh
git push origin feat/your-feature-name
```
6. Open a pull request (PR) against the **dev branch** of the original repository. Please provide a clear title and description for your PR, explaining the purpose of the changes.

## Contribution Guidelines

- **Coding Standards**: Follow the coding standards and conventions used in the project. Ensure your code is well-formatted and easy to read.
- **Testing**: Write tests to cover your code changes. Ensure existing tests pass before submitting a PR.
- **Documentation**: Update relevant documentation, such as CHANGELOG.md or JavaDocs, to reflect your changes.
- **Commit Messages**: Write clear and descriptive commit messages, following [Conventional Commits](https://www.conventionalcommits.org/) format where applicable (optional).
- **Pull Request Reviews**: Be open to feedback and willing to make changes if required during the PR review process.
- **License**: Ensure your contributions comply with the project's [license](LICENSE).
## Reporting Issues
If you encounter any issues or have suggestions for improvements, please [open an issue](https://github.com/rikkarth/tooler-tools/issues) on GitHub and provide detailed information about the problem or suggestion.
## Get in Touch
If you have any questions or need further assistance, feel free to reach out to us through GitHub issues or [discussions](https://github.com/rikkarth/tooler-tools/discussions).
## Acknowledgements
We appreciate your interest in contributing to our project! Your help is invaluable in making this project better.
Loading

0 comments on commit 056049a

Please sign in to comment.