JarCasting
JarCasting JarCasting

LoadCoder Log

This project is a container for the log related submodules

License

License
GroupId

GroupId

com.loadcoder
ArtifactId

ArtifactId

loadcoder-log
Last Version

Last Version

3.0.0
Release Date

Release Date
Type

Type

pom
Description

Description

LoadCoder Log
This project is a container for the log related submodules
Project URL

Project URL

http://loadcoder.com

Download loadcoder-log

Filename Size
loadcoder-log-3.0.0.pom 1 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/com.loadcoder/loadcoder-log/ -->
<dependency>
    <groupId>com.loadcoder</groupId>
    <artifactId>loadcoder-log</artifactId>
    <version>3.0.0</version>
    <type>pom</type>
</dependency>
// https://jarcasting.com/artifacts/com.loadcoder/loadcoder-log/
implementation 'com.loadcoder:loadcoder-log:3.0.0'
// https://jarcasting.com/artifacts/com.loadcoder/loadcoder-log/
implementation ("com.loadcoder:loadcoder-log:3.0.0")
'com.loadcoder:loadcoder-log:pom:3.0.0'
<dependency org="com.loadcoder" name="loadcoder-log" rev="3.0.0">
  <artifact name="loadcoder-log" type="pom" />
</dependency>
@Grapes(
@Grab(group='com.loadcoder', module='loadcoder-log', version='3.0.0')
)
libraryDependencies += "com.loadcoder" % "loadcoder-log" % "3.0.0"
[com.loadcoder/loadcoder-log "3.0.0"]

Dependencies

compile (2)

Group / Artifact Type Version
org.slf4j : slf4j-api jar 1.7.26
com.loadcoder : loadcoder-utilities jar 3.0.0

test (4)

Group / Artifact Type Version
com.loadcoder : loadcoder-testutilities jar 3.0.0
org.testng : testng jar 6.14.3
org.mockito : mockito-all jar 1.10.19
org.sonarsource.java : sonar-jacoco-listeners jar 3.8

Project Modules

  • loadcoder-logback

1. Introduction

Loadcoder is a tool for javacoders to create and run load towards application/code to be performance tested.

Visit loadcoder.com for further information

2. Version Control

The sources for this library are kept in the following repository at GitHub:

https://github.com/loadcoder/loadcoder

3. Community

If you would like to contribute to Loadcoder, introduce yourself through [email protected] and elaborate what you think of Loadcoder and your thoughts of taking the tool further.

The next step is that you will be invited to the loadcoder github organisation as a member.

3.1 Issues and feature branches.

Issues are used to keep track of everything that happens in the source code. The main purpose of an Issue is to explain the purpose of the change. Depending on the nature of the change, a description of the change should also be added. For example, an Issue for a bug can have a description that explains the cause of the problem, and suggest a solution.

Issues shall be done by implementing the needed changes in a branch. Once the branch is fully developed it can be merged into the master branch. As a member you will be able to create and push you own branches.

3.2 Merging to master, and Pull Requests

A branch can only be made through a Pull Request (since it will require certain approvals). A Pull Request created by a member can not be merged to master without the approval of the owner of the code (see the CODEOWNERS file). In order to achieve this, create a Pull Request for your branch once it's ready, and invite the code owner and other members that needs to review it. The branch can be merged to master once it's successfully reviewed.

The following are guidelines to follow as a member and contributor of Loadcoder:

  • All changes shall be preceded by a describing Issue in order for you and others to understand what the purpose is with the change. In order to map the branch to the corresponding Issue, add the Issue ID (#[number]) in the name of the branch you are working in, similar to any of the following:
bugfix_#3_memory-leak-in-chart
feature_#3_new-cool-chart-colors

Also state the Issue you are working with in the git commit messages.

git commit -m "#3 Fix memory leak in the chart functionality" ChartFunctionality.java

  • Keep the users in focus and keep things simple. Loadcoder's user APIs must be kept understandable.

  • Write unittests for your functional changes, and make sure everything builds and all tests passes.

  • Document your changes. Comment the code and write javadocs if needed. Also suggest documentation for loadcoder.com as Issues in https://github.com/loadcoder/loadcoder-site

4. Contributors

Thanks to the following developers who have contributed code to this class library:

Stefan Vahlgren (Author)

5. Contact

Email: [email protected]

6. License

Loadcoder is licensed under the terms of the GNU GENERAL PUBLIC LICENSE Version 3 or later.

6.1 Copyright Notice

Copyright (C) 2018 Stefan Vahlgren at Loadcoder

com.loadcoder

loadcoder

Versions

Version
3.0.0
3.0.0-beta
2.0.0
1.0.2-beta
1.0.1
1.0.0
1.0.0-beta3
1.0.0-beta2
1.0.0-beta1